The short answer
A memo or destination tag routes a deposit to the right account when many customers share one address. XRP deposits typically require a destination tag; XLM, EOS and some other assets require a memo. Omitting or mistyping it can delay the deposit or, in some cases, make it unrecoverable.
Why a second field exists at all
On most networks an exchange can generate a unique deposit address for every customer. On some, that is impractical or expensive, so the platform uses one address for many customers and distinguishes them with an extra field carried in the transaction.
Coinbase describes destination tags and memos as extra fields that let it route deposits from one shared address to the correct customer account, and says they are required for all deposits of certain assets. The XRP Ledger documents the same concept: the tag identifies which account a payment is intended for.
So the address tells the network where to deliver the funds, and the tag tells the platform who they belong to. Both are part of the instruction.
Which assets use them
The set varies by platform, which is why the deposit page is the authority rather than a general list. Commonly documented cases include XRP, which uses a destination tag, and XLM, STX and EOS, which use a memo.
Two things follow. First, an asset that needs a tag on one platform may not need one on another, if that platform issues unique addresses. Second, the tag is specific to that account at that platform: a tag from an old deposit page, or from a different exchange, is the wrong tag.
Always copy the address and the tag from the deposit page you are sending to, at the time you are sending.
What happens when it is missing or wrong
The transaction itself usually succeeds: the funds reach the shared address and the network considers the job done. The problem is on the platform side, where an arriving deposit cannot be matched to an account.
Documentation from major platforms is consistent and blunt about the consequences: omitting or entering an incorrect tag or memo can delay a transaction or cause loss of funds, and in some cases makes the deposit irretrievable. Where recovery is offered, it is a manual support process, sometimes with a fee, and never guaranteed.
A wrong tag is worse than a missing one in at least one respect: it may match another customer’s account.
Getting it right, every time
Open the deposit page for the exact asset and network. Copy the address and the tag or memo separately, and paste each into its own field on the sending side — never both into the address field, and never the tag into the address.
If the sending interface has no tag field at all, stop. That interface may not support sending to a tagged destination, and proceeding produces exactly the untagged deposit you are trying to avoid.
For a first transfer to any tagged destination, send a small test amount and confirm it is credited before sending the rest. Platform documentation recommends the same thing, and this is the case where it pays for itself most often.
Frequently asked
What happens if I forget the destination tag?
The transaction usually confirms, but the platform cannot match the deposit to your account. Depending on the platform, this means a delay while support investigates, or in some documented cases an unrecoverable deposit.
Can I add a tag after sending?
No. The tag is part of the transaction and cannot be changed once it is sent. Contact the platform through its official support route with the transaction details.
Do I need a memo for USDC or ETH?
Typically no, because those deposits use addresses unique to your account. The deposit page is the authority — if it shows a tag or memo field, it is required.
Is the tag the same every time?
It is specific to your account at that platform, and can change. Copy it from the current deposit page rather than reusing an old one.
Before you act
- Copy the address and the memo or tag from the current deposit page.
- Paste each into its own field; never combine them.
- Stop if the sending interface has no field for the tag.
- Send a small test amount to a tagged destination the first time.
Sources & further reading
- Coinbase: destination tags and memos
Extra fields that route deposits from a shared address, required for certain assets.
- XRP Ledger: source and destination tags
Protocol-level description of what a destination tag identifies.
- Kraken: destination tag for XRP deposits
A unique and mandatory tag generated with the deposit address.
- Kraken: cryptocurrency deposit is missing
What a platform investigates when a deposit cannot be matched.
Sources checked on 18 September 2026. Network features and platform support can change; check the relevant provider before acting.
AI-assisted editorial content; no independent expert review or transaction verification is claimed. Tokens and bridges carry issuer, market and smart-contract risks. This is educational information, not investment advice. Read our editorial policy.