Niches · Agent checkout protocols
Produce evidence of what the person approved when a purchase is disputed
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A record the merchant or issuer can read that names the person's approval (items, amount, merchant, time, the person's own words where kept), the agent and platform, and maps to a documented dispute reason.
How agents ask for it: I never asked for this, refund it
, show what I approved
, the agent bought the wrong thing
Does the job, with a limit 5
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| American Express Agentic Commerce Experiences (ACE) F American Express Company | Agent Purchase Protection terms cover purchases that deviate from the Card Member-authenticated intent sent by a registered agent, excluding subjective intent such as 'best'. It is described as a future benefit, full terms are not published and no registered agent is listed yet. source |
| Agent Payments Protocol (AP2) C Google LLC | Closed mandates record signed items, amount, payee and merchant, but v0.2 removed the Intent Mandate and its natural-language description that v0.1 named as dispute evidence (acc-11, open), and no dispute reason mapping is given. source |
| Mastercard Agent Pay E Mastercard | Verifiable Intent's selective disclosure is described as proof of intent for dispute resolution, and existing chargeback rights apply. No Agent Pay dispute reasons or liability rules are published, and open issue 37 asks whether a purchase must match what the user asked (acc-16). source |
| Universal Commerce Protocol (UCP) BB UCP Authors (Google, Shopify and co-developers) | Mandates in the AP2 extension are stored as evidence of user consent and the UCP-Agent profile names the platform, but no mapping to dispute reasons or liability is given. source |
| Visa Intelligent Commerce D Visa Inc. | The agent reports purchase outcomes as commerce signals, which with the passkey-signed instruction are used to resolve disputes, but no dispute reasons or liability rules for agent purchases are published. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Agentic Commerce Protocol (ACP) C OpenAI and Stripe | Refund semantics are out of scope of delegate payment, intent traces record why a session was cancelled, not what was approved, and the order carries no required agent or platform identity (acc-07, open). source |
What stops agents finishing
- the spec dropped the intent record that dispute rules relied on
- no required agent identity on the order
Around it
Before: checkout-protocols.buy-for-person, checkout-protocols.delegated-purchase. After: payment-platforms.refund-and-dispute.
Where this comes from
Weight 12 of 100 in Agent checkout protocols: 3 of 18 accounts (acc-07, acc-10, acc-11); issues about evidence are open on ACP and AP2 but no dispute outcome was reported
The same as data: /api/v1/use-cases/checkout-protocols.dispute-evidence.json, or the MCP tool get_use_case with id checkout-protocols.dispute-evidence. Other jobs in this category: /api/v1/niches?category=checkout-protocols.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.