A chargeback is the reversal of a card payment raised by the cardholder's bank, the card issuer, through the card network's dispute process. It usually follows a claim that goods never arrived, were not as described, or that the cardholder did not make the transaction. The money is pulled back from the merchant, who may contest it with evidence.
Why do chargebacks matter once AI agents act?
Agents now sit on both sides of the dispute. Issuers use them to take a cardholder's complaint, check the transaction and prepare the claim. Merchants use them to gather delivery records, order history and correspondence to defend it. Both sides work to the card network's rules, which set the reasons a chargeback may be raised under, the evidence each reason needs, and strict deadlines.
That structure suits agents well, because much of the work is matching facts to rules. It also makes errors costly. A claim filed under the wrong reason, or a defence missing the one document the reason requires, is usually lost and cannot be refiled. The rules on what banks let agents do are in AI agents in banking.
How does a chargeback work in practice?
- The cardholder disputes a transaction with their issuer.
- The issuer checks it and, if valid, raises a chargeback under a specific reason.
- The merchant's bank, the acquirer, debits the merchant and notifies them.
- The merchant accepts the loss or contests it with evidence.
- The issuer reviews the evidence and decides; unresolved cases can go to the card network.
On the issuer side, an agent can draft the claim and select the likely reason; whether a person must approve before it is raised is covered in can an AI agent raise a chargeback for a cardholder? On the merchant side, an agent can assemble the response, using the chargeback dispute evidence checklist as its brief.
What does that look like in an example?
An online furniture retailer receives a chargeback for 600, reason "not received". Its disputes agent pulls the courier's proof of delivery, which shows a signature and a photo at the order address, plus the order confirmation and two emails in which the customer asked about assembly after the delivery date. It drafts the response and a disputes analyst submits it.
A second chargeback the same day shows a delivery photo at a different postcode. The agent recommends accepting the loss rather than contesting, and the analyst agrees. Knowing when not to fight is part of the job. The full method is in how to handle chargeback disputes with an AI agent.
How is a chargeback different from a refund?
A refund is voluntary: the merchant sends the money back, usually at the customer's request. A chargeback is forced: the issuer takes the money back through the network, whether the merchant agrees or not, and the merchant usually pays a fee as well. A customer who cannot get a refund may turn to a chargeback; a merchant who refunds promptly often avoids one.
Which related terms should you know?
- Representment: the merchant's evidence-backed challenge to a chargeback.
- Friendly fraud: a cardholder disputing a payment they did make, sometimes by mistake.
- Reason code: the network category under which the chargeback is raised.
Questions people ask
Can a merchant stop a customer raising a chargeback?
No. The right sits with the cardholder and their issuer. The merchant's say comes afterwards, through the evidence it provides.
Do chargebacks apply to bank transfers?
No. Chargebacks belong to card payments. Bank transfers have different routes, such as a payment recall request or, for scams, a reimbursement claim.