Before depositing XRP into an exchange, copy the receiving address and its destination tag from the same current deposit screen, then verify both in the sending application. Do not assume that an address saved from an earlier transfer includes the tag or that a successful blockchain payment guarantees a credit to your exchange account.
A destination tag is a number attached to a payment that helps a recipient identify whom it belongs to. XRP Ledger documentation explains that the tag itself has no on-ledger processing function. A business can use it to match a payment arriving at a shared address with the appropriate customer in its own records.
First identify the kind of destination
Open the receiving service through your usual trusted route and choose XRP deposits. Read the instructions for that specific destination. Coinbase says tags generally are not needed for a private, self-custody wallet with a unique recipient address, but requirements are determined by the receiving platform. Do not invent a tag simply because another transfer required one.
Kraken provides a useful example of a shared destination: its support instructions say customers use a shared XRP deposit address and must supply their unique destination tag. The address gets the payment to Kraken; the tag identifies the customer account. Correctly entering only one of those fields is insufficient.
An order-specific destination requires another check. MoonPay says an XRP sell order has its own address and tag, distinct from a standing wallet address. Its instructions expressly warn against reusing a tag from a previous sell order. A saved contact can therefore be accurate for an old transaction and unsuitable for the new one.
Check the final payment, not only the copied text
- Confirm that the selected asset and network match the receiving service’s instructions.
- Copy the destination address and, when required, the destination tag from the same current account or order.
- Paste the tag into the application’s designated destination-tag field. A free-text note is not a substitute.
- Review the completed confirmation screen. Check that saved-contact settings, scanning or autofill have not replaced either value.
- If using a small test transfer, check the recipient’s minimum deposit and fees first. Wait for the intended account credit before treating the test as successful.
Coinbase suggests a small test amount as a way to check the address and tag. That is a practical check, not insurance against every mistake. It is also not a reason to reuse order-specific instructions after the order changes.
X-addresses and required tags solve different problems
XRP Ledger documentation describes an X-address format that combines a classic address and a tag in one string. Whether your sending and receiving applications support that format still matters. Follow their instructions rather than manually converting an address using an unfamiliar service.
The ledger also allows a receiving account to require a destination tag, rejecting payments that omit one. This can prevent a missing-field error. It does not prove that a number entered by the sender belongs to the intended exchange customer. A present tag and a correct tag are different checks.
If the deposit has not appeared
Stop and collect the record of the original transfer before sending again. Note the transaction hash, asset, network, amount, destination address, tag supplied and the receiving account or order. Check whether the transaction was actually submitted and whether the ledger reports a successful payment. Keep that separate from the exchange’s crediting status.
If the payment went to the intended service but the tag was wrong or missing, contact that service through its official support route. Coinbase asks customers reporting an incorrect tag to provide the transaction hash. MoonPay asks for the sell-order ID and transaction hash when an XRP sell-order tag was omitted.
Kraken warns that an omitted tag can cause a significant delay and may leave funds irretrievable. Its recovery guidance makes clear that recovery is not guaranteed. Sending another payment with the correct tag does not edit the first transaction or automatically resolve its account assignment.
Keep the two records separate
The XRP profile explains the underlying network, while our wallet guide distinguishes holding keys from holding an exchange balance. That distinction explains this problem: the ledger can record a payment to a shared address while the business still needs information to credit the intended customer. Checking the address-tag pair before sending is simpler than asking support to reconstruct the intention afterward.