The swap reference and the recipient reference are different
Keep the KOT.CASH order reference separate from the destination tag supplied by your receiving platform. They identify different things. Do not paste an order number into the tag field because both values look like numbers. Start from the deposit screen for the exact XRP account you intend to fund, rather than from a previous withdrawal or an unrelated message.
XRP Ledger documentation explains that a destination tag can identify a beneficiary behind a shared address. It is information used by the receiving service; its presence is not proof that your balance has already been credited. A source tag has a different role. Do not substitute one for the other when copying payout instructions.
Read each receiving detail by its purpose
| Detail | Where to get it | Mistake to avoid |
|---|---|---|
| XRP address | Current deposit instructions of the intended recipient | Treating an address from a previous transfer as permanent instructions |
| Destination tag | The same receiving account instructions | Replacing it with the swap order reference |
| Address format | The format the receiving and sending interfaces actually support | Assuming an encoded address is accepted everywhere |
| Credit status | The receiving platform account history | Calling a visible network payment a completed account credit |
Resolve an unclear tag before sending USDT
- Open the intended recipient account
Confirm that the deposit page is for XRP and belongs to the account you want to credit. Read any current restrictions there. Keep the address and the tag from the same set of instructions; do not assemble them from two saved screenshots.
- Compare the payout form with those instructions
If the receiver supplies a tag, verify that you can enter the required details in the offered payout route. If a field or address format is unclear, stop preparation and ask support before funding. Do not experiment by putting a tag into an address string.
- Resolve explicit no-tag instructions
Some receiving situations do not call for a tag. Follow the actual receiver instructions rather than inventing a value such as zero. If the interface and the receiver disagree, clarify that disagreement instead of assuming that a filled field is always safer.
A missing credit needs a trace, not another blind payment
The XRPL address documentation distinguishes classic addresses from X-addresses that encode a tag. This does not establish support for every format in a particular exchange interface. Check what the offered form accepts; do not manually shorten, rewrite or decode payment details as an improvised workaround.
After a payout, preserve the order reference and the XRP transaction reference separately. If the receiver has not credited the account, compare the destination details with its instructions and contact the appropriate support channel with the factual references. Recovery of a missing or incorrect tag depends on the receiving service and the actual payment; it is not guaranteed by this guide. Avoid sending another payment solely to repair the first, and never disclose recovery phrases or private keys in a ticket.
Questions about the receiving tag
- Can I use the exchange order number as the destination tag?
- No. Use the tag provided for the intended receiving account. The swap reference identifies the exchange request, not the beneficiary behind a receiving address.
- Does a successful XRP transaction prove that my exchange account is credited?
- It does not establish the receiving platform balance. Check the account history separately and retain the transaction reference if a support investigation is needed.
- Should I enter zero if the recipient says no tag is needed?
- Do not invent a tag. Follow the receiving instructions and clarify any mismatch with the payout form before funding the exchange.
Receiver identification documentation
Reviewed: