An XRP payment without a destination tag, or with the wrong one, still succeeds on the ledger. The coins reach the recipient's shared account, but the service cannot tell which customer they belong to.
Why tags matter
Exchanges keep one XRP Ledger account for many customers and tell deposits apart by a number, as described in the XRPL tags documentation. If the account sets RequireDest, a tagless payment fails with tecDST_TAG_NEEDED and your XRP stays with you.
What to do
- Do not resend or "top up with a tag".
- Collect the transaction hash, sender and recipient, amount, time and the expected tag (see our memo and tag guide).
- Contact the recipient's official support; for a swap on the XRP to USDT page, include the order number.
- Ignore anyone offering paid "recovery"; only the recipient can credit the payment, and the outcome depends on their rules.
If the payment failed with tecDST_TAG_NEEDED, nothing is lost: send again with the correct tag. A wrong tag that matches another customer's number may have been credited to them automatically, which is why support needs the exact data.
XRP Ledger payments settle in seconds, so if nothing is credited after a few minutes, check the tag and contact support straight away.
Keep the support ticket number and all correspondence.
Avoid it next time
Save the address together with its tag, check the tag field before signing and test with a small amount first.
FAQ
Can I add a destination tag after sending?
No. The ledger entry cannot be changed; only the recipient can match the payment.
Why did my tagless payment fail?
The recipient requires tags, so the ledger rejected it with tecDST_TAG_NEEDED and nothing left your account.