What kind of ATOM destination did you select?
| Destination | Instruction to establish | Assumption to avoid |
|---|---|---|
| Your own wallet account | The current receive details for ATOM on the intended chain | That a rule from a different hosted platform supplies your memo |
| An account inside a receiving service | Its deposit address and any memo it issues for that account | That the shared address alone identifies your customer balance |
| Another chain in a multichain wallet | Whether the selected route pays to that chain at all | That the Cosmos ecosystem is one interchangeable receiving network |
| A saved account-book entry | That its full details still match the current deposit instruction | That an unchanged contact name proves the routing information is current |
A personal wallet and a hosted balance can issue different details
Crypto.com’s documentation for its Onchain wallet says that its ATOM receive address does not need a memo, and explains the difference from a shared hosted address. This is a concrete example of why the recipient instruction matters. It is not a universal rule that every product using the same brand, every wallet or every exchange has identical requirements.
For an ATOM payout into another service, open that service’s current deposit page and retain all the routing details it supplies. If a memo is required but you cannot identify where the exchange will preserve it, clarify that before funding with ETH. Do not solve an interface mismatch by omitting the field or copying a value from a past deposit into another account.
A multichain wallet still needs a specific receiving chain
- Locate the intended Cosmos Hub account
- The Cosmos site presents the Hub alongside other chains in the ecosystem. Seeing a familiar wallet application in that ecosystem does not establish that its currently selected chain matches an ATOM payout. Check the account’s asset and receive instruction rather than selecting a destination only because the wallet supports Cosmos-based networks.
- Keep ETH funding separate from ATOM routing
- Your ETH deposit follows the sending instruction issued for the exchange. The ATOM receiving address and any memo belong to the payout side. Neither should be substituted for the ETH deposit destination. Review the two sides independently when switching between a wallet, a receiving platform and the exchange screen.
- Check the payout before diagnosing internal credit
- When available, compare the ATOM payout’s destination and memo with the receiving instruction. If a hosted account has not credited the payment, preserve that record and ask the recipient about its account mapping. Keep the ETH transfer reference and exchange identifier as separate evidence of how the conversion was funded.
Receiving ATOM into the intended account
- My wallet shows no ATOM memo. Should I invent one?
- Use the recipient’s own instruction. A personal receive screen may supply no memo, while a hosted service may require one. If the exchange form and recipient instruction conflict, resolve the discrepancy before paying. A guessed number is not a substitute for recipient-issued routing details.
- Can I use the ATOM receive details from another app in the same ecosystem?
- Only use the details for the exact account and chain you intend to receive into. Sharing an ecosystem, wallet brand or ticker does not establish identical routing. Reopen the desired destination and compare its current address and any memo with the exchange payout selection.
Recipient and network references
Reviewed: