USDT exists on several blockchains, and a business that accepts it has to decide which networks to support. For CryptoLike, USDT on TRON (TRC20) and USDT on Ethereum (ERC20) are two separate assets: each has its own address format, its own network fee paid by the sender and its own confirmation threshold. This article compares them for accepting payments and shows how to accept USDT on TRON, accept USDT on Ethereum, or both, with one integration.
What is the difference between USDT TRC20 and USDT ERC20?
USDT TRC20 and USDT ERC20 are the same stablecoin issued on two different blockchains: TRC20 is the token standard of the TRON network, ERC20 the token standard of Ethereum. CryptoLike treats them as two assets, each with its own deposit address, confirmation threshold, balance and line in the fee schedule. A token sent on one network never appears on the other.
The difference matters in three places: what the payer needs to send the transfer, how the network confirms it, and what happens on the wrong network. The checkout page, statuses and webhooks work the same way for both.
USDT TRC20 vs ERC20 at a glance
CryptoLike accepts USDT on TRON (API network tron, shown to the payer as "TRON (TRC20)") and on Ethereum (API network eth, shown as "Ethereum (ERC20)"). The comparison covers the network facts that affect a payment. Confirmation thresholds are set per asset and published in GET /v1/currencies and on the coins page, so the table points there instead of repeating numbers.
| Aspect | USDT on TRON (TRC20) | USDT on Ethereum (ERC20) |
|---|---|---|
| Token standard | TRC20 | ERC20 |
| Address format | Base58Check, 34 characters, starts with T |
0x followed by 40 hexadecimal characters |
| Network fee of a transfer | Paid by the sender in TRX: the transfer consumes bandwidth and energy; what staked resources do not cover is paid by burning TRX | Paid by the sender in ETH, as gas |
| Block interval | One block every 3 s | One slot every 12 s |
| When a block becomes irreversible | "Solidified" once enough super representatives have built on it, typically in about 1 minute | "Finalized" by validator votes on checkpoints; an epoch is 32 slots, about 6.4 min |
| Confirmation threshold in CryptoLike | Set per asset: GET /v1/currencies and the coins catalogue |
Set per asset: GET /v1/currencies and the coins catalogue |
| Transfer on the wrong network | Not detected and not credited; the checkout page warns before the payer sends | Not detected and not credited; the checkout page warns before the payer sends |
Checked on 2026-09-24 against the TRON and Ethereum developer documentation (listed in Sources) and the CryptoLike checkout contract.
Who pays the network fee, and in which coin?
On an incoming payment the payer pays the network fee of their own transfer, and not in USDT: on TRON it is paid in TRX, on Ethereum in ETH. The USDT amount shown on the CryptoLike checkout page arrives in full, while the network fee comes out of the payer's TRX or ETH balance. A wallet that holds only USDT cannot send the transfer.
A common reason a first USDT payment stalls: the customer has USDT but no TRX or ETH. The fee depends on network load and, on TRON, on whether the sender has staked TRX for energy; CryptoLike does not set it.
Two other charges are separate from the payer's network fee:
- Platform fee. CryptoLike charges it per asset, only when a payment is confirmed and credited. You choose who bears it: you (the default) or the payer, in which case it is included in the amount the payer is asked to send. The current schedule is on the pricing page, with an "as of" date.
- Network fee on payouts. When you send USDT out, the payout estimate shows the platform fee, the reserved network fee and the total debit before you confirm. For a token payout the network fee is reserved and charged in the payout asset, so your balance does not need TRX or ETH.
How are confirmations counted on TRON and Ethereum?
A confirmation is a block added to the chain on top of the block that contains the transfer. CryptoLike counts confirmations on the transfer's own network and credits a USDT payment once the asset's threshold is reached. The threshold is set per asset, published in GET /v1/currencies and on the coins page, and shown to the payer as "n of N confirmations".
The two networks produce blocks at different rates — TRON every 3 s, Ethereum every 12 s — and make blocks irreversible in different ways, so the same number of blocks means something different on each. That is why the threshold belongs to the asset, not to "USDT" in general. The article on how many confirmations a crypto payment needs explains how thresholds relate to block reorganisations; the glossary entry on confirmations gives the short definition.
Meanwhile the payment is pending ("Payment detected. Waiting for confirmation."); at the threshold it becomes paid, the funds are credited to your balance and a signed webhook reports it.
What happens if the payer uses the wrong network?
A transfer sent on the wrong network never reaches the CryptoLike payment. The payment watches one asset on one network, so USDT sent on another chain is not detected, not credited and cannot be recovered through the payment. The checkout page shows a network warning next to the address from the moment the asset is chosen, before the payer sends anything.
On a TRC20 payment the warning reads: "Send only USDT on the TRON (TRC20) network to this address. Funds sent on another network cannot be recovered." The address format helps too: a TRON address starts with T, an Ethereum address with 0x, and a wallet normally refuses an address of the wrong format. The case the format does not catch is an 0x address used on another network that shares Ethereum's address format; CryptoLike accepts USDT only on TRON and Ethereum.
Recovery steps:
- Payer, payment still open: send the amount again on the network named on the page, before the timer runs out.
- Payer, payment expired: ask the merchant for a new payment.
- Merchant: the payment stays
newand expires atttl_expires_at; nothing reaches your balance. Tell the customer which network the page named and create a new payment.
Which network should a business accept?
CryptoLike lets a business accept both networks at once: create a payment in USDT without fixing the network, and the payer chooses TRON (TRC20) or Ethereum (ERC20) on the checkout page. Fix one network only when there is a reason — for example, your customers hold USDT on one of them, or your finance team reconciles and pays out on one network only.
Points to weigh:
- Where your customers hold USDT. Payers send from the network their wallet or exchange uses.
- The payer's network fee. TRX on TRON, ETH on Ethereum; for a small order the payer may prefer the network where the fee is smaller relative to the amount.
- Time to credit. Block interval and threshold decide how long
pendinglasts; compare the assets in the coins catalogue. - Your payouts. Balances are kept per asset; receiving on the network you pay out on keeps the money where you spend it.
How to accept USDT on both networks with CryptoLike
CryptoLike creates one payment in USDT and lets the payer pick the network: send "currency": "USDT" without coin_id, and the checkout page offers the USDT assets you offer for invoices (Coins → For invoices in the cabinet). Both options carry the USDT icon with a small TRON or Ethereum badge and the network name, so the payer can match it to the network in their wallet. To fix one network, pass the coin_id of that asset from GET /v1/currencies; the response then already carries the address and the exact amount.
{
"amount": "25.00",
"currency": "USDT",
"order_id": "A-1002",
"return_url": "https://shop.example/thanks"
}With "currency": "USD" the payer chooses the asset and network on the page, and the rate is locked at that moment for the payment's lifetime. The WooCommerce plugin, the other CMS plugins and payment links use the same checkout page. The step-by-step setup is in the guide on how to accept USDT TRC20 payments. Choosing between USDT and USDC is covered in USDT or USDC for business payments.
Sources
Public network facts in this article were checked on 2026-09-24:
- TRON accounts and address format
- TRON resource model: bandwidth and energy
- TRON consensus: block interval and solidified blocks
- Ethereum accounts and address format
- Ethereum blocks and slot time
- Ethereum gas, paid in ETH
- Ethereum proof-of-stake and finality
FAQ
Is USDT TRC20 the same as USDT ERC20?
It is the same stablecoin on two networks, and the tokens do not move between them by themselves. CryptoLike lists them as two assets with separate addresses, confirmation thresholds and balances.
Can I send USDT TRC20 to an ERC20 address?
No. A TRC20 transfer goes to a TRON address, and an ERC20 transfer to an Ethereum address. On a CryptoLike payment, send only on the network named on the checkout page: funds sent on another network cannot be recovered.
Why does the payer need TRX to send USDT on TRON?
A TRC20 transfer is a smart-contract call: it consumes bandwidth and energy, and what staked TRX does not cover is paid by burning TRX. On Ethereum, ETH pays for gas in the same way.
Which network credits a payment sooner?
TRON produces a block every 3 s and Ethereum every 12 s, but the time to credit also depends on the confirmation threshold of each asset. CryptoLike publishes the threshold in GET /v1/currencies and in the coins catalogue, and the checkout page shows the progress as "n of N confirmations".
Can one payment accept both networks?
Yes. Create the payment in USDT, or in a fiat currency, without coin_id: the payer chooses the asset on the checkout page, and from that moment the payment is bound to that network, its address and its amount.