Chargeback vs Dispute: What Is the Difference?

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.

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 acquirer's chargeback 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 — the card schemes' own penalty for a ratio that runs too high, separate from the acquirer's fee. Winning at representment restores the amount — unless the issuer escalates to pre-arbitration; it does not undo the fee or the ratio entry.

The chargeback process: how a dispute becomes a chargeback

The chargeback process runs through four parties — cardholder, issuer, acquirer and merchant — with the card scheme sitting between issuer and acquirer to carry the case. The cardholder contacts their issuing bank (the bank or card issuer behind the credit card or debit card) and disputes a line on their credit card statement. The issuer checks the claim and, if it stands, raises a chargeback through the card scheme. The acquiring bank and the merchant's payment processor then debit the merchant's account and pass the case to the merchant.

Two things decide where the case lands. The first is who decides: until the bank decides, a dispute can still be closed by the merchant with a refund or an explanation — typically prompted by a retrieval request (the issuer asking for the transaction receipt) or an Ethoca/Verifi alert, both of which surface before the chargeback is filed; once the bank decides in the cardholder's favour, only the card scheme's rules apply. The second is the cost: a chargeback fee is charged by the acquirer per case, on top of the reversed amount, and every case adds to the merchant's chargeback ratio. The time limits for each step differ by scheme — see chargeback time limits by card scheme.

Friendly fraud is a dispute problem, not a fraud problem

A large share of disputes come from real cardholders 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.

Friendly fraud, chargeback fraud, true fraud and merchant error: key differences

Not every dispute has the same cause, and the right response depends on which one you are looking at:

• Friendly fraud. A genuine cardholder disputes a legitimate purchase because they do not recognise it or forgot it. The cardholder's concern is sincere; the fix is clearer communication.
• Chargeback fraud. The cardholder knowingly files a dispute for something they received and then keeps both the goods and the money. This is the case that needs evidence, not a refund.
• True fraud. A stolen card or identity theft: someone else made the initial transaction. Authentication and fraud prevention tools address this class, and the liability shift depends on the authentication result.
• Merchant error. A duplicate charge, a wrong amount, an order never shipped. The dispute is correct and the answer is an immediate refund.

Sorting disputes into these four groups before answering is what separates effective dispute management from a generic evidence pack sent to every case.

What to do at each stage

1. 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.
2. At the dispute stage. If the claim is right and you learn about it before the chargeback is raised — through an Ethoca/Verifi alert or a retrieval request — refund at once: a refund issued at this point closes the case without a chargeback fee or a ratio entry. A refund issued after the chargeback is raised can mean losing the amount twice. If the claim is wrong, gather the evidence now, while the records are fresh.
3. 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 cardholder accepted. A generic evidence pack loses to a targeted one.

Each of these depends on having the payment record, the 3DS result, and the chargeback reason code and status in one place rather than spread across systems that do not talk to each other.

Chargeback ratio: why each case counts twice

Every chargeback costs its own amount and fee, and it also counts toward the merchant's chargeback ratio, which the schemes use to decide who goes into a monitoring programme. Mastercard calculates the chargeback-to-transaction ratio (CTR) as the chargebacks received in a calendar month divided by the merchant's Mastercard sales transactions in the preceding month.

• A CTR above 1% with at least 100 chargebacks in a month makes the merchant a Chargeback-Monitored Merchant.
• A CTR of 1.5% or more with at least 100 chargebacks in each of two consecutive months makes it an Excessive Chargeback Merchant. Fees then apply to every chargeback above the threshold, and the status holds until the ratio stays below 1.5% for two consecutive months.

Visa runs its own monitoring programme with its own thresholds and fees. Either way, the ratio is a lagging number: by the time it crosses a threshold, the chargebacks behind it are already counted. The habits that keep it down are the ones above — refund a valid claim before it becomes a chargeback, answer the rest with evidence that matches the reason code, and watch the ratio per merchant, per acquirer and per card scheme rather than as one blended figure.

How a dispute management system supports this

Payneteasy's Dispute Management System brings chargeback management into the gateway that already holds the payment:

• Automatic chargeback notifications. As soon as the issuer registers a chargeback and it comes through the payment network, the team gets the reason code, transaction data and status by email or in the dashboard. The merchant's system receives the same event as a callback.
• Stage mapping by scheme. Each case is shown at the stage it has reached under Visa or Mastercard rules, together with the action that stage requires.
• Chargeback ratio calculation. The ratio for Visa and Mastercard payments is calculated and checked against each scheme's thresholds. For PSPs, fraud/chargeback ratio and reason reports can be filtered by merchant, project, gate and processor.
• Ethoca and Verifi alerts through the platform. Early warnings from issuers arrive without a separate integration, so a valid claim can be refunded while it is still a dispute.

The aim is simple: know about each case early enough to choose between a refund and a response, and see the ratio approach a threshold before the scheme flags it.