PROTOTYPE · Stable402_Request_Sequence_v1 — §8.2 of Stable402_Acquisition_Strategy. Reuses the A1 x402 path; reject branches (451 / 403) shown as first-class.
Stable402 · The compliant x402 request
One agent payment, gated at the edge — screen, enforce, settle, record, export
A request walkthrough of the x402-middleware: the agent asks to pay, the edge middleware screens and enforces before any money moves, then settles, records a verifiable receipt, and hands off the examiner bundle. The proof it's a real gate and not a logger: pick Sanctioned counterparty or Out of scope and watch it stop at 451 / 403 — no funds move.
edge gates run before settlement
—
Pick a scenario to run the request.
Gate — halts if it fails
Monitor — observes, logs, doesn't halt
Output — settle / receipt / export
Sources. Flow = production x402-middleware (A1 path): Coinbase Smart Wallet on Base · Cloudflare Worker (Chainalysis OFAC oracle, KV-cached; AML pattern monitor) · ACK-ID delegation · EIP-3009 transferWithAuthorization · W3C Verifiable Credential receipt in R2.
Examiner bundle = kya-export-worker (OFAC-trace + SAR-narrative). HTTP 451 = Unavailable For Legal Reasons; 403 = Forbidden.
Full thesis: Stable402_Acquisition_Strategy_2026-06-01.md.