What is x402 Payment Streaming?
x402 payment streaming is the pattern of continuous or high-frequency resource consumption paired with periodic x402 settlement — using schemes like deferred (batch settlement) or rapid exact payments to maintain an ongoing payment relationship between an agent and a resource server.
WHY IT MATTERS
Some agent workflows don't fit the discrete request-response model of x402's exact scheme. A market data agent consuming a real-time price feed, an AI assistant in a long-running session purchasing token-by-token inference, or a crawler processing thousands of pages per hour all need continuous payment relationships.
x402 payment streaming addresses this through several approaches:
- Rapid exact payments — making x402
exactpayments at high frequency (every few seconds), viable on low-fee L2s like Base - Deferred settlement — Cloudflare's proposed
deferredscheme where agents sign cryptographic commitments per resource and settle in daily batches - Upto authorisations — the planned
uptoscheme enables authorising a maximum spend for an extended session, with the server settling actual consumption periodically
The deferred scheme is particularly compelling for streaming. Cloudflare's pay-per-crawl prototype uses it: crawlers sign per-page commitments using HTTP Message Signatures, and settlement happens once per day via connected payment methods. This avoids per-request on-chain transactions entirely while maintaining cryptographic proof of each consumption event.
Payment streaming creates new challenges: how do you cap aggregate spend on a stream? What if the connection drops mid-stream? How do you handle disputes for partial delivery? These are active design questions in the x402 ecosystem.
HOW POLICYLAYER USES THIS
PolicyLayer enforces aggregate spending limits on streaming flows — capping total per-session and per-day spending regardless of how many individual payments comprise the stream. Spending velocity alerts trigger when streaming payment rates exceed configured thresholds.