A number with no default

One blank destination tag, and a deposit lands nowhere you can find

A destination tag is a small number attached to a payment, and unlike the address itself, nothing fills it in for you. This page explains what the field is, why a shared-address cashier needs it, and what actually happens when it is missing or wrong.

A destination tag is a number, separate from the deposit address, that a casino's cashier may ask you to include alongside a payment. It is not part of the address itself, it is not required by the underlying network for a transaction to succeed, and it has no default value: if a field asks for one and you leave it blank, most wallets will send the payment anyway, exactly as instructed, tag or no tag.

That last point is the one that catches people out. A payment sent to the right address with no destination tag is not an error from the network's point of view — it settles normally, just like any other transaction. The problem, where one exists, sits entirely on the receiving end: at an operator that relies on the tag to know which customer a payment belongs to.

The same five fields on every deposit or withdrawal screen this site describes: address, destination tag, amount, network fee and confirmation count. Data status: operator terms read 24 August–12 September 2026, licence registers checked 8–13 September 2026, XRP-specific cashier facts captured 2 September 2026.

Why a shared address needs a tag at all

A business that receives deposits from thousands of players does not, in practice, open a separate account on the network for each one. Managing that many accounts, each with its own reserve and its own record-keeping, would be far more overhead than most cashiers want to carry. Instead, many operators open one account and give every depositor the same address, distinguishing between them with an additional piece of information: the destination tag.

Once you understand that structure, the purpose of the tag stops being mysterious. The address says which company the money is for. The tag says which customer of that company it is for. Two pieces of information, doing two different jobs, and only one of them is unique to you.

Why a destination tag has no default

Four moments in the life of an XRP payment where the destination tag, not identity or a password, decides whether the money is found.

On many other networks, an address is treated as a complete instruction: you get your own, and the network alone is enough to identify who a payment belongs to. The destination tag exists specifically because that assumption breaks down at a shared-address cashier, and the network itself has no opinion on whether a given account needs one — it simply carries whatever number, if any, a sender includes alongside a payment.

That means the tag is not a network-level safety feature by default. Some operators configure their receiving account to reject any payment that arrives without a tag, forcing the sender to resubmit with one attached; many do not, and an untagged payment is accepted exactly as if it had arrived correctly, sitting inside the operator's account with no field on it that says whose deposit it is. A depositor has no way to check from the outside whether a given cashier's account has that protection turned on, which is the practical reason to treat the tag as mandatory at any operator that asks for one, rather than assuming a safety net exists.

What a blank tag actually does to a deposit

Sending XRP to the correct address without a required tag does not fail, bounce back, or trigger an error message in most cases. The payment settles on the network exactly as any other transaction would; it is valid, it is final, and it is sitting inside the operator's account. What is missing is the one piece of information that would have told that operator which of its many depositors the money came from.

From that point, the money is not lost in any technical sense — it exists, on the public record, inside an account the operator controls — but it is also not automatically yours in the operator's own system. Recovering it depends entirely on the operator's own support process: providing the transaction details, the amount, and the timestamp, and asking a human being to match the payment to your account. Whether that process exists at all, and how it works, is a matter of that operator's own policy, not a guarantee this site can make on any operator's behalf.

Sent with the wrong tag, rather than none at all

A payment sent with an incorrect tag — a typo, a tag copied from an old deposit, a tag meant for a different account entirely — is arguably the harder case, because the money does not sit unclaimed. It gets matched, correctly according to the system reading the tag, to whichever customer that tag actually belongs to. That is a different problem from a missing tag: it is not a question of finding an unlabelled deposit, it is a question of a payment credited to somebody else's account, and resolving it is entirely dependent on that operator's own internal process, since the network itself has already done exactly what it was told to do.

Not every wallet or exchange treats the field the same way

Some sending wallets and exchange withdrawal screens present the tag as a required field the moment an address is recognised as belonging to a shared-account cashier; others leave it as an optional extra, sometimes hidden behind a label like “memo” or an “advanced” toggle that a sender has to go looking for. Neither behaviour is wrong on the network's own terms, since the tag is genuinely optional there — but it means the responsibility for including it correctly sits with whichever interface you are sending from, not with any built-in check the network performs on your behalf.

That inconsistency is also why copying a tag from an old screenshot, a saved note, or a previous deposit is worth double-checking rather than assuming it still applies. A tag is specific to one destination account and, at some operators, may even be specific to one deposit session rather than staying fixed for your account indefinitely. Reading the current cashier page each time, rather than relying on memory, avoids a category of mistake that has nothing to do with the network and everything to do with which number was actually current.

It is worth being clear about one thing this field is not: it has nothing to do with the account reserve that every account on the network is required to hold. The reserve is a network-level rule about how much balance an account must keep untouched at all times; the tag is a piece of routing information attached to an individual payment. A depositor who has read about the reserve and assumes it somehow explains a missing or misrouted deposit is looking at the wrong mechanism — the two concepts solve entirely different problems and neither substitutes for understanding the other.

Confirming a tag actually made it into the payment

Once a payment has been sent, whether the tag went through correctly is not something to take on faith — it is printed on the public record alongside every other detail of the transaction, readable independently of anything a casino's own dashboard shows. Reading your own transaction walks through where the tag sits among the handful of fields worth checking, which is a more reliable way to confirm a deposit was tagged correctly than waiting to see whether a balance updates.

Copying the pair, not just the address

The practical response to all of this is simple to state and easy to get wrong in practice: treat the address and the tag as one instruction, copied together, every single time. An address copied without its accompanying tag is not obviously incomplete to a wallet — nothing in the interface objects, because from the network's point of view nothing is wrong. Depositing XRP walks through the full sequence, including where the tag fits among the other steps of a deposit, so the two pieces of information are handled in the same motion rather than as an afterthought.

When something has already gone wrong

If a payment has already gone out with no tag, with the wrong tag, or the destination tag question turns out not to be the actual issue at all, the practical options and what can still be recovered are laid out on stuck payment, which covers the tag failure alongside the other common ways an XRP payment can look stuck from the outside.

Operators that print a destination-tag rule in their own terms are marked as such in the table on best ripple casinos.

What exactly is a destination tag?

It is a number, separate from the deposit address, that some cashiers use to identify which customer a payment belongs to when many depositors share one address. It carries no meaning to the underlying network on its own; the network simply records it alongside the payment, and it is the receiving operator that decides what the number means.

Does the network require a destination tag for a payment to go through?

No. A payment sent without one still settles normally on the network; nothing about the transaction itself fails. The tag only matters to operators that rely on it to sort deposits by customer, and whether a given operator's account rejects untagged payments is a setting only that operator controls.

What happens if I send a deposit and forget the destination tag?

The payment is not lost technically — it settles and sits inside the operator's account — but it is not automatically matched to your player account either. Recovering it means contacting the operator's support with the transaction details, the amount and the timestamp, and asking them to match the deposit manually; whether that process exists and how it works depends entirely on that operator's own policy.

Is a wrong destination tag better or worse than a missing one?

In one sense worse: a payment with a wrong-but-valid tag is typically credited correctly to whichever account that tag belongs to, which is a different customer's balance rather than an unclaimed deposit. Both situations depend on the operator's own process to resolve, but a wrong tag involves someone else's account rather than simply an unlabelled payment.