x402 vs L402: Which HTTP 402 Payment Protocol Wins?
Both x402 and L402 are built on the same long-dormant idea: HTTP status code 402 Payment Required, finally put to work so machines can pay for resources over the web. But they come from different worlds — x402 from the stablecoin/EVM ecosystem, L402 from Bitcoin and the Lightning Network — and that shapes everything about how they behave.
If you’re deciding which to build on for an API, an AI agent, or a paid service, here’s the honest comparison.
The 30-second answer
- Choose x402 if you want stablecoin (USDC) settlement, EVM/Solana ecosystems, dead-simple HTTP integration, and the largest, fastest-growing agent-payments community. This is where most new AI-agent tooling is being built in 2026.
- Choose L402 if you’re committed to Bitcoin and the Lightning Network, want sub-cent payments with Lightning’s settlement model, and value its macaroon-based authentication.
Both are legitimate. The deciding factor is usually which money and which chain you want to settle in.
What they share
Both protocols use the same core handshake:
- A client requests a protected resource.
- The server replies with HTTP 402 Payment Required plus payment instructions.
- The client pays.
- The client retries with proof of payment, and the resource is released.
This is the elegance of the 402 approach: payment becomes a native part of the HTTP request/response cycle, with no accounts, no checkout pages, and no API keys required up front.
What’s different
| Dimension | x402 | L402 |
|---|---|---|
| Origin | Coinbase (2025) | Lightning Labs ecosystem (originally “LSAT”) |
| Settlement asset | USDC and other stablecoins | Bitcoin (sats) |
| Network | Base, Solana, other EVM chains | Bitcoin / Lightning Network |
| Auth mechanism | Signed payment payload + facilitator settlement | Macaroon credential + Lightning invoice preimage |
| Best for | Agent ↔ API payments, stablecoin pricing | Bitcoin-native services, Lightning apps |
| Ecosystem momentum (2026) | Very large, fast-growing | Established, Bitcoin-focused |
Settlement: stablecoins vs Bitcoin
This is the biggest practical difference. x402 settles in USDC, so prices are stable and denominated in dollars — convenient for API pricing and accounting. L402 settles in Bitcoin over Lightning, so amounts are in sats and carry BTC volatility, but inherit Lightning’s instant, low-fee settlement.
Authentication model
L402 pairs a macaroon (a bearer credential with caveats) with a Lightning invoice; once the invoice is paid, the preimage unlocks the macaroon. x402 instead has the client present a signed payment that a facilitator verifies and settles on-chain, after which the request proceeds. x402’s model maps very cleanly onto stateless HTTP and is simple to add to an existing API as middleware.
Ecosystem and tooling
In 2026, the momentum behind agent payments is concentrated around x402 — it’s the protocol most new AI-agent SDKs, MCP server monetization tools, and facilitators target, and it composes with higher-level agent standards like Google’s AP2 and the A2A x402 extension. L402 has a smaller but durable footprint anchored in the Bitcoin/Lightning community.
Which should you choose?
Ask three questions:
- What money do you want to receive? Dollars (USDC) → x402. Bitcoin → L402.
- Where do your users and agents already hold funds? EVM/Solana wallets → x402. Lightning wallets → L402.
- What ecosystem do you want to plug into? AI-agent and MCP tooling → x402. Bitcoin-native apps → L402.
For most teams building AI agents that pay for APIs and tools, x402 is the pragmatic default in 2026 — not because L402 is bad, but because the surrounding ecosystem (facilitators, SDKs, agent frameworks) is overwhelmingly there.
Can you support both?
Yes. Since both ride on HTTP 402, a server can advertise multiple payment schemes in its 402 response and let the client pick. A few gateways and routers already abstract over more than one rail. If you’re unsure, starting with x402 and leaving room to add L402 later is a low-risk path.
Next steps
- New to the protocol? Start with What is x402?
- Building? Browse the x402 facilitator list and paid MCP servers.
- Comparing more options? See our protocol comparison.
x402 and L402 both prove the same thesis: the web finally needs HTTP 402. The only real question is which money flows through it.