Accept USDC payments on BNB Chain (BEP-20)

GramPayBot supports Binance-Peg USDC on BNB Smart Chain mainnet. The buyer sends the supported BEP-20 representation to the merchant’s configured EVM address, while GramPayBot monitors the transfer without taking custody.

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

Which wallet address should the merchant add?

Add a public 0x... address you control and have tested on BNB Smart Chain. An Ethereum-compatible wallet may show the same address on several networks, but BSC, Ethereum and Base have separate balances and contracts.

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

This USDC is not issued natively by Circle

The supported BSC contract is 0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d with 18 decimals. It is a Binance-Peg representation, not Circle-native USDC. Circle’s native USDC catalog does not define this BSC token as issuer-native.

The official BNB Chain MPP registry distinguishes it as BINANCE_PEG_USDC. Open the exact contract in BscScan, compare every character and use the token verification checklist. The USDC name and logo do not change its provenance.

What the buyer must select

The buyer selects BNB Smart Chain, BSC or BEP20 for USDC. Ethereum/ERC20, Base, Solana and the retired Beacon Chain/BEP2 route are different. If an exchange lists only “USDC” without a network, open the network selector and verify BSC explicitly.

A self-custody sender needs BNB for gas. Network fees vary, while an exchange can charge a separate withdrawal fee or impose a minimum.

How GramPayBot confirms the payment

The product route is network enum bsc plus token USDC. GramPayBot matches the exact 18-decimal contract, configured recipient and invoice amount on BNB Smart Chain. BNB, another BEP-20 token or native USDC on another network does not qualify.

Open the transaction hash in BscScan and check successful status, chain, contract, recipient and token-transfer amount. A submitted exchange withdrawal or a screenshot is not final evidence.

Wrong representation and recovery risk

Do not treat Binance-Peg USDC as interchangeable with Circle-native USDC. A bridge, exchange or wallet may use different asset labels and redemption rules. Test a low-value invoice and confirm that the merchant can use or withdraw the received representation.

For native Circle USDC, use USDC on Base or USDC on Ethereum. For Binance-Peg Tether, see USDT on BNB Chain. Every pair is listed in the route hub.