The Two Most Mature Agent Payment Instruments
Of the five major agent payment protocols (x402, MPP, AP2, Visa TAP, Mastercard Agent Pay), x402 and MPP are the two most operationally mature in 2026. Both are in production with real transaction volumes. Both have established merchant integrations. They differ in almost every architectural choice underneath that operational maturity, which makes their comparison the cleanest way to understand the protocol landscape.
At a Glance
| Dimension | x402 (Coinbase) | MPP (Stripe) |
|---|---|---|
| Layer | HTTP-level signalling + crypto settlement | Managed credentials on card/bank rails |
| Sponsor and standards body | Coinbase, donated to Linux Foundation | Stripe (proprietary) |
| Settlement rail | USDC on Base, extending | Card and bank through Stripe |
| Authorisation model | Per-request, signed payment header | Pre-authorised constraints (caps, categories, bounds) |
| Attestation primitive | ERC-8004 native | Stripe transaction metadata |
| Currency support | USDC default, multi-stablecoin | USD, EUR, plus 135+ supported by Stripe |
| Best for | Crypto-native agent flows, micropayments | Card-rail agent commerce, recurring transactions |
Architectural Differences That Matter
Authorisation model. x402 authorises per-request: every payment is explicitly constructed and signed for the specific request being paid for. MPP authorises in advance: the user creates a managed profile with constraints, and any transaction within the constraints proceeds without further authorisation. The trade-off is between fine-grained per-request control (x402) and operational efficiency at higher transaction volumes (MPP).
Currency. x402's default rail is USDC on Base, with extensions to other stablecoins. Multi-currency support exists but the primary use case is dollar-equivalent stablecoin transactions. MPP supports the full range of currencies Stripe handles (135+), including local currencies in many regions. For multi-currency agent commerce, MPP has the broader native coverage.
Settlement speed. x402 settlements are typically minutes (subject to chain finality). MPP settlements follow card-rail timelines (T+1 to T+3 for most transactions). For real-time agent commerce flows, x402 has the faster end-to-end settlement.
Fees. x402 transaction fees are minimal (Base gas plus any merchant-side margin), making micropayments viable down to fractions of a cent. MPP fees follow card-rail pricing (typical 2.9% plus $0.30 in the US), which makes micropayments below roughly $1 economically unviable. For sub-dollar agent payments, x402 is the only viable option.
Where x402 Wins
Any flow involving micropayments (sub-dollar per-fetch Pay-Per-Crawl, per-citation attribution payments, per-API-call agent fees) needs x402-class economics. The fee structure of card rails makes these flows economically unviable. x402 also wins where settlement speed matters (real-time agent commerce, immediate revenue recognition) and where crypto-native infrastructure is already in place.
Where MPP Wins
Any flow involving consumer-facing card commerce wins on MPP because the user already has a card on file with Stripe-supported merchants and does not need to onboard to a crypto wallet. MPP also wins for higher-value agent transactions ($10+) where the card-rail fee is not material relative to the transaction value, and for multi-currency flows where Stripe's native support is broader than current x402 stablecoin coverage.
How They Compose in Mature Stacks
Mature agent commerce stacks use both. x402 handles the long tail of micropayments (per-fetch content access, per-API-call agent fees) where card economics fail. MPP handles the higher-value consumer commerce (subscription purchases, retail transactions) where card rails are operationally mature. AP2 sits above both, providing the agent-side intent and authorisation that lets a single agent transact across both rails as appropriate.
What Publishers Should Implement
For most publishers, the question is whether to implement x402 explicitly. The answer depends on per-fetch pricing. If your typical per-fetch rate is below $0.10 (which covers most general content monetization), x402 is required because card-rail economics make those payments unviable. If your per-fetch rate is consistently above $0.10 and your transaction volume is high enough to justify card-rail integration, you can defer x402 implementation. Most mid-market publishers should support x402 either directly or through a marketplace partner that handles x402 settlement on their behalf.