Destination tag

A destination tag is a number attached to a payment on the XRP Ledger that tells the receiver, usually an exchange, which customer the money is for. Exchanges such as Kraken give many customers one shared XRP deposit address and tell them apart only by tag, so a deposit sent without the right number can be delayed or lost.

One address, many customers

Why does an exchange ask for a number on top of the address? Kraken’s XRP deposit page, last updated October 19, 2026, says all Kraken accounts share a single XRP deposit address, rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh. Each customer gets a unique tag ten digits long, and the exchange uses it to decide whose account to credit.

The page is blunt about the risk. “Forgetting to include the Destination Tag will lead to significant delays in crediting the deposit to your account, and might even make the deposit irretrievable in certain cases,” it warns, and it sends anyone who forgot to a support ticket.

What the ledger does with the number

Very little, by design. The XRP Ledger’s documentation on tags says they “do not have direct on-ledger functionality” and only tell off-ledger systems how to process a payment. A tag is a 32-bit unsigned integer, a whole number from 0 to 4,294,967,295.

The reason for sharing one address is cost. On this ledger an address has to be a funded, permanent account, and a reserve must be set aside for each one indefinitely.

We asked the public xrplcluster.com server at 13:26 UTC on November 19, 2026, and it reported a base reserve of 1 XRP per account plus 0.2 XRP for each object an account owns, the same figures the reserves page lists for the main network.

A flag that bounces tagless payments

Receivers can make the tag compulsory. According to the ledger’s tutorial, when the Require Destination Tag setting is on, “the XRP Ledger rejects any payment to your address if it does not specify a destination tag.” Our account_info query at 13:26 UTC, on validated ledger 108,433,096, showed that flag switched on for Kraken’s deposit address.

That stops a blank tag. It does nothing about a wrong one, because the ledger “has no way of knowing whether any specific tag is valid,” the tutorial says, and businesses must be ready to receive payments carrying the wrong number. A mistyped tag can still deliver the coins to the shared address, where the receiving business then has to work out whose they are.

Where you see it

At Kraken the tag is generated together with the deposit address, and the sender has to enter both. The XRPL documentation suggests an alternative for businesses, the X-address, which packs the address and the tag into one string so customers don’t have to keep track of two pieces of information.

Other networks use the same trick under a different name. Kraken asks for a “Memo” on Stellar deposits sent to its shared address, though since December 13, 2022 it also offers muxed addresses starting with M that make the memo unnecessary. Whatever the network, copy the tag rather than retyping it, and send a small amount first when the sum is large.