In everyday use the words are swapped freely, and that is where merchants lose money. A dispute is the cardholder's claim: they tell their issuing bank that a charge is wrong, unauthorised, or for something they never received. A chargeback is what the card scheme does about it — the funds are pulled back from the merchant and returned to the cardholder, usually with a fee attached. Every chargeback starts as a dispute. Not every dispute has to become one, and that gap is where a merchant can still act.
Chargeback vs dispute: the difference in one table
The two words describe different moments, different actors and different money movements. Reading them as synonyms is what makes merchants answer the wrong thing at the wrong stage.
| Dispute | Chargeback |
|---|
| What it is | A claim raised by the cardholder with their bank | A forced reversal of the payment executed through the card scheme |
| Who starts it | The cardholder | The issuing bank, acting on the upheld claim |
| Money movement | None yet — the claim is being examined | Funds leave the merchant and return to the cardholder |
| Merchant cost | Time and evidence | The transaction amount, a scheme fee, and a hit to the dispute ratio |
| Can it be stopped | Yes — a refund or a resolved complaint ends it | Only by winning representment after the fact |
Why the distinction costs money
A dispute is still a conversation. A customer who cannot find your name on their statement, or who has not received an order, often files with their bank simply because that is the fastest button available to them. Reached early, most of these end in a refund or an explanation and never touch the scheme.
A chargeback is an accounting event. The money is gone before the merchant argues anything, the scheme fee applies whether or not the case is later won, and the case counts toward the ratio that determines whether a merchant is placed in a monitoring programme. Winning a chargeback restores the amount; it does not undo the fee or the ratio entry.
Friendly fraud is a dispute problem, not a fraud problem
A large share of disputes come from real customers who genuinely do not recognise a charge — an unfamiliar descriptor, a subscription renewal they forgot, a family member's purchase. The transaction was legitimate and the authentication was valid, yet the claim is sincere.
These cases are not solved by fraud tooling, because nothing was fraudulent at authorisation. They are solved earlier, in the checkout and the statement descriptor: a recognisable merchant name, a clear renewal notice, and a visible refund policy remove the reason to call the bank at all.
What to do at each stage
- Before the claim. Make the descriptor recognisable, confirm delivery in writing, and keep support reachable — the customer who can reach you does not call the bank.
- At the dispute stage. If the claim is right, refund immediately: a refund closes the case without a scheme fee or a ratio entry. If it is wrong, gather the evidence now, while the records are fresh.
- At the chargeback stage. Answer inside the scheme's response window with what the reason code actually asks for — delivery proof, authentication result, the terms the customer accepted. A generic evidence pack loses to a targeted one.
Each of these depends on having the payment record, the authentication result and the delivery data in one place rather than in three systems that do not talk to each other.
Related product
One management system across your providers, so the records behind a disputed payment sit together when you need to answer inside a 20-day window.
Related product
Most disputes start at checkout: a recognisable, brandable payment page and a clear renewal notice remove the reason to call the bank at all.
