Skip to main content
Use the Solana network identifiers reference to distinguish the x402 network ID from the RPC genesis hash, or start with the Solana Mainnet Express guide. import DiscordHelpCard from “/snippets/discord-help-card.mdx”;

BNB Smart Chain

BNB Smart Chain (BSC, chain 56) supports x402 v2 exact payments using Permit2. Both supported stablecoins have 18 decimals: Set the token and amount explicitly. For 0.01 USDC, use this payment requirement:
Use a BSC-capable v2 Permit2 client. Before its first payment, the payer must approve the selected token for canonical Permit2 at 0x000000000022D473030F116dDEE9F6B43aC78BA3. That approval requires BNB in the payer’s wallet. After approval, payments require a signature and the facilitator pays settlement gas. Having a merchant API key does not sponsor the initial approval. BSC does not support x402 v1, EIP-3009 transfers, upto, or batch settlement. Do not assume six-decimal USDC amounts, a default dollar-price asset, or Base’s token authorization fields. These Binance-Peg tokens are distinct from native USDC on other networks. Try the live Echo routes for BSC mainnet USDC or BSC testnet USDC. Each charges and refunds 0.01 token. The testnet route uses the 18-decimal community test token 0x64544969ed7EBf5f083679233325356EbE738930 (not Circle-issued USDC) and requires testnet BNB for the initial Permit2 approval. For current availability and fees, check the facilitator’s /supported and /pricing endpoints.

BSC testnet

BSC testnet (eip155:97) is free on both the production and staging facilitators: https://facilitator.payai.network and https://dev-facilitator.payai.network. It supports v2 exact Permit2 payments. Configure a token deployed on chain 97 and its actual decimals; do not reuse the mainnet USDC or USDT addresses. The initial token approval requires testnet BNB (tBNB), which is BNB on BSC testnet. Check your chosen endpoint’s /supported and /pricing before integrating.

Solana batch settlement

Batch settlement is available as a public preview for USDC. The public /supported endpoint advertises the shared-lane fee payer and admission limits. Its /verify and /settle requests work without an API key on the shared lane; credentials remain available for paid usage and assigned enterprise lanes.

Need help?