The Untapped Potential of HTTP 402 Payment Required

When Tim Berners-Lee and the Internet Engineering Task Force drafted the HTTP specification in the late 1990s, they reserved a status code specifically for digital cash: 402 Payment Required.

Unlike 200 (OK), 404 (Not Found), or 500 (Internal Server Error), HTTP 402 spent nearly three decades in digital limbo. It was never formally deprecated, but neither was it widely adopted. Why did this native payment code remain dormant, and why is it re-emerging in 2026 as the foundation for the AI economy?

Why HTTP 402 could not work in 1997

In the 1990s and 2000s, digital currency did not exist in any standardized, interoperable form. Financial rails were built around national clearinghouses, correspondent banking, and centralized card networks:

• Batch processing: Credit card networks clear transactions in batch runs, not real-time per-packet streams.
• Minimum fee floors: A 30¢ flat interchange fee makes selling an individual web page for $0.001 impossible.
• Human-in-the-loop necessity: Banking risk engines relied on billing addresses, postal codes, and fraud scoring calibrated for humans.

The x402 open protocol ecosystem

The emergence of modern distributed ledgers and price-stable digital dollars (USDC and EURC) changes the equation. Internet endpoints now have access to sub-cent settlement rails that finalize within seconds at negligible network fees.

The open x402 protocol establishes standard headers that turn any REST endpoint or GraphQL query into a pay-per-call monetized resource:

HTTP/1.1 402 Payment Required
x402-price: 0.002
x402-currency: USDC
x402-recipient: 8xK9vL...2mP9
x402-network: solana

FurlPay's independent role

FurlPay does not claim to have invented HTTP 402 or the open x402 standard. Instead, FurlPay is developing the independent application and tooling layer that makes x402 usable for real enterprises:

• MCP wallet servers: Giving AI agents structured tools to check daily allowances before spending.
• WebAuthn passkey ceilings: Ensuring human operators retain cryptographic control over total budget.
• Developer SDKs: Drop-in TypeScript and Python clients that intercept 402s and resolve payments.