What a memo or destination tag does and when a swap requires one

05 September 2026

A memo or destination tag is an extra string of numbers or letters that tells the receiving exchange or smart contract which user a deposit belongs to. When a swap requires one, you must include it exactly; otherwise the exchange cannot credit the incoming funds to your account, and the swap will fail or the money will be lost.

Why memos and tags exist

Most blockchains treat a transaction as a simple transfer from address A to address B. If you send tokens to an exchange’s single deposit address, the exchange has no way to know which customer sent them. The memo or tag acts as an account number inside that one address. It is the exchange’s internal identifier for you.

This is common on three types of chains:

• XRP Ledger calls it a destination tag.
• Stellar calls it a memo.
• EOS and some other networks use a memo field in the same way.

Ethereum, Bitcoin, and most EVM-compatible chains do not use memos - transactions there are addressed to a unique receiving address, not a shared one. But some sidechains or layer‑2s that batch funds into a single address do require them.

When a cross-chain swap requires one

During a cross-chain swap (the subject of the hub page you are reading about swapping crypto across chains), the process works without a bridge or a centralised account. The exchanger receives your funds on one chain, then sends equivalent funds to you on another chain. That final send goes from the exchanger’s pooled wallet to your receiving address.

If the receiving chain’s token requires a memo, you must supply it. For example, if you swap Bitcoin for XRP, the exchanger will send XRP to your address. If your XRP address is a deposit address at a third-party service that uses destination tags, the exchanger may also ask you to provide a tag. But the more common case: the exchanger itself has one large XRP wallet. When it sends you XRP, it can send directly to your personal XRP wallet address - no tag needed, because you control that wallet and it is not shared.

The tag becomes mandatory when your receiving address is the exchange’s deposit address for you, not your own wallet address. This happens if you are swapping into an account on a centralised exchange, or into a service that uses a shared deposit address.

Common pitfalls

• Leaving the tag blank. If the receiving network requires one, the transaction will reject or the funds will land in the exchange’s general pool with no owner.
• Typing the wrong tag. The funds will credit to someone else’s account. Reversing this is difficult or impossible.
• Assuming every network uses memos. There is no reason to guess - check the receiving address’s requirements before you initiate the swap. The exchanger’s swap interface should clearly show you the field and its label.

What to do when you start a swap

1. Look at the destination field for your receiving token. If your receiving token is XRP, you will see a “Destination Tag” field.
2. If the field appears, fill it with the exact tag your receiving account expects. If you are sending to your own wallet, you usually will not have a tag; leave it blank only if the wallet says zero or empty is acceptable.
3. If the field does not appear, the swap does not need one. Do not add anything.

If you are unsure, test with a very small amount first. That is the only reliable way to confirm that the tag and address combination work. Once the small transfer clears, repeat with the full amount.

Memos and destination tags are simple: they are just a routing number for a single deposit address. Include them correctly, and the swap proceeds. Get them wrong, and the transaction may not complete at all.

Back to ethereum