An XRP destination tag is a numeric code attached to a payment alongside the receiving address, telling the recipient's internal systems which customer or account the incoming funds belong to. The XRP Ledger documentation describes destination tags as a feature of XRP Ledger payments that can indicate a specific purpose for payments sent to multi-purpose addresses. They appear most often when depositing XRP at an exchange, where many customers share a single address and the tag is what separates one depositor's funds from everyone else's.

What an XRP destination tag does

A destination tag identifies the beneficiary of a payment when the receiving address serves more than one customer. According to the XRP Ledger documentation, a payment to an exchange or stablecoin issuer address can use a destination tag to indicate which customer to credit, and a payment to a merchant could indicate which item or cart the payment is buying.

The tag does nothing on the ledger itself. Source and destination tags have no direct on-ledger functionality; they exist only to tell off-ledger systems how to process a payment. In transactions, tags are formatted as 32-bit unsigned integers, which is why a destination tag is always a plain number rather than a string of letters.

Coinbase's support documentation describes a destination tag or memo as an additional address feature necessary for identifying a transaction recipient beyond a wallet address. Different platforms use different labels for the field, but the job is the same: whenever a platform serves many customers through a single deposit address, it needs an extra identifier to route incoming funds to the right account.

Why the XRP Ledger uses tags instead of extra addresses

On many other networks, platforms hand each customer a separate deposit address. The XRP Ledger documentation explains why that approach fits XRP poorly: an address must be a funded, permanent account to receive payments, and the reserve amount must be set aside indefinitely for each address. Spinning up an account per customer consumes network resources and locks up funds, so tags act as a more lightweight way to map deposits and payments to individual customers. That design choice is also visible to users: instead of a unique address per customer, an XRP deposit screen typically pairs a shared address with a numeric tag.

Giving customers the ability to send and receive transactions from a business's XRP Ledger address through another interface is known as providing hosted accounts, and hosted accounts typically use source and destination tags for each customer.

When a destination tag is needed

A tag is required whenever the receiving address serves multiple accounts and its owner asks for one. Exchange deposits are the typical case. The XRP Ledger documentation lists the main business uses for tags: direct mappings to customer accounts, matching return payments to the outgoing payments that prompted them, mapping payments to quotes that expire, and disposable tags that customers can generate for specific deposits.

The requirement always comes from the receiving side, so the safest habit is simple: open the recipient platform's deposit page and copy both the address and the tag exactly as shown. The same caution applies whether funds are sent from an exchange account, a mobile app, or a hardware device.

Some receiving addresses enforce the rule at the ledger level. With the RequireDest setting enabled, the XRP Ledger rejects a payment that arrives without a destination tag instead of crediting money the recipient cannot assign. The sender can then send the payment again with the correct tag included.

What happens if XRP is sent without a tag

If the address enforces RequireDest, the payment is rejected by the ledger, so nothing is credited and the sender can resend with the tag included. If the address accepts untagged payments, the funds arrive, but it is not immediately obvious which customer to credit. The XRP Ledger documentation notes that this can require manual intervention and a discussion with the sender to figure out who the intended recipient was. The result is a slow, manual process rather than an automatic credit, and since confirmed ledger payments cannot be undone by the sender, the outcome depends on the receiving platform's support process rather than any on-ledger fix — which is why copying the tag before sending is always the better path.

Source tags, return payments and X-addresses

Destination tags have a mirror. Source tags indicate the originator or source of a payment, and they are most commonly included so the recipient knows where to send a return, or bounced, payment. When returning an incoming payment, the source tag from the incoming payment should be used as the destination tag of the outgoing return payment.

There is also a format that folds both pieces of information together. An X-address combines a classic address with a tag into a single address that encodes both, and the tag inside an X-address acts as a source tag when sending and a destination tag when receiving. For a customer, that means keeping track of a single string instead of an address plus a separate tag.

Tags also carry a privacy dimension. All XRP Ledger transactions are public, so assigning tags in numerical order provides less privacy and can make it possible to guess which tags correspond to which users' addresses. The documentation suggests assigning tags in an unpredictable order within reserved ranges instead.

Frequently asked questions

Is a destination tag the same as a memo?

For the sender, yes in practice. Coinbase treats destination tags and memos as the same additional address feature that identifies a transaction recipient beyond the wallet address. Whatever the field is called on the deposit page, the value should be copied into the matching field in the wallet before sending.

What does an XRP destination tag look like?

It is a plain number. XRP Ledger transactions format tags as 32-bit unsigned integers, so a valid destination tag contains digits only, with no letters or symbols.

Is a destination tag needed when sending to a personal wallet?

Tags exist to sort payments arriving at multi-purpose addresses, such as those run by exchanges and stablecoin issuers. Follow the receiving side's instructions: if the deposit screen shows a tag, include it, and if a personal wallet does not ask for one, there is no tag to copy.

What if XRP was already sent without the required tag?

If the address had RequireDest enabled, the payment was rejected and nothing was credited, so it can simply be resent with the tag. If the payment went through untagged, the recipient may need manual intervention and a discussion with the sender before the deposit can be assigned, and the receiving platform should be contacted with the transaction details.

Source: Cryptsy