AI Technology03-10-20267 min read

The Chargeback Arms Race

Chargebacks are heading for 337 million a year, most of them aren't real fraud, and each one costs a multiple of its face value. A practical look at the six AI jobs hiding in one dispute, what each of them needs to be governed, and why agentic commerce will change the volume.

Paul Coerkamp
Paul Coerkamp
CEO & Co-Founder
The Chargeback Arms Race

Chargebacks rarely make the agenda of an AI strategy meeting, and I think they deserve a place on it. For card issuers, acquirers and merchants a dispute is a cost line, an operations burden and a customer experience problem all at once, and the volume keeps growing.

In this article I'll look at why dispute volumes are rising and why most disputes have nothing to do with fraud. Then I'll break the dispute lifecycle into six jobs that AI can take over today, and for each job describe what needs to be governed. In payments, that governance is usually what decides whether a project succeeds.

Key message: Most chargebacks start as a communication failure. Communication can be automated, while judgment has to stay with people.

The problem in three numbers

Research commissioned by one of the card networks projects that chargeback volumes will reach 337 million in 2026, up 42 percent from 2023. Visa estimates that up to 75 percent of chargebacks are first party misuse, meaning real customers disputing real purchases rather than criminals. And the latest LexisNexis True Cost of Fraud study puts the total cost at more than five dollars for every dollar lost, once fees, labor, lost goods and churn are counted.

The paper war, in three numbers

Every party in the chain pays for this. The cardholder waits weeks for an answer, and the merchant loses the sale, the goods and a fee on top. Issuers and acquirers keep large back office teams busy exchanging evidence with each other. Even when a dispute is won, everyone involved ends up worse off than before it started.

Why most disputes are not fraud

If three quarters of disputes are first party misuse, then most of what runs through the "fraud" pipeline is a communication problem. Typical causes are a merchant descriptor the customer does not recognize, a subscription that renewed after a free trial, a family member who used the card, or a refund that took so long that the customer went to the bank instead of the merchant.

None of these involve a criminal. Still, the moment the customer taps "dispute this charge", each of them turns into a formal, regulated case that can run for weeks. Banking apps have made that tap very easy, and the process behind it has hardly changed.

The card schemes see this too, and their rules are moving toward evidence. Visa's Compelling Evidence 3.0 lets merchants counter friendly fraud claims with prior purchase history, device data and delivery proof. Winning a dispute therefore depends more on data and less on argument.

Six AI jobs in one dispute

Mapped from start to finish, a dispute contains six jobs. Each of them can be automated today, and each needs its own controls.

Six AI jobs hiding in one dispute

Before a case exists: recognize and deflect

The cheapest chargeback is one that never becomes a case. A customer asks "what is this charge?" and the assistant resolves the descriptor to a merchant name, shows the receipt and asks whether someone else in the household might have made the purchase. We think this first job, recognition, has the highest return in the whole chain. It only works if answers come from verified transaction and merchant data; the assistant should never guess who a merchant is.

Sometimes the customer does want their money back. A refund arranged between issuer and merchant in near real time costs a fraction of a formal dispute, and the alert and mediation networks for that already exist. What tends to be missing is the conversation that guides the customer there. This second job, deflection, comes with a firm rule. The customer's right to dispute must never be obstructed, so deflection can offer a better route but may not block the formal one.

Intake

If a dispute has to be filed after all, the quality of the intake decides much of the outcome. Structured questions get the reason code right the first time, record exactly what the customer claims and pick up first party signals. A wrong reason code at intake can lose a case months before anyone reviews it. Two things need to be governed here. The regulatory clock has to start at the right moment, and the reason code logic has to be versioned, so that every decision can be traced back later.

Triage, evidence and learning

Disputes differ in how much attention they need. Scoring on dispute history, delivery confirmations and device data separates the clear cases from the ambiguous ones, and investigators can spend their time where judgment is needed. Triage should never lead to automated denials, and the scoring needs monitoring for bias, since a supervisor will want to know which customers get the benefit of the doubt.

On the merchant and acquirer side, representment is document work under a deadline: prior purchases, logins and delivery confirmations, formatted to each network's requirements. The controls are simple to state. Use only evidence the scheme accepts, and make every document traceable to its source system.

The sixth job is learning. Each closed dispute holds a lesson that rarely gets used. Root cause analysis per merchant and per descriptor, fed back into descriptor fixes and merchant coaching, stops the same confusion from producing the same disputes again (provided every root cause has a clear owner, otherwise the insights never turn into changes).

Taken together, the six jobs describe a case, which is something quite different from a conversation. A dispute runs for weeks, touches several systems and ends in something an auditor can reconstruct. The same thinking applies before any dispute exists: a proactive confirmation call about a suspicious transaction today prevents a dispute next month.

The regulatory clock

Disputes run on deadlines set outside the organization. In Europe, PSD2 requires a payment service provider to refund an unauthorized transaction no later than the end of the following business day, unless it has reasonable grounds to suspect fraud and reports them to the authorities. In the United States, Regulation Z gives card issuers 30 days to acknowledge a billing error and two complete billing cycles, never more than 90 days, to resolve it. The card schemes add their own deadlines for every stage.

For AI this has a direct consequence. Deadlines cannot live in a prompt or depend on someone remembering them. The system that runs the case has to enforce them and escalate when one comes close.

What agentic commerce will change

One development is worth preparing for now. The card networks are introducing agentic payments, where AI agents shop and pay on behalf of a customer. The dispute infrastructure for those payments is not ready yet, and the industry has started to say so.

A purchase made by an agent is, by definition, one the customer did not make personally. The confusion that drives most chargebacks today will therefore occur far more often. On top of that, the consumer AI that makes purchases can also draft and file disputes.

We expect that within two years a double digit share of disputes will be written by software. Manual dispute operations will not scale to that volume. The logical response is to run the six jobs above as governed cases, with automation handling the volume and people making the decisions.

Four principles for governing dispute AI

The general governance rules for AI in banking apply here in their strictest form:

  1. A named person makes the final decision. An AI that automatically denies valid disputes creates a compliance incident, whatever it saves in efficiency.
  2. Deadlines are enforced by the system. Provisional credit and scheme timelines are hard constraints.
  3. Triage models are monitored, both for accuracy and for how they treat different groups of customers.
  4. Every step is logged. In a dispute the audit trail serves compliance and, as Compelling Evidence 3.0 shows, also forms the evidence itself.

Chargebacks will not disappear. The share that exists only because nobody explained a charge can shrink considerably, though, and the remaining disputes can be handled faster and with better evidence. If your team is working on dispute operations, we'd be glad to walk you through how these six jobs run on one governed platform. You can reach us here.

Updated on 12 October 2026.

Paul Coerkamp
Paul Coerkamp
CEO & Co-Founder
Writes about Business Strategy, Enterprise Sales, AI Implementation, Startup M&A
Paul Coerkamp on LinkedIn
Published on 03-10-2026

Related Articles

9 Things I Really Hate About AI
AI Technology12-05-2025

9 Things I Really Hate About AI

I think it's great that technology is so embedded in our daily lives. It helps us get knowledge faster, finish tasks more efficiently, gives us inspiration, and occasionally scares the hell out of us with those crazy (fake) videos. I help a lot of companies implement AI, so in the end it pays my bills. But after spending a ridiculous amount of time with all these new technologies, it's time to write down the things I really hate about AI.

Read More →
A Conversation Is Not a Case
AI Technology06-10-2026

A Conversation Is Not a Case

The 95 percent pilot failure stat is making the rounds again, this time with a diagnosis I actually agree with: chatbots automate sessions, but a bank runs cases. Why the unit of work decides whether your AI survives production, and the day eight test that shows which one you built.

Read More →
Agentic AI Languages and Dialects: Why Voice Quality Is Still the Hard Part
AI Technology10-04-2026

Agentic AI Languages and Dialects: Why Voice Quality Is Still the Hard Part

Agentic systems promise autonomous workflows, but speech and dialect quality fail first. Why Arabic, Turkish, Chinese and more run into the same gap.

Read More →

Stay Updated

New posts on conversational AI, enterprise automation and customer experience, sent to your inbox when they go live

No spam, unsubscribe at any time