Destination tags & memos explained (XRP, TON, Stellar)

Some networks use a single shared address for many users and rely on an extra identifier — a destination tag (XRP), memo (Stellar, some Cosmos chains) or comment (TON) — to credit the right account. Get it wrong and your deposit can be delayed or misrouted.

When a tag/memo is needed

You'll typically see a tag or memo field when:

• Depositing XRP to an exchange or shared wallet (a numeric destination tag).
• Depositing on Stellar (XLM) to a shared address (a memo).
• Sometimes on TON (a text comment) for certain services.

A personal self-custody wallet usually does not require one — the address alone is enough.

When NOT to use one

Adding a tag/memo where it isn't expected can cause problems just as easily as omitting one where it is. The rule: only include a destination tag or memo if the receiving service explicitly asks for it for that route.

How CryptoRoute handles it

Routes flag networks where a memo or tag may be required, and the deposit instructions show a dedicated field only when the provider supports it for that route. If you're sending to your own wallet that doesn't use tags, you can leave it empty.

If you're ever unsure, check with the wallet or exchange you're depositing to — they'll tell you whether their address needs a tag or memo.