What is a destination tag and why do some swaps require one

05 September 2026

A destination tag is a numeric label attached to a transaction on certain blockchains to identify which user or account the funds are intended for. Cross-chain swaps require one when the receiving blockchain uses a shared deposit address rather than giving each user a unique address.

How destination tags work

On networks like Ripple (XRP) and Stellar (XLM), every account can receive many payments into a single public address. The destination tag acts like an apartment number in a large building: the address gets the mail to the right building, but the tag tells the post office which mailbox inside that building should receive it.

When a cross-chain swap service sends you XRP or XLM, it cannot generate a new address for each trade the way Ethereum or Solana can. Instead, it maintains one or a few addresses and uses your unique destination tag to credit the correct user. Without the tag, the service receives the funds but cannot determine who sent them.

Why some swaps require one

The requirement arises from a fundamental design difference between blockchains.

Unique-address blockchains (Ethereum, Bitcoin, most EVM chains) give each user a distinct address. You can send tokens from any source to that address, and only the private key holder controls it. The swap service can ask you to deposit to one address and receive from another; no tag is needed because the address itself identifies the destination.

Shared-address blockchains (Ripple, Stellar) use a smaller address space and do not generate new addresses for every user. A service might hold millions of user balances in a single address. The destination tag is the only way to route incoming payments to the correct account. If you send funds without the tag, the service sees an anonymous deposit and must either manually investigate (slow, expensive) or treat the funds as lost.

What happens if you forget the tag

The swap service cannot automatically credit your account. The funds land in the shared address, but the service does not know they belong to you. Recovery is possible but requires you to prove ownership of the sending address and provide the missing tag. Many services charge a recovery fee or simply refuse to process the swap until you submit a corrected transaction. In practice, a missing tag often means your swap fails and you must contact support.

Relationship to cross-chain swaps

This page is part of a larger explanation about getting an asset from one chain to another without a bridge or centralised account. When you use a cross-chain swap service to move tokens from Ethereum to XRP Ledger, the service must give you an XRP address and a destination tag. You send your Ethereum tokens to the service's Ethereum address; the service converts them and sends XRP to its own shared XRP address with your tag attached. The tag is what makes the service's internal ledger entry possible. Without it, the conversion step cannot complete.

Practical advice

• Always copy the destination tag exactly as shown. Do not add leading zeros or spaces.
• Some services display the tag and address as a single string. Separate them carefully.
• Test with a small amount if you are unsure. A failed test costs less than a full swap.
• Keep a record of the tag assigned to each swap. You may need it later if the service requires manual reconciliation.

The destination tag is not a security measure. It is an accounting convenience that some blockchains force on services because they cannot create unique addresses at scale. Understanding it prevents the most common cause of failed cross-chain swaps on Ripple and Stellar.

Back to trust wallet