Deposit Memos and Destination Tags: Why a Missing Tag Costs a Recovery
On Stellar and XRP, an exchange can publish a single deposit address for every customer and use a second field to say whose deposit it is. That field is a memo on Stellar and a destination tag on XRP. It is not a password and it does not change the amount; it is the routing instruction the exchange reads when the transaction arrives. This guide explains why the address alone is not enough, what Stellar's muxed addresses changed, and what the exchange says happens when the field is missing.
Cover artwork: CoinSoso · AI-generated, not a photograph of a real venue, product or market capture.
Key takeaways
- A memo or destination tag identifies the account a deposit belongs to when many customers share one exchange address.
- Kraken uses one Stellar deposit address for all accounts and a numerical memo to route each deposit; leaving it out can delay crediting and can be irretrievable.
- Stellar muxed addresses start with M instead of G; when one is used, Kraken says a memo is no longer required.
- An XRP destination tag is ten numbers long and mandatory for Kraken XRP deposits; forgetting it can make the deposit irretrievable.
- The tag is a routing field, not a security code; sending the right amount to the right address with the wrong tag is still a misrouted deposit.
Two fields, two jobs
A deposit instruction usually has two parts. The address says where on the chain the funds go. The memo or destination tag says which customer the exchange should credit once the funds arrive. When an exchange gives every customer its own address, the second field is redundant, and many chains and venues do not ask for one. When an exchange gives every customer the same address, the second field is the only thing that distinguishes one deposit from another.
That design is common on chains where address generation is expensive or where the venue prefers to consolidate. Kraken’s help pages describe both cases directly. Its Stellar article says that all Kraken accounts use a single Lumens deposit address, and its XRP article says that all Kraken accounts share a single XRP deposit address. In both, the routing field is what assigns the transaction to an account.
The Stellar memo
Kraken’s Stellar article gives the mechanics:
- The shared deposit address is
GA5XIGA5C7QTPTWXQHY6MCJRMTRZDOSHR6EFIBNDQTCQHG262N4GGKTM. - When a customer creates an XLM deposit address, Kraken also generates a unique memo.
- The memo is numerical. The article’s example is
01234567. - The memo must be included with all XLM deposits to the account.
The warning is explicit: leaving out the memo leads to significant delays in crediting the transaction and can be irretrievable in certain cases. The same article describes what to do if it happens — start a chat with the chatbot — which is a support path, not a reversal on the chain.
There is one documented exception. Since December 13, 2022, Kraken has supported Stellar muxed addresses for deposits and withdrawals. A muxed address starts with M instead of G, and when it is used the memo is no longer required. The address itself carries the routing information that the memo used to carry. If the deposit instruction shows an M address, the memo field is not the thing to worry about; if it shows a G address, it is.
The XRP destination tag
Kraken’s XRP article follows the same pattern with different vocabulary:
- The shared deposit address is
rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh. - A unique and mandatory destination tag is generated with the deposit address.
- The tag is ten numbers long. The article’s example is
0123456789. - It must be included with all XRP deposits.
The warning is stronger than the Stellar one: forgetting the tag leads to significant delays in crediting the deposit and might even make the deposit irretrievable in certain cases. The article also notes that XRP Account Delete transfers are not supported, which is a separate constraint on a different XRP transaction type.
Why the address alone is not enough
A chain confirms that a transaction moved funds from one address to another. It does not know which exchange customer should be credited. When the destination is a shared address, the chain’s record shows one recipient and many possible owners. The memo or tag is the exchange’s own routing layer on top of that record.
This is the part that surprises people: the transaction can be fully confirmed and still be uncredited. The confirmation answers “did the transfer happen?” The credit answers “whose transfer was it?” Those are different questions, and only the first is settled by the blockchain.
It also explains why the tag is not a security control. It is not secret in the way a password is, and it does not authorize anything. It identifies an account. Someone who knows your tag and sends to the shared address is sending to your account, which is exactly the intended behavior — and the reason a tag should be copied from the deposit screen rather than reused from memory.
What a miss costs
The documented consequences fall into three buckets:
| Outcome | What it looks like |
|---|---|
| Delayed credit | The transaction confirms, the exchange sees it, and the account is credited after a manual review |
| Manual recovery | Support matches the transaction to an account using other evidence; this takes time and is not guaranteed |
| Irretrievable | The exchange cannot establish the owner, and the funds are not credited |
Kraken’s articles use “significant delays” in both cases and “irretrievable in certain cases” in both. The XRP article adds “might even make the deposit irretrievable”. The precise outcome depends on the facts of the deposit and the venue’s process, which is why the articles route the customer to support rather than promising a recovery.
A pre-send checklist
- Read the deposit screen, not a saved address. Shared addresses are stable, but the tag is account-specific and the instruction screen is the authoritative pairing.
- Copy the memo or tag as a separate field. A tag pasted into the address field is a different transaction, and a tag pasted into a note field that the chain ignores is no tag at all.
- Check the address prefix on Stellar. An
Maddress is muxed and carries its own routing; aGaddress needs the memo. - Check the tag length and format. Kraken describes the XRP tag as ten numbers and the XLM memo as numerical. A tag with letters or the wrong length is a signal to stop.
- Send a small test first when the route is new. A test deposit costs a fee and a confirmation wait; a misrouted deposit costs a support case. The same discipline for a first transfer is set out in moving coins off an exchange.
- Keep the transaction hash. If something goes wrong, the hash is the evidence support needs, and it is easier to copy at send time than to reconstruct later.
The field is part of the address
The useful mental model is that the deposit instruction is a pair, not an address with an optional note. On a shared-address chain, the memo or tag is as load-bearing as the address itself. The address gets the funds to the venue; the tag gets them to the account. Sending with one and not the other is an incomplete instruction, and the venue’s own documentation says the result can be a delay that support has to untangle.
The address-level checks that catch a wrong or poisoned destination before the send are in checking a deposit address before you send, and the other half of a deposit receipt — what the network charges to move the funds at all — is in withdrawal fees versus network fees.
Risk note. The address formats, examples and consequences in this article were read from Kraken’s Stellar and XRP deposit help articles on 2026-10-26, and the article was last reviewed on 2026-10-31. Other venues may use different address formats and different recovery processes. Nothing here is investment advice.
Sources
How this was researched. Written from primary documentation and the exchange or protocol's own published material, with sources listed at the end of the article.
Primary sources for the factual claims on this page. A date appears only where a human has actually read the source; where it is missing, the check is still outstanding.
- Kraken Support — Memo for Stellar Lumens (XLM) deposits(read 2026-10-26)
- Kraken Support — Destination tag for Ripple (XRP) deposits(read 2026-10-26)
Frequently asked questions
Is a memo the same as a destination tag?
They serve the same routing purpose on different chains. Stellar calls the field a memo; XRP calls it a destination tag. Each exchange reads the field its chain provides and uses it to decide which customer account to credit.
Why does the exchange give everyone the same deposit address?
Because the address is not the customer identifier in that design. Kraken states that all of its accounts use a single Stellar deposit address and a single XRP deposit address, and that the memo or tag determines which account a transaction is assigned to. One address plus a routing field is cheaper to operate than one address per customer.
Do I still need a memo if I use a Stellar muxed address?
Kraken's help article says no. Since December 13, 2022 it has supported Stellar muxed addresses for deposits and withdrawals, and it states that when the muxed address is used a memo is no longer required. Muxed addresses start with M rather than G.
Can support recover a deposit sent without the tag?
Sometimes, but it is a manual process rather than a chain-level correction. Kraken's XRP article directs a customer who forgot the tag to submit a support ticket, and its Stellar article directs them to start a chat with the chatbot. Both articles warn that the outcome can be a significant delay and, in some cases, an irretrievable deposit.
Is the tag checked by the blockchain?
The field travels with the transaction, but the credit decision is the exchange's. The chain confirms that a transaction was included; the exchange reads the memo or tag and matches it to an account. That is why a confirmed transaction can still be uncredited.
Where to go next
Independent research. Each card shows the platform’s invite code, and its Create Account button is a referral link that may earn us a commission at no extra cost to you. Whether an account can be opened is decided by the platform at sign-up.
Binance
One of the largest global exchanges by traded volume, with a very broad product range.
20% Trading Fee Rebate
Use invite code con888 when signing up to enjoy trading fee benefits.
Download from the exchange's official download service. Verify the source and follow the on-screen installation instructions.
Do not install an APK from an unknown source, or one that has been modified or cannot be checked.
OKX
A large global exchange offering spot, derivatives and a self-custody wallet.
20% Trading Fee Rebate
Enter invite code con888 when signing up to check available trading fee benefits.
Download from the exchange's official download service. Verify the source and follow the on-screen installation instructions.
Do not install an APK from an unknown source, or one that has been modified or cannot be checked.