Understanding x402, AP2, MPP, ACP in Agentic Payments

The rise of agentic payments is transforming how autonomous systems, AI agents, and machines transact. Four protocols—x402, AP2, MPP, and ACP—dominate the conversation, each addressing a specific layer of agentic payment workflows. Rather than competing directly, these protocols solve distinct problems and are increasingly likely to coexist in the same payment ecosystem.

Protocol Breakdown: What Each Does

x402: This protocol focuses on settlement and leverages the dormant HTTP 402 status code, enabling agents to request a resource, receive pricing details, and pay in stablecoins like USDC—all within the same HTTP request. It’s ideal for machine-to-machine transactions, such as API calls or compute jobs. As of Q1 2026, x402 had processed over 100 million cumulative transactions on Base, with adoption concentrated in high-value payments. Founding members of the x402 Foundation include AWS, Google, Visa, and Mastercard, underscoring its institutional backing.

AP2: Google’s Agent Payments Protocol (AP2) sits at the authorization layer. It enables cryptographically signed mandates to verify user intent, agent actions, and payment approvals. This protocol doesn’t move money; instead, it provides verifiable trust for merchants and networks in agent-driven transactions. AP2 is rail-agnostic, supporting cards, stablecoins, and bank transfers, and its adoption has been bolstered by partnerships with Mastercard, PayPal, and American Express.

MPP: The Machine Payments Protocol, co-authored by Stripe and Tempo, excels at session-based payments. It allows agents to establish spending limits and stream micropayments over time without requiring an on-chain transaction for every interaction. MPP is compatible with various payment rails, including stablecoins, Visa cards, and the Lightning Network, and is particularly suited for metered or ongoing agent workloads like data processing or cloud compute services.

ACP: Developed by OpenAI and Stripe, the Agentic Commerce Protocol standardizes agent-to-merchant checkouts. It focuses on consumer-oriented purchases, structuring transactions so merchants retain control over catalog, pricing, and fulfillment. ACP integrates seamlessly with fiat payment systems through existing providers, making it ideal for conversational commerce and digital goods.

Where They Overlap—and What They Don’t Cover

These protocols often appear competitive but largely address different layers of a transaction:

x402 and MPP: Settlement-focused but optimized for different transaction types—x402 for one-shot payments, MPP for ongoing streams.
AP2: Complements settlement protocols by providing verifiable authorization and trust.
ACP: Focuses on structuring commerce at the checkout layer, often working in tandem with AP2 or x402 for payment and authorization.

Notably, none of these protocols address wallet management, spending limits, or compliance reporting. These gaps underscore the importance of robust wallet and policy infrastructure to support multiple protocols simultaneously.

Market Outlook and Adoption Trends

Adoption of these protocols reflects their complementary roles. x402 has seen strong traction in the machine-to-machine economy, while AP2 and ACP cater to more consumer-facing applications. MPP’s session-based architecture is gaining attention for its efficiency in high-frequency transactions, with Lightspark recently adapting it for Bitcoin payments over the Lightning Network.

Industry players are hedging their bets by supporting multiple protocols. For example, Visa and Mastercard are deeply involved in both x402 and AP2. This suggests the future of agentic payments won’t be a winner-takes-all scenario but rather a layered ecosystem where different protocols interoperate.

Key Takeaway for Payments Teams

For businesses, the critical question isn’t which protocol to adopt but whether their wallet and governance systems can handle multiple protocols without constant rebuilding. Supporting a diverse stack is increasingly essential as agentic payments evolve and new standards emerge.

As the market matures, expect further innovation at the intersections of these protocols, particularly around security, compliance, and user experience. The collaboration between Fireblocks and the x402 Foundation to enhance protocol security is a prime example of the industry tackling existing gaps.

Image source: Shutterstock