Ask402

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

x402MPPL402AP2ACP
JobPay per requestPay per request, session or subscriptionPay per request or for accessProve a purchase was authorizedShopping checkout
FromCoinbaseTempo and StripeLightning LabsGoogleOpenAI and Stripe
Governed byx402 Foundation (Linux Foundation)Authors, with an IETF draftLightning LabsFIDO AllianceOpenAI and Stripe
Uses HTTP 402YesYesYesNoNo
Pays withBlockchain tokens, mostly USDCStablecoins, cards, LightningBitcoin LightningCards firstThe buyer's existing payment method
Needs an account with the sellerNoNoNoDepends on the merchantMerchant integration
Typical amountUnder a cent to a few dollarsUnder a cent upwardsA few satoshis upwardsA normal purchaseA 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 seeIt is
Status 402 and a PAYMENT-REQUIRED headerx402 version 2
Status 402 and a JSON body with x402Version and acceptsx402 version 1
Status 402 and WWW-Authenticate: Payment ...MPP
Status 402 and WWW-Authenticate: L402 ... (or LSAT)L402
More than one of the aboveThe endpoint accepts several. Pay with whichever your client supports

The 402 checker reads all of these and lists every offer.

Quick picks

You want toUse
Charge agents for API calls in stablecoinsx402
Charge for API calls and accept cards tooMPP, or x402 and MPP together
Charge in bitcoin over LightningL402
Let an agent shop at a merchant with a cardACP for checkout, with AP2-style authorization
Pay for many tools from one agent walletx402, 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

Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.

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.