# Agent payment dispute-evidence packet

**Version:** 1.0
**Last updated:** 2026-11-19
**Source:** KLA Digital (kla.digital/blog/agent-payment-dispute-evidence)

---

## About this packet

Use this packet when a payment made by an AI agent is disputed and an investigator must state which
assertions the records support, which they contradict and which remain unresolved. It keeps the
instruction, the captured offer, the model input, the final checkout, the authorization and the
receipt as separate records, and gives withheld items and unchecked timing claims their own status.

**Research date:** 26 October 2026.

**Sources read, at these versions:**

- Fernando Henrique D. Milan, _Agent Decision Commitments for Payments_, individual Internet-Draft
  revision 00, dated 15 October 2026, intended status Experimental. An individual draft has no
  standing as an IETF standard. Its implementation status section reports a prototype holder
  implementation that is not publicly available and no interoperability testing.
  <https://www.ietf.org/archive/id/draft-milan-agent-decision-commitment-00.txt>;
  <https://datatracker.ietf.org/doc/draft-milan-agent-decision-commitment/00/>
- Agent Payments Protocol (AP2) v0.2.0 (28 April 2026), specification and security and privacy
  considerations at commit `b4587ac1d055888a73b4b21750973cffba961793`. This pin matches the version
  analysed by the study below; it is not asserted to be the latest release.
  <https://github.com/google-agentic-commerce/AP2/blob/b4587ac1d055888a73b4b21750973cffba961793/docs/ap2/specification.md>;
  <https://github.com/google-agentic-commerce/AP2/blob/b4587ac1d055888a73b4b21750973cffba961793/docs/ap2/security_and_privacy_considerations.md>
- Avital Aviv and colleagues, _Beyond the Mandate: A Systematic Security Analysis of the Agent
  Payments Protocol (AP2)_, preprint, arXiv 2608.23858 version 1 (submitted 24 August 2026).
  Constructed testbed; the authors limit transfer to future implementations and do not measure
  effects on payment rails. <https://arxiv.org/html/2608.23858v1>
- Kayode L. Ogunsusi, _Securing Agentic Commerce Through Behavior-Aware Fraud Detection and
  Cybersecurity for Trusted AI-Agent Payment Authorization_ (ACAGS), arXiv 2610.27483 version 1
  (uploaded 20 October 2026; journal issue dated August 2026). Synthetic transaction data with
  simulated agent characteristics. <https://arxiv.org/pdf/2610.27483v1>
- EMVCo, request for feedback on a draft framework for card-based agentic payments (1 September
  2026), and Q3 2026 newsletter (9 October 2026), which still describes the framework as a draft.
  <https://www.emvco.com/news-publications/emvco-requests-feedback-on-framework-for-secure-interoperable-and-scalable-card-based-agentic-payments/>;
  <https://www.emvco.com/news-publications/emvco-newsletter-q3-2026/>

**Assumptions and limits:**

- This is an editorial investigation template. It is not an ADC message, an AP2 implementation, a
  signed evidence bundle or a legal opinion.
- The Agent Decision Commitments draft states that it establishes the integrity and timing of
  evidence. It leaves open whether recorded inputs were authentic or accurate and whether the
  context receipt is complete, and it does not allocate liability. This packet carries the same
  limits.
- AP2 v0.2 security guidance requires the merchant to verify that `checkout_hash` matches the hash
  of the latest `checkout_jwt`. That check concerns the signed checkout object. An earlier quotation
  captured by the agent is a different object. Checking AP2 checkout matching would require actual
  signed objects and verified roles.
- The fields are not claimed to satisfy the ADC draft's required fields, canonicalization,
  disclosure rules or verification steps. No ADC attestation level is assigned.
- The worked example is invented and was prepared by document inspection only. No payment ran, no
  protocol code ran, and no hash, signature or timestamp was independently verified.
- This packet makes no claim about the legal sufficiency of any record or about the outcome of any
  chargeback or dispute process.

## Case header

| Field                                   | Record |
| --------------------------------------- | ------ |
| Case identifier                         |        |
| Disputed assertion, in one sentence     |        |
| Agent, principal and supplier           |        |
| Amount, currency and spending limit     |        |
| Investigator, role and authorized scope |        |
| Items outside the investigator's scope  |        |
| Clock sources and uncertainty           |        |

## Record table

One row per record. Keep the instruction, the captured offer, the model input, the final checkout,
the authorization and execution request, and the completion receipt as separate rows.

| Record                                                        | Actor and time | Available content | What it supports | What remains open | Verification performed and result |
| ------------------------------------------------------------- | -------------- | ----------------- | ---------------- | ----------------- | --------------------------------- |
| Instruction and requirements                                  |                |                   |                  |                   |                                   |
| Captured offer or quotation                                   |                |                   |                  |                   |                                   |
| Content actually supplied to the model                        |                |                   |                  |                   |                                   |
| Final checkout approved for execution                         |                |                   |                  |                   |                                   |
| Authorization and execution request                           |                |                   |                  |                   |                                   |
| Completion receipt                                            |                |                   |                  |                   |                                   |
| Risk score: model version, inputs, threshold, action informed |                |                   |                  |                   |                                   |
| Withheld or restricted items, with reason                     |                |                   |                  |                   |                                   |
| Commitment or timing observation                              |                |                   |                  |                   |                                   |

Use one of these statuses for each verification entry: `checked: passed`, `checked: failed`,
`not_checked`, `withheld` or `unavailable`. Record each finding separately. "The amount matches",
"the terms differ", "this item was withheld" and "this timing claim was not checked" are four
findings.

## Assertion worksheet

| Assertion | Records relied on | Status: supported, contradicted or unresolved | Smallest additional evidence needed | Owner |
| --------- | ----------------- | --------------------------------------------- | ----------------------------------- | ----- |
|           |                   |                                               |                                     |       |
|           |                   |                                               |                                     |       |
|           |                   |                                               |                                     |       |

For each suspected change, name the actor and the boundary where it may have happened (for example,
"the checkout omitted a required feature, and the approval record contains no feature-level
comparison").

## Worked example: SYN-PAY-001 (synthetic)

All actors, times, values and events are invented.

Operations required export access in a one-year data subscription from a fictional supplier, Example
Data. Maximum spend €500. The agent purchased a €480 tier without export access. The investigator is
a fictional internal operations reviewer authorized to inspect service terms and transaction
records. Personal contact details are outside that reviewer's scope.

Disputed assertion: "The purchased service included export access when the agent authorized
payment."

| Record                       | Actor and time (UTC)                  | Available content                                                     | What it supports; what stays open                                                       |
| ---------------------------- | ------------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| P1 instruction               | Operations manager, 09:00             | Annual subscription, approved supplier, export required, €500 ceiling | States the requirement in this invented case; no authentic identity evidence supplied   |
| P2 quotation Q1              | Captured by agent, 09:02              | €480; export included; expiry 09:05                                   | Shows captured text; supplier origin and capture accuracy unverified                    |
| P3 model input M1            | Agent-side adapter, 09:03             | Selected Q1 text including export and expiry                          | Shows what the example lists; completeness and provider receipt unverified              |
| P4 final checkout Q2         | Fictional merchant, 09:06             | €480; annual Basic tier; export excluded                              | Supports a comparison with P1 and P2 within the example; no merchant signature supplied |
| P5 authorization and request | Agent, 09:07                          | €480 to Example Data; references Q2                                   | Amount and supplier match the budget; the feature requirement conflicts with Q2         |
| P6 completion receipt        | Fictional processor, 09:08            | Q2 paid; €480                                                         | Records fictional completion; no settlement or network confirmation                     |
| P7 contact note              | Operations manager, 09:00             | Item listed; personal contact detail withheld under the scope rule    | Existence visible; contents unavailable to the reviewer                                 |
| P8 commitment observation    | Fictional holder or witness, 09:06:30 | Claimed commitment before P5                                          | Chronology illustrative only; verification status `not_checked`                         |

Assertion worksheet for the example:

| Assertion                                               | Records relied on | Status                                              | Smallest additional evidence needed                                    |
| ------------------------------------------------------- | ----------------- | --------------------------------------------------- | ---------------------------------------------------------------------- |
| The amount was within the spending limit                | P1, P5, P6        | Supported within the example                        | Processor or settlement confirmation                                   |
| The supplier was the approved supplier                  | P1, P5            | Supported within the example                        | Authenticated supplier identity                                        |
| The purchased service included export access            | P1, P2, P4, P5    | Contradicted by P4                                  | None for the contradiction; the supplier's terms history to explain it |
| The agent used the quotation that was valid at checkout | P2, P4            | Unresolved: Q1 expired at 09:05, before Q2 at 09:06 | Supplier offer history; the agent's selection log                      |
| The model received exactly P3                           | P3                | Unresolved                                          | Provider-side receipt of the input                                     |
| A commitment existed before authorization               | P8                | Unresolved: `not_checked`                           | The commitment, its anchor and a recorded verification result          |

### Six variations

These are conditional conclusions from invented records. They are not measured software results or
newly found protocol vulnerabilities.

| Case                    | Change or retained baseline condition            | Supported narrow observation                                  | Conclusion that remains unavailable                               |
| ----------------------- | ------------------------------------------------ | ------------------------------------------------------------- | ----------------------------------------------------------------- |
| Changed amount          | P6 says €520                                     | P6 conflicts with the €480 request and €500 ceiling           | Which actor caused it; whether a real rail would accept it        |
| Expired offer           | Baseline: Q1 expires before Q2                   | The captured offer was time-limited; final terms differ       | Supplier misconduct or automatic invalidity of a payment          |
| Missing input           | Remove P3                                        | The packet cannot expose the listed model input               | That the model never received Q1                                  |
| Delayed timing evidence | P8 time becomes 09:09                            | The illustrative observation follows authorization            | Any independently established earlier commitment                  |
| Misleading source       | Q1 promises a feature the supplier never offered | The packet preserves a false statement by scenario definition | A matching record's truth or authorship                           |
| Restricted detail       | Keep P7 withheld                                 | Reviewer sees an unavailable item and reason                  | Its exact contents or relevance without further authorized review |

## Reader exercise (not yet run)

Give the worked example to an authorized reviewer who did not build it. Ask them to reconstruct the
event using only the rows above, list conclusions as supported, contradicted or unresolved, and
request the smallest additional evidence set. Record the reviewer's role, time spent, requested
items and disagreements. KLA has not run this exercise and reports no comprehension or success
rates.
