USDT on Tron, Ethereum or BNB Chain: which network should your customers use?

The same dollar token lives on several networks, with different fees, speeds and address formats. Here is how to choose which ones to offer, and how to keep customers from sending on the wrong one.

The Valtu team

2 min read

USDT is not one token but several: Tether issues it on Tron, Ethereum, BNB Chain and other networks, and each version is a separate token that only exists on its own network. For a payments product the question isn't "do we accept USDT?" but "on which networks?"

What changes from one network to the next

  • Who pays fees, and in what. Every transfer pays a network fee in that network's own coin: TRX on Tron, ETH on Ethereum, BNB on BNB Chain. A customer sending USDT needs a little of that coin too, and so do your payout wallets.
  • How much those fees are. Ethereum is usually the most expensive of the three for a token transfer. Tron and BNB Chain are usually much cheaper, which is why they carry a large share of everyday USDT payments. Fees move with network demand, so check current figures rather than relying on a number in a blog post.
  • How fast a deposit is final. Each network has its own finality. Valtu credits a deposit only once it is deep enough on its chain, and on Tron it reads only solidified blocks, so a deposit is final when it is seen. See when is a deposit final.
  • What an address looks like. Tron addresses start with T. Ethereum and BNB Chain share the same 0x… format, and with Valtu one customer has the same EVM address on every EVM network we support. See one address, five networks.

A practical default

Most teams start with the networks their customers already use. If your customers come from exchanges and wallets popular in emerging markets, USDT on Tron is usually expected. If they are DeFi-native or institutional, USDT on Ethereum and USDC on Ethereum matter more. USDT on BNB Chain sits in between and is cheap to move.

Offering more networks costs you little with Valtu: one wallet per customer has an address on every network, and deposits on all of them arrive through the same webhook.

Avoid the wrong-network mistake

Most lost-payment tickets are a customer sending on a network you didn't show them. Three habits prevent most of them:

  1. Name the network next to every address. "USDT on Tron (TRC-20)", not just "USDT".
  2. Show only the networks you support for that coin. The networks and coins page lists what Valtu supports today.
  3. Use payment links when you can. A payment link asks the payer to choose the coin and network first, then shows the matching address.

Valtu only counts the real token contract on each network, so look-alike tokens sent to your customers' addresses are ignored rather than credited.

Keep reading

More from the blog

networks · developers One address, five networks: how EVM deposit addresses work With Valtu, a customer's 0x address is the same on Ethereum, BNB Chain, Polygon, Base and Lisk. Here is why that works, and what it means for deposits sent on any of them.

1 min read

 payments · stablecoins Deposit addresses or payment links: two ways to take stablecoin payments A permanent address per customer suits top-ups and balances. A payment link suits invoices and checkouts. Here is when to use each, and how both work with Valtu.

1 min read

 networks · deposits When is a deposit final? Seeing a transaction isn't the same as being able to rely on it. How Valtu decides a deposit is final on each network, and the one status your ledger should credit on.

2 min read

Start with a test workspace today.

Same dashboard, same API, free test coins. Go live when your team is ready.

Get started Talk to sales