Merchants lose chargebacks for two reasons: they miss the response deadline, or they send generic evidence instead of evidence matched to the specific reason code. Fought correctly — targeted evidence, on time, through representment — win rates of 40%+ are realistic for friendly-fraud disputes, versus the roughly 20% industry-wide average that includes merchants who barely respond. But the bigger money is upstream: clear billing descriptors, delivery confirmation, AVS/CVV, and dispute alerts prevent the majority of chargebacks from ever being filed, and keep you safely under the ~1% ratio where the card networks' monitoring programs begin.
What actually happens when a customer disputes a charge?
A chargeback is a forced reversal of a card payment, initiated by the cardholder's bank, that pulls the money back out of your account while the dispute is decided. Note the order of operations: the money leaves first, then you argue. Understanding the machine helps you work it:
- Dispute filed. The cardholder calls their bank (or taps a button in their banking app — which is much of why dispute volume keeps climbing). The issuing bank assigns a reason code and pulls the funds from your account, plus a chargeback fee of typically $15–$50.
- Retrieval request (sometimes). For some disputes the issuer first asks for a copy of the transaction record — a "retrieval" or "soft" inquiry. Respond to these. Ignored retrievals convert into chargebacks you're barred from contesting.
- Representment. Your one real turn. You "re-present" the transaction with a rebuttal letter and evidence, through your processor's dispute portal, before a deadline that's typically tight — often you have far less calendar time than the customer had to file. Miss it and you lose by default; a large share of all chargebacks are lost exactly this way.
- Issuer decision. The issuing bank reviews your packet against the cardholder's claim and either reverses the chargeback (you get the money back) or upholds it.
- Pre-arbitration and arbitration. Either side can push back once more (pre-arb); after that the card network itself rules, charging hundreds of dollars in fees to the loser. For a small merchant, arbitration is almost never worth it — the filing fees exceed most disputed tickets.
One more cost merchants forget: win or lose, the dispute still counts toward your chargeback ratio. Winning gets your money back; it does not un-ring the bell with the network's monitoring programs. That asymmetry drives most of the strategy in this guide.
What do chargeback reason codes really mean?
Every dispute carries a reason code — Visa's look like "10.4," Mastercard's like "4837" — and the specific code dictates what evidence can win. The dozens of codes collapse into four families:
- Fraud ("I didn't make this charge"): the cardholder claims the card was used without authorization. The largest family by volume — and heavily polluted by friendly fraud, below.
- Authorization ("this was never properly approved"): the transaction was processed without a valid authorization, after a decline, or on an expired approval. Almost always a merchant-side process error — and almost always unwinnable, because the network logs are what they are.
- Processing errors ("the mechanics were wrong"): duplicate charge, wrong amount, currency error, credit processed as a sale. Winnable only when your records show the mechanics were actually right.
- Consumer disputes ("I made the charge, but…"): item not received, not as described, defective, canceled subscription still billing, credit not processed. This family is where documentation habits decide everything.
When a dispute lands, the first move is always the same: read the actual reason code, not the summary line in the portal. Merchants routinely send "the customer is lying" packets to processing-error codes and delivery confirmations to fraud codes — and lose disputes they had the evidence to win.
True fraud vs. friendly fraud — why the difference matters
True fraud means a stolen card or account was used by someone other than the cardholder. Friendly fraud means the real cardholder disputes a legitimate charge — because they didn't recognize your billing descriptor, forgot the purchase, a family member made it, they missed a subscription renewal, or they've learned that disputing is faster than requesting a refund. Industry estimates consistently attribute more than half of all chargebacks to friendly fraud, and the share has grown as banking apps made disputing a one-tap action.
The distinction drives strategy:
- True fraud on a card-present EMV transaction usually isn't your liability — since the EMV liability shift, a chip/tap transaction generally puts counterfeit fraud back on the issuer. If you're still swiping or keying cards that could be dipped, that protection evaporates, which is one of several reasons old terminals cost real money.
- True fraud online is your liability — card-not-present fraud lands on the merchant. Your defense is screening before the sale (AVS, CVV, velocity checks), not fighting after it.
- Friendly fraud is where fighting pays. The cardholder made the purchase, which means evidence of that fact exists — and packets proving it win at rates far above the all-dispute average.
Never re-bill a customer to "recover" a chargeback, and never fight a dispute you know the customer deserves to win. Both generate second chargebacks with worse codes, inflate your ratio, and can flag your account for exactly the kind of review that ends in termination. The dispute system is slow and often unfair to merchants — but trying to go around it is how a chargeback problem becomes a high-risk merchant account problem.
What evidence actually wins a representment?
Representment is document review, not storytelling. The issuer's analyst spends minutes per case, looking for whether specific evidence rebuts the specific claim. Match the packet to the reason family:
| Dispute type | What the cardholder claims | Evidence that wins |
|---|---|---|
| Fraud (card-not-present) | "I didn't make this charge" | AVS and CVV match results, device/IP data tying the order to the cardholder, delivery to the cardholder's verified billing address with signature, history of prior undisputed orders from the same account, login or account activity after the purchase |
| Fraud (card-present) | "I didn't make this charge" | EMV chip/tap transaction record (often shifts liability off you entirely), signed receipt, surveillance still if available |
| Item not received | "It never arrived" / "service never happened" | Carrier tracking showing delivery to the address on the order, signature confirmation, geolocated proof-of-delivery photo; for services, signed work orders, appointment logs, before/after photos |
| Not as described / defective | "It wasn't what I ordered" | The product page or quote as sold, correspondence showing the customer's specifications, your posted return policy and proof it was presented at checkout, evidence the customer never attempted a return |
| Canceled recurring / subscription | "I canceled and was still billed" | Signed or click-through agreement with billing terms, cancellation policy presented at signup, logs showing no cancellation request before the billing date — or proof the cancellation postdates the charge |
| Credit not processed | "I returned it and got no refund" | Refund transaction record with date and amount, or return policy showing the item didn't qualify and was outside the window |
| Duplicate / processing error | "I was charged twice / wrong amount" | Batch records showing two distinct transactions (different items, times, or tickets), itemized receipts for each |
Packet mechanics matter almost as much as contents: lead with a one-paragraph rebuttal that names the reason code and states exactly which attached document defeats it, label every exhibit, and submit before the deadline with a day to spare. Analysts decide fast; make the winning document impossible to miss.
Build the evidence packet at the time of sale, not at dispute time. If your checkout captures AVS/CVV results, your carrier setting requires signature over a ticket threshold, and your CRM stores quotes and correspondence by order number, then "fighting a chargeback" becomes a fifteen-minute assembly job instead of an archaeology dig against a deadline.
The prevention stack: stopping disputes before they're filed
Every dispute you prevent is worth more than one you win — no fee, no ratio hit, no hour of packet-building. The stack, cheapest layer first:
- Fix your billing descriptor. The single highest-leverage move in chargeback prevention is making the name on the cardholder's statement match the name on your door. "LSP*HOLDINGS DBA 4402" generates disputes; "JOES PIZZA DALLAS 214-838-XXXX" generates phone calls instead. Ask your processor to set a clear descriptor with a phone number — it's a settings change.
- Receipts and confirmations, instantly. Email or text a receipt with your business name, the amount, and what was purchased. For online orders, confirmations plus shipping notifications with tracking. Customers dispute what they can't reconcile.
- Delivery confirmation as policy. Tracking on everything; signature required above a ticket threshold that makes sense for your margins (many merchants use $100–$250). For service businesses: signed completion forms with a photo.
- AVS and CVV on every card-not-present transaction. These screen out true fraud before it becomes a chargeback — and produce match records that win representments when friendly fraud strikes anyway. As a bonus, AVS also prevents interchange downgrades, a double dividend covered in our fee-reduction playbook. Selling online? The full screening stack is in how to accept payments online.
- Dispute alerts (Ethoca, Verifi). These network-affiliated services intercept a dispute at the issuer and give you a window — often 24–72 hours — to refund proactively before it becomes a formal chargeback that hits your ratio. Alerts cost a per-event fee (commonly $20–$40) and make clear economic sense once you're seeing more than a handful of disputes a month or you're anywhere near a monitoring threshold.
- Clear policies at the point of commitment. Return windows, cancellation terms, and recurring billing disclosures presented — and acknowledged — at checkout or signature. These documents are simultaneously prevention (fewer surprised customers) and evidence (winning exhibits when a dispute files anyway).
- Watch your dispute reporting weekly. A spike in one reason code is a diagnosis: fraud codes point at screening gaps, "not received" points at a carrier or fulfillment problem, subscription codes point at a cancellation flow that's too hard to find. Good transaction reporting turns chargebacks from ambushes into trend lines.
Track your ratio per network, not blended. Visa and Mastercard each count their own disputes against their own transaction counts, so a merchant whose volume skews Visa can trip VDMP while the blended number still looks safe. One column each in a spreadsheet — disputes and transactions by network, monthly — is the whole early-warning system.
Monitoring thresholds: what happens above 1%
Your chargeback ratio is the number of disputes divided by the number of transactions in a month — and at roughly 0.9%–1%, the card networks stop treating disputes as your problem and start treating you as theirs. Visa's dispute monitoring program (VDMP) and Mastercard's excessive chargeback program (ECP) enroll merchants around those levels (with "excessive" tiers above 1.5%–1.8%), and enrollment is not a warning letter:
- You're placed on a remediation plan with monthly reporting and a timeline to bring the ratio down.
- Fines begin after a grace period and escalate the longer you stay enrolled — from hundreds to thousands of dollars per month, passed through your acquirer to you.
- Your processor's risk department gets involved, which can mean reserves held against your deposits.
- If the ratio doesn't come down over several months, the endgame is account termination and MATCH-listing — the industry's shared blacklist, which makes opening a replacement account difficult and expensive for years.
The practical implication for a small merchant: low transaction counts make the ratio treacherous. A shop doing 800 transactions a month is eight disputes away from 1%. That's why prevention and alerts aren't enterprise luxuries — they're how small merchants keep a bad month from becoming a program enrollment. If your business model runs structurally high dispute rates (subscriptions, travel, CBD, coaching), plan for it deliberately — our high-risk merchant account guide covers that world.
When you should just refund
Fighting everything is a strategy for people who bill by the hour. The refund math for everyone else:
- Refund when the customer comes to you first. A refund request handled today is a dispute that never files, never costs a fee, and never touches your ratio. Make refunds easy to request — a customer who can't find your refund path will find their bank's dispute button.
- Refund small tickets. Between the chargeback fee ($15–$50), the original processing fee you don't recover, and an hour of packet work, fighting a dispute has a real cost floor around $25–$40. Below that, winning is losing slowly.
- Refund weak cases. If your evidence doesn't map to the reason code in the table above, conceding early at least ends the clock.
- Fight clear friendly fraud on meaningful tickets — with targeted evidence, on time. Cardholders who learn disputes against your business get contested file fewer of them; serial abusers move on to softer targets.
One caveat: a refund only prevents the chargeback if it lands before the dispute files — which is precisely the window alert services exist to create.
- The money leaves your account when the dispute files — representment is your one real turn, and the deadline is short.
- Read the reason code first: evidence matched to the code wins; generic packets lose.
- More than half of chargebacks are friendly fraud — the category where good records win most often.
- Prevention beats representment: clear descriptors, receipts, delivery confirmation, AVS/CVV, and alerts stop most disputes from filing.
- Stay far below the ~1% monitoring threshold — even disputes you win count against it, and small merchants hit it fast.
Frequently asked questions
How do I fight a chargeback and actually win?
Respond through your processor's dispute portal before the deadline with evidence targeted to the specific reason code — delivery confirmation for "not received," AVS/CVV and device data for card-not-present fraud, signed agreements for subscription disputes. Lead with a one-paragraph rebuttal naming the code and the exhibit that defeats it. Targeted packets win at rates well above the ~20% all-dispute average.
What is friendly fraud and how common is it?
It's the real cardholder disputing a legitimate charge — unrecognized descriptor, forgotten purchase, family member's order, or refund-by-dispute. Industry estimates put it at more than half of all chargebacks, and it's the category most worth contesting because evidence of the purchase genuinely exists.
What does a chargeback cost me even if I win?
The chargeback fee — typically $15–$50 — is usually non-refundable, the original processing fee is gone, you've spent time on the packet, and the dispute still counts toward your monitoring ratio. Winning recovers the sale amount and nothing else, which is why prevention is worth more than the best representment.
What happens if my chargeback ratio goes over 1%?
Around 0.9%–1%, Visa's and Mastercard's monitoring programs enroll you: remediation plans, escalating monthly fines passed through your acquirer, possible reserves — and if the ratio stays high for several months, account termination and MATCH-listing. A merchant doing 800 transactions a month reaches 1% at just eight disputes.
When is refunding smarter than fighting?
When the customer contacts you before their bank, when the ticket is under the ~$25–$40 real cost of fighting, or when your evidence doesn't match the reason code. A proactive refund never touches your ratio; a fought-and-won chargeback still does.
Getting hit with disputes you shouldn't be losing?
We'll review your recent chargebacks, fix your descriptor, wire up alerts, and set up the evidence workflow — so disputes become a fifteen-minute task instead of a monthly tax.