All guides

Pair guides

XRP to USDT: check the destination tag and the receiving network

An XRP-to-USDT swap combines an XRP Ledger deposit with a stablecoin payout on a separately selected network. The destination tag belongs to a particular transfer instruction; it is not a universal code you can copy between every address in the order.

An XRP logo coin and Tether USDT coin stand on opposite sides of a memo-shaped stone gate.
AI-generated editorial illustration with recognizable XRP and USDT marks. A required destination tag or memo is a separate detail from the wallet address. Follow the exact order instructions.

Check the XRP account you are sending from

Verify that your spendable balance is native XRP on the supported Mainnet route. A wrapped token on an EVM chain is a different asset arrangement even if its name includes XRP. In a self-custody wallet, the displayed total can include funds constrained by account requirements, so use the wallet’s spendable amount and current transaction preview.

A custodial XRP withdrawal has another set of conditions: its enabled network, minimum withdrawal, fee presentation and extra-ID fields. Look at those before creating an order. If the sending platform cannot supply a destination tag when the provider requires one, a technically valid address alone will not make that withdrawal suitable.

Choose which USDT balance you want to receive

USDT is available through multiple site-listed network options. Start with the destination wallet or exchange deposit screen and choose a network that it explicitly accepts. Receiving USDT on TRON, Ethereum or Solana creates a balance on that chosen chain; it does not create a generic USDT balance that every service can credit.

The receiving address and any required destination memo belong to the USDT payout side. Do not place the XRP deposit tag into that field merely because both are called extra IDs. If the receiving service supplies no compatible network from the live quote options, stop and choose a supported destination rather than guessing from the address characters.

Understand memos and refund addresses

Understand what an XRP destination tag identifies

A service can receive funds for several customers or orders at a shared XRP Ledger address. A destination tag tells its own accounting system which payment the transfer is intended for. The tag does not replace the address or change an XRP payment into a transfer on another blockchain.

Use the tag displayed for the confirmed provider deposit, when one is required. A refund destination may have its own tag, and the payout destination may have a separate memo convention. Keep those roles distinct. Never invent a tag, reuse one from an older order, or treat an application’s no-memo placeholder as a general instruction for the wallet transaction.

Work through a deposit example without inventing a live rate

Suppose an illustrative order expects 100 XRP and displays a provider address with a required destination tag. Your exchange withdrawal preview says entering 100 XRP will deliver 99.8 XRP after its fee. That withdrawal would not meet the order’s exact deposit requirement, even if the address and tag were both correct.

Reconcile the net delivery before confirming the withdrawal. Depending on the sender’s interface, that could mean entering a different gross amount or creating an order for a supported net amount. This example does not specify a current fee or XRP-to-USDT rate. The live provider quote supplies the receive estimate, and your actual withdrawal preview supplies the delivery calculation.

CheckWhat to verify
SourceXRP Mainnet, including the current provider tag when required
DestinationThe exact selected receiving asset and network, accepted by the destination
AmountNet delivered source amount matches the active order
TrackingSwap ID plus separate deposit and payout transaction hashes

Review the provider and create the swap

Request a quote for XRP Mainnet to the chosen USDT network and the intended deposit amount. Compare provider policies, rate type and the amount expected at the destination. Provider verification requirements may vary; choosing a privacy rating does not make the transaction exempt from all screening or support checks.

In the wallet-details step, enter the USDT receiving address and the correct extra information if requested for that destination. The optional refund address must receive XRP on the source network, with its own tag when the receiving service requires one. Review the route and create the swap before copying any provider deposit information.

Send the deposit with the correct extra field

When the order is awaiting deposit, compare the complete provider address, amount, network and tag with your sending screen. The site’s QR code encodes the address only. After scanning, you still need to enter the exact amount and the required destination tag separately; the QR image does not prove those other fields were populated.

Recheck the wallet’s final confirmation instead of relying on the form you initially filled. Some interfaces label the extra field Memo, Tag or Destination tag. Confirm that you are using the appropriate field for an XRP transfer, and that any saved withdrawal-address entry has not silently supplied an old tag.

Track the XRP deposit and the USDT payout separately

Copy the Swap ID for the order and retain the XRP transaction hash from the sender. If a required tag is missing or wrong, a successful on-chain payment may still need manual attribution by the receiving service. Do not resend merely because the provider has not matched it. Contact support with the existing transfer evidence first.

Once the provider reports a payout, inspect the destination network and the USDT receiving service’s crediting rules. The payout has its own transaction hash on that network. A sender-side XRP confirmation does not demonstrate a completed stablecoin payout, and a provider payout does not automatically remove a custodial service’s deposit minimum or confirmation policy.

A FEW MORE DETAILS

Common questions

Does every XRP payment require a destination tag?

No. A receiving service may require one for its account or order mapping. Follow the exact address instructions rather than assuming all XRP destinations use the same rule.

Can the QR code include my required tag automatically?

The Tornado Swap deposit QR currently contains only the address. Enter the required tag and amount separately in the sending wallet.

Is my XRP deposit tag also my USDT receiving memo?

No. Extra IDs belong to the address and transfer leg they describe. Check each independently.

What if I already sent XRP with the wrong tag?

Keep the existing transaction hash and Swap ID, then contact support. Recovery or attribution depends on the receiving service; do not assume another transfer will fix it.

Prepared by Tornado Swap to explain the swap workflow. Network conditions and provider offers can change; check the current order instructions before sending funds.

Keep reading