USDT TRC20 vs ERC20 vs BEP20: A Merchant's Guide
Which USDT network should you accept? A merchant's comparison of TRC20, ERC20 and BEP20, covering address formats, fees, finality and the wrong-network trap.
A customer clicks "Pay with USDT", opens their wallet, and gets asked a question they didn't expect: which network? For a merchant, TRC20 vs ERC20 vs BEP20 isn't trivia. It decides what the payment costs the customer, how long you wait before shipping, and whether the money shows up at all.
Here's how the three USDT networks actually differ, seen from the receiving side of the counter, and which USDT network makes sense to accept first.
What a "network" means for USDT
USDT isn't one token. It's the same dollar-pegged asset issued as separate tokens on separate blockchains, and each version lives in its own world. USDT on TRON can't see USDT on Ethereum, and a transfer on one chain never shows up on another.
The labels people use are shorthand for the token standard on each chain:
- TRC20: USDT on TRON
- ERC20: USDT on Ethereum
- BEP20: USDT on BNB Smart Chain (usually just "BSC")
Each of these is a smart contract with its own address. Wallets and payment systems recognise real USDT by that contract address, not by the name, because anyone can deploy a token called "USDT". A well-built payment system checks the contract on every incoming transfer and ignores look-alikes.
Worth knowing: Tether's list of supported protocols includes Ethereum and TRON, but doesn't list a USD₮ contract on BNB Smart Chain. The USDT you see on BSC is a Binance-pegged token. Exchanges generally treat it as USDT, so day to day it rarely matters. If you ever want to redeem directly with the issuer, it does.
TRC20 vs ERC20 vs BEP20 at a glance
| TRC20 (TRON) | ERC20 (Ethereum) | BEP20 (BNB Chain) | |
|---|---|---|---|
| Address format | T + 33 characters |
0x + 40 hex characters |
0x + 40 hex characters (same as Ethereum) |
| Fee paid in | TRX, or staked energy/bandwidth | ETH (gas) | BNB (gas) |
| Fee behaviour | Depends on the sender's resources | Moves with network demand, often the priciest of the three | Usually low |
| Block time | About 3 seconds | 12-second slots | Under a second |
| Practical finality | About a minute | About 15 minutes | A few blocks, around a second |
| USDT contract | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t |
0xdAC17F958D2ee523a2206206994597C13D831ec7 |
0x55d398326f99059fF775485246999027B3197955 |
| Token decimals | 6 | 6 | 18 |
| Issued by | Tether | Tether | Binance (pegged) |
Address formats: T... versus 0x...
TRON addresses start with a capital T and are 34 characters long. Ethereum and BNB Chain addresses both start with 0x followed by 40 hex characters.
For a merchant, this is the difference that matters most.
Because TRON and EVM addresses look nothing alike, most wallets and exchanges refuse to send ERC20 USDT to a T... address. The format check catches the mistake before any money moves.
Ethereum and BNB Chain share one address format, so no check can tell them apart. An 0x address is valid on both. If a customer picks BEP20 when you expected ERC20, the wallet happily sends it, the transfer succeeds on BNB Chain, and a system that only watches Ethereum never sees it.
If you collect refund or payout addresses from customers, a quick format check is worth having:
const ADDRESS_FORMATS = {
TRC20: /^T[1-9A-HJ-NP-Za-km-z]{33}$/, // base58, 34 chars total
ERC20: /^0x[0-9a-fA-F]{40}$/,
BEP20: /^0x[0-9a-fA-F]{40}$/, // identical to ERC20
};
function looksValid(network, address) {
const pattern = ADDRESS_FORMATS[network];
return Boolean(pattern && pattern.test(String(address ?? '').trim()));
}
looksValid('TRC20', 'TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t'); // true
looksValid('ERC20', 'TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t'); // false
looksValid('TRC20', undefined); // false, no crash on an empty form fieldTreat this as a sanity check, not proof. TRON addresses carry a base58check checksum and EVM addresses can carry a mixed-case checksum, and a proper library verifies both. And look at the last two patterns again: nothing in an 0x address tells you which chain the customer had in mind.
Fees: who pays, and in what coin
On all three networks the sender pays the network fee on an incoming payment. Your customer covers it, and you receive whatever they sent. The catch is that the fee is paid in the chain's native coin, not in USDT.
- TRON. A USDT transfer is a smart-contract call, so it uses two resources: bandwidth and energy. Bandwidth comes with a small free daily allowance; energy has no free quota. If the sender hasn't staked TRX or had energy delegated to them, TRX is burned from their account to cover the shortfall. We break this down in TRC20 USDT transaction fees explained.
- Ethereum. The sender pays gas in ETH. The price per unit of gas follows demand, so the same transfer can cost very different amounts on a quiet weekend and during a market rush.
- BNB Chain. Same gas model as Ethereum, paid in BNB, and usually far cheaper.
Two things regularly trip customers up. In most wallets, a balance of only USDT, with no TRX, ETH or BNB to cover the fee, can't be sent. A few wallets offer workarounds such as paying the fee in USDT, but you can't assume your customer has one.
The second is exchanges. Customers paying straight from an exchange pay a withdrawal fee the exchange sets, which on many exchanges comes out of the amount they type in. If you match payments by exact amount, a 50 USDT invoice that arrives as 49 won't match.
Your own network costs show up later, when you move funds out. That's when you need TRX, ETH or BNB on your side, or a provider that charges a known payout fee.
Confirmations: when the money is actually yours
A transaction appearing in a block isn't the same as it being final. Each chain gets there differently.
TRON produces a block about every 3 seconds, with 27 Super Representatives taking turns. A block becomes solidified, meaning irreversible, once 19 different SRs (70% of the 27) have produced blocks on top of it. In practice that's roughly a minute.
Ethereum runs on 12-second slots grouped into 32-slot epochs. Per ethereum.org, a block takes about 15 minutes to finalize. Many processors accept a fixed number of blocks earlier than that, which is a risk trade-off rather than a guarantee.
BNB Chain has cut its block time several times. As of late 2026 it runs 0.45-second blocks, following the Fermi hard fork in January 2026, and BNB Chain reports that fast finality normally arrives within a few blocks, around a second.
The rule of thumb for merchants: don't release anything you can't take back until the transfer is confirmed. A download link or a licence key sent on an unconfirmed transaction is a gift if that transaction disappears.
USDT sent to the wrong network: what happens and how to prevent it
When a customer says "I paid but nothing happened", the cause is usually one of three things: wrong network, wrong amount, or paid after the invoice expired. Wrong network is the one that can actually strand money.
What happens depends on the combination:
| Customer sends | To your address on | What happens |
|---|---|---|
| ERC20 or BEP20 | TRON (T...) |
Usually blocked by the wallet's address check |
| TRC20 | Ethereum or BSC (0x...) |
Usually blocked the same way |
| BEP20 | Ethereum (0x...) |
Goes through; funds land at the same address on BNB Chain |
| ERC20 | BNB Chain (0x...) |
Goes through; funds land at the same address on Ethereum |
When funds land on the "other" EVM chain, recovery depends on who holds the private key. If it's a wallet you control with an ordinary key, you can usually reach the funds by adding the other network to that wallet. If it's an exchange deposit address or a provider-managed address, it's up to them, and not every provider can or will recover it.
Ways to prevent it, roughly in order of impact:
- One network per payment, named everywhere. Next to the address, on the QR screen, in the confirmation email. "USDT on TRON (TRC20)" beats a bare "USDT".
- Make the network part of the order, not an afterthought. In TillCrypto the network is baked into the currency you request, for example
"currency": "USDT-TRC20", and the checkout labels the address with it. If the customer sends a different coin on the same chain (say TRX instead of USDT), or the wrong amount, the transfer is recorded as "unmatched" for manual review instead of vanishing. A transfer on a different chain is never seen, which is why the network label matters so much. - If you run your own wallets and accept both ERC20 and BEP20, watch every address on both chains. A BEP20 payment sitting in an address you only monitor on Ethereum is invisible, even though you hold the key.
- Give support a script. Ask for the transaction hash first. A block explorer tells you the chain, token and amount in seconds. For the rest of the messy cases, see crypto payment edge cases.
Which USDT network should a merchant accept?
For most merchants, start with TRC20.
- TRC20 is widely held by people who use USDT to move money rather than to trade. Costs are predictable once you understand energy, and finality takes about a minute. For most small merchants, it's the place to start.
- ERC20 has the broadest support across wallets, exchanges and DeFi, but fees swing with congestion and full finality is slow. It makes sense when your customers are Ethereum-native or pay larger amounts where the fee matters less.
- BEP20 is cheap, fast and popular with Binance users. Keep in mind that it's a Binance-pegged token, and that it shares the
0xformat with Ethereum, so wrong-network mistakes happen silently.
Start with one network, get your checkout and support process clean, then add networks when customers actually ask. That's the order TillCrypto is following too: USDT on TRC20 (plus TRX) is live now, and USDT and USDC on ERC20 and BEP20 are coming soon. If you're setting this up from scratch, how to accept USDT payments on your website walks through the whole flow.
Sources and further reading
- Tether: Supported Protocols
- TRON Developer Hub: Resource Model (Bandwidth and Energy)
- TRON Developer Hub: Super Representatives
- TRON Protocol Docs: DPoS Consensus
- ethereum.org: Proof-of-Stake
- ethereum.org: Single Slot Finality
- ethereum.org: Gas and Fees
- BNB Chain: Fermi Hard Fork Accelerates BSC to 0.45-Second Block Times
- BNB Chain Docs: BNB Smart Chain Introduction