How Chargebacks Work

By Midcove Editorial Team, Payments & Risk · Last updated: August 7, 2026

A chargeback is a forced reversal of a card transaction, initiated by the cardholder’s bank rather than by the merchant. If you accept cards, understanding how chargebacks work is not optional — every dispute takes back revenue you already earned, adds a fee on top, and counts against ratios that your processor watches closely. A merchant who understands the mechanics responds faster, wins more cases, and keeps their merchant account in good standing.

This guide walks through the entire chargeback process in plain language: what a chargeback actually is (and how it differs from a refund), why disputes happen in the first place, how the dispute lifecycle moves from the cardholder’s complaint to a final decision, and why the deadlines built into that lifecycle punish slow responders. We’ll also cover what evidence actually wins a representment, and what chargebacks really cost beyond the transaction amount itself.

The short version: a chargeback happens to a merchant, a refund is something a merchant does — and once a dispute is filed, a strict clock starts running whether you’re watching it or not.

In this guide:

• What a chargeback actually is
• Why chargebacks happen
• The dispute lifecycle, step by step
• Dispute deadlines and why speed matters
• What evidence wins a dispute
• The real cost of chargebacks
• The takeaway
• Frequently asked questions

What a Chargeback Actually Is

A chargeback is a transaction reversal that starts on the cardholder’s side. When a cardholder disputes a charge, their bank — the issuer — pulls the funds back from the merchant’s account and returns them to the cardholder, often before the merchant has had any chance to respond. The mechanism exists because card network rules give consumers a way to recover money when something genuinely goes wrong: a stolen card, an order that never arrived, a subscription that kept billing after cancellation.

That makes a chargeback fundamentally different from a refund. A refund is voluntary: the merchant reviews the situation, agrees to return the money, and keeps control of the interaction. A chargeback bypasses the merchant entirely. The issuer takes the funds, a chargeback fee is added on top, and the dispute is recorded against the merchant’s account — win or lose.

This is why “just refund it” is often the cheaper outcome when a customer complains directly. A refund costs the transaction amount. A chargeback costs the transaction amount, plus a fee, plus a permanent mark on your dispute ratio.

Why Chargebacks Happen

Disputes fall into three broad buckets, and knowing which one you’re dealing with shapes both your response and your prevention strategy.

True fraud

The cardholder genuinely didn’t authorize the transaction — their card number was stolen, their account was compromised, or someone used their card without permission. These disputes protect the consumer, and they’re difficult for a merchant to win because the cardholder really didn’t make the purchase. The right play here is prevention, not fighting: screening tools like AVS and CVV checks, plus the kind of IP, email, phone, and BIN blocking found in payment fraud prevention software, stop many of these transactions before they settle.

Friendly fraud

Friendly fraud is the industry’s term for a dispute filed by the real cardholder against a legitimate transaction. Sometimes it’s genuine confusion — the billing descriptor on the statement doesn’t match the store name, or a family member made the purchase. Sometimes it’s opportunistic: the customer received the goods and disputes the charge anyway, treating the chargeback process as a no-questions-asked refund button. Friendly fraud is the category merchants can most often win, because the merchant usually holds evidence that the transaction was real and fulfilled.

Merchant error

The third bucket is self-inflicted: duplicate charges, orders that shipped late or never shipped, subscriptions billed after cancellation, unclear return policies, or unresponsive customer service that left a refund request with nowhere to go but the bank. These disputes are legitimate from the cardholder’s point of view, and the fix is operational — better descriptors, faster support, cleaner billing logic. Our guide on how to reduce chargebacks covers prevention in depth.

Not every chargeback reflects wrongdoing by the merchant, and not every one reflects wrongdoing by the customer. The dispute process exists precisely to sort out which is which — one case at a time.

How Chargebacks Work: The Dispute Lifecycle Step by Step

Every card network runs its own dispute program with its own terminology, but the lifecycle follows the same shape across Visa, Mastercard, and the other networks. Here is how a dispute typically moves from complaint to conclusion.

1. The cardholder disputes the charge

The cardholder contacts their issuing bank and disputes a transaction. In many cases the issuer reviews the claim first; some issuers may resolve simple cases (like a duplicate charge) without ever involving the merchant. If the issuer accepts the dispute, it files a chargeback through the card network.

2. A reason code is assigned

Every chargeback carries a reason code — a network-defined code that states the alleged problem: fraud, goods not received, product unacceptable, credit not processed, duplicate processing, and so on. The reason code matters enormously, because it defines what you’re being accused of and therefore what evidence can rebut it. Card networks publish their dispute categories publicly — Visa’s dispute rules are one example — and each code has its own evidence expectations.

3. Funds are withdrawn and the merchant is notified

The chargeback flows from the network to the acquirer or processor, which debits the disputed amount (plus a chargeback fee) from the merchant’s account and passes the notification along. This is a critical moment: the clock on your response window starts here, not when you happen to notice the debit on a statement.

4. The merchant accepts or fights

You have two options. Accept the chargeback — the cardholder keeps the funds and the case closes — which is rational when the dispute is legitimate or the amount is too small to justify the effort. Or fight it through representment: literally “re-presenting” the transaction to the issuer with a rebuttal letter and compelling evidence that the charge was valid.

5. The issuer decides

The issuing bank reviews the evidence from both sides and rules on the case. If the merchant wins, the funds are returned (though the chargeback fee usually isn’t). If the cardholder wins, the reversal stands. In a minority of cases the dispute can continue — a second-cycle dispute or, rarely, arbitration at the card network, where the network itself rules and the loser typically pays additional fees. For most merchants, most of the time, the issuer’s representment decision is the end of the road.

Dispute Deadlines: Why Speed Matters

Every stage of the chargeback process runs on deadlines set by the card networks — typically measured in days, and enforced without sympathy. Cardholders have a filing window counted from the transaction or delivery date. Merchants have a response window counted from the chargeback date. Miss yours, and the case is decided against you by default, regardless of how strong your evidence was.

That makes speed a structural advantage, for three reasons:

• Late discovery burns the window. A merchant who learns about a dispute from a monthly statement may have already lost most of the response period. Real-time dispute alerts convert the full window into usable time.
• Evidence gathering takes time. Pulling authorization records, delivery confirmation, and customer correspondence from scattered systems can take days on its own. If your transaction records live in one searchable place, assembly takes minutes instead.
• Early response can stop escalation. Some processor and issuer programs allow a merchant to resolve an inquiry before it hardens into a formal chargeback — but only if the merchant reacts while that option is still open.

This is the operational case for chargeback management software: alerts the moment a dispute opens, every case’s deadline visible in one queue, and evidence uploads attached directly to the dispute record — so no case dies of a missed date.

What Evidence Wins a Dispute

Representment is won on documents, not indignation. The issuer’s analyst wants specific proof that rebuts the specific reason code, presented clearly. The strongest packages typically include:

• Authorization data. AVS and CVV match results, approval codes, and 3-D Secure results showing the transaction was verified at the time of sale.
• Proof of fulfillment. Carrier tracking with delivery confirmation to the cardholder’s address, signed delivery receipts, or server logs showing a digital product was downloaded or a service was accessed.
• Customer identity links. Evidence connecting the buyer to the cardholder: matching billing address, a customer account with order history, an email address or IP address used across prior undisputed purchases.
• Communication records. Emails, support tickets, or chat logs showing the customer acknowledged the order, received it, or never attempted to resolve the issue with you first.
• Policy acceptance. Proof the cardholder agreed to your terms, refund policy, or subscription billing schedule at checkout — decisive in “credit not processed” and recurring-billing disputes.
• A concise rebuttal letter. A short cover narrative that names the reason code, states why the charge is valid, and points to each exhibit. Analysts review many cases; clarity wins.

Match the evidence to the code. A fraud code calls for authorization and identity evidence; a “goods not received” code calls for delivery proof; a “credit not processed” code calls for your refund policy and the customer’s acceptance of it. A generic document dump addressed to no particular allegation is the most common way merchants lose winnable cases.

The Real Cost of Chargebacks (It’s Not Just the Transaction)

The reversed sale is only the first line of the bill. The full cost of a chargeback includes:

• Chargeback fees. Processors charge a per-dispute fee — commonly in the $15–$100 range depending on the processor and merchant category — and most keep the fee even when the merchant wins the case.
• Lost goods and fulfillment costs. In a lost dispute you’re out the product, the shipping, and the processing fees on the original sale, on top of the sale itself.
• Operational time. Every fought case consumes staff hours gathering evidence and writing rebuttals.
• Your chargeback ratio. Networks and processors track disputes as a percentage of your transactions. Every chargeback counts against the ratio whether you win or lose — winning the case does not remove the dispute from the count.
• MID standing. A ratio that climbs too high can land a merchant in a network monitoring program, trigger higher fees or rolling reserves, and ultimately get the merchant account terminated. A terminated MID can follow a business for years and make getting approved elsewhere far harder.

This is why chargebacks belong in a broader risk picture, not just a case-by-case workflow. Watching dispute trends per MID, spotting a climbing ratio early, and acting before a processor does is the core of merchant risk management. And because the cheapest chargeback is the one that never happens, prevention — clear descriptors, responsive support, and fraud screening at the point of sale — pays for itself many times over. The PCI Security Standards Council‘s requirements for protecting card data exist in part because stolen credentials are the raw material of the fraud disputes merchants can least afford.

The Takeaway

A chargeback is a forced reversal with a strict clock attached. Disputes come from three places — true fraud, friendly fraud, and merchant error — and each calls for a different mix of prevention and defense. Once a dispute is filed, the lifecycle is predictable: reason code, notification, representment, decision. The merchants who consistently win are the ones who hear about disputes immediately, match evidence to the reason code, and submit well before the deadline.

Just as important: track the pattern, not just the case. Fees, ratios, and MID standing are where chargebacks do their lasting damage, and they respond to systems, not heroics. Know about every dispute the moment it opens, keep your evidence organized before you need it, and treat your dispute ratio as a metric you manage — not a number you discover.

Frequently Asked Questions