USDT (Tether) is issued on several blockchains. The token is worth the same everywhere — one USDT is one USDT — but the network it travels on changes the address format, the transfer fee, how fast it settles, and how a payment gateway verifies it. Q8QPay supports three: Tron (TRC20), Ethereum (ERC20), and BNB Smart Chain (BSC).
The quick comparison
| Network | Chain | Address format | Decimals | Confirmations |
|---|---|---|---|---|
| TRC20 | Tron | Starts with "T", 34 characters | 6 | 20 |
| ERC20 | Ethereum | Starts with "0x", 42 characters | 6 | 12 |
| BSC | BNB Smart Chain | Starts with "0x", 42 characters | 18 | 15 |
USDT-TRC20 (Tron)
TRC20 is the most popular network for USDT transfers, largely because Tron's transaction fees are very low and settlement is fast. For everyday commerce — where customers pay small-to-medium amounts and expect a quick confirmation — TRC20 is usually the path of least friction. Q8QPay waits for 20 confirmations before treating a TRC20 payment as final.
USDT-ERC20 (Ethereum)
ERC20 runs on Ethereum, the most widely integrated chain in crypto. It has the deepest tooling and exchange support, which matters if your customers hold USDT on Ethereum and would rather not bridge it elsewhere. The trade-off is gas: Ethereum network fees are the highest of the three and can spike during congestion, so ERC20 tends to suit larger payments where a few dollars of gas is negligible. Q8QPay confirms ERC20 payments after 12 blocks.
USDT-BSC (BNB Smart Chain)
BSC offers low fees similar to Tron with EVM compatibility similar to Ethereum, making it a popular middle ground. One important technical detail: USDT on BSC uses 18 decimals, whereas TRC20 and ERC20 use 6. A payment gateway has to account for that difference when it parses on-chain amounts, or matching breaks. Q8QPay handles the decimal conversion per network and waits for 15 confirmations on BSC.
Which should you accept?
For most merchants, the answer is "more than one." Offering TRC20 and at least one EVM network (ERC20 or BSC) lets customers pay from whichever chain their USDT already lives on, which reduces abandoned checkouts. Whatever you enable, the verification rules are identical across networks in Q8QPay: a payment must match the invoice's network, address, and exact amount before it confirms.
How Q8QPay treats all three the same
Regardless of network, Q8QPay applies the same exact-match policy: the payment's network must equal the invoice's asset code, the destination must equal your payout address, and the amount must match to four decimal places within the invoice's expiry window. The chain underneath changes; the guarantee to you does not.