Sending XRP with a Destination Tag: What to Check Before Every Exchange Transfer

When you move XRP from a wallet to an exchange, one small numeric field decides whether your balance lands in your account within seconds or sits with support for weeks. That field is the destination tag. It is neither an optional extra nor a payment reference of the kind you add to a bank transfer. It is the only piece of information an exchange has to work out which customer the money belongs to.

The short answer first: if the tag is missing, your money is usually not lost, but it has not arrived either. It sits in the exchange pooled account, and whether you get it back depends on how well that exchange runs its support desk and whether it assigns the transaction manually at all.

What is a destination tag on XRP, and why does almost every exchange require one?

A destination tag is a number that assigns an XRP payment to a specific customer account inside a shared receiving address. Technically it is an unsigned 32-bit integer, according to the XRP Ledger documentation. The permitted range therefore runs from 0 to 4,294,967,295.

The reason for this design lies in how the XRP Ledger is built. Every address on the network has to hold a minimum amount of XRP permanently in order to exist at all. That base reserve currently stands at 1 XRP, and each additional entry in the account ties up a further 0.2 XRP. We queried these values directly from the network on September 16, 2026, against validated ledger number 107,024,932.

For an exchange with millions of customers, a separate address per customer would therefore be expensive and would inflate the network permanently. The exchange uses a single deposit address for everyone instead and separates customers through the tag. The address is identical for thousands of users. Only your number belongs to you.

The practical rule follows directly from that. For a transfer to an exchange you have to carry over two details correctly, the address and the tag. For a transfer to your own wallet you generally need no tag, because only one recipient exists there.

How to spot a destination tag in the deposit dialogue

The labels differ from provider to provider. Destination tag, target tag, XRP tag or simply tag are all common. Some interfaces show the number in a separate field directly below the address, others only reveal it once you have selected XRP as the coin. If you are shown a bare address with no further field at all, that does not automatically mean no tag is needed. It can also mean you are in the wrong dialogue, for example in a view meant for a different cryptocurrency.

Why an XRP deposit without a destination tag is not credited automatically

A common misconception holds that a payment without a tag goes nowhere. That is not the case. The transaction is executed normally on the XRP Ledger and validly confirmed, the balance does change hands and then sits at the exchange pooled address. On the ledger, everything looks like a successful transaction.

The problem arises one level up, in the exchange accounting system. That system looks for a tag, finds none and cannot allocate the incoming funds to any of its many accounts. The amount is left in an intermediate state: genuinely present, yet without an owner in the internal database.

What happens next is no longer a technical question but one of internal process. Large regulated providers have a documented procedure for such cases and allocate the deposit manually after a review, often against a processing fee and with a waiting time of several weeks. Smaller platforms sometimes point out that a subsequent allocation is technically not provided for.

Keep this case clearly apart from a payment sent to the wrong address. There the balance has landed with a stranger, and the outlook is considerably worse. What can still be done in that situation is covered in our separate article on crypto sent to the wrong address.

The Require Destination Tag flag: when the XRP Ledger rejects your payment on its own

The XRP Ledger has a safeguard against precisely this error. An account holder can set an option on their address that the protocol calls asfRequireDest. While it is active, the network rejects every incoming payment that carries no destination tag.

The rejection code is tecDST_TAG_NEEDED. The official reference for the tec error codes describes it as the case in which a payment omits the destination tag even though the receiving account has set the flag.

For you as the sender, that is the friendliest form of failure. With a tec code the transaction is still recorded in the ledger and the transaction fee is spent, but the transferred amount is not delivered. Fees on the XRP Ledger sit in the range of fractions of a cent. You lose practically nothing and get immediate, clear feedback instead of waiting weeks for a credit.

That raises a question nobody has asked systematically so far: how many of the exchanges that German investors actually use have this protection switched on?

Our own survey: 114 exchange accounts on the XRP Ledger checked

cryptoticker.io compiled this analysis itself on September 16, 2026. We wanted to know at which trading venues the network catches a missing tag on its own, and at which the error runs through unchecked.

The method in one sentence: we pulled the publicly attributed XRP Ledger accounts of 25 exchanges from the open name directory at XRPScan and, for every single account, queried the network directly to read whether the requireDestinationTag flag is set.

We checked 114 accounts across 25 trading venues, each against the validated ledger of September 16, 2026. The result: at 21 of the 25 exchanges, at least one publicly attributed account carries the protective flag. At four houses we found no flag set at all among the accounts we checked.

The spread within individual houses is striking. At one provider all ten accounts checked carried the flag, at others it was one out of seven or one out of ten. That is to be expected and unremarkable in itself, because alongside its deposit address an exchange runs further accounts for internal settlement, for withdrawals and for cold storage. Those accounts do not need the protection.

What these figures expressly do not mean

The limits of this survey belong with it, otherwise a measurement reads as a verdict. Three things we could not check.

First, the attribution of accounts to exchanges comes from a third party public directory. We did not have the houses themselves confirm which address is genuinely the active deposit address. Second, from the outside we cannot see which address your provider shows you in its deposit dialogue, and that is the one that matters to you. Third, a missing flag says nothing about the quality of a provider: some platforms hold XRP on a purely custodial basis and give their customers no ledger deposit address of their own, while others catch the error at a different technical level.

Only the general reading is therefore robust, and it is enough for your decision. At some of the common trading venues the protocol safeguard applies, at others it demonstrably does not. You cannot rely on it. Anyone switching account or choosing a new one right now will find the venues available in Germany, fees included, in our comparison of the best crypto exchanges.

XRP sent without a tag: which steps actually help now

If it has already happened, speed and complete details are what count. Support can only allocate your deposit if you identify it unambiguously.

Secure the transaction hash from your sending wallet first. That is the long string which names every transfer on the ledger uniquely, and it is the most important piece of evidence. Note the sending address, the receiving address, the exact amount and the timestamp alongside it.

Then open a ticket with your exchange support desk and describe the transaction in plain words: deposit without a destination tag, with a request for manual allocation. Stay on the official channel of your account. Expect a processing time of several weeks and the possibility of a fee.

What you should not do matters just as much. Never respond to offers of help that reach you by direct message or email afterwards, and never hand over your seed or private keys. A separate scam has grown up around lost deposits, in which criminals pose as support staff. An exchange will never ask you for your seed.

Destination tag, memo and note: which coins besides XRP are affected

The pattern is not confined to XRP. It turns up wherever a network provides no low-cost individual addresses and exchanges therefore work with pooled accounts.

On Stellar the field is called memo, on Cosmos likewise memo, and on Hedera a note is used. The label changes, the mechanics stay the same: one shared address, one additional field to tell payments apart. The consequences of a missing entry match each other too.

Remember the broader rule, then. If a deposit dialogue shows you a second mandatory field alongside the address, that field is exactly as binding as the address itself. An additional field left empty is the most common avoidable error in transfers between a wallet and a trading venue.

Check in two minutes whether your XRP transfer needs a tag

This order costs you little time and covers the realistic sources of error.

Always open the deposit dialogue only after selecting XRP as the cryptocurrency, and read the page in full. Take the address and the tag across by copy function or QR code alone, never by typing them out. A transposed digit in the tag means your payment is credited to someone else's account, and that case is considerably harder to cure than a missing tag.

With a larger amount, send a small test transfer first and wait for the credit before the rest follows. The network fee on the XRP Ledger is so small that this test is effectively free. Afterwards check that the amount credited matches the amount sent exactly.

For the return leg, meaning withdrawals from the exchange to your own wallet, a withdrawal whitelist is worth adding. It limits withdrawals to addresses you have registered in advance and takes the option of a transfer away from an attacker even once they are inside your account.

Why so many XRP transfers are going wrong right now

The subject is pressing for a concrete reason. Deadlines forcing customers to act are running out at several trading venues in these weeks: cryptoticker.io reported on the closure of CoinEx on September 15 and on the withdrawal deadline at KuCoin on September 8, alongside ongoing delistings of individual tokens at further exchanges.

Deadlines like these set holdings in motion. Balances move from one platform to the next or into self-custody, and they move under time pressure. Experience shows that transfer errors cluster precisely when users operate an interface for the first time while watching a deadline.

If you are pulling XRP off a platform in the coming weeks, do not plan the transfer for the final day. If something goes wrong and support has to step in manually, you need a buffer. Once a withdrawal deadline has passed, a solvable allocation problem quickly turns into an unsolvable one.

Self-custody instead of a pooled account: when your own XRP wallet is worth it

The tag issue affects payments to pooled addresses alone. Transfer to your own wallet and it falls away, because only one recipient exists there and the address belongs to you alone.

That is an argument for self-custody, though not a free pass. Your own wallet shifts responsibility entirely to you: the protection of your recovery words then decides over your balance, and nobody can reverse a mistake on your behalf. For larger holdings you intend to keep for a while anyway, a hardware wallet is the established route. How the devices differ and what to look for when buying is set out in our hardware wallet comparison.

Note one peculiarity of self-custody with XRP: your own address also has to hold the base reserve of 1 XRP permanently before the account is activated on the ledger at all. A freshly created XRP wallet is not a valid account until the first sufficient deposit, so a first transfer that is too small can fail. Plan the opening deposit accordingly.

Checking the destination tag: what to take away

1. Treat the tag like the address. On every transfer to an exchange, copy both details out of the deposit dialogue and type neither of them. If you are considering a change of trading venue anyway, compare the providers available in Germany beforehand in our crypto exchange comparison.
2. Test before you send the whole amount. A small advance transfer costs fractions of a cent on the XRP Ledger and shows you within seconds whether the address and the tag are right. Secure the return leg as well with a withdrawal whitelist.
3. Do not rely on the network to protect you. Our survey of September 16, 2026 shows that the protective flag was not set on the checked accounts of four of the 25 houses. Anyone holding larger amounts long term bypasses the pooled account entirely and uses their own wallet, for instance a device from our hardware wallet comparison.

(As of September 16, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)