Jul 19, 2026·11 min read

x402 vs MPP vs AP2: Agent Payment Protocols Compared (2026)

x402 vs MPP vs AP2: fees, rails, settlement speed and integration effort compared — plus which agent payment protocol actually fits your workload.

  • #protocols
  • #comparison
  • #x402
  • #mpp
  • #machine payments protocol

x402 vs MPP vs AP2 is the wrong comparison to make as a three-way horse race, because these protocols sit at different layers of the agentic commerce stack. x402 and MPP move money for machines. AP2 proves an agent was allowed to spend it. Mastercard Agent Pay and Visa TAP identify the agent to the card network. Most production systems in 2026 run two of them at once, not one.

The short version: if you are charging an agent per API call, you want x402 or MPP. If you are selling products to consumers through an agent, you want AP2 plus whatever card network your processor supports. If you are doing both, you will implement both.

The one thing to understand first: these are layers, not rivals

Layer Question it answers Protocols Who runs it
Commerce What is the agent buying, from whom? UCP, ACP (Stripe + OpenAI) Google, Stripe/OpenAI
Authorization Did the user actually authorize this spend? AP2 (mandates) Google, now FIDO Alliance
Identity Is this request from a legitimate agent, not a scraper? Visa TAP, Web Bot Auth Visa, Cloudflare, Mastercard
Execution How does the money physically move? x402, MPP, Agentic Tokens Coinbase, Stripe + Tempo, Mastercard

AP2 is the governance layer that any rail can adopt. x402 and MPP are the rails. That is why “x402 vs AP2” comparisons that declare a winner are usually confused — the two compose rather than compete, and the x402 protocol itself says nothing about who authorized the agent.

Side-by-side comparison

x402 MPP Mastercard Agent Pay Google AP2
Layer Execution Execution Execution + identity Authorization
Launched May 2025 Mar 18, 2026 2025, expanded Jun 2026 2025, v0.2 Apr 2026
Steward x402 Foundation (Linux Foundation) Stripe + Tempo Mastercard FIDO Alliance
Settlement rails Stablecoins (USDC, EURC) on Base, Solana, any EIP-3009 EVM chain Stablecoins on Tempo, Lightning, Solana, cards via Stripe SPTs Card network (MDES tokens); accounts and stablecoins added 2026 Rail-agnostic — cards, ACH, stablecoins
Billing model One fixed-price payment per HTTP request Per request, or session/streaming against a pre-authorized cap Normal card authorization with agent metadata Mandate scoping, not billing
Typical ticket $0.001 and up $0.001 and up $5–10 minimum to clear fees Any
Protocol fee Zero — gas only (~$0.00025 on Solana, fractions of a cent on Base) Stripe processing fees on card SPTs; gas on Tempo Standard interchange + network fees None — it is a specification
Settlement ~2 seconds, 24/7 Sub-second on Tempo; card timing on SPTs T+1 to T+2, banking hours Depends on rail
Chargebacks None — final on confirmation Refunds via Stripe on card rails 60–180 day dispute windows Mandate is the dispute evidence
Integration effort Low: one 402 handler + a facilitator Low if you already use Stripe Low for merchants — existing processor, CDN-level bot auth Moderate: mandate signing + verification
Best for Agent-to-agent API and data payments Metered/streaming billing, mixed card + stablecoin Consumer retail through agents Any payment that needs provable consent

x402: the machine-to-machine rail

x402 revives the HTTP 402 Payment Required status code that has sat unused in the HTTP spec since the 1990s. The flow is deliberately tiny: the client requests a resource, the server answers 402 with payment details, the client submits a stablecoin payment, and retries with the transaction hash attached. No accounts, no API keys, no session.

What it gets right:

  • Zero protocol fees. The only cost is onchain gas — roughly $0.00025 per transaction on Solana, fractions of a cent on Base. Coinbase’s CDP facilitator offers 1,000 free transactions per month, then $0.001 each.
  • Sub-cent economics. The minimum viable payment is around $0.001, versus the $5–10 floor that card interchange imposes (~2.9% + $0.30 on US Stripe pricing).
  • Settles in about two seconds, 24/7, across borders. No banking hours, no correspondent banks.
  • Permissionless facilitators. Anyone can run one, so you are not locked to a vendor.

What to be honest about:

  • x402 is stablecoin-only. No cards, no ACH. If your customers hold balances in dollars in a bank account, x402 does not help you today.
  • Raw volume numbers do not equal commercial adoption. On public blockchains anyone can generate arbitrarily many zero-value transactions, so headline “transaction count” figures for any payment protocol (x402 included) overstate real buyer-seller exchange by an unknown margin. Treat public volume charts as plumbing tests — indicators the rails work — not as proof of revenue flowing through them. The adoption metric that matters is settled commercial volume from real merchants, which the protocol is still early in building.
  • Merchant coverage is narrow. The services accepting x402 are overwhelmingly crypto- and AI-native — API providers, GPU compute, storage, scraping. Mainstream SaaS and retail have not integrated it.

x402 is the right pick when an autonomous agent is paying another machine for data or compute, unattended, in sub-dollar increments. The open-source example project walks through a working implementation, and @harpd/x402-logging-middleware drops into the handler so every 402 settlement lands in an audit log you can reconcile.

MPP: Stripe’s multi-rail answer, and the session model

The Machine Payments Protocol launched on March 18, 2026, co-authored by Stripe and Tempo (with Visa contributing card-rail specs). It uses the same HTTP 402 challenge-response pattern as x402, and it is explicitly backwards-compatible with x402’s exact payment flows — an MPP client can consume an existing x402 service unchanged.

Two design differences matter:

1. Multiple rails. MPP settles in stablecoins on Tempo, over Bitcoin Lightning via Lightspark, on Solana, or in fiat through Stripe’s Shared Payment Tokens (SPTs) — scoped, time-limited card credentials that keep raw card numbers out of the agent’s context. Card payments show up in the Stripe Dashboard like any other transaction, with the same tax, fraud, and refund handling.

2. Sessions. This is the real differentiator. Instead of settling onchain per request, the agent opens a session with a spending cap, accumulates charges across many requests, and settles once — like a bar tab. For per-token LLM billing or streaming data feeds, that removes the per-request settlement cost x402 carries. Stripe extended this with streaming payments at Stripe Sessions 2026.

MPP launched with a directory of 100+ integrated services (Anthropic, OpenAI, Shopify, Dune, Alchemy) and supports splitting a single payment across up to ten payees — useful for marketplaces.

Pick MPP when you already run on Stripe, when you need cards and stablecoins behind one integration, or when your billing is continuous rather than one-shot.

AP2 and Mastercard Agent Pay: the trust layer

Neither of these is really an x402 alternative — they solve the question x402 does not ask: was this agent actually authorized?

Google’s Agent Payments Protocol handles consent with cryptographic Mandates built on Verifiable Credentials:

  • Intent Mandate — the user’s standing instruction (“buy the tickets when they drop, up to $200”), signed up front.
  • Cart Mandate — locks the exact items and price, signed by the merchant first, then countersigned by the user.
  • Payment Mandate — flags to the network and issuer that the transaction was agent-initiated, and whether a human was present.

Chained together, the three produce a non-repudiable audit trail: merchants can prove authorization, issuers can risk-score agent traffic differently, and disputes have evidence. AP2 is rail-agnostic by design — the same mandate can authorize a card payment, a bank transfer, or a stablecoin transfer. Google donated AP2 to the FIDO Alliance in April 2026 alongside Verifiable Intent, co-developed with Mastercard, and v0.2 added “Human Not Present” payments for fully autonomous purchases.

Mastercard Agent Pay works at the network layer. Agents must pass Know Your Agent (KYA) vetting before they can hold an Agentic Token — an MDES network token extended with agent identity, consent, and spend-limit fields. The consumer never shares raw card credentials, the token presents to the merchant’s existing processor like a normal card, and disputes carry agent attribution. US Mastercard cardholders were enabled by mid-November 2025; Agent Pay for Machines, launched June 2026, extends the program to high-frequency, low-value machine payments across cards, accounts, and stablecoins.

On the merchant side, the practical work is small: Mastercard’s Acceptance Framework relies on Web Bot Auth verified at the CDN layer, and Visa’s Trusted Agent Protocol (launched October 2025, built with Cloudflare on RFC 9421 HTTP Message Signatures) does the equivalent job of distinguishing a legitimate agent from a scraper.

Which one should you use? Six concrete scenarios

1. You sell API or data access and want pay-per-call from agents. Start with x402. It is the thinnest thing that works, costs nothing beyond gas, and settles in seconds. Add MPP later if customers ask to pay by card.

2. You bill by the token, the second, or the stream. Use MPP sessions. Per-request onchain settlement breaks down when the unit of consumption is smaller than the gas fee.

3. You are a retailer selling to consumers through agents. You are not choosing a payment rail — your processor is. Make sure your processor supports AP2 or your network’s program (Agent Pay / TAP), and focus your effort on the merchant-of-record layer (UCP or ACP).

4. You are a B2B SaaS already on Stripe. MPP with SPTs is the lowest-friction path: agent payments land in the dashboard you already use, with refunds and tax intact.

5. You are building agent-to-agent payments across borders, 24/7. x402 on stablecoins. Cards impose banking hours, FX legs, and a fee floor that sub-dollar machine traffic cannot absorb. See the real cost comparison of card rails vs USDC for agents for the arithmetic.

6. Any of the above, in a regulated environment. Whatever rail you pick, you still need the audit trail. That is protocol-independent: capture intent, authorization, amount, and settlement per transaction. Agent transaction audit schema is a copyable structure, and agent payment guardrails covers the policy layer — spend caps, destination allowlists, velocity limits — that contains an agent whose judgment goes wrong.

The honest outlook

Do not expect to pick one protocol and be done. Stripe is a founding member of the x402 Foundation and also ships MPP. Visa contributed card-rail specs to MPP while running its own TAP and Intelligent Commerce programs. Mastercard has said publicly that it participates in all the major protocols. The convergence is real, and the interoperability story is the part that is still unsettled.

The defensible engineering posture in 2026 is: build on the layer that is hardest to rip out — your own authorization and audit model — and treat the payment rail as a swappable adapter behind it.

FAQ

Is x402 the same as MPP? No, but they are compatible. x402 is Coinbase’s stablecoin-only HTTP 402 protocol (May 2025). MPP is Stripe and Tempo’s multi-rail protocol (March 2026) that supports cards, Lightning, and stablecoins, and adds session-based billing. MPP is backwards-compatible with x402’s exact payment flows, so MPP clients can pay existing x402 services.

Does AP2 replace x402? No. AP2 does not move money — it proves an agent was authorized to move it. An AP2 mandate can authorize a card payment, a bank transfer, or an x402 stablecoin payment. They compose.

Which protocol has the lowest fees? x402 and MPP on stablecoin rails. x402 charges zero protocol fees, leaving only gas (fractions of a cent on Base or Solana). Card-based agent payments still carry interchange, which sets a practical floor of roughly $5–10 per transaction.

How big is x402 really? Smaller than the headline numbers suggest. Public trackers counted 200M+ transactions by mid-2026, but Artemis Analytics attributes more than 95% of that to signaling and wash trading; real daily commercial volume was reported around $28,000 in early 2026. Average machine-to-machine transaction value is roughly $0.31.

Do I need Mastercard Agent Pay if I use AP2? They do different jobs. Agent Pay is the card-network implementation — agent identity, Agentic Tokens, dispute attribution. AP2 is the governance layer for consent. A single transaction can carry both, and Mastercard co-developed Verifiable Intent with Google precisely to make them interoperate.