USDT between networks

How to pay someone whose USDT wallet is on a different network

Contents
  1. First, read the address
  2. Why a normal transfer cannot do it
  3. Option 1 — ask for an address on your network
  4. Option 2 — swap across networks, straight to their address
  5. Option 3 — go through an exchange account
  6. Which option fits: side by side
  7. Timing: when the receiver sees the money
  8. What the receiver sees on their side
  9. Getting the amount exact when the rate floats
  10. The mistakes we see most on this kind of payment
  11. When the receiver is an exchange or a service
  12. When the receiver is a person with a 0x address
  13. Checklist before you pay
  14. FAQ

You owe someone 300 USDT. Your USDT sits in a TRON wallet. They send you their address and it starts with 0x. That address is not on TRON, and your wallet will refuse it — or, worse, a different wallet will accept it and send the money somewhere it cannot be collected.

This is the most common way USDT gets stuck, and it has three clean solutions. Which one fits depends on who is receiving.

First, read the address

The first characters tell you the network. This takes ten seconds and prevents most losses.

The address starts withLengthNetworkUSDT there is called
T 34 charactersTRONUSDT TRC-20
0x 42 charactersEthereum orBNB Smart ChainUSDT ERC-20 orUSDT BEP-20
UQ or EQ 48 charactersTONUSDT on TON
anything else, 32–44 letters and digitsvariesusuallySolanaUSDT on Solana

The second row is the trap. Ethereum and BNB Smart Chain share one address format, so the address alone cannot tell you which of the two the receiver means. You have to ask.

Why a normal transfer cannot do it

USDT is not one token that lives everywhere. Each network has its own USDT contract and its own ledger. A transfer is an entry in one ledger, and an address from another network does not exist in it. Nothing in a wallet can "send TRC-20 to a 0x address": the token has to leave one network and be paid out on the other.

Option 1 — ask for an address on your network

It costs nothing and is often possible. Many wallets hold several networks behind one recovery phrase, and most exchanges accept USDT on four or five. Ask: "Can you receive USDT on TRON? Send me that address."

Use this when the receiver is a person with a multi-network wallet, or an exchange account. It does not work when the receiver's system accepts one network only — a payment page, an invoice, a contract.

Option 2 — swap across networks, straight to their address

A cross-network swap takes USDT on your network and pays out USDT on theirs. The payout address does not have to be yours: you can paste the receiver's.

  1. Choose the pair — for example USDT TRC-20 → USDT BEP-20.
  2. Enter the amount and check the "You get" figure: that is what the receiver will see arrive.
  3. Paste the receiver's address in the recipient field. If it belongs to an exchange on TON, add the memo they gave you.
  4. Send the deposit from your wallet to the one-time address shown.
  5. When the status page shows the payout hash, send that hash to the receiver.

Step 5 matters. The payment reaches them from a payout address, not from your wallet, so they cannot recognise it by sender. The transaction hash is the proof that it is yours.

Getting the amount exact. The rate is floating, and the network fee comes out of the payout. If the receiver must get at least 300 USDT, raise the amount you send until "You get" shows a little more than 300, and send promptly: the final figure is set when your deposit confirms.

Option 3 — go through an exchange account

If you already have an exchange account, deposit USDT on your network and withdraw it on theirs. It works, with three costs: the wait for your deposit to be credited, a fixed withdrawal fee, and an account that knows about the payment. For a one-off payment from a wallet, option 2 is fewer steps; for someone who lives on an exchange anyway, this is fine.

Which option fits: side by side

Ask for an address on your networkCross-network swap to their addressThrough an exchange account
Needs from the receiverA second addressNothing — the address they already gaveNothing
Needs from youOne messageOne deposit from your walletAn account, a deposit and a withdrawal
Fee you payYour network's transfer feeThe network fee, taken out of the payoutDeposit wait, then a fixed withdrawal fee
Who knows about the paymentThe two of youThe two of youYou, the receiver and the exchange
Works for a payment page or an invoiceRarelyYesYes
Works for a one-off payment from a cold walletYes, if they can obligeYesOnly if you already have the account

The first option is the cheapest when it is available. The second is the one that always works when the receiver's side is fixed. The third makes sense only if the account already exists and you do not mind the payment being on record there.

Timing: when the receiver sees the money

With a cross-network swap, the receiver's money moves in two steps: your deposit has to confirm on your network, then the payout is sent on theirs. The first step is where the time goes, and it depends on the network you send from.

You send USDT fromConfirmations before the swap startsTypical time to payout
TRON (TRC-20)1≈ 2–5 min
BNB Smart Chain (BEP-20)10≈ 2–5 min
Ethereum (ERC-20)15≈ 4–10 min
TON20≈ 3–7 min

These are the estimates shown on the pair pages; a congested network can be slower. If the receiver is an exchange, add their own crediting time on top — exchanges wait for their own number of confirmations before the balance updates, and that number is theirs, not ours.

If the payment has a deadline — a seller holding goods, an invoice that expires — start early enough that the slowest step still fits, and keep the status page open: it tells you which step you are at without asking anyone.

What the receiver sees on their side

On a block explorer the payout is a normal USDT transfer to their address. The sender shown is a payout address, not your wallet, and that is the point where people get confused on both sides.

  • In a self-custody wallet the balance simply grows by the payout amount. If the wallet is on the right network, there is nothing to do. If the wallet is set to a different network, see the 0x section below.
  • At an exchange the deposit appears in the deposit history once their confirmations are done. The record shows the amount and the hash; the sender address means nothing to them.
  • For a payment page the page checks for an incoming transfer to the address it generated, usually for a set amount. If the payout is a little above what the page asked for, most systems accept it; below, most do not — which is why "You get" has to be at least the figure they asked for.

Send the payout hash as soon as the status page shows it. With the hash, the receiver can look the payment up on the explorer before their own wallet or exchange has caught up.

Getting the amount exact when the rate floats

The rate is floating, and the network fee comes out of the payout. Two things follow for a payment that must land on an exact figure.

First, the "You get" figure is an estimate until your deposit confirms; the final amount is set at that moment. On a fast network the two are close; on a slow one there is more room for the market to move. For USDT to USDT the rate is close to one, so the movement is small, but it is not zero.

Second, the payout follows the amount that actually arrives in the deposit address, not the number you typed. If you send from an exchange that takes a withdrawal fee out of the amount, less arrives, and the payout is smaller. Send from a wallet you control, or add the exchange's withdrawal fee on top of the amount you enter.

So, for a payment that must be at least 300 USDT: raise the amount you send until "You get" shows somewhat more than 300, send promptly, and send the full amount in one transaction. Each pair has a minimum and a maximum; both are shown next to the amount field, and a payment below the minimum will not be accepted.

The mistakes we see most on this kind of payment

  • Your own address in the recipient field. The form does not know whose address it is. If you paste your own, you have moved your USDT between networks and still owe the payment.
  • The receiver's network guessed from a 0x address. Ethereum and BNB Smart Chain look the same. Guessing wrong at a self-custody wallet is recoverable by switching networks; guessing wrong at an exchange may not be.
  • No memo for an exchange on TON. The deposit lands in the exchange's shared address with nothing to say whose it is.
  • Sending from an exchange with the withdrawal fee forgotten. Less arrives than you entered, so less is paid out.
  • Closing the status page. The link is your only record of the swap. Save it before you send.

When the receiver is an exchange or a service

A deposit address at an exchange is not a personal wallet, and three extra rules apply.

  • The network must match the one on their deposit page. If they generated a BEP-20 address and you pay out ERC-20 to it, the format matches and the money may still not be credited.
  • On TON, the memo is part of the address. Exchanges give all customers one TON address and tell them apart by memo. No memo, no credit until their support sorts it out.
  • Check their minimum deposit. A payout below it can be ignored by their system.

When the receiver is a person with a 0x address

A self-custody wallet uses the same 0x address on Ethereum and on BNB Smart Chain. USDT sent on either network arrives at that address — but on that network only. If they are looking at Ethereum and you paid on BNB Smart Chain, their balance shows zero until they switch networks in the wallet. Nothing is lost; tell them which network you used.

They will also need that network's coin to move the USDT on: ETH on Ethereum, BNB on BNB Smart Chain.

Checklist before you pay

FAQ

Can they tell the payment came from me?

Not from the sender address — it arrives from a payout address. Send them the transaction hash from the status page.

The address starts with 0x. Which network do I choose?

Ask. If you cannot ask and it is a personal wallet, either network will arrive at the same address; if it is an exchange, do not guess.

I already sent to the wrong network. Now what?

It depends on who controls the receiving address. That case has its own guide: Sent USDT to the wrong network: what can and can't be recovered.