# Produce evidence of what the person approved when a purchase is disputed

> Produce evidence of what the person approved when a purchase is disputed: 0 companies fully do it, 5 with a limit, 21 carry the tag. Every listing in Agent checkout protocols with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/checkout-protocols.dispute-evidence/
- Markdown: https://www.anchorterminal.com/niches/checkout-protocols.dispute-evidence/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/checkout-protocols.dispute-evidence/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/checkout-protocols.dispute-evidence/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 5 | 21 | 12 | 3 |

## 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

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.

- **American Express Agentic Commerce Experiences (ACE) (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.
- **Agent Payments Protocol (AP2) (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.
- **Mastercard Agent Pay (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).
- **Universal Commerce Protocol (UCP) (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.
- **Visa Intelligent Commerce (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.

- not this job: Agentic Commerce Protocol (ACP) (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).

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/checkout-protocols.dispute-evidence.json, or the MCP tool get_use_case with id checkout-protocols.dispute-evidence. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
