BriefingRegulationArchiveProfile
PaymentLeaks
BriefingRegulationArchive
ES|EN
Sign in
Access
Home/Glossary/x402

Agentic Commerce

What is x402? The HTTP-Native Payment Protocol for AI Agents

x402 is an HTTP-native protocol that revives the 402 Payment Required status code for AI agent payments, now governed by the Linux Foundation.

Last updated: 2026-04-06

x402 is an open protocol that revives the HTTP 402 Payment Required status code (defined but unused since 1997) to enable machine-to-machine payments between AI agents and APIs. It was originally proposed by Coinbase in 2024 and donated to the Linux Foundation in early 2026 as a neutral project.

The flow works as follows: a client (e.g., an LLM agent) calls an API. The server replies with HTTP 402 and a header describing price, chain, and payment method (typically a stablecoin such as USDC on Base or Solana). The agent pays on-chain and retries the request with a proof-of-payment header, receiving the resource.

x402 competes with proposals like UnionPay's APOP and Google's AP2. Its key advantage is simplicity: no pre-existing accounts, no OAuth tokens, no monthly billing. This makes it especially suited to microtransactions and on-demand API calls issued by autonomous agents.

Since entering the Linux Foundation, x402 has added support from Cloudflare, Stripe (via Stripe Connect), and several Web3 infrastructure providers. It is a core building block of the emerging agentic commerce ecosystem.

The 2026 technical debate pits x402 against the regulatory friction in the IMF Note (April 22) and the Fed B2B Connectivity Paper (April 23): both authorities acknowledge that deterministic settlement finality clashes with the probabilistic behaviour of AI agents — a transaction the agent thinks it paid may not be confirmed on-chain before the HTTP timeout. The UK FCA tested this friction in its Sandbox cohort 2 and published preliminary findings in March 2026 favouring hybrid x402+escrow models.

For businesses considering monetized endpoints exposed to AI agents, x402 forces three decisions: (1) settlement chain (Base for cost, Solana for latency, Ethereum L1 for compatibility), (2) refund policy on agent failures (automatic refunds, dispute windows, escrow), (3) KYC posture for the paying wallet (Coinbase Verifications, Circle Verite, APOP X.509 certificates). Each decision opens or closes entire channels of agentic commerce.

Key facts

  • •Revives the HTTP 402 Payment Required status code (RFC 7231)
  • •Originally proposed by Coinbase in 2024
  • •Donated to the Linux Foundation in 2026
  • •Supports stablecoins (USDC) on Base, Solana, and other chains
  • •Designed for machine-to-machine AI agent payments
  • •No pre-existing accounts or OAuth required
  • •Supported by Cloudflare, Stripe, and Web3 providers
  • •UK FCA Sandbox cohort 2 (Mar 2026) testing hybrid x402+escrow
  • •Competes with APOP (UnionPay) and AP2 (Google) for the agentic standard

Recent briefings mentioning this term

  • Briefing of 2026-04-03
  • Briefing of 2026-04-06

Related terms

apop

APOP (Agentic Payment Open Protocol) is the AI agent payment standard launched by UnionPay on April 3, 2026 as a rival to x402 and Google's AP2.

← Back to glossary
PaymentLeaks

PaymentLeaks is built by Ignacio De Navascués — 12 years in the payments industry. Daily intelligence on global payments, fintech and sovereign rails, hand-curated and analyzed every morning.

Content
  • Today's briefing
  • Archive
  • Regulation
  • Convergence
  • Glossary
Subscription
  • Premium €15/mo
  • See sample
  • FAQ
About
  • About PaymentLeaks
  • Podcast
  • Privacy
  • Terms
© 2026 PaymentLeaks · MadridIndependent analysis. Not financial advice.