Build with x402
x402b extends the x402 standard with non-custodial escrow on the Boson Diamond. A buyer requests a resource, gets a 402 Payment Required with a Boson escrow option, signs a meta-transaction, and a facilitator settles it on-chain.
Pages
- HTTP-402 + escrow concept — the model and why it exists.
- Buyer side (x402-client) — making paid requests from a client.
- Seller side (x402-server) — protecting an HTTP resource.
- Facilitator (x402-facilitator) — running the relayer.
- Fulfillment channels — delivering the goods after payment.
- Token-auth strategies — ERC-3009, EIP-2612, Permit2, plain approve.
- State-machine integration — advancing the exchange in
nextActions.
Quickstart
If you want to skip the reading and try it: Quickstart → Accept x402 escrow payments.