USDT does not live on a single chain. The same asset is issued separately on several networks, each with its own address space. Send funds on a network the recipient does not support and they do not bounce back — in most cases support cannot recover them either.
This is the most consequential error in USDT spending, and also the most avoidable. Avoiding it requires no understanding of how blockchains work, only one rule: use the network the order page states right now, and check it character by character.
This guide covers the checking method and the common misreadings. Supported networks change; whatever the page shows at the moment you order is what counts.
Key points
- The same asset does not move between networks, and misdirected funds are usually unrecoverable
- Take the network from the current order page, never from a saved address or old note
- Similar address formats do not mean the same network — appearance proves nothing
- Transfers also need the network's native asset for fees; USDT alone may not be enough
- A small test transfer is the cheapest insurance available
Why it happens
Sending on the wrong network is rarely a knowledge problem; it is a process problem. The three usual causes: reusing a saved address, losing track while switching between two pages, and assuming that because two addresses look alike the networks match.
That last one matters most. Some networks use identical or near-identical address formats that cannot be told apart by eye. An address that "looks right" is not evidence of anything. The only reliable source is the network name printed on the order page.
Four steps to run every single time
Treat it as a fixed routine. Do not skip a step because last time went fine.
- Find the network name on the order page and copy it exactly. Do not write it from memory.
- Select that identical network on the sending side. If the names do not correspond, stop and ask — do not pick the closest-looking option.
- Copy the full address, paste it, then verify the opening and closing characters against the page.
- Confirm the sending account holds the native asset that network requires for fees.
Fees are paid in the native asset, not in USDT
On most networks the transfer fee is paid in that network's native asset rather than deducted from your USDT. A wallet holding only USDT may therefore be unable to send anything at all.
Exchange accounts usually handle the fee for you, so this rarely bites when withdrawing from an exchange. It is common when sending from a self-custody wallet. Confirming you hold enough of the native asset beforehand is much simpler than discovering it mid-transfer.
The amount received may differ from the amount sent
When withdrawing from an exchange, the fee may come out of the amount you entered, so the recipient receives less than the figure you typed. If the merchant's order requires an exact amount, that shortfall can stop it matching automatically.
So read the field carefully: is the number "what you pay" or "what they receive"? When in doubt, work backwards from the amount the order requires, or choose the option where you bear the fee separately.
Is a test transfer worth it
Sending a small amount first and confirming arrival before sending the rest costs one extra fee and buys certainty.
The test is simple: if that extra fee is smaller than a loss you could not absorb, it is worth paying. That is especially true for larger amounts, first-time addresses, or a platform you have not used before.
One exception: if the merchant's order requires a single exact payment, a test transfer will not work. Check carefully and send once instead.
If you have already sent to the wrong place
First establish where it went. If it reached the recipient platform's address on a different network, some platforms offer a paid recovery service, though without guarantees and often with a minimum amount. If it reached an address nobody controls, recovery is generally impossible.
Either way, contact the receiving platform's official support immediately with the transaction hash, network name, amount and time. Do not trust anyone offering to "recover" funds for a fee — in this scenario those offers are almost always a second fraud.
Frequently asked questions
The two platforms name networks differently. How do I map them?
Go by the full name each page uses and do not infer from abbreviations. If the sending side has no option that clearly corresponds, treat the route as unconfirmed and ask the platform rather than choosing something similar.
Should I pick the cheapest network or the one they specify?
The one they specify. The fee difference is almost always far smaller than the loss from sending on the wrong network. Compare costs only among the options the order page itself offers.
How long does a transfer take?
It depends on network conditions and how many confirmations the recipient requires, so there is no fixed figure. The recipient normally states the confirmations needed. Until they mark it received, treat the transfer as incomplete.
I sent it but their page shows nothing received.
Use the transaction hash on that network's block explorer to confirm the status and the actual receiving address. If the chain shows success but they have not credited it, contact their support with the hash. If the chain shows no success, the problem is on the sending side.
Sources
Public sources used for this guide. Sources checked on 2026-09-08. We have not tested this with a real purchase.
- Tether: supported protocolsReviewed 2026-09-08
- Bitrefill: supported payment assets and networksReviewed 2026-09-08