TRON / TRC20
USDT is supported on this route. Transfers of the same-named token on another network cannot match.
Product comparison
TRC20, ERC20 or BEP20?
Start with where customers hold their assets and which networks their wallets or exchanges support. The order API is shared; networks, token versions and confirmation rules remain distinct.
Three networks, key differences
| Network | Configured assets | Integration focus |
|---|---|---|
| TRON / TRC20 | USDT | Identify TRON; USDC and TRX are not accepted |
| Ethereum / ERC20 | USDT / native USDC | A 0x address does not identify the network; check contracts |
| BNB Smart Chain / BEP20 | USDT / Binance-Peg USDC | Check token versions, contracts and decimals |
Steps to follow
Choose a network customers can use
This comparison focuses on three networks without assuming one is always cheapest or fastest. Polygon, Solana and Base are additional available choices.
01 Identify the network of the customer’s assets, not just the symbol.
02 Check wallet or exchange networks, transfer restrictions and current costs.
03 Enable the route and wallet; make the order network explicit.
04 Apply network-specific confirmation rules, then use one verified callback flow.
BoltUtil checks payments and sends signed callbacks. Your server verifies signatures and order status, deduplicates events, then delivers goods, activates service or credits accounts.
Integration notes
What matters before production
Ethereum / ERC20
Configured USDT and native USDC are supported. Select Ethereum; a 0x address does not identify the network.
BNB Smart Chain / BEP20
Configured USDT / USDC versions are supported. USDC is Binance-Peg; check its contract and decimals.
network: "TRC20" currency: "USDT"
network: "ERC20" currency: "USDT" or "USDC"
network: "BEP20" currency: "USDT" or "USDC"
Select one enabled token / network pair for each order.
The same address format does not imply the same network.Flow and parameter illustration only. No requests are sent. Use enabled networks, assets and wallets as documented.
Read API docsProduct comparison
Questions merchants ask before going live
Which network is always cheapest or fastest?
There is no fixed answer. Costs, wallet or exchange restrictions and network conditions vary. Offer usable, correctly configured options for your customers.
Does BoltUtil hold the payment?
No. Customers transfer directly to your configured wallet. BoltUtil checks orders and payments without custody or access to private keys, seed phrases or withdrawal authority.
Do all networks support USDT and USDC?
TRON supports USDT only. Other networks support the configured USDT / USDC versions. Availability depends on enabled channels and merchant wallets; use the API and checkout response as the source of truth.
Can I fulfill when a customer returns?
returnUrl is navigation, not payment evidence. Use a verified callback or trusted server-side status query, check the order and fulfill once.
How are payment differences handled?
Free merchants can view their own review records. Qualifying manual-transfer differences can create review records; verify ownership when several orders are candidates. Active membership is required to accept or reject an association. Acceptance confirms payment and triggers the configured callback.
Can customers connect a wallet without entering the amount?
Yes. Wallet checkout prepares the recipient, token and complete payable amount on supported networks and devices. Customers review and confirm in their wallet. First use may require unlocking, connection approval or a network switch. QR codes and copied addresses remain available for manual transfer; both methods require on-chain confirmation.
Launch a cleaner USDT / USDC payment flow
Create orders, monitor transfers, and notify your backend without asking customers to send screenshots.