A customer rejects a charge. The purchase was made by an AI agent. The bank now has to decide what happened, and the approval record it holds answers only one of the three things the customer may be saying.
Three Disputes That Look Alike
An agent purchase can be contested in three ways, and each calls for different evidence.
- "I did not authorise this." This is the classic fraud claim. A record that the customer approved this amount and this payee answers it.
- "I authorised the agent, and it bought the wrong thing." This is agent error. The approval record does not answer it, because the customer did approve.
- "I authorised it, and now I say I did not." This is first-party fraud, also called friendly fraud. The approval record answers it only if it shows what the customer actually asked for.
At the dispute desk all three arrive as the same message, a cardholder who rejects a charge.
The Agent That Buys Anyway
The second dispute is not a rare edge case. On 5 November 2026 Visa published a benchmark in which 22 AI models from 12 labs worked through 15 shopping tasks, three attempts each. The models passed 57.2 percent of the runs. About 54 percent of the failed runs still ended in a purchase. Either the product did not meet the requirements the customer had stated, or the agent had not uncovered all of them before it bought.
The test covered the buying decision and stopped before checkout. Visa says it will extend it to checkout, payment and order placement. Our reading is that every one of those failed purchases could have been made by a registered agent with a valid credential and a customer approval. Nothing in the payment would have looked wrong.
The Claim Nobody Can Check
The third dispute grows with the second. American Banker reported on 6 November 2026 that first-party fraud is rising and could worsen as agentic commerce spreads. A fraud analyst quoted there expects some customers to claim that they never authorised an agent when in fact they did. She names audit logs, read together with transaction history and dispute patterns, as the material that separates a legitimate dispute from an attempt to defraud.
An approval record protects the bank against the first dispute. Only a record of what the customer asked for can decide the second and the third.
What the Card Networks Are Building
The networks have seen the gap, and their answers are on the public record.
Mastercard introduced Verifiable Intent on 5 March 2026, co-developed with Google. It links three things in one record, the cardholder who authorised the agent, the instructions the customer gave, and the interaction between agent and merchant that led to the purchase. Mastercard says that in a dispute all parties can rely on that audit trail, and that details are disclosed only as far as the dispute requires.
At the end of April 2026 the FIDO Alliance took Google's Agent Payments Protocol and Mastercard's Verifiable Intent into its standards work. Its payments working group is chaired by members from Mastercard and Visa. On 26 May 2026 the Alliance's chief technology officer listed among the aims better dispute resolution through structured, portable evidence of user intent, which issuers, networks and merchants can validate without relying on proprietary logs. The post names no delivery date.
On 30 September 2026 Mastercard added a probability score that indicates how likely it is that a transaction was initiated by an AI agent. It is rolling out for testing in the United States. The score tells an issuer that an agent was involved. It does not tell the issuer what the customer asked that agent to do.
American Express announced on 14 April 2026 that it will in future protect eligible card members against charges caused by agent error, where the card member has authorised the agent and the agent has sent American Express the customer's authenticated purchase intent. The announcement gives no start date and says terms will apply.
The first live case arrived on 12 November 2026. Travelport, Booked AI, Basis Theory and Mastercard reported a flight purchase in which the customer's approval was linked to the transaction through Verifiable Intent, so that a payment that did not match the approval would not have gone through. That purchase is part of the comparison in How Autonomous Agents Execute Payments.
What Is Still Missing
None of these announcements says that a card network's dispute rules have changed. They describe evidence. They do not yet say who must accept that evidence, within which deadline, and with what effect on a chargeback.
The second gap is the content of the record. The flight announcement states that the customer approved the booking and the amount. It does not say whether fare rules, change conditions or refund terms were part of what was approved. Those are the points on which a travel dispute usually turns.
The third gap is the way back. An agent that can buy on a mandate has no standard way to return, claim or reverse on the same mandate. That is the Undo Architecture described in How Autonomous Agents Execute Payments, and no announcement in this analysis closes it.
What to Settle Before the First Dispute
Issuers, merchants and agent operators can decide four things today, whatever standard prevails.
- Keep the customer's instruction and not only the approval. The wording of the request, its limits and its time are what the second and third dispute turn on.
- Record what the agent was shown and what it chose, including the price and the conditions attached to the offer.
- Decide which of the three disputes you will accept without evidence and which you will contest, before the first one arrives.
- Agree who holds the record and for how long. Size the retention to the dispute window and not to the default of your logging.
A wallet with a spending cap does not answer any of this, as A Price Cap Is Not an Amount sets out. The cap limits the loss. It does not tell anyone whether the purchase was the one the customer wanted.
contraco helps issuers, merchants and agent operators define the evidence a dispute will need before the first one arrives. The conversation starts at transformation@contraco.net.