One of the first confusing things merchants discover about stablecoin payments is that USDT does not live on only one blockchain. A customer may say, “I want to pay in USDT,” and then immediately ask whether the merchant accepts ERC20, TRC20 or BEP20. To someone who does not spend much time in crypto, that sounds like three versions of the same thing.
In practical terms, that is close to what the customer sees: the asset is still called USDT and is intended to track the U.S. dollar. But the payment can travel over different blockchain networks, and each network has its own transaction system, fees, confirmation process, wallet support and token contract.
That is why a merchant should never think only in terms of “accepting USDT.” A real checkout also needs to answer a second question: USDT on which network?
The token name tells you what the customer is paying with. The network tells you where the payment is actually happening.
USDT is a token, not a blockchain
The easiest way to understand this is to separate the asset from the network. USDT is a stablecoin token. Ethereum, TRON and BNB Smart Chain are blockchain networks that can carry tokens and record transactions.
Tether has issued USD₮ on multiple blockchain protocols over time. Ethereum and TRON are two major examples. Other ecosystems may also make USDT available through native issuance, bridges or pegged representations. The important point for a merchant is that the same familiar ticker can exist in different technical environments.
A useful comparison is email. The message may contain the same words, but it still needs a delivery system and a valid destination. With crypto, the asset is the value being moved; the blockchain is the system recording that movement.
Asset: USDT.
Network: Ethereum, TRON, BNB Smart Chain or another supported chain.
A merchant checkout needs both pieces to identify the payment correctly.
What ERC20, TRC20 and BEP20 actually mean
These labels refer to token standards or network conventions. They help wallets, exchanges and applications understand how tokens behave on a particular blockchain.
ERC20 — Ethereum
ERC-20 is Ethereum's widely used standard for fungible tokens. It defines common functions for transferring tokens, checking balances and interacting with wallets and applications. USDT on Ethereum is commonly described as USDT ERC20.
TRC20 — TRON
TRC20 is the token standard used on the TRON network. When a wallet or exchange offers a TRC20 USDT withdrawal, the transfer is being sent through TRON and must be received in a compatible TRON address and payment flow.
BEP20 — BNB Smart Chain
BEP-20 is the fungible-token standard on BNB Smart Chain and was designed with an interface similar to Ethereum's ERC-20. USDT used on BNB Smart Chain is commonly referred to by users and exchanges as BEP20 USDT.
There is an extra detail that matters for technically careful merchants: not every token with the same ticker on every chain has the same issuance path. On BNB Smart Chain, for example, USDT used by many wallets and exchanges may be represented as a pegged token rather than the same native contract used on Ethereum. That is one reason payment systems should verify the exact network and token contract they support instead of trusting a ticker symbol alone.
Why would USDT be offered on more than one network?
Different users live in different crypto ecosystems. One customer may keep assets on Ethereum. Another may use TRON because their exchange or wallet makes TRC20 transfers convenient. Another may already use BNB Smart Chain for trading, apps or lower-value transfers.
Supporting multiple networks allows the same stablecoin concept to reach users who have different wallets, exchanges and transaction preferences. It also means the customer may encounter different network fees and confirmation experiences even though the amount is still displayed in USDT.
For merchants, this is less about deciding that one blockchain is universally “best” and more about understanding where customers already hold and move USDT. A network that is inexpensive for one customer may be inconvenient for another if their funds are somewhere else.
Why the network cannot be treated as a small technical detail
A payment request is not complete if it only says “Send 100 USDT.” The customer also needs to know which network to use. That network determines what address format is expected, which blockchain the payment system will monitor and which transaction can be matched to the order.
If a checkout expects a BEP20 payment but the customer sends over TRON, the payment will not appear on BNB Smart Chain. If the system is monitoring Ethereum and the customer sends on another network, an Ethereum scanner cannot confirm a transaction that never happened on Ethereum.
Some wallets use similar-looking address formats across EVM-compatible chains, which can make the situation even more confusing. A familiar-looking address does not mean the customer can ignore the network. The merchant's supported chain, token contract and receiving setup still have to match the actual transfer.
1. Token: USDT.
2. Network: for example BNB Smart Chain (BEP20).
3. Receiving address: the address configured for that payment flow.
4. Exact payment amount: the amount the payment system expects to verify.
The network also changes what the customer pays in gas
USDT may be denominated in dollars, but the blockchain's transaction fee is usually paid with that network's native asset. On Ethereum, a token transfer consumes ETH for gas. On BNB Smart Chain, the user generally needs BNB. On TRON, the network has its own resource and fee model.
This matters at checkout because a customer can own enough USDT to pay the merchant and still be unable to send it if the wallet does not have what the network requires for the transaction fee.
A good merchant payment page therefore should not hide the network. Clear labeling reduces the chance that a customer reaches the final step and discovers they cannot complete the transfer from the wallet they intended to use.
Why multiple networks make merchant payment software more useful
If a merchant only publishes a wallet address, the customer and merchant are left to manage most of this context themselves. The merchant may have to ask which network was used, search for the transaction and work out which order the payment belongs to.
A USDT payment gateway can make the process more structured. It can create a payment request for a specific network, show the customer the right receiving information, monitor the relevant blockchain and connect the confirmed transfer to the merchant's order.
This is one reason network support is a real product decision rather than a logo list. Every additional chain needs reliable monitoring, confirmation rules, token configuration, payment matching and operational health checks. Adding a network only matters if the payment can be verified dependably after the customer sends it.
What this means for USDTonPay
USDTonPay is built around a simple merchant idea: the customer pays USDT directly to the wallet configured by the merchant, while the system handles payment creation, blockchain verification, order matching and status records.
Today, that means the payment system has to know much more than the word “USDT.” It needs to know the supported network, the token being monitored, the receiving wallet, the amount expected and the blockchain transaction that proves the payment happened.
USDTonPay currently supports USDT payments on BNB Smart Chain (BEP20), and we plan to expand network support based on merchant demand. TRC20, TON and ERC20 are part of that roadmap. The goal is not to support the largest possible number of chains on paper. It is to add the networks merchants and their customers actually need, and then verify payments on those networks reliably.
The merchant experience should remain the same even as more networks are added: choose a supported network, create the payment, let the customer send USDT directly to the merchant wallet, and let the payment system identify and confirm the correct transaction.
The simplest rule for merchants
If there is one thing to remember, it is this: USDT is not enough information by itself. Every crypto payment also has a network.
ERC20, TRC20 and BEP20 are not three different dollar prices. They describe different technical routes for moving tokens. The customer may think mainly about convenience and fees; the merchant has to think about correct receiving information, reliable verification and order matching.
Once that distinction is clear, multi-network USDT payments become much easier to understand. The stablecoin can stay familiar while the payment infrastructure handles the complexity underneath.
