Which Agent Payment Protocol Should You Build On? Choose based on the transaction your system needs: x402 is built for paying for an API or other digital resource in an HTTP request flow; AP2 represents what a user authorizes an agent to do; and the Agentic Commerce Protocol (ACP) structures interactions among a buyer, the buyer’s agent, and a business during a purchase. They address different layers of agent commerce, so the right choice is an architecture decision—not a contest with one universal winner.
What is each protocol designed to do?
| Protocol | Best fit | Core interaction | Documented implementation detail |
|---|---|---|---|
| x402 | Charging for an API, data, content, or tool call | A client pays for access to a digital resource within an HTTP request flow. | Solana’s documentation describes PAYMENT-REQUIRED, PAYMENT-SIGNATURE, and PAYMENT-RESPONSE headers; its documented Solana schemes include exact and upto. Support varies by network and client. Solana implementation comparison |
| AP2 | Recording a user’s delegated authority and transaction approval | Signed mandates represent user constraints and approval for a finalized checkout or transaction. | AP2 describes itself as an extension for A2A and UCP, with a credential chain intended to provide auditable evidence. AP2 overview |
| ACP | Connecting a buyer, their agent, and a merchant for a purchase | A structured commerce interaction that can include product discovery, checkout, and secure payment-token handoff. | The repository publishes a checkout OpenAPI specification, JSON schemas, examples, and implementation links. It labels ACP beta. ACP repository |
The distinction is the job being solved: x402 makes a digital resource payable, AP2 captures authorization, and ACP organizes a merchant purchase interaction. A system may need more than one of those capabilities.
As an Amazon Associate I earn from qualifying purchases.
When should you choose x402?
Choose it for request-priced digital access
Start with x402 when an agent or backend needs to pay for an API response, premium content, metered data, or a tool call as part of its request flow. The model is useful when the billable unit is access to a digital resource rather than a full retail checkout.
Coinbase describes its CDP facilitator as verifying and settling payments, and says sellers can receive funds at addresses they control while buyers can pay through a CDP wallet or another signer. Those are statements about Coinbase’s implementation, not guarantees about every x402 deployment. Coinbase x402 overview
#1 Best Overall
Check the implementation details before integrating
- Confirm the network and payment asset the client and service support.
- Check whether the client supports the payment scheme you need; Solana’s documentation lists
exactanduptofor its documented schemes, but support depends on network and client. - Decide whether payment verification and settlement will use a facilitator or local resource-server verification.
- Specify how your application handles failed payment, retries, duplicate requests, refunds, and access granted after settlement.
- Confirm the signing and wallet model for both the paying agent and the service receiving funds.
Coinbase’s overview reports more than 100 million x402 payments processed across Base and Solana, but does not give a measurement window. Treat that as Coinbase’s own reported figure, not an independently verified adoption comparison; the reviewed official AP2 and ACP sources do not provide comparable transaction totals.
When should you choose AP2?
Choose it when delegated authority must be explicit
AP2 is the closer fit when a person delegates purchasing authority to an agent and the system needs to retain evidence of the limits and approvals involved. Its core concepts are Checkout Mandates and Payment Mandates, described as cryptographically signed credentials linked into an audit trail.
Rank #2
Open mandates can carry a user’s constraints before a specific cart or transaction is set. Closed mandates bind approval to a finalized checkout or transaction amount. This distinction helps separate standing instructions from approval of a particular purchase. AP2 overview
Use its accountability claims carefully
AP2’s documentation emphasizes user control, privacy, selective disclosure, and evidence that may help with dispute handling. Its FAQ describes a network adjudicator comparing a user-signed Checkout Mandate with disputed transaction details. That evidence may support review; it is not a promise that a particular dispute will be decided in the user’s favor. AP2 FAQ
AP2 describes itself as payment-agnostic, with cards and stablecoins among the possible payment methods. Its FAQ also discusses an A2A/x402 implementation path and closer alignment between the projects. That makes composition a design consideration, not proof that every AP2 and x402 implementation interoperates today. AP2 FAQ
Validate the live implementation, not just the model
The AP2 documentation presents sample flows and links to specifications, documentation, and an SDK. Its FAQ says the samples mock payment service providers and that an SDK and MCP server were being developed at the time described. Check the current repository release, provider integrations, and implementation status before treating a sample as production-ready. AP2 FAQ
Rank #4
When should you choose ACP?
Choose it for agent-assisted merchant checkout
ACP is designed to connect buyers, their agents, and businesses completing purchases. The repository describes businesses exposing products to agent surfaces, agents supporting discovery and transactions, and payment providers passing secure payment tokens. That makes ACP the most directly relevant option for a structured merchant purchase, rather than charging once for each API or tool request. ACP repository
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check beta status and checkout coverage
The repository identifies ACP as beta and is maintained by OpenAI and Stripe. Its quick links label the 2026-04-17 specification snapshot as the latest stable version in that repository view, alongside unreleased development. That is a snapshot label, not a guarantee that the same version remains current. Verify the repository’s present specification and whether its checkout, payment-handler, commerce-backend, and fulfillment coverage fit your use case.
Best Value
Can you combine x402, AP2, and ACP?
Potentially, where distinct system needs justify separate layers. For example, an agent might need AP2-style evidence of a user’s spending authority and x402-style payment for a digital resource. AP2’s FAQ explicitly discusses x402 compatibility, but the exact versions and end-to-end behavior still need validation. ACP addresses the buyer-agent-business purchase interaction, so it is relevant when the transaction is a merchant checkout rather than a single paid resource request.
Before composing protocols, map which component handles authorization, checkout, payment execution, settlement, and dispute records. Assign each responsibility once, then test the complete path—including rejected payments and interrupted transactions—against the versions and providers you will actually deploy.
How should you make the build decision?
- Define the billable interaction. Is it one digital request, an agent’s authority to spend, or a purchase from a merchant? That answer points first to x402, AP2, or ACP respectively.
- Map the required safeguards. Decide whether you need signed records of user constraints and transaction-specific approval, not just a payment exchange.
- Confirm real provider and rail support. Check the merchant or service, payment provider, network, asset, wallet or signer, facilitator, and geographic availability for your exact deployment. Protocol documentation alone does not establish that a required provider or country is supported.
- Assess the integration surface. Verify the current stable specification, SDK/runtime, examples, production integrations, and governance. In particular, distinguish a sample or beta implementation from a production service you can rely on.
- Design operational recourse. Define how your system handles authorization limits, sensitive-data disclosure, failed or duplicate payments, refunds, fulfillment failures, audit retention, and disputes.
- Test the end-to-end transaction. Validate the exact protocol versions and all participating services together. The available protocol descriptions do not establish comparative cost, latency, security, legal liability, or universal geographic availability.
Which protocol should you build on?
- Build around x402 if the main requirement is pay-per-request access to an API or other digital resource.
- Build around AP2 if the main requirement is representing and auditing what a user permitted an agent to purchase.
- Build around ACP if the main requirement is a structured buyer-agent-merchant checkout interaction.
- Consider composition when the system needs both delegated authorization and a separate payment or commerce interaction, but verify interoperability rather than assuming it.
None of these protocol descriptions, by itself, proves that a particular deployment is secure, available in your market, or ready for your production requirements. Choose by transaction shape, then validate the providers, versions, and operational responsibilities that complete the actual flow.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
