Tether (USDT) in an Exchange — Networks, Fees, and the Wrong-Network Risk
Tether is one, but its networks are not. TRC20, ERC20, and BEP20 differ in fee and speed, and sending on the wrong network means the money is gone. A practical guide to working with USDT in an exchange and proving every transfer with a transaction hash.
Tether (USDT) is no longer a fringe currency; for many exchanges it has become the main tool for moving value. But one common misconception costs someone money every day: they imagine "Tether is Tether" and that the network it travels on makes no difference. It does — and that difference sometimes costs the entire amount.
This article is about exactly what's hidden behind a USDT address: the network. How the networks differ, why sending on the wrong network destroys the money, and how to record every transfer so it can later be proven and reconciled.
One token, several networks
Tether is not an independent "currency" with its own dedicated blockchain. Tether is a token issued on other blockchains. That same one-dollar Tether can live on different networks, and each version has its own rules, fees, and speed.
Three common networks where the most Tether volume moves:
- TRC20 (on Tron): the most used network for Tether in the Iranian and regional market. Very low fee, fast confirmation.
- ERC20 (on Ethereum): the oldest and most "official" rail, but the network fee (gas) is often expensive and variable.
- BEP20 (on Binance Smart Chain): low fee, good speed, but tied to the Binance ecosystem.
Key point: addresses are not interchangeable between networks in the way you think. An ERC20 address and a BEP20 address may look identical (both start with 0x), but a Tron address is completely different (it starts with T). This surface resemblance is itself a source of error.
Network comparison table
| Feature | TRC20 (Tron) | ERC20 (Ethereum) | BEP20 (BSC) |
|---|---|---|---|
| Address format | Starts with T |
Starts with 0x |
Starts with 0x |
| Network fee | Very low | High and variable | Low |
| Confirmation speed | Fast (seconds) | Medium | Fast |
| Sender prerequisite | Tron energy/bandwidth | Ether (ETH) for gas | BNB for gas |
| Common regional use | Very high | Medium | Medium |
Note that each network requires a different "fuel." On Ethereum you need Ether, on BSC you need BNB, and on Tron you need resources called energy and bandwidth. That energy topic is its own discussion, which we cover in detail in the Tron energy rental guide; because mismanaging it multiplies the fee of every TRC20 transfer.
The fatal error: sending on the wrong network
Here is the most important part of the article. Imagine a customer gets an address from you to send Tether. You give a TRC20 address, but the customer sends the Tether from their wallet on the ERC20 network. What happens?
At best, the money gets stuck somewhere hard or expensive to access. At worst — and this case is more common — the money is lost forever. The network whose destination is your address does not recognize an address from another network; or you don't hold that address's private key.
Sending Tether on the wrong network is like pouring money into an account no one holds the key to. The transaction is recorded as "successful," but the money is effectively gone.
A few simple rules that catch this disaster:
- Always state the network next to the address. Don't write "your Tether address"; write "your Tether address on the TRC20 network."
- Check the address format. If it's supposed to be TRC20 but the address starts with
0x, something is wrong. - Before releasing the currency, wait for confirmation on that same network. The customer saying "I sent it" is not enough; the transaction must have settled on the correct network.
Transaction hash: the undeniable proof of every transfer
Every transfer on a blockchain has a unique identifier called a transaction hash or TxID. This string permanently and publicly records the sender address, recipient address, amount, token, and network. Unlike a bank receipt, which can be forged, a transaction hash cannot be forged — it is either on the blockchain or it isn't.
For an exchange, this means every crypto transfer must be recorded with its transaction hash. Why?
- Reconciliation: when the wallet balance doesn't match the ledger, transaction hashes are the only way to trace which transfer went unrecorded or was recorded twice.
- Proof in disputes: if a customer says "I sent it but you didn't pay" or the reverse, the transaction hash moves the judgment from words to a document.
- Audit and transparency: any crypto record without a hash is effectively an unbacked claim.
A numerical example
Suppose a customer claims to have sent 5,000 Tether on TRC20. You take the transaction hash and check it on the Tron explorer. Three things must read:
- Amount: exactly 5,000 USDT (not 4,950, not 5,000 on a different token).
- Token: USDT, not a similar token with a misleading name.
- Destination address: exactly your wallet address, not one that differs by a single character.
If all three read, the money has arrived. If one doesn't, don't hand over anything yet.
Nexto: recording a crypto transaction from the TxID
Typing this information manually is both tedious and error-prone — a single wrong digit in the address or amount invalidates the whole entry. In Nexto exchange accounting software, instead of manual typing, you just enter the link or transaction hash; the system reads the amount, token, and wallet addresses directly from the blockchain itself and performs the lookup across all three networks TRC20, ERC20, and BEP20.
This means:
- The network is detected from the transaction's real data, not guessed.
- The recorded amount is the exact amount that actually settled on-chain, not something someone typed.
- The crypto accounting voucher is built automatically and the transaction hash stays in it as a reference — so later reconciliation is certain.
The goal is simple: no crypto transfer enters the ledger without a blockchain document, and no operator has to eyeball-match a 34-character address.
Conclusion
Tether is one, but its networks are three (and more), and this difference is real, not technical fussiness. TRC20, ERC20, and BEP20 differ in fee, speed, and address format; and sending on the wrong network takes the money away not late, but forever. The only safe way is to explicitly state the network, check the address format, and wait for confirmation on the correct network. And so that every transfer stays provable later, record the transaction hash — this document, unlike a receipt, cannot be forged. If you also deal with other kinds of value transfer, an overview of remittance types gives a fuller picture.
Want to see how automatic recording of a crypto transaction from a hash, across all three networks, works in practice? Build a dedicated demo and follow a Tether transfer from hash to voucher.
See all of this inside Nexto
A complete, private instance with sample data — no install, no credit card.