Destination Tag and Memo Explained: XRP, XLM, TON and ATOM

Ця стаття доступна такими мовами:

Author logo
Tangem team
•
Post image

 

A destination tag (or memo) is a short routing code that tells an exchange which customer to credit when a deposit arrives at a shared address. It doesn't change where coins go on-chain. It tells the exchange's internal system who sent them.

 

Required when depositing to most exchanges. Not needed when sending to your own wallet. And if you forgot it, the situation is usually fixable, but slow.

This article is for information only and is not financial advice. Exchange recovery policies change. Check your exchange's help center for the latest terms.

What is a destination tag (or memo)?

Think of a major exchange like an apartment building with a single street address. Every tenant lives there, but the postal carrier needs an apartment number to deliver to the right person. A destination tag is that apartment number.

Why exchanges use shared addresses

Exchanges often assign one on-chain address to thousands of customers. When your XRP deposit lands, the ledger records only the receiving address, not your name or account ID. The destination tag is what the exchange's system reads to match the incoming funds to your account. Without it, the exchange can't automatically credit you.

 

This approach also reduces costs. Managing millions of individual addresses requires more infrastructure, more signing operations, and more on-chain overhead. One shared address with routing codes is operationally simpler.

Memo vs destination tag vs comment

Different networks use different names for the same idea:

NetworkField nameFormatLimit
XRP LedgerDestination tag32-bit unsigned integer0 to 4,294,967,295
Stellar (XLM)MemoText, ID, hash, or returnText: up to 28 bytes
TONComment (memo/message/tag)Plain text 
Cosmos (ATOM)MemoFree-form textService-dependent
Hedera (HBAR)MemoUTF-8 textUp to 100 bytes

The field name changes by network. The purpose is the same: routing within the exchange's internal system.

Destination tags and memos by network

XRP destination tag

On the XRP Ledger, a destination tag is a 32-bit unsigned integer, any whole number from 0 to 4,294,967,295. The ledger itself doesn't interpret the value; the receiving service defines what each number means.

 

Exchanges can enable a setting called RequireDest (asfRequireDest) on their deposit address. When active, the ledger rejects any payment that omits a destination tag entirely, returning a tecDST_TAG_NEEDED error. But it doesn't check whether the tag you supplied is correct; that's the exchange's job.

 

X-addresses are a newer format that encodes a classic XRP Ledger address and a destination tag together in a single string, reducing the chance of omitting the tag. Not all exchanges or wallets support them yet. For everything you need to know about XRP, including address formats, see our full XRP guide.

Stellar (XLM) memo

Stellar supports four memo types: MEMO_TEXT (ASCII or UTF-8, up to 28 bytes), MEMO_ID (a 64-bit unsigned integer), MEMO_HASH (a 32-byte hash), and MEMO_RETURN (a 32-byte hash identifying a refunded transaction). Most exchanges use MEMO_ID or MEMO_TEXT for deposit routing.

 

Stellar addresses begin with G and are 56 characters in Strkey format. A newer alternative, muxed accounts, combines a traditional G... address with a 64-bit ID in an M... address. Muxed accounts exist as a client-side abstraction rather than separate ledger accounts, and they can replace pooled-account memos for services that support them. Not all wallets and exchanges support muxed accounts yet, so many services still rely on transaction memos. To store Stellar (XLM) safely, understanding the memo requirement is the first step.

TON comment (memo)

TON's routing field is officially called a comment and is carried in the message body. Exchanges often label it "memo," "message," or "tag" in their UI. The underlying mechanism is the same. Comments are case-sensitive. When an exchange uses automated attribution, the value you supply must match exactly, including capitalization and spacing. A missing or incorrect comment can leave a transfer uncredited even when it reaches the shared address on-chain.

 

One naming note: Toncoin was officially renamed to Gram (GRAM) at 12:00 UTC on June 15, 2026. The blockchain itself remains The Open Network (TON). No swap or migration was required. Older guides still say "Toncoin." Tangem lists the asset as Gram (prev. Toncoin), GRAM on the TON network. To store TON safely, verify the current label in your exchange's deposit screen.

Cosmos (ATOM) memo

Cosmos SDK transactions include an optional free-form memo string in the transaction body. Whether a receiving service requires it is entirely service-dependent. It's not a Cosmos protocol requirement. Some exchanges use it for internal routing; others don't need it at all. Always check the exchange's deposit instructions before sending. For more on managing ATOM, see our guide to staking ATOM with a hardware wallet.

Hedera (HBAR) memo

Hedera transactions support an optional memo containing UTF-8 text up to 100 bytes. The memo is visible to all network participants. As with Cosmos, whether an exchange requires it depends on the exchange's own deposit system.

When you need a memo, and when you don't

The receiving side decides. If the deposit screen shows a memo or tag field, you must include it.

ScenarioMemo required?
Exchange → exchangeUsually yes, use the receiving exchange's tag
Exchange → your own walletNo
Your wallet → exchangeYes, use the exchange's deposit tag
Wallet → wallet (personal)No, unless the recipient explicitly asks

Your wallet address directly identifies your funds. No routing code is needed because there's no shared-address ambiguity.

How to send XRP, XLM, TON, or ATOM to an exchange with a memo

  1. Open your wallet app and select the coin and the correct network (XRP Ledger, Stellar, TON, Cosmos Hub, or Hedera).
  2. Go to the exchange's deposit page and copy both the deposit address and the memo/tag/comment exactly as shown.
  3. In the Tangem app, tap Send and paste the deposit address into the recipient field.
  4. Enter the memo or destination tag in the dedicated field. Copy-paste, don't type it manually.
  5. Send a small test amount first. Confirm it arrives and is credited to your exchange account before sending the remainder.
  6. Once the test clears, send the rest. Keep the transaction ID (TxID) from your wallet's history.

Tangem lets you include a memo or destination tag where the network requires one. For XRP sent to an exchange, use the destination tag supplied by that exchange; you can also save it with the address in the Address Book so it fills in on future sends.

How to withdraw to your Tangem wallet (no memo needed)

When you withdraw XRP, XLM, Gram, ATOM, or HBAR to your own Tangem wallet address, you don't need a destination tag or memo. Your address is controlled only by you, so there's no shared-address ambiguity to resolve.

 

Open each asset’s Receive screen and copy the address for the network you’ll use.

  1. If an asset isn’t on your wallet’s main screen, open Manage tokens, find it, enable the required network, and tap Save.

     

  2. Open the asset, tap Receive, and copy its address. On the sending platform, choose the same network before withdrawing.

For native-coin withdrawals, choose XRP Ledger for XRP, Stellar for XLM, TON for GRAM, Cosmos for ATOM, and Hedera for HBAR. GRAM and ATOM are also listed on other networks in Tangem, so check which network the sending platform offers before copying an address. Do not send XLM, GRAM, ATOM, or HBAR to an XRP Ledger address.

 

If the exchange's withdrawal form forces you to enter a tag value anyway, you can enter any number. In Tangem, that value doesn't affect funds sent to your own address.

 

Two reserve requirements worth knowing before your first deposit:

  • A 5 XRP deposit to a new XRP Ledger account leaves 4 XRP available, as 1 XRP is reserved for activation.

     

  • A new Stellar account requires a 1 XLM base reserve. Each additional non-XLM asset trustline increases the minimum balance by 0.5 XLM.

To withdraw crypto from any exchange to Tangem, follow the step-by-step guide. For Binance specifically, see how to withdraw from Binance to Tangem, and for Coinbase, see how to withdraw from Coinbase to Tangem.

Forgot the memo or used the wrong one? What to do

Don't panic, and don't resend. A second transaction with the correct memo won't recover the first one.

If you sent to an exchange without a memo

Find the transaction ID (TxID) in a block explorer using your sending address. Then contact the exchange's official support center and submit their deposit recovery form. You'll typically need:

  • The confirmed TxID
  • The coin type and network
  • The amount sent
  • Your account ID or registered contact details on that exchange

KuCoin (as of October 2026) handles missing-memo recoveries through its self-service recovery tool. A missing or incorrect memo typically incurs a fee of 40 USDT, and KuCoin states that processing takes up to 5 working days after payment of the fee. Recovery is not guaranteed.

 

Binance.US (as of October 2026) requires use of the Deposit Recovery Tool, a valid TxID, a screenshot of the sending transaction, and a supported network. It may additionally request a video. The fee for deposits sent without a memo is 5% of the deposited amount. Advanced Verification is required. Processing typically takes a few business days.

If you entered someone else's memo

This is the harder case. If the incorrect memo belongs to another user, Binance.US states that the deposit may be credited to that user and that they cannot assist with recovery. KuCoin similarly notes that a memo belonging to another customer cannot be retrieved. Contact the exchange's support immediately with your TxID, but understand that recovery isn't guaranteed.

If you sent to your own wallet with a memo

No action needed. When the receiving address is your own personal wallet, the memo has no effect on-chain. Your funds arrived correctly.

Warning about fake recovery services. After a missed-memo incident, scammers frequently contact victims via DMs or search ads claiming they can recover funds for an upfront fee. Never share your seed phrase, private keys, passwords, or additional funds with anyone offering recovery assistance. If you encounter a scam, report it to the FBI's IC3 at ic3.gov and the FTC at ReportFraud.ftc.gov. Outside the US, contact your local financial crimes authority.

How to avoid memo mistakes

  • Always copy and paste both the address and the memo/tag. Manual entry is the #1 way people accidentally lose crypto.
  • Verify the network before sending. An XLM memo on the wrong network is a separate problem from a missing memo.
  • Send a test amount first. A small test transaction costs little and confirms everything is set up correctly before you commit the full amount.
  • Save exchange deposit details carefully. The Tangem app's address book lets you store frequently used addresses. Label each entry with the asset, network, and required memo/tag, and always refresh from the exchange's current deposit page before reuse. Deposit addresses and tags can change.
  • Watch for address poisoning. Copy the destination address only from the exchange's current deposit page or your verified address book, never from transaction history. Compare the full address before approving.

Final thoughts

A destination tag or memo is a routing code, not a security feature. It exists because exchanges assign one shared address to many customers and need a way to sort incoming deposits. You need it when depositing to an exchange. You don't need it when withdrawing to your own wallet.

 

If you forgot a memo, act through official channels only, keep your TxID, and never pay an unsolicited recovery service. The best protection is a habit: copy and paste both fields, send a test amount, and store your deposit details in a verified address book. Keep your XRP, XLM, Gram, and ATOM in a wallet you control, and the memo question becomes much simpler.

Поширені запитання

  • A destination tag is a 32-bit unsigned integer attached to an XRP Ledger transaction. It tells the receiving service, typically an exchange, which customer account to credit when the payment arrives at a shared deposit address. The tag has no effect on ledger routing; its meaning is defined entirely by the receiving service.

  • Your funds arrive at the exchange's shared address but can't be automatically credited to your account. Don't resend. Find the TxID on a block explorer, then contact the exchange via its official help center to submit a recovery request. Expect a review fee and processing time of several business days. Recovery is possible but not guaranteed, and policies vary by exchange.

  • No. When you withdraw XRP, XLM, Gram, ATOM, or HBAR to a personal wallet address you control, no destination tag or memo is required. If the exchange's withdrawal form forces you to enter a value, you can enter any number. It won't affect your funds.

  • They serve the same purpose but live on different networks. A destination tag is the XRP Ledger's term for a 32-bit integer routing code. A memo is the equivalent field on Stellar, Cosmos, and Hedera. TON calls it a comment. All of them tell the receiving service which customer to credit at a shared address.

  • It depends on the exchange. KuCoin states that processing takes up to 5 working days after payment of the fee (as of October 2026). Binance.US typically processes submissions within a few business days. Neither exchange guarantees recovery, and timelines can extend if additional verification is required.

  • Yes. The Tangem app displays the memo and destination tag fields for XRP, XLM, Gram (TON), ATOM, HBAR, and other supported networks when sending. It also includes an XRP destination-tag reminder to reduce the chance of omitting the field when sending to an exchange.

  • No. Deposit details can change. Open the exchange's current deposit screen and copy both the address and the destination tag again before sending funds.

  • Don't use the saved memo. Refresh the asset, network, address, and memo from the exchange's current deposit page. If you already sent the transfer, contact the exchange through its official support channel with the TxID.

  • Don't send the transfer. Return to the exchange's current deposit page, then copy the address and memo again exactly as shown. If the transfer has already been sent, contact the exchange via its official support channel and provide the TxID.

  • An X-address encodes both a classic XRP Ledger address and a destination tag in a single string. Use it only when both the sending wallet and receiving service support it. If an exchange provides separate address and tag fields, copy those fields exactly as shown.

Author logo
Автор Tangem team

We are a team of Tangem Wallet users dedicated to simplifying self-custody for everyone.

Author logo
Рецензент Patrick Dike-Ndulue

Senior editor covering crypto, onchain equities, and technology.