What is a destination tag and when does a swap require one

05 September 2026

A destination tag is a short numeric or alphanumeric code attached to a crypto payment, used to identify which account within a shared wallet should receive the funds. A swap requires one whenever the receiving chain’s protocol uses a single public address for many users, and omitting the tag means the funds land in a pool with no clear owner.

Think of it like an apartment building. The public address is the building’s street number. The destination tag is the unit number. Mail sent to the building without a unit number sits in the lobby, unclaimed. Some networks work that way by design; others do not.

Why some chains need tags. A few major networks - most notably XRP Ledger, Stellar, and certain EOS-based systems - do not give every user a unique address. Instead, one address acts as a gateway, and each user gets a tag. When you send tokens to that address, the network’s software looks at the tag to credit the right account. Without it, the transaction is technically valid but functionally incomplete. The receiving side cannot know who the payment was for, and the funds may be frozen or returned only after manual review - if at all.

Why a swap triggers the requirement. Swapping across chains involves two separate ledgers. You send an asset on chain A; the exchanger credits you on chain B. When the exchanger gives you a deposit address on chain B, that address may be shared across many customers. To keep your incoming swap separate from someone else’s, the exchanger assigns you a destination tag. You must include that tag in your outgoing transaction on chain A. If you forget it, the exchanger sees a payment arrive but cannot match it to your swap order. Support tickets, delays, and sometimes permanent loss follow.

When a swap does not need a tag. Most modern chains - Ethereum, Bitcoin, Solana, and their many forks - give each user a unique address. A swap to those networks uses a fresh, one-time address generated for your order. No tag is required because the address itself identifies you. Some exchanges still offer tags on those chains as an extra layer, but they are optional. If a swap interface asks for a tag, it is because the destination chain uses shared addresses. If it does not ask, you do not need one.

How to tell which case you are in. Read the swap’s deposit instructions before you confirm. A required tag is usually shown as a separate field, often labelled “Destination Tag,” “Memo,” or “Note.” Some interfaces call it “Payment ID.” If the field is present and marked mandatory, treat it as part of the address. Copy both the address and the tag exactly. Do not assume a tag is optional just because the field is blank by default.

A practical warning. Tags are not secrets. They are not passwords. But they are precise. A wrong digit sends your funds to another user’s account on the same shared address, and reversing that is painful. The receiving network’s operators may be able to help, but they have no obligation, and the process takes weeks if it works at all. Double-check the tag against the swap’s confirmation screen, not just against your clipboard.

What to do if you forgot the tag. Contact the exchanger’s support immediately. Provide the transaction hash, the exact amount, and the address you sent to. Some exchangers can manually credit the funds if the tag was omitted but the address matches. Others cannot. Success depends on their internal policies and whether the receiving network allows manual intervention. Do not send a second payment with the correct tag and hope the first one gets merged - that rarely works and often creates a second problem.

The broader context. This page sits under a hub titled “Swapping crypto across chains.” That hub covers the mechanics of moving value without a bridge or a centralised account. Destination tags are one of the small, easy-to-miss details that separate a clean swap from a support ticket. The hub page explains the overall flow; this page is the part you read before you hit send. Read it once, then read the hub. Then send.

Back to regulation