x402, MPP, L402, AP2 and ACP: how do the agent payment protocols compare?
Short answer
x402, MPP and L402 are payment handshakes built on HTTP status 402, for paying per request. They differ in what they pay with. x402 uses blockchain tokens, MPP adds cards, and L402 uses Bitcoin Lightning. AP2 and ACP are different in kind. AP2 proves a person authorized an agent's purchase, and ACP is a shopping checkout standard. Neither uses 402.
The one-table answer
| x402 | MPP | L402 | AP2 | ACP | |
|---|---|---|---|---|---|
| Job | Pay per request | Pay per request, session or subscription | Pay per request or for access | Prove a purchase was authorized | Shopping checkout |
| From | Coinbase | Tempo and Stripe | Lightning Labs | OpenAI and Stripe | |
| Governed by | x402 Foundation (Linux Foundation) | Authors, with an IETF draft | Lightning Labs | FIDO Alliance | OpenAI and Stripe |
| Uses HTTP 402 | Yes | Yes | Yes | No | No |
| Pays with | Blockchain tokens, mostly USDC | Stablecoins, cards, Lightning | Bitcoin Lightning | Cards first | The buyer's existing payment method |
| Needs an account with the seller | No | No | No | Depends on the merchant | Merchant integration |
| Typical amount | Under a cent to a few dollars | Under a cent upwards | A few satoshis upwards | A normal purchase | A normal purchase |
Two families
Paying for a request. x402, MPP and L402 all answer the same question: how does a program pay for this one HTTP call, right now, without signing up? All three reply 402 Payment Required and expect the request to be repeated with proof of payment. They differ in the header that carries the price and in the money they accept.
Buying on someone's behalf. AP2 and ACP deal with an agent making a purchase for a person: who approved it, what is in the order, how the merchant gets paid and who is responsible afterwards. They involve carts, mandates and merchants, not single HTTP calls.
The two families work together more than they compete. An agent can prove authorization with AP2 and settle with x402.
How to tell what an endpoint speaks
| You see | It is |
|---|---|
Status 402 and a PAYMENT-REQUIRED header | x402 version 2 |
Status 402 and a JSON body with x402Version and accepts | x402 version 1 |
Status 402 and WWW-Authenticate: Payment ... | MPP |
Status 402 and WWW-Authenticate: L402 ... (or LSAT) | L402 |
| More than one of the above | The endpoint accepts several. Pay with whichever your client supports |
The 402 checker reads all of these and lists every offer.
Quick picks
| You want to | Use |
|---|---|
| Charge agents for API calls in stablecoins | x402 |
| Charge for API calls and accept cards too | MPP, or x402 and MPP together |
| Charge in bitcoin over Lightning | L402 |
| Let an agent shop at a merchant with a card | ACP for checkout, with AP2-style authorization |
| Pay for many tools from one agent wallet | x402, which has the most wallets and catalogs today |
Others worth knowing
- UCP (Universal Commerce Protocol) is a discovery-to-checkout standard co-developed by Google, Shopify and others. It builds on AP2, A2A and MCP.
- Verifiable Intent, co-developed by Mastercard and Google, was donated to the FIDO Alliance in April 2026 alongside AP2.
Each comparison in detail
Sources
- x402 version 2 specification
- MPP compared with x402, mpp.dev
- L402 protocol specification
- AP2 protocol site
- Agentic Commerce Protocol repository
- Universal Commerce Protocol site
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.