Skip to content

Stablecoin Memo or Destination Tag: When You Need One and How to Send

When a stablecoin deposit needs a memo or destination tag (RLUSD and USDC on XRP Ledger, USDC on Stellar, USDT on TON), how to send with one, and what Coinbase, Kraken and Binance do if you forget it. Includes an on-ledger check of Kraken's tag-required XRP address, 16 Nov 2026.

Stablecoin Insider cover reading Stablecoin Memos and Destination Tags in white capitals on a dark bronze textured background
Cover: Stablecoin Insider

Table of Contents

You need a memo or destination tag only when you send stablecoins to a shared address, usually an exchange, on a network that uses one: XRP Ledger destination tags for RLUSD and USDC, Stellar memos for USDC and EURC, and similar fields on TON and Hedera. Coinbase and Kraken list none for USDT or USDC on Ethereum, TRON or Solana.

The rule comes from the receiving platform, not the stablecoin. Coinbase says tag and memo requirements "are determined by the receiving platform" and are generally not needed for a self-custody wallet (Coinbase). This guide shows which stablecoin networks use the field, how to send with it, what an exchange address that requires a tag looks like on-ledger, and what Coinbase, Kraken and Binance say happens if you forget it.

Last updated: 16 November 2026. Network docs, issuer address lists, exchange help pages and on-ledger data re-checked on this date.

Key Takeaways

  • A destination tag or memo tells a business which customer to credit when many customers share one deposit address. The address gets the coins to the business; the tag gets them to your account.
  • Stablecoins that live on tag or memo networks include RLUSD and USDC on the XRP Ledger, USDC and EURC on Stellar, USDT on TON and USDC on Hedera, per Ripple, Circle and Tether address lists.
  • Kraken's shared XRP deposit address has the XRP Ledger's "require destination tag" flag switched on, so the ledger rejects payments to it that carry no tag. It cannot catch a wrong tag.
  • Forgot the tag? Kraken lists recovery for the network fee, Binance returns the deposit to the sending address for a fee, and Coinbase asks for the transaction hash. None of them guarantees recovery.

What is a memo or destination tag?

A memo or destination tag is an extra identifier sent alongside the address so that the receiving business knows which customer to credit. The XRP Ledger docs describe destination tags as 32-bit unsigned integers that "indicate the beneficiary or destination for a payment", for example which exchange customer to credit, and stress that they have no on-ledger effect beyond carrying that information (XRPL.org).

Stellar calls the same idea a memo. Custodial services, "including cryptocurrency exchanges", often run one pooled account and use either memos or muxed accounts to map payments to customers (Stellar docs). The reason is cost: on both networks every separate address is a funded on-ledger account with a reserve, so one shared address plus a tag is cheaper than one address per customer (XRPL.org).

Which stablecoin networks use a memo or tag?

The networks below carry a dedicated field that exchanges use to route stablecoin deposits. Each row links to the network docs and to the issuer page listing the stablecoin on that network.

NetworkStablecoins listed by issuerField and formatBuilt-in safeguard
XRP LedgerRLUSD (Ripple), USDC (Circle)Destination tag, 32-bit unsigned integer (XRPL)Receiver can require a tag; the ledger rejects untagged payments (XRPL). An X-address packs address and tag into one string.
StellarUSDC (Circle), EURC (Circle)Memo: text up to 28 bytes, 64-bit ID, or 32-byte hash (Stellar)Muxed M-address embeds a 64-bit ID (Stellar). SEP-29 lets an account flag "memo required" for wallets to check.
TONUSDT (Tether)Text comment: payload starting with 32 zero bits, then the text (TON docs)None described in the docs we read
HederaUSDC (Circle)Transaction memo, up to 100 bytes UTF-8, visible to everyone (Hedera)None described in the docs we read

Two patterns stand out. Only the XRP Ledger can make the network itself refuse a payment without a tag; on Stellar the SEP-29 flag is a convention that the sending wallet has to check, and the spec says the sender should "prevent the transaction from submission" if the memo is missing (SEP-29). And the stablecoins most people move, USDT and USDC on Ethereum, TRON and Solana, are not affected: neither Coinbase's list nor Kraken's list of assets needing a tag or memo includes those networks.

Note that a network appearing in the table does not mean every platform asks for a memo on it. Coinbase lists memos for XLM and HBAR and a tag for XRP, while Kraken lists XRP, XLM, STX and EOS. Always follow the deposit screen of the platform you are sending to.

How do you send stablecoins with a memo or destination tag?

You send stablecoins with a memo or destination tag by copying both values from the recipient's deposit screen, choosing the same network on your send screen, and pasting the tag into its own field before you confirm. The five steps below apply to RLUSD, USDC, EURC or USDT on any tag or memo network.

Five-step diagram for a stablecoin deposit with a memo or tag: read the receive screen, match network, paste tag, test, check explorer.
Graphic: Stablecoin Insider. Source: XRPL.org, Stellar docs, Coinbase and Kraken, read 16 Nov 2026.

Step 1: Copy the address and the tag from the receive screen

Copy the address and the destination tag or memo as two separate values from the recipient's deposit page. Coinbase shows both under Receive crypto (Coinbase); Kraken generates a ten-digit XRP tag together with its deposit address (Kraken). Kraken asks you to make sure the tag or memo is included when using a QR code for XRP, XLM or STX, and says EOS memos must be typed manually (Kraken).

Step 2: Pick the same network on both sides

Pick the same network the deposit page names. USDC exists on the XRP Ledger, Stellar, Hedera and dozens of other chains, so "USDC" alone is not enough. A tag typed on the right address but the wrong network does not help; see our guide to choosing a USDC network before you send.

Step 3: Paste the tag or memo into its own field

Paste the tag or memo into the separate Destination tag or Memo field, not after the address. If the platform gives you a combined address instead, use that: an XRP Ledger X-address encodes the address and tag together (XRPL.org), and a Stellar M-address embeds the customer ID, which is why Kraken asks for an XLM memo only "if not using a muxed address" (Kraken). Do not add a memo ID to an M-address as well: Stellar calls a mismatch between the two a malformed transaction (Stellar docs). On Stellar, use the memo type the platform specifies, since text and ID memos are different formats (Stellar).

Step 4: Send a small test amount first

Send a small test amount and wait until the platform credits it before sending the rest. Coinbase recommends this "to confirm the address and tag/memo are correct" (Coinbase).

Step 5: Check the tag or memo on the explorer

Check the transaction on a block explorer and confirm that the tag or memo shows the value you were given. On XRPSCAN the destination tag appears as "DT:" next to the recipient. Our guide to checking a USDT or USDC transaction on a block explorer covers status, finality and the other fields.

How to Check a USDT or USDC Transaction on a Block Explorer
Read a stablecoin transaction field by field, decode its fee and know when it is final.

What does an exchange address that requires a tag look like?

An exchange address that requires a tag carries the XRP Ledger's RequireDest flag, which explorers display and the ledger enforces. We checked the shared XRP deposit address Kraken publishes, rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh (Kraken), through the public XRPL API at 11:23 CET on 16 November 2026: requireDestinationTag returned true at validated ledger 108,365,481.

XRPSCAN page for Kraken's shared XRP deposit address with a Require Destination Tag badge and incoming payments showing DT tags.
Screenshot: XRPSCAN account page for rLHzPs…v1rBJh, captured 16 Nov 2026, 11:20 CET.

The transaction history shows why the tag matters. In the 400 most recent transactions on that address, from 01:07 to 11:21 CET on 16 November 2026, there were 395 incoming payments. All 395 carried a destination tag, and they used 275 different tag values. One on-ledger address took payments for 275 different tags in about ten hours, so the tag is what separates one depositor from the next.

The flag protects against a missing tag, not a wrong one. When the receiving account requires a tag, a payment without one fails with tecDST_TAG_NEEDED (XRPL.org); the payment does not go through, and only the XRP paid as the transaction cost is destroyed. The XRPL docs say the flag exists so the ledger "rejects their payment instead of giving you money you don't know what to do with" (XRPL.org). A payment with a mistyped tag, though, is valid and lands on the exchange's address. The check runs on Payment transactions, which on the XRP Ledger carry both XRP and issued tokens such as RLUSD (Ripple). Not every exchange address sets it; check the explorer before you rely on it.

🔎
How we checked this guide: we read the XRP Ledger, Stellar, TON and Hedera developer docs, the Circle, Tether and Ripple address lists, and the Coinbase, Kraken and Binance help pages on 16 November 2026. We queried Kraken's published XRP deposit address through the public XRPL API (account settings plus its 400 most recent transactions) and captured its XRPSCAN page the same day. We did not send a test deposit. No exchange or explorer paid to be mentioned. See our methodology.

What happens if you forget the memo or tag?

If you forget the memo or tag, the stablecoins usually reach the exchange's shared address but no customer account, and only the exchange can move them back. The table compares what three exchanges publish; rows link to each help page.

ExchangeWhat it says happensFeeWhat to send support
CoinbaseMissing or incorrect tag: funds "will not be credited to the correct Coinbase account". For a wrong tag, support "may be able to assist" (Coinbase)None publishedTransaction hash
KrakenMissing or incorrect tag/memo: credit or refund; recovery "is not guaranteed" (Kraken). Its XRP page warns a missing tag may be "irretrievable in certain cases" (Kraken)Network feeTxID, asset and amount, deposit address, date and time
BinanceTag/Memo Recovery returns the deposit to the original sender's address. If your tag belongs to another user, the deposit may go to them and Binance "is unable to assist" (Binance)Transaction fee of that crypto; no recovery if the rest is under the withdrawal minimumCoin, exact amount and TxID in the recovery form

The difference that matters most is where the money goes back to. Kraken may credit your account, while Binance sends the deposit back to the address it came from, so if you sent from another exchange you will also need that exchange's help (Binance). Do not send a second deposit to "fix" the first, and contact the exchange only through its own website or app, not through someone offering paid recovery.

💡
Stablecoin Insider's take: the memo problem is a legacy of shared exchange addresses, and the networks already have better tools. X-addresses on the XRP Ledger and muxed M-addresses on Stellar put the customer ID inside the address, so there is nothing separate to forget. Until every platform accepts them, the safest habit is the slow one: copy both fields, send a test, and check the tag on the explorer.

Sent USDC to the wrong chain rather than without a memo? That is a different problem with different fixes.

Comparing exchanges before you deposit? See Coinbase vs Kraken for fees and USDC rewards, or RLUSD vs USDC if you are choosing which stablecoin to hold on the XRP Ledger.

For the full picture, see our Stablecoin payments and cards hub.

FAQ

Do you need a memo to send USDT on TRON or USDC on Ethereum?

You do not need a memo to send USDT on TRON or USDC on Ethereum to Coinbase or Kraken: neither exchange lists those networks among assets that need a tag or memo (Coinbase, Kraken). If a deposit screen on another platform shows a memo field for a network, follow that screen.

Do you need a destination tag to send RLUSD to your own wallet?

You generally do not need a destination tag to send RLUSD to your own self-custody wallet, because that address belongs only to you (Coinbase). The receiving XRP Ledger account still needs a trust line to the RLUSD issuer before it can receive RLUSD (Ripple).

Is a destination tag or memo private?

A destination tag or memo is not private: it is written into a public transaction. Hedera states its memo is "visible to all participants in the network" (Hedera), and the XRPL docs advise businesses to assign tags in an unpredictable order because sequential tags can reveal information about users (XRPL.org). Never put a password or recovery phrase in a memo.

What is an X-address?

An X-address is an XRP Ledger address format that combines a classic address and a tag into one string, so the tag cannot be left out. The XRPL docs suggest showing customers an X-address because it is easier than keeping track of two pieces of information (XRPL.org). Use one only if the receiving platform shows it.

What if you typed someone else's tag?

If you typed someone else's tag, the exchange may credit their account instead of yours. Binance says that in this case it is "unable to assist" (Binance). Contact the exchange with the transaction hash anyway, but treat a wrong tag as riskier than a missing one.

Sources: XRPL.org source and destination tags, XRPL.org tec result codes, Stellar operations and transactions, Stellar pooled accounts, muxed accounts and memos, Stellar SEP-29, TON jetton interface, Hedera transaction properties, Circle USDC contract addresses, Circle EURC contract addresses, Tether supported protocols, Ripple RLUSD token addresses, Coinbase destination tags and memos, Kraken crypto deposits, Kraken XRP destination tag, Kraken deposit recovery, Binance tag/memo recovery and XRPSCAN, plus the public XRP Ledger API; all read on 16 November 2026.

This content is provided for informational and educational purposes only and doesn't constitute financial, investment, legal or tax advice. Network rules, exchange policies and fees were read on 16 November 2026 and can change. Companies and assets mentioned: Ripple (RLUSD), Circle (USDC, EURC), Tether (USDT), Coinbase, Kraken, Binance, XRPSCAN, the XRP Ledger, Stellar, TON and Hedera.

Latest