A destination tag is a number you attach to an XRP payment so the recipient can tell which of its customers the money is for. It has nothing to do with the address itself. When you deposit XRP to an exchange, the address you are given is shared by thousands of users, and the tag is the only thing that says the deposit is yours.
Forget the tag on an exchange deposit and the XRP does not vanish from the ledger, but it lands in a shared account with no record of who sent it. Getting it credited then means a support ticket and, sometimes, no recovery at all.
This guide explains what a tag is, why XRP works this way, what happens when one is missing, and when you actually need one. Generic address and memo mechanics on other chains are a separate topic; here the focus is XRP. For the wider send and receive flow, see how to send and receive XRP, and if you are new to exchanges, how to buy XRP.
What a destination tag is
A destination tag is a 32-bit unsigned integer included in a payment to indicate the beneficiary of that payment, such as which customer an exchange should credit (source: XRP Ledger, source and destination tags). It has no direct on-ledger effect; it is information for the recipient's own off-ledger systems.
That distinction matters. The tag does not change how the XRP moves on the ledger, and it is not part of your address. It is a label the receiving business reads after the payment arrives, to map the deposit to an account in its books. Because it carries no on-chain function, a tag is not secret and not sensitive: sharing yours cannot let anyone take your funds, it only tells a business where to file an incoming payment. Think of the address as the building and the destination tag as the apartment number, both are needed for mail to reach the right person inside a large shared building.
Why exchange deposits need one
Exchanges need a tag because of how the XRP Ledger handles accounts. Every XRP address must be a funded, permanent account that holds at least the reserve, so giving each customer their own address would waste resources and tie up reserve XRP (source: XRP Ledger, accounts). Instead, exchanges pool everyone into a few shared accounts.
This pooling is not unique to crypto; it is the same idea as an omnibus account, where one account holds the assets of many clients under a single name (source: Investopedia, omnibus account). The problem the tag solves is the direct result: once thousands of customers share one deposit address, an incoming payment on its own says nothing about who it belongs to. The destination tag is the exchange's internal customer number for that deposit. It is a deliberately lightweight design, one shared account plus a per-customer tag, chosen precisely so exchanges do not have to fund and maintain a separate reserved account for every single user, which the reserve rules would otherwise require.
What happens if you forget the tag
Send to a shared exchange address without the required destination tag and the payment still succeeds on the ledger, but the exchange cannot tell whose balance to credit. Resolving it means a manual support process where you prove the deposit was yours. Because a validated XRP payment cannot be reversed, recovery is not guaranteed (source: FTC, scams).
How bad it gets depends on the exchange. A well-run one can usually match an untagged deposit to you from the sending address and transaction hash, then credit it after review, though this can take days. A smaller or stricter platform may be unable or unwilling to help, especially if the deposit came from another shared address that the exchange cannot tie to a single person. There is no automatic refund on the ledger; recovery depends entirely on the receiving business. That is why the tag is treated as mandatory, not optional, for exchange deposits.
The worst case is a withdrawal from one exchange straight to another exchange's deposit address with the tag left off. Now two shared accounts are involved: the receiving exchange sees a payment from an omnibus address it cannot resolve to a person, and even proving the deposit was yours can require the sending exchange to cooperate. This is exactly the situation destination tags are designed to prevent, and it is why the safe habit is to slow down on any exchange-to-exchange XRP transfer and confirm the tag twice before sending.
When you need a tag and when you don't
The rule of thumb is simple. You need a destination tag whenever you send to a shared address, which in practice means almost every exchange, custodial service, or earn platform. You usually do not need one when sending to your own self-custody wallet, because that address is yours alone with no roomful of customers to sort out.
There are a few nuances worth knowing. Some exchanges enable a setting that outright rejects any deposit missing a tag, so the payment fails and your XRP stays with you rather than landing untagged; that is a safety feature, not an error on your part. Other addresses do not use tags at all, and sending one does no harm. When in doubt, follow what the receiving service tells you: if it shows a tag next to the deposit address, it is required, and if it shows no tag field, you do not add one. Your personal wallet will generally give you a plain address with no tag, which is the normal case for wallet-to-wallet transfers.
X-addresses and avoiding the mistake
The cleanest way to avoid a missing tag is an X-address, a newer format that bundles the classic address and the destination tag into one string, so both travel together and cannot be separated by accident (source: XRP Ledger, address encoding). If a service gives you an X-address, you paste one value and you are done.
When you only have a classic address plus a separate tag, treat the two as a pair. Copy and paste each one rather than typing, put the tag in the tag field and never in the address field, and verify both before confirming. A common slip is pasting the tag where the address goes, or vice versa, so glance at each field once more before you approve. Many exchanges also let you enable a required-tag setting on their side, which is worth using if you receive XRP deposits. The recurring advice from the send and receive guide applies with extra force here: send a small test deposit first, confirm it is credited to your account with the tag attached, and only then move the full amount. A minute of caution is far cheaper than a support queue.
Source tags and safe practice
A destination tag has a mirror image called a source tag, which identifies the sender so a recipient knows where to send a return. When a business bounces a payment back, it uses the incoming source tag as the destination tag on the return. You rarely set source tags by hand; the sending service handles them.
Pulling it together, safe XRP deposit practice comes down to a short routine. Assume any exchange or custodial deposit needs a destination tag unless the platform clearly says otherwise. Copy the address and the tag exactly, prefer an X-address when offered, and send a small test first. If a platform generates a fresh tag each time you deposit, use the current one rather than an old saved value, since a stale tag can misroute the credit just as a missing one can. Keep in mind that the tag is not private, so a support agent legitimately asking for your deposit tag is normal, whereas anyone asking for your wallet's secret key or recovery phrase is not, and that request is always a scam. For the custody and key-safety side of that, the security guides go deeper; the destination tag itself is purely a routing label.
Frequently asked questions
Is a destination tag secret, and can someone steal my XRP if they know it?
No. A destination tag is public routing information, not a credential. It only tells a business which customer account a deposit belongs to, so sharing it cannot let anyone move or take your funds. The values that must stay secret are your wallet's secret key and recovery phrase, which are entirely separate from a tag.
What is the difference between a destination tag and a memo on other chains?
They solve the same problem in different ways. Chains that use a shared deposit address, such as several with a "memo" or "note" field, rely on that field to route a deposit to the right customer, just as XRP uses a numeric destination tag. The mechanics and formats differ per network, so always use the specific field and value your receiving service asks for.
Can I recover XRP I sent to an exchange without a tag?
Often, but not always, and never automatically. Because the payment is valid and irreversible on the ledger, recovery depends on the exchange being able and willing to match the untagged deposit to you, usually from the sending address and transaction details. Open a support ticket promptly with the transaction hash. Some platforms recover it after review; others cannot.
Researched and written for the BloFin Academy. This article is educational and is not financial, investment, or legal advice. Always do your own research.