Disputes and chargebacks

A chargeback is the cardholder's bank taking money back out of your account, on the cardholder's word, months after you thought the sale was finished. You do not approve it and you cannot stop it. You can only answer it afterwards.

This is the one flow in the primer that runs on someone else's initiative. Everything else — authorize, capture, void, refund — starts with you. A dispute starts with the cardholder telling their issuer that something is wrong.

Why it exists

The cardholder's protection is the product. People hand a card to strangers on the internet because the card comes with a way to undo the payment when the goods never turn up. The chargeback is that mechanism, and the whole card system rests on it.

That framing is worth holding on to, because it explains why the process feels tilted against merchants. It is tilted against merchants. The alternative is a payment method nobody trusts.

The sequence

Two things surprise people the first time.

The money leaves before you are asked. The debit is provisional but it is real, and it lands in your funding as an adjustment. You are arguing to get it back, not arguing to avoid losing it. See funding for how adjustments show up in a deposit.

Arbitration is a threat, not a plan. The network charges a fee to whoever loses, and that fee usually exceeds the transaction. Taking a small disputed sale to arbitration costs more than writing it off however the decision goes.

What the cardholder is actually claiming

Every dispute carries a reason code: the network's identifier for the category of claim. The code decides what evidence counts, so reading it first is not optional.

Visa groups its codes into four families, and Mastercard's codes map onto much the same ideas under different numbers.

Family	The claim	What answers it
Fraud	"I did not make this transaction"	Proof the genuine cardholder did: authentication data, delivery to the verified address, account history
Authorization	"This was charged without a valid approval"	The approval record — or nothing, if there is not one
Processing error	"The amount, currency, or date is wrong, or I was charged twice"	The transaction record showing what was actually submitted
Consumer dispute	"The goods never arrived, or were not what was described, or I cancelled"	Delivery confirmation, the description the customer saw, your terms, the cancellation trail

The families sort neatly into who can fix them. Authorization and processing-error disputes are your own systems failing — a late capture, a duplicate submission, a force capture with no approval behind it. Those are bugs, and capture covers the operations that cause them. Consumer disputes are the business failing: slow delivery, unclear descriptions, a cancellation nobody actioned. Fraud disputes are the only family where somebody else is at fault, and even there the question is whether you collected enough evidence at authorization to prove it.

Winning a representment

Representment means re-presenting the transaction with evidence. It is the merchant's one substantive move.

Most representments fail for reasons that have nothing to do with the merits. The deadline passed. The evidence answered a different question from the one the reason code asked. Nobody could find the delivery confirmation because it lived in a system the disputes team had no access to.

Answering a chargeback

Read the reason code before you gather anything.

1. Find the reason code and the response deadline on the dispute notice.
2. Check whether you already refunded this transaction. If you did, send the refund record and stop.
3. Gather only the evidence that the reason code asks for.
4. Submit before the deadline. A late response is a lost case.

Do not send the same evidence pack for every reason code.

Two cases deserve a rule of their own, because both look like wins and are not.

If you have already refunded the transaction, say so and prove it. Otherwise you pay twice: once as the refund and once as the chargeback.

If the disputed amount is small, compare the cost of fighting against the cost of accepting. Staff time and the dispute fee both land whatever the outcome. Accepting a small loss is often the commercially correct answer, and it does not remove the chargeback from your ratio.

The fee lands either way

A dispute arrives with a fee from your provider, and winning does not refund it. That is the detail that changes the arithmetic: on low-value transactions the fee alone can exceed the sale, so a merchant who wins every case can still lose money on disputes.

The amount is set by your contract rather than by the networks, so it sits alongside the other contract-dependent figures in this primer. Ask your provider what it charges, and whether it charges again at pre-arbitration.

Chargeback ratio, and why your acquirer cares

Your chargeback ratio is disputed transactions as a share of volume. Both networks run monitoring programmes against it, and both use the same shape: a floor on the raw count and a threshold on the ratio, with consequences once you breach both.

Cross the thresholds and you get fines, mandatory remediation plans, and heavier terms from your acquirer — a larger reserve, slower funding, or the end of the relationship. This is the mechanism behind the claim in funding that dispute performance is a treasury problem: the ratio sets your reserve, and the reserve is working capital you do not have.

Watching the ratio

Track the ratio monthly, not quarterly.

1. Get the current count floor and ratio threshold from your acquirer, for each network you accept.
2. Confirm which month's transaction count each network divides by.
3. Compare your figure against the threshold every month.
4. Act when you are approaching the threshold, not when you have crossed it.

Step 2 is not pedantry. The networks do not compute the denominator the same way, so the same business can produce two different ratios and breach one programme while looking healthy under the other. Confirm the current thresholds and the denominator with your acquirer; both change, and a stale number in a dashboard is worse than no number.

Note also what the ratio does not count. A refund is not a dispute. This is the concrete payoff of the argument in voids, reversals, and refunds: refunding an unhappy customer keeps them out of this flow entirely, and out of the ratio.

Disputes are not ACH returns

Both take money back after the fact, and treating them as one thing produces bad systems.

	Card chargeback	ACH return
Who initiates	The cardholder, via the issuer	The receiving bank, sometimes at the customer's instruction
Can you contest it?	Yes, by representment	No. A return is final; recovery is a matter between you and the customer
Evidence process	Structured, with deadlines and arbitration	None
Typical window	Commonly 120 days, longer for some reason codes	Two banking days, or 60 calendar days for unauthorized consumer debits
Comes with a reason	A network reason code	An R-code

The row that matters is the second. There is no representment for an ACH return. If an ACH debit comes back, the payments system is finished with it and you are left chasing the customer directly.

Deadlines

The cardholder's filing window and your response window are both scheme rules, and both are collected with the rest of the timing figures on timing, end to end. The response window is the one to build an alert against: providers routinely compress it inside their own portals, so your real deadline is earlier than the network's.

Visa's and Mastercard's dispute rules are published, and the Mastercard transaction processing rules cited on the authorization page are the same document that governs much of this flow. Check the current version before you rely on a window; these change.

Terms introduced

• Chargeback — the issuer reversing a settled transaction on the cardholder's behalf.
• Reason code — the network's identifier for what the cardholder is claiming, which determines what evidence counts.
• Representment — re-presenting a disputed transaction to the issuer with evidence.
• Pre-arbitration — a second exchange after a representment is rejected, before arbitration.
• Arbitration — the network deciding the case and charging the loser a fee.
• Dispute fee — your provider's per-dispute charge, which you pay whether you win or lose.
• Chargeback ratio — disputed transactions as a share of volume, measured against network monitoring thresholds.

Disputes and chargebacks

0 of 5 answered

1. Why is the reason code the first thing to read on a dispute notice?

   It defines what the cardholder is claiming, and therefore which evidence counts.It sets the dispute fee your provider will charge.It tells you whether the transaction was authorized correctly.It determines whether the chargeback counts towards your ratio.
2. A chargeback arrives for a transaction you already refunded in full. What should you do?

   Contest it, sending the refund record as the evidence.Accept it, because the customer has been made whole either way.Refund it again so the records match, then accept the chargeback.Escalate straight to pre-arbitration, since the facts are not in dispute.
3. A chargeback is filed against a transaction you were funded for last month. What happens to the money while you decide whether to contest it?

   It is already debited from you. Contesting is an attempt to get it back.It is frozen pending the outcome, and moves only once the case is decided.Nothing moves until you either accept the chargeback or lose a representment.The issuer holds it, and your provider is not involved until arbitration.
4. Why is arbitration rarely the right destination for a disputed transaction?

   The network charges the losing side a fee that usually exceeds the transaction.The network almost always finds for the issuer.Entering arbitration doubles the entry's weight in your chargeback ratio.Arbitration is only available to acquirers, not to merchants.
5. What is the key structural difference between a card chargeback and an ACH return?

   A chargeback can be contested with evidence; an ACH return is final.A chargeback takes money back, whereas an ACH return only flags the transaction.An ACH return can be contested, but only within two banking days.A chargeback arrives with a reason code, whereas an ACH return gives no reason.