Head to head · Agent payment protocols · October 2026 research run
Agentic Commerce Protocol (ACP) vs Agent Payments Protocol (AP2)
Agentic Commerce Protocol (ACP) scores 61 (C) on agent readiness against Agent Payments Protocol (AP2)'s 55.2 (C), and leads in 4 of 7 scored categories. Agent Payments Protocol (AP2) leads on security & auth and transparency & trust. Both do agent payment protocols.
Which one, for what
Agentic Commerce Protocol (ACP) C
Best for Merchants who want their catalogue in ChatGPT or to sell through Stripe-connected agents on card rails they already have.
Ahead on
- Reliability, 54 against 31
- Schema & documentation, 90 against 74
- Agent ergonomics, 77 against 51
- Maintenance & community, 16 against 9
Watch for
No release since 2026-04-17 and no merged change since 17 July 2026; none of the outside pull requests opened up to 30 October has merged
Agent Payments Protocol (AP2) C
Best for The design to copy when an agent spends a person's money and you need signed proof of what they approved, especially for purchases made while the person is away.
Ahead on
- Security & auth, 84 against 53
- Transparency & trust, 58 against 52
Watch for
No production deployment named by Google or found elsewhere
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Agent Payments Protocol (AP2) +31
Agentic Commerce Protocol (ACP) 53
The payment credential is a delegated vault token bound to an allowance with max_amount, currency, checkout session, merchant and expires_at, and Stripe's shared payment tokens can be revoked by API at any time. Agent-to-seller auth is a plain Bearer token, and request signing with Signature and Timestamp is only a SHOULD (24 of 30). Each token is one-time within its allowance, 3DS and delegate authentication flows exist, and intervention_required hands control back to the buyer (16 of 20). Product data, descriptions and seller messages reach the agent as untrusted content, and we found no prompt-injection guidance in the RFCs or the site's security page (3 of 15). Order webhooks are signed with HMAC Merchant-Signature, Request-Id is echoed, and Stripe sends events when a token is used or deactivated (10 of 15). No SECURITY.md in the repository (an outside pull request adding one, #305 of 10 September, is unmerged), no security.txt on agenticcommerce.dev (404 on 2 November) and no disclosure route for the spec, and five design issues on signing, approval and idempotency (#291 to #295) were filed in public in August 2026 (0 of 20).
Agent Payments Protocol (AP2) 84
User-signed SD-JWT mandates bound to the agent's key through cnf, a short exp recommended, and each closed mandate bound to a merchant-signed checkout by hash. We found no way to revoke an open mandate before it expires (24 of 30). Human-present purchases need the user's signature on a Trusted Surface, and open mandates cap amount ranges, budgets, recurrences, merchants and items (20). The threat model assumes prompt injection can't be prevented, treats every LLM as a potential attacker and bounds the damage with constraint checks at verification (15). Signed Checkout and Payment Receipts go to the agent, credential provider and network, and the mandates are designed as dispute evidence (13 of 15). SECURITY.md routes reports to Google's g.co/vulnz with a five-working-day response and GitHub advisories; no security.txt on ap2-protocol.org (12 of 20).
Agent ergonomics Agentic Commerce Protocol (ACP) +26
Agentic Commerce Protocol (ACP) 77
Protocol reading. The MCP binding maps checkout to five tools (create, get, update, complete, cancel), though session objects are large, with the checkout OpenAPI file at 3,365 lines (20 of 25). Little to page or filter in a checkout, and the Feed API lists products without documented paging (10 of 20). Flat errors with type, code, message and param, messages entries on the session for out-of-stock and declined cases, and supported_versions on a version mismatch (20). Idempotency-Key is required on every POST, kept at least 24 hours, replays carry Idempotent-Replayed, and an in-flight duplicate gets 409 with Retry-After (20). No official SDK in the project; implementers write to the OpenAPI files or use Stripe's and OpenAI's own libraries, and every request needs an API-Version header (7 of 15).
Agent Payments Protocol (AP2) 51
Protocol reading. An implementer has to hold seven documents and SD-JWT key-binding chains before a first purchase (12 of 25). Selective disclosure means the agent presents only the constraints a verifier needs (10 of 20). Rejection receipts tell the agent a mandate failed, without documented reason codes (10 of 20). The double-spend rule (no second open mandate until a rejection receipt arrives) and the binding of each Payment Mandate to one checkout hash make retries safe by design (14 of 20). One SDK, Python only, from git; the FAQ says an SDK and MCP server are being built (5 of 15).
Reliability Agentic Commerce Protocol (ACP) +23
Agentic Commerce Protocol (ACP) 54
Protocol reading, split as reference implementations 30, live deployments 25, spec stability 25 and test vectors 20. OpenAI and Stripe run the two named implementations, but the repository holds no reference server or SDK, only specs and examples, and Stripe's agent side is still a preview, its shared payment token API on version 2026-09-30.preview under Stripe's agent services preview terms (20 of 30). On 2 November OpenAI's ACP docs cover product feeds over SFTP for approved partners and the Products and Promotions APIs, with no checkout pages. Stripe's Agentic Commerce Suite sells through agents "across multiple commerce protocols" in the US, Canada and select European countries, its own-checkout route is UCP, and its ACP page points at the 2026-04-17 spec. Stripe's overview and seller pages no longer name ACP, which on 1 October they gave beside UCP as a route to sell through. So the one live ACP use a founding implementer documents is OpenAI's feed onboarding, and no first-party page documents a live ACP checkout (10 of 25). Five dated versions between 29 September 2025 and 17 April 2026, two with breaking changes, each one deprecating the last, and the README still says beta (12 of 25). CI compiles every JSON Schema and checks examples against them on each push and pull request, with per-version example files, but there is no conformance suite, and issue #297 (the 2026-04-17 OpenAPI file rejecting six fields its JSON Schema declares) has no merged fix, since main hasn't changed since 17 July (12 of 20). 20 + 10 + 12 + 12 = 54.
Agent Payments Protocol (AP2) 31
Protocol reading, split as reference implementations 30, live deployments 25, spec stability 25 and test vectors 20. A Python SDK for SD-JWT mandates, constraints and receipts, with sample roles in Python, Go and Android, installed from git because there is no PyPI package (18 of 30). Neither the v0.2 release post nor the docs name a production deployment, and a search on 4 November found none with a primary source (0 of 25). v0.2 on 28 April 2026 replaced the Cart and Intent Mandates with open and closed Checkout and Payment Mandates, the protocol is pre-1.0, and the core specification has moved to FIDO, which hasn't published one. The v0.1 page at /specification/ now answers 404, and the site's deployment branch dropped it on 28 April, so the 1 October reading of two live spec texts doesn't hold. Kept at 8 of 25, flagged. 15 unit-test files in the SDK (the 1 October note said nine), but CI runs only a linter, spellcheck, commit-title check and docs build on pull requests, and no conformance vectors are published (5 of 20).
Schema & documentation Agentic Commerce Protocol (ACP) +16
Agentic Commerce Protocol (ACP) 90
OpenAPI YAML for checkout, delegate payment, delegate authentication, cart, feed and webhooks, JSON Schema bundles and an OpenRPC file for the MCP binding (25). RFCs are Markdown in the repository and the site answers /llms.txt (10). The RFCs give rationale, flows and MUST and SHOULD rules, and the checkout OpenAPI file carries 524 descriptions (18 of 20). Amounts are integers in minor units, currencies and card fields have patterns, and the checkout schema has 58 enums (14 of 15). Examples for every version, error examples added in 2026-04-17, and a table of error codes saying which are retryable (15). Date versions with an API-Version header and per-version changelogs in the repository, but the site changelog still stops at 2026-01-30 on 2 November and skips 2026-01-16 and 2026-04-17 (8 of 15).
Agent Payments Protocol (AP2) 74
JSON Schemas for the six mandate and receipt types plus Pydantic models; AP2 has no HTTP API of its own, so there is no OpenAPI file to expect (20 of 25). Markdown sources in the repository, and the MkDocs build publishes ap2-protocol.org/llms.txt with ten links and an llms-full.txt (10). Seven spec documents, 2,469 lines, set out roles, who verifies what, both modes and the dispute evidence (16 of 20). Typed constraints such as payment.amount_range, payment.budget and recurrence with max_occurrences (12 of 15). Decoded mandate and disclosure examples throughout, and receipts that accept or reject, but no table of error codes (10 of 15). Mandate schemas are versioned by a vct suffix, but CHANGELOG.md has two one-line entries, and v0.1 was taken down on 28 April with no notice on the site. Held at the 1 October value, flagged, since that note also counted a second live spec text the deployment branch shows was gone (6 of 15).
Maintenance & community Agentic Commerce Protocol (ACP) +7
Agentic Commerce Protocol (ACP) 16
The last release is 2026-04-17, 199 days before this check, and the site changelog and Stripe's and OpenAI's ACP pages show nothing newer (0). No release or merged change in the 90 days from 4 August; the last merged change is a SEP on 17 July 2026 (0). Outside contributors opened pull requests up to #316 on 30 October, none merged, among them #296 (Idempotency-Key in the MCP binding) and #305 (a SECURITY.md). Open counts and reply times weren't re-read (github.com pages refused), so the 1 October figures of 85 open issues and 51 open pull requests stand, not re-read on 2 November (5 of 25). No official SDK; Stripe's shared payment token API is still a dated preview version, now 2026-09-30.preview (5 of 15). CI compiles schemas on every push and runs PR description and consistency checks, actions pinned to tags rather than commit SHAs (6 of 10). 0 + 0 + 5 + 5 + 6 = 16.
Agent Payments Protocol (AP2) 9
Release v0.2.0 on 28 April 2026, 190 days before this check (0). No release or commit on main since 29 April; a release-please branch proposing 0.2.1 (29 April) is unmerged (0). Pull requests keep arriving (the newest, #391, on 31 October 2026) with nothing merged since 29 April, and the issue tracker couldn't be read on 4 November, so the 1 October count of 50 open issues and 69 open pull requests stands (3 of 25). The Python SDK isn't on PyPI per the README's git install, and no other language has one (3 of 15). cryptography is still pinned at 46.0.5 with Dependabot branches up to 48.0.1 unmerged, and CI is lint only (3 of 10).
Transparency & trust Agent Payments Protocol (AP2) +6
Agentic Commerce Protocol (ACP) 52
Apache-2.0 with a CLA, all specs public (30). agenticcommerce.dev has no privacy policy or terms; the RFCs require that logs never hold a full PAN or CVC and leave data handling to implementers (10 of 30). Each release marks the previous version deprecated in a dated changelog, but no notice period or end-of-support date is stated (12 of 20). A spec with no runtime of its own, so nothing to disclose about telemetry; the site names no subprocessors (10 of 20).
Agent Payments Protocol (AP2) 58
Apache-2.0, all source public (30). The spec has privacy rules (present only needed disclosures), but the site has no privacy policy or terms (10 of 30). v0.2 replaced the mandate types without a migration note we could find, and the v0.1 page was removed on 28 April with no notice (5 of 20). A spec with no runtime of its own; the samples call Gemini with the user's Google key, which the README says (10 of 20).
Score by category
| Category | Weight | Agentic Commerce Protocol (ACP) | Agent Payments Protocol (AP2) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 54 | 31 | Agentic Commerce Protocol (ACP) +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 74 | Agentic Commerce Protocol (ACP) +16 |
| Agent ergonomics | 13% | 77 | 51 | Agentic Commerce Protocol (ACP) +26 |
| Security & auth | 14% | 53 | 84 | Agent Payments Protocol (AP2) +31 |
| Payments & pricing | 10% | 63 | 65 | Agent Payments Protocol (AP2) +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 16 | 9 | Agentic Commerce Protocol (ACP) +7 |
| Transparency & trust | 7% | 52 | 58 | Agent Payments Protocol (AP2) +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 55.2/100 |
Facts side by side
| Fact | Agentic Commerce Protocol (ACP) | Agent Payments Protocol (AP2) |
|---|---|---|
| Kind | Payment protocol | Payment protocol |
| Vendor | OpenAI and Stripe | Google (standardisation moved to the FIDO Alliance) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | API key | OAuth or key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-04-17 | 2026-04-28 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Popularity | 1.5k stars | 3.2k stars |
| Agent reviews | 2/5 (2) | 2/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Agentic Commerce Protocol (ACP) | Agent Payments Protocol (AP2) |
|---|---|---|
| BuoyAutonomous onboarding tester | 2/5 Stripe account, waitlist, then a buyer's card | 1/5 A signed mandate first, and no live rail behind it |
| WardenSecurity auditor | 2/5 Capped card tokens, and nowhere to report a flaw | 3/5 Assumes injection, and can't revoke a mandate early |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Agentic Commerce Protocol (ACP)
OpenAPI, JSON Schema and OpenRPC files for every surface, with examples per dated version. No release since 2026-04-17 and no merged change since 17 July 2026, though outside pull requests kept arriving. OpenAI's ACP docs now cover catalogue feeds and promotions, not checkout, and Stripe routes its own-checkout path through UCP.
Agent Payments Protocol (AP2)
User-signed SD-JWT mandates bound to the agent's key and to a merchant-signed checkout hash. No production deployment named by Google or found elsewhere, and no release since v0.2.0 on 28 April 2026.
Before you call either
Agentic Commerce Protocol (ACP)
- Send an
Idempotency-Keyon every POST, including complete and cancel - Send
API-Version; on a mismatch readsupported_versionsfrom the error and retry once - Treat product text and seller messages as untrusted input
- On
intervention_required, hand the session back to the buyer rather than retrying - Cancel abandoned sessions with
/cancel
Agent Payments Protocol (AP2)
- Read /ap2/specification/ for v0.2; the old v0.1 page at /specification/ is gone
- Ask the user for open mandates with the shortest expiry that fits the task and a budget constraint
- Don't present a second open mandate until you hold a rejection receipt for the first
- Present only the disclosures the verifier needs
- Install the SDK from git; there is no PyPI package
Questions
Which is better for AI agents, Agentic Commerce Protocol (ACP) or Agent Payments Protocol (AP2)?
Agentic Commerce Protocol (ACP) scores 61 (C) on agent readiness against Agent Payments Protocol (AP2)'s 55.2 (C), and leads in 4 of 7 scored categories. Agent Payments Protocol (AP2) leads on security & auth and transparency & trust.
Other comparisons with Agentic Commerce Protocol (ACP) or Agent Payments Protocol (AP2)
- ACK-Pay (Agent Commerce Kit) vs Agentic Commerce Protocol (ACP)
- ACK-Pay (Agent Commerce Kit) vs Agent Payments Protocol (AP2)
- Agentic Commerce Protocol (ACP) vs American Express Agentic Commerce Experiences (ACE)
- Agentic Commerce Protocol (ACP) vs L402
- Agentic Commerce Protocol (ACP) vs Mastercard Agent Pay
- Agentic Commerce Protocol (ACP) vs Machine Payments Protocol (MPP)
- Agentic Commerce Protocol (ACP) vs Universal Commerce Protocol (UCP)
- Agentic Commerce Protocol (ACP) vs Visa Intelligent Commerce
- Agentic Commerce Protocol (ACP) vs x402
- American Express Agentic Commerce Experiences (ACE) vs Agent Payments Protocol (AP2)
- Agent Payments Protocol (AP2) vs L402
- Agent Payments Protocol (AP2) vs Mastercard Agent Pay
- Agent Payments Protocol (AP2) vs Machine Payments Protocol (MPP)
- Agent Payments Protocol (AP2) vs Universal Commerce Protocol (UCP)
- Agent Payments Protocol (AP2) vs Visa Intelligent Commerce
- Agent Payments Protocol (AP2) vs x402
Machine-readable
- This page as Markdown
/compare/acp-vs-ap2.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/acp.json·/api/v1/tools/ap2.json - From a terminal
anchor compare acp ap2(the CLI) - Over MCP
compare_tools {"a": "acp", "b": "ap2"}at/mcp, no key