15 TOKEN × NETWORK ROUTES
Supported USDT and USDC payment routes
Choose the exact token and blockchain pair before adding a receiving wallet or sending a payment. GramPayBot currently monitors 15 routes across eight networks.
GramPayBot treats each token and network pair as a separate route. “USDT” alone is not enough: USDT on Ethereum and USDT on TRON use different networks, address handling and token contracts. The buyer must send the asset shown by the invoice through that exact network.
Accept USDT on TRON (TRC20) — receiving address, official contract, TRX fees and transaction verification.
Accept USDT on Ethereum or accept USDC on Ethereum — EVM address, exact ERC-20 contract and ETH gas.
Accept USDT on Solana or accept USDC on Solana — wallet versus mint, SPL transfer matching and SOL fees.
Accept USDT on BNB Chain or accept USDC on Base — exact EVM network, representation, contract decimals and gas asset.
Accept USDT on Optimism or accept USDC on Optimism — OP Mainnet labels, bridged versus native assets and ETH gas.
Accept USDC on BNB Chain or accept USDT on Base — non-native provenance, exact contracts and withdrawal-network checks.
Accept USDT on Polygon or accept USDC on Polygon — PoS route, POL gas and native USDC versus bridged USDT.
Accept USDT on Arbitrum or accept USDC on Arbitrum — USDT0 versus native USDC, exact contracts and ETH gas.
Complete supported matrix
The matrix below is written directly in this page. “Fee asset” is the network-native asset normally used by the sender for on-chain execution; a wallet or exchange may apply its own withdrawal fee.
| Token | Network | Standard or representation | Fee asset |
|---|---|---|---|
| USDT | Ethereum | ERC-20, issuer-native | ETH |
| USDC | Ethereum | ERC-20, issuer-native | ETH |
| USDT | Optimism | ERC-20, canonical bridged | ETH |
| USDC | Optimism | ERC-20, issuer-native | ETH |
| USDT | BNB Chain | BEP-20, Binance-Peg | BNB |
| USDC | BNB Chain | BEP-20, Binance-Peg | BNB |
| USDT | Base | ERC-20, canonical bridged | ETH |
| USDC | Base | ERC-20, issuer-native | ETH |
| USDT | Polygon | ERC-20, canonical bridged | POL |
| USDC | Polygon | ERC-20, issuer-native | POL |
| USDT | Arbitrum | ERC-20, USDT0 omnichain | ETH |
| USDC | Arbitrum | ERC-20, issuer-native | ETH |
| USDT | TRON | TRC20, issuer-native | TRX |
| USDT | Solana | SPL token, issuer-native | SOL |
| USDC | Solana | SPL token, issuer-native | SOL |
Choose the receiving address family
- EVM routes: Ethereum, Optimism, BNB Chain, Base, Polygon and Arbitrum normally use a
0xaddress. The same visible address can exist on several EVM networks, but balances and transfers remain network-specific. - TRON: use a merchant-controlled Base58Check address beginning with
T. Read the TRON wallet address guide. - Solana: use the public wallet address required by the payment flow, not the USDT or USDC mint address.
Never paste a token contract or mint into the merchant receiving-wallet field. A contract identifies the asset; a wallet address identifies the recipient.
Verify the token before accepting it
Names, tickers and logos can be copied. Match the full contract or mint against the issuer or the official registry for the exact network. Then inspect the same identifier in the correct explorer. Transfer count and holder count are secondary signals, not proof.
Use the USDT and USDC token verification checklist for all 15 identifiers and explorer links.
Safe first invoice
- Select one token and one network in GramPayBot.
- Add a public receiving address you control for that network.
- Verify the token contract or mint independently.
- Create a low-value test invoice.
- Make the buyer select the same network in their wallet or exchange.
- Confirm the recipient, contract, amount and successful status on-chain.
GramPayBot monitors the payment but does not hold customer funds. A successful transfer goes directly to the configured merchant wallet.