Skip to main content
b402 is a multichain payment protocol that gives AI agents and web services gasless, confidential, multi-token transactions across EVM-compatible chains.
Traditional systems rely on centralized processors, accounts, and manual flows. b402 removes those barriers — enabling machine-to-machine, HTTP-native payments that settle instantly on-chain with minimal fees.
No. Any service — from API providers to AI agents to websites — can integrate b402 to enable programmatic, per-request or usage-based payments.
The b402 reference implementations are written in TypeScript, but the protocol is open and language-agnostic. Anyone can implement it in Go, Rust, or any environment that supports HTTP requests and ECDSA/EIP-712 signing. Developers are encouraged to open PRs or RFCs in the GitHub repository to expand SDK coverage.
The Facilitator is managed by the b402 core team. It is currently live on BNB Chain and Base.
NetworkTokensStatus
BNB ChainUSDT, USDC, USD1Mainnet
BaseUSDC, USDTMainnet
Gas is covered by the Facilitator (EOA) or Paymaster (Smart Wallet). The protocol is chain-agnostic by design — additional EVM chains and tokens will be added as the network expands. See Network & Token Support for contract addresses.
x402 relies on EIP-3009 (transferWithAuthorization), which is built into USDC but not implemented by most tokens (USDT, USD1, etc.). b402 introduces its own Relayer contract that accepts EIP-712 signed messages and executes standard transfer() calls on behalf of the user. This means any whitelisted ERC-20 token works, on any deployed chain.
Not natively. However, facilitators or third-party gateways can integrate fiat payment bridges for deposits or withdrawals if required.
No. Agents or buyers sign locally in their runtime environment (browser, VM, or enclave). Servers and facilitators only verify signatures — they never have access to private keys.
b402’s privacy pool uses a custom implementation inspired by RAILGUN’s zero-knowledge proof system. RAILGUN pioneered compliant on-chain privacy using zkSNARKs, encrypted commitments, and Merkle trees — b402 builds on these foundational cryptographic primitives.How b402 differs from Tornado Cash:
  • Tornado Cash used fixed-denomination pools and offered no compliance mechanism. It was sanctioned by OFAC in 2022.
  • b402’s privacy pool supports arbitrary amounts, integrates with ERC-4337 smart wallets for gasless operation, and is designed with compliance in mind — shielded balances can be verified against screening requirements without revealing transaction details.
b402 does not use Tornado Cash code or architecture.