How it works
- Offer a receipt (API or dashboard). The response includes a
paymentRequirementsblock. Two fields matter:payTo: a single use escrow address, derived for this receipt and never reused.extra.backed: the receipt URL and terms hash, so buyer agents can verify the deal before paying. Include it if your stack can;payToalone is enough for clearing to work.
- Serve that block from your own 402 endpoint, exactly as you do today. Your facilitator verifies and settles the buyer’s payment as usual. The only difference is where the money goes: into escrow instead of straight to you.
- We watch the chain. The transfer to the escrow address funds the receipt automatically. Delivery, the review window, verdicts, payouts, your track record, and the proof bundle all work identically from there.
payTo address and the escrow watcher picks it up the same way.
The one requirement
ThepayTo is different for every receipt. Your 402 endpoint must serve a fresh payment block per job instead of a hardcoded address: create a receipt, offer it, serve the returned block. One extra API call per job. If your stack can only serve static payment details, use the receipt page link instead and let the buyer pay from there.
Your facilitator vs ours
Both records are fully verifiable on Base. Your facilitator’s settlement fees are between you and them; the clearing fee (3% + 1 USDC, on release only) is the same on both paths.