Learn

Agentic payments protocols compared: Which is best for your AI agents? (ACP vs AP2 vs x402)

March 12, 2026

Key takeaways

  • ACP (Agentic Commerce Protocol), co-developed by OpenAI and Stripe, standardizes checkout flows between AI agents and merchants - first deployed in ChatGPT's Instant Checkout, now evolving toward an app-based model with Shopify and PayPal integration.
  • AP2 (Agent Payments Protocol), developed by Google with 60+ partners, defines the trust and authorization layer for agent-led payments using cryptographically signed mandates - supporting both traditional card payments and crypto via its x402 extension.
  • x402, created by Coinbase, enables instant stablecoin payments over HTTP by reviving the 402 status code - purpose-built for machine-to-machine microtransactions and API monetization.
  • Crossmint provides agent payments and wallets through a single API surface so agentic products and platforms can easily support every AI payment protocol and agentic commerce infrastructure as the landscape evolves.

Introduction

You're building AI agents that need to transact in the real world. Maybe your agents are purchasing cloud resources on behalf of users, paying for API calls from other agents, or completing e-commerce checkouts autonomously. You need a payment layer that works for machines and not just humans.

Three protocols have emerged to solve this problem, each backed by a major tech company: ACP from OpenAI and Stripe, AP2 from Google, and x402 from Coinbase. They approach agent payments from different angles. Checkout flows, authorization frameworks, and on-chain settlement. They're more complementary than competitive. But choosing which to support (and how to integrate them) is a real engineering decision with long-term consequences.

This guide compares all three on architecture, use cases, and production readiness. We'll also show you why teams building agentic products are choosing Crossmint for agent payments and wallets.

What is ACP (Agentic Commerce Protocol)?

ACP is an open-source specification co-developed by OpenAI and Stripe, first released in September 2025 under the Apache 2.0 license. It defines how AI agents interact with merchants to complete purchases through four RESTful endpoints: Create Checkout, Update Checkout, Complete Checkout, and Cancel Checkout. Payment is handled via SharedPaymentTokens - single-use, time-bound, amount-restricted tokens that give users control while letting agents transact programmatically.

ACP's first major deployment was OpenAI's Instant Checkout in ChatGPT, which launched in February 2026 with US Etsy sellers. However, OpenAI scaled back in-chat purchasing in early March 2026, shifting toward an app-based model. The protocol remains an open standard with support from Stripe, Salesforce, Shopify, and PayPal (which is building its own ACP server). The pivot highlights that ACP's long-term value is as an open protocol for agent-merchant communication, not a single-platform feature.

ACP's strength is standardizing how agents interact with merchant catalogs and checkout flows. The trade-off is that it's designed for human-present commerce. It doesn't natively address machine-to-machine payments, micropayments, or stablecoin-native settlement.

What is AP2 (Agent Payments Protocol)?

AP2 is an open protocol developed by Google with more than 60 organizations, including Adyen, American Express, Mastercard, PayPal, Coinbase, Revolut, and Worldpay. It works as an extension of Google's Agent2Agent (A2A) protocol and the Model Context Protocol (MCP).

AP2 solves the trust and authorization problem for agent payments. Its core mechanism is the Mandate - a tamper-proof, cryptographically signed (ECDSA) JSON-LD object that serves as verifiable proof of a user's payment instructions. AP2 defines three mandate types: Intent Mandates (conditions under which an agent can purchase), Cart Mandates (explicit user authorization for specific items and prices), and Payment Mandates (shared with payment networks to signal agent involvement).

AP2 supports two transaction modes: real-time purchases where the human approves a Cart Mandate with a cryptographic signature, and delegated tasks where the human signs an Intent Mandate upfront and the agent acts autonomously later. In collaboration with Coinbase and MetaMask, Google launched the A2A x402 extension for agent-based crypto payments.

AP2's strength is its comprehensive authorization and audit framework. The trade-off is that AP2 is a framework, not a payment rail - it defines how agents get permission to pay, not how the money moves.

What is x402?

x402 is an open payment protocol created by Coinbase that enables instant stablecoin payments over HTTP by reviving the 402 status code. When a client requests a paid resource, the server responds with HTTP 402 and payment instructions (amount, currency, destination wallet). The client signs a payment, attaches it to the request header, and gets the resource. No accounts, no sessions, no API keys.

x402 V2 launched in December 2025 with wallet-based identity, dynamic payment recipients, and multi-chain support. The x402 Foundation, co-governed with Cloudflare, was launched in September 2025. Stripe integrated x402 for USDC payments on Base in February 2026. The protocol supports Base, Ethereum, Polygon, Solana, Avalanche, Sui, and other chains, with zero processing fees beyond on-chain gas.

x402 is ideal for machine-to-machine payments like API calls, data feeds, compute resources, agent-to-agent services. The trade-off is that it's stablecoin-only and doesn't handle physical goods commerce.

ACP vs. AP2 vs. x402: a head-to-head comparison

Protocol type and layer

  • ACP: Checkout and merchant integration layer - defines how agents browse, select, and purchase from merchants
  • AP2: Authorization and trust layer - defines how agents get cryptographically verified permission to transact
  • x402: Execution and settlement layer - defines how payments are made instantly over HTTP using stablecoins
  • Crossmint: Unified platform supports major agentic payment protocols through a single API, alongside agent wallets, virtual cards, and stablecoin infrastructure

Payment methods supported

  • ACP: Traditional payments via Stripe (cards, bank transfers, digital wallets); PayPal integration coming; fiat-only today
  • AP2: Framework supports cards, bank transfers, real-time payments, and stablecoins (via A2A x402 extension); payment-rail agnostic
  • x402: Stablecoin-native (USDC primary); supports Base, Ethereum, Polygon, Solana, Avalanche, Sui, and other chains; zero processing fees (only onchain gas)
  • Crossmint: Fiat and major stablecoin payments; supports 50+ blockchain networks; bridges fiat and crypto in a single agent transaction

Transaction model

  • ACP: Human-present conversational checkout - agent helps user complete a purchase inside a chat interface (e.g., ChatGPT)
  • AP2: Both human-present (Cart Mandate with real-time approval) and human-not-present (delegated Intent Mandate for autonomous agent action)
  • x402: Fully autonomous machine-to-machine - agent sends HTTP request, receives 402 response with payment terms, signs and pays, receives resource
  • Crossmint: All of the above. Agents can transact autonomously (via x402/stablecoins), with user approval (via AP2-style mandates), or through conversational checkout, using Crossmint's agent wallets with programmable guardrails

Production readiness

  • ACP: Launched in ChatGPT Instant Checkout (February 2026); OpenAI pivoted to app-based model in March 2026; protocol remains open standard with Stripe, Shopify, Salesforce, and PayPal support
  • AP2: Specification published; industry coalition formed; A2A x402 extension is production-ready for crypto payments; broader card-based implementation still maturing
  • x402: V2 launched December 2025; Stripe integrated x402 on Base in February 2026; Cloudflare supports x402 transactions
  • Crossmint: Agent wallets, virtual cards, and x402 support live in production; launched lobster.cash as an open payment standard for OpenClaw agents (powered by Visa, Circle, Solana, and Stytch)

Pricing model

  • ACP: Stripe processing fees apply (typically 2.9% + $0.30 for cards); merchants remain merchant of record
  • AP2: No protocol fees; underlying payment processor fees apply
  • x402: Zero protocol fees; users pay only blockchain gas fees (fractions of a cent on L2s like Base)
  • Crossmint: Usage-based pricing; contact sales for enterprise terms

Ideal use cases

Use ACP for shopping agents that interact with merchant catalogs. If your agent helps users discover and purchase physical or digital goods and you want a standardized protocol for agent-merchant communication with Stripe handling payment processing, ACP provides that foundation. OpenAI's early pivot from in-chat checkout to app-based purchasing shows the protocol is still finding its production form, but the merchant ecosystem support from Stripe, Shopify, Salesforce, and PayPal is real.

Use AP2 for enterprise multi-agent systems that need auditable authorization. If your agents operate across platforms, interact with multiple payment networks, or need to prove that a specific human authorized a specific purchase, AP2's cryptographic mandate system provides the compliance infrastructure. The A2A x402 extension makes AP2 the natural choice for enterprises that want both traditional and crypto payment support under one authorization framework.

Use x402 for the machine economy. If your agents pay for API calls, data feeds, compute resources, or services from other agents, x402's HTTP-native stablecoin payments are the most efficient path. The zero-fee model (beyond minimal gas costs on L2s) makes x402 uniquely suited for high-frequency, low-value transactions.

The practical challenge is that production agent systems often need elements of all three. An agent that shops for users needs ACP's checkout flow, AP2-style authorization when acting on delegated authority, and x402 when paying another agent for a data lookup. That's three protocol integrations, three sets of wallet infrastructure, and three compliance surfaces to manage.

Why platforms choose Crossmint for agentic payments

The protocols above define how agents should pay. Crossmint provides the all-in-one agentic payments infrastructure to make it happen. Rather than picking one protocol and building around it, Crossmint gives your agents everything they need to transact like through a single API:

  • Agent wallets - Fiat and stablecoin wallets purpose-built for AI agents. Non-custodial stablecoin wallets with programmable guardrails (spending limits, merchant whitelisting, approval requirements, auditable logs). Virtual card wallets that hold tokenized card details securely without exposing raw card data.
  • Agent virtual cards - Derive virtual card numbers from your existing Visa or Mastercard, letting agents pay at any merchant that accepts cards. Scoped permissions and guardrails control spending limits, merchant access, and transaction caps.
  • Stablecoin onramps - Fund agent wallets by connecting any major debit or credit card, including Visa and Mastercard. Top up virtual cards or stablecoin wallets directly. Fiat payments supported globally, stablecoin onramps available in 150+ countries.
  • Agentic checkout - APIs for agents to purchase physical goods, software, flights, and more. Support for Amazon, Shopify, and other major merchants at retail price. Crossmint acts as Merchant of Record and handles returns and chargebacks - zero operational overhead.
  • Agentic credentials - Verifiable credentials built on open-source W3C standards. Agents can prove they act on behalf of a specific user or hold certain affiliations. Any third party can verify them, enabling trust across platforms without centralized identity providers.
  • Secure by design - Agent wallets are purpose-built with a dual key architecture to balance security, autonomy, compliance and ease of use. Humans set spending permissions and approve transactions; agents can only request payment actions within those guardrails.

We also created lobster.cash alongside Visa, Circle, Solana, and Stytch to provide an open payment standard for OpenClaw agents.

As new payment protocols emerge and mature, Crossmint's multi-protocol architecture and all in one agentic payments infrastructure means your integration doesn't need to change. You can build with one API surface and gain support for new standards as they go live.

Building an agentic product or platform? Reach out to us here and we can help you bring your agents onto agentic payment rails.

FAQs

What's the main difference between ACP, AP2, and x402?

They operate at different layers of the payment stack. ACP (OpenAI/Stripe) standardizes the checkout flow between agents and merchants. AP2 (Google) standardizes the authorization and trust framework. x402 (Coinbase) standardizes the settlement layer using stablecoins over HTTP. In practice, they're complementary: an agent system might use AP2 for authorization, ACP for e-commerce checkout, and x402 for machine-to-machine payments.

Which agent payment protocol is most production-ready?

x402 has the most production traction - V2 launched December 2025, Stripe integrated x402 on Base in February 2026, and Cloudflare supports x402 transactions. ACP launched in ChatGPT's Instant Checkout but OpenAI pivoted to an app-based model within weeks. AP2's A2A x402 extension is production-ready for crypto, but broader card-based implementations are still maturing. Crossmint allows you to access all production-ready agent payment protocols through a single API.

Do I need to support all three protocols?

It depends on what your agents do. If they only shop for users, ACP may be sufficient. If they only pay for APIs, x402 alone works. But agents that operate across multiple domains will likely need elements of all three. Crossmint's unified API lets you support multiple protocols through a single integration.

Is there a platform that supports all agent payment protocols?

Crossmint provides a unified API surface that supports x402 for stablecoin payments today, with multi-protocol architecture designed to support ACP and AP2 as they mature. Beyond protocol support, Crossmint adds embedded agent wallets with programmable guardrails, virtual Visa and Mastercard cards for traditional commerce, and a security model that keeps sensitive payment data out of the agent's context.

‍