Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
HTTP-402 + escrow concept · Boson Protocol
Skip to content

HTTP-402 + escrow concept

x402 is an open spec for in-band HTTP-402 payments: an HTTP server can respond 402 Payment Required with payment options, and a client can re-request with payment proof in an X-PAYMENT header. The server validates and serves.

x402 is payment-method-agnostic. x402b is the Boson-flavored scheme that uses Boson escrow as the payment method.

Why escrow?

Plain x402 says "send funds and you get the resource". Escrow x402 says "lock funds; the resource must be delivered before they release; either party can dispute".

This gets you:

  • Non-custodial. No platform holds money.
  • Dispute resolution. If the delivery is broken, the buyer can raise a dispute. Boson's DR resolves.
  • Re-fundable. A failed delivery refunds automatically.
  • Composable with other Boson features — vouchers (rNFTs), royalties, agent fees.

The flow

Two flows

FlowDescriptionBest for
DeferredCommit now; redeem later (buyer or server triggers)Physical goods, time-bounded redemption
AtomicCommit + redeem in one txDigital goods, agent-to-agent commerce

Where it differs from plain x402

Plain x402x402b (Boson escrow)
Pay directPay to escrow
Trust the sellerTrust the protocol
No native disputeBuilt-in dispute resolution
GenericBoson-specific (offers, exchanges)

Next