XRP Destination Tags: Check the Address and the Recipient Reference
An XRP destination tag is additional routing information that a receiving service can use to identify which customer should receive credit at a shared address. If the receiving instructions require a tag, the address alone is insufficient for reliable account crediting. Always use the current instructions for your own receiving account.
Understand the two pieces of information
The address identifies an XRP Ledger account. A destination tag can help the service associate the payment with an off-ledger customer account. It is not a second wallet address, a password or proof of ownership.
Some receiving arrangements need a tag and others do not. Do not copy a tag from a tutorial or another user. This article does not supply a usable deposit address or reference.
Read the receiving page before sending
Open the deposit page, select the intended asset and supported network, and check the instructions shown for your account. Availability, minimums and service status can change.
If the page supplies both an address and a required tag, copy each into the corresponding field in the sending service. If the sender cannot supply the required information, stop and clarify the supported transfer method before initiating payment.
Check representations and field labels
A source tag and a destination tag describe different ends of a payment. A label such as memo on another interface should not be assumed to mean an arbitrary message; confirm how that sender maps its input to the receiving requirement.
Some address representations can encode additional information. Do not manually append text to an address or assume every sender supports the same representation. Reconcile what the sender will actually submit with the receiver’s instructions.
Separate ledger completion from account credit
A transaction can be recorded on a network without being automatically assigned to the intended customer balance. A small transfer does not remove the need to satisfy minimums, required fields and supported-network rules.
Review the network selection checklist for the general principle that assets and networks must match. Its USDT examples do not establish XRP-specific address or tag rules.
Keep evidence if credit is missing
Check the sending history and current deposit status. Record the transaction identifier, asset, network, amount, destination address and submitted tag, then contact official support through the help center if needed. Do not share passwords, private keys or recovery phrases.
Recovery of a missing or incorrect tag can depend on the receiving service’s capabilities and evidence requirements. Do not promise automatic recovery, a fixed recovery time or a guaranteed refund. Avoid sending another payment merely to try to correct the first.
Common questions
Does every XRP transfer require a destination tag?
No. Follow the specific receiving account’s instructions.
Does network success always mean my exchange balance is credited?
No. The service must also match the payment to the intended customer.
Is a missing tag always recoverable?
No. Contact the receiving service; recovery is not guaranteed.
