There are broadly two ways to send USDT to someone: through an exchange's internal payment feature, or as a public on-chain transfer. Both look like "moving coins across", but the mechanisms are different and so are the conditions under which each works.
Telling them apart avoids two kinds of waste: repeatedly attempting an internal payment the other side cannot receive, and paying a network fee when an internal route was available.
This guide describes the mechanics. Whether a feature is open to your account, and what it costs, comes from each platform's current page; this site does not determine eligibility.
Key points
- Internal payments require both sides on the same platform, with the feature open to you
- On-chain transfers work anywhere but need the right network and a fee in the native asset
- Neither is reversible, so checking before sending matters equally
- Use whichever the merchant's checkout offers; do not reroute on your own
How the two differ
The table covers structural differences rather than specific rates — rates change with platform policy, so use the current page for those.
| Exchange-internal payment | On-chain transfer | |
|---|---|---|
| Recorded on | The platform's own ledger | A public network |
| Requires | Both parties on that platform, feature enabled | Any wallet or platform supporting the network |
| Network selection | Not applicable | Required, and must match the recipient |
| Network fee | Usually none | Yes, paid in the network's native asset |
| Speed | Usually near-instant | Depends on the network and confirmations required |
| Reversible | No | No |
| Who to contact | That platform's support | Investigate the sending and receiving sides separately |
When an internal payment fits
Consider it only when the merchant's checkout explicitly offers that route and your account can use it. When both hold, it is usually simpler: no network to choose and no network fee to cover.
Do not try to talk a merchant into accepting it because it is cheaper. Pay by whatever the checkout offers — rerouting on your own initiative tends to leave the order unable to match automatically.
When it is an on-chain transfer
When the other party is not on the same platform, or checkout simply gives you a receiving address, you are making an on-chain transfer. The work then is choosing the right network, verifying the address, and confirming the amount that will arrive.
If your funds sit in a self-custody wallet, an on-chain transfer is usually the only option. In that case, also confirm the wallet holds the network's native asset to cover the fee.
An exchange account and a Web3 wallet are not the same thing
Inside a single exchange app there are typically two separate places to hold funds: the exchange account and a Web3 wallet. Which one holds your assets changes what you can do with them.
Funds in the exchange account leave through the withdrawal flow, with the platform submitting the on-chain transaction. Funds in the Web3 wallet are sent by you signing a transaction, with the fee taken from the wallet's native asset. Fees, limits and steps all differ, so establish which side holds your funds before transferring.
Frequently asked questions
Why is the internal payment option sometimes unavailable?
The other side may not be on the same platform, your account may not have completed the required verification, the feature may not be available in your region, or the merchant's checkout may simply not offer it. The platform's own message is the reference.
Is an internal payment safer?
It removes network selection, so it removes that failure mode. But sending to the wrong recipient or the wrong amount remains possible, and it is equally irreversible. The checks before sending still apply.
Can I send internally to their exchange account and let them withdraw?
That changes the payment route the merchant specified, so the order usually will not match automatically and ends up needing manual handling. Unless the merchant says otherwise, pay the way checkout tells you to.
Sources
Public sources used for this guide. Sources checked on 2026-09-08. We have not tested this with a real purchase.
- Bitrefill: pay with cryptocurrencyReviewed 2026-09-08
- Bitrefill: delivery errors and refundsReviewed 2026-09-08