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 with two transfer methods. The token decides which one applies. All four supported stablecoins have 18 decimals: Set the token and amount explicitly, because BSC has no default dollar-price asset. PayAI pays settlement gas for both methods.

EIP-3009 tokens (USD1, U)

The payer signs a transfer authorization and the facilitator submits it. The payer needs no token approval and no BNB. The merchant must put the token’s EIP-712 domain in extra.name and extra.version. For 0.01 USD1, use this price in your route configuration:
It produces this payment requirement:
extra.name and extra.version must match the token exactly. If they are missing, verification fails with invalid_exact_evm_missing_eip712_domain. If they are wrong, it fails with invalid_exact_evm_signature. Do not reuse the values of another token, such as Base USDC. For U, use United Stables and 1. These payments were tested with signatures from standard wallets (externally owned accounts). Signatures from smart contract wallets are untested on BSC.

Permit2 tokens (Binance-Peg USDC, USDT)

Binance-Peg USDC and USDT have no EIP-3009 functions, so they use Permit2. 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.

Limits and live routes

BSC does not support x402 v1, upto, or batch settlement. Do not assume six-decimal USDC amounts, a default dollar-price asset, or Base’s token authorization fields. The Binance-Peg tokens are distinct from native USDC on other networks. Try the live Echo routes for BSC mainnet USDC or BSC testnet USDC. Both routes use Permit2. 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 https://facilitator.payai.network. It supports v2 exact payments with the same two transfer methods. Configure a token deployed on chain 97 and its actual decimals; do not reuse the mainnet token addresses. For an EIP-3009 token, set that token’s own EIP-712 domain in extra.name and extra.version. For a Permit2 token, the initial token approval requires testnet BNB (tBNB), which is BNB on BSC testnet. Check the facilitator’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?