Accept USDT payments on BNB Chain (BEP-20)

GramPayBot supports the Binance-Peg USDT representation on BNB Smart Chain mainnet. The customer sends the supported BEP-20 token to the merchant’s configured EVM address, and GramPayBot monitors the transfer without taking custody of the funds.

• Network:
  BNB Smart Chain mainnet
• Chain ID:
  56
• Token standard:
  BEP-20
• Receiving address:
  0x + 40 hexadecimal characters
• Network fee asset:
  BNB
• USDT contract:
  0x55d398326f99059ff775485246999027b3197955
• Decimals:
  18
• Representation:
  Binance-Peg, not issuer-native

Which wallet address should the merchant add?

Add a public 0x... address you control and have tested on BNB Smart Chain. BSC is EVM-compatible, so an Ethereum wallet may display the same address, but Ethereum and BSC balances and token contracts are separate.

Use the EVM wallet address guide to check all 42 characters, account control and exchange-deposit restrictions. Never provide a private key or seed phrase.

This route is Binance-Peg USDT

The supported contract is 0x55d398326f99059ff775485246999027b3197955 with 18 decimals. This BSC representation is commonly labelled USDT, USDT BEP20, Binance-Peg BSC-USD or Binance-Peg USDT. It is not Tether’s issuer-native Ethereum or TRON contract.

The BNB Chain official MPP asset registry records this contract as BINANCE_PEG_USDT. Open the exact address in BscScan, compare every character and follow the token verification checklist. Token name, logo and activity are supporting signals, not identity proof.

What the buyer must select

The buyer must select BNB Smart Chain, BSC or BEP20, depending on the wallet or exchange wording. Do not select the retired Beacon Chain/BEP2 route, Ethereum/ERC20, TRON/TRC20 or another network.

A self-custody sender needs BNB for gas. A centralized exchange may charge its own withdrawal fee and impose a minimum. Network costs vary, so do not publish a fixed fee.

How GramPayBot confirms the payment

The product route is network enum bsc plus token USDT. GramPayBot checks the BNB Smart Chain transfer against the supported contract, configured recipient and invoice amount. The 18-decimal contract precision is handled by the route catalog; do not round the invoice manually using Ethereum USDT’s six-decimal assumption.

Open the transaction hash in BscScan and verify successful status, chain, contract, recipient and token-transfer amount. BNB, another BEP-20 token or USDT on another chain does not qualify.

Wrong route and recovery risk

The same 0x... address on Ethereum and BSC does not make wrong-network payments automatically recoverable. Exchange deposit addresses and smart-contract wallets can support only specific networks. Underpayments and transfers after expiry require separate review.

For another EVM route, see USDT on Ethereum or USDC on Base. Every supported pair is listed in the route hub.