Chargeback Win Rate: What's Realistic and How to Raise It
Chargebacks, Fraud & Security

Chargeback Win Rate: What's Realistic and How to Improve It

Calculate your chargeback win rate the right way, see why net recovery matters more, and use simple math to decide which disputes are worth fighting.

Woman with red nails and gold watch holds a smartphone at a dark desk beside a laptop and an alarm clock

Photo: Pixabay

On this page 7 sections
  1. How to Calculate Your Chargeback Win Rate Without Fooling Yourself
  2. Win Rate vs. Net Recovery: A Worked Example
  3. Why Chargeback Win Rates Swing by Reason Code
  4. Decide Which Disputes to Fight With Expected Value
  5. A Won Dispute Still Counts Against Your Chargeback Ratio
  6. Close the Evidence Gaps That Lose Winnable Cases
  7. Log Every Dispute so the Numbers Mean Something

Key takeaways

  • Measure win rate per reason code, with disputes grouped by the month you received them, and report net recovery in dollars next to it.
  • In the illustrative example, fighting weak cases loses money unless each response costs less than about $9.33.
  • When a Visa arbitration loss carries a published $600 fee, you need better than 60% odds to justify escalating a $400 dispute.
  • Winning a dispute recovers the money, but Visa's monitoring program has already counted the dispute against your ratio.

No chargeback win rate is "good" across the board. The number depends on which disputes you count and which reason codes make up your caseload. A store that only fights "item not received" claims, with tracking that matches the order address, can win most of them. A store fighting online fraud claims on orders that skipped customer authentication will lose most of them. To raise the rate, stop fighting cases you can't win and close the evidence gaps in the ones you can. Then judge the results by dollars kept, not by the percentage alone.

Treat any "average chargeback win rate" you find online with suspicion. Each one defines a win differently, draws on a different mix of merchants, and usually comes from a company that sells dispute services. Your own history, broken down by reason code, is a better benchmark.

How to Calculate Your Chargeback Win Rate Without Fooling Yourself

The formula is disputes won ÷ disputes contested. Three choices inside it can move the result a lot.

The denominator. Dividing by disputes you contested measures the quality of your responses. Dividing by every chargeback you received measures how much of your total dispute volume you claw back. Both are useful because they answer different questions, so label which one you're reporting.

What counts as a win. Representment is your evidence-backed response to a chargeback, sent through your processor to the card issuer. A case reversed at representment can come back if the issuer escalates to pre-arbitration. Count final outcomes, not first-round results, and track partial wins (part of the amount returned) on their own line.

Timing. Group disputes by the month you received them, and calculate only after that group has been resolved. If you divide this month's wins by this month's new disputes, you mix cases from different periods and the number swings for no real reason. Our walkthrough of how the chargeback dispute lifecycle works maps every stage a case can pass through.

Win Rate vs. Net Recovery: A Worked Example

Win rate tells you how often you're right. Net recovery tells you whether fighting pays:

Net recovery rate = (dollars recovered − cost to fight) ÷ dollars disputed

The cost to fight is mostly staff time, plus fees for any outside service. Many processors also charge a per-chargeback fee when the dispute arrives and keep it even if you win. That is one processor's pricing, not a network rule, so check your merchant agreement. You pay it whether or not you respond, so it belongs in your total chargeback cost but shouldn't affect whether you contest a particular case.

Illustrative assumptions: two merchants each receive 100 chargebacks in a quarter. Every dispute is for $80, so each has $8,000 disputed. Each response costs $15 in staff time. Merchant A fights all 100. Merchant B fights only the 40 cases with strong evidence. Merchant A fights those same 40 and gets the same results on them.

Merchant A: Fights AllMerchant B: Fights Selectively
Disputes contested10040
Disputes won3528
Contested win rate35%70%
Dollars recovered$2,800$2,240
Cost to respond$1,500$600
Net recovered$1,300$1,640
Net recovery rate16.25%20.5%

By win rate, B looks twice as good. Net recovery shows a smaller gap of about four points, and A brought back more gross dollars. Look at A's 60 weak cases. They produced 7 wins worth $560 and cost $900 in labor, a $340 loss.

That result depends on cost. Divide $560 by 60 cases and the break-even is about $9.33 per response. If templates or automation brought A's cost per case below that, the weak cases would pay for themselves and fighting everything would come out ahead. Plug in your own cost per case before you decide your strategy.

Why Chargeback Win Rates Swing by Reason Code

The card networks sort disputes into types: the cardholder says they didn't authorize the sale, the authorization was faulty, the processing was wrong, or the customer disputes what they got. Evidence that wins one type does nothing for another. Our guides to Visa chargeback reason codes and what each Mastercard reason code asks you to prove list the specific codes.

Dispute TypeWhat Usually Decides ItGeneral Outlook
Fraud, card presentWhether the chip was read or the card tappedStronger with chip or tap records, weaker on keyed or swiped sales
Fraud, card not presentAuthentication, AVS and CVV results, device and IP data, prior undisputed ordersHard without authentication or purchase history
AuthorizationA valid approval for that amount and dateWinnable with the approval, not without it
Processing errorWhether the duplicate or wrong amount actually happenedUsually lost when the error is real
Not receivedDelivery confirmation to the order addressOften winnable with matching tracking
Not as describedListing, photos, customer messagesAmong the hardest consumer disputes
Canceled recurringSignup terms, renewal notices, cancellation logWinnable with clean records and no cancellation request
Credit not processedRefund proof, or proof the return policy was shownDepends on your refund records

The online fraud row has a defined path on Visa. Visa's Compelling Evidence 3.0 (CE 3.0) applies to reason code 10.4, "Other Fraud: Card-Absent Environment." According to Chargebacks911's summary, you need two earlier purchases on the same card that were processed more than 120 and no more than 365 days before the dispute, and neither can have been reported as fraud. cside's breakdown adds that at least two of four data points (user ID, shipping address, IP address, device ID) must match across all three transactions, and one of the matches must be the IP address or device ID. A merchant who doesn't store device and IP data at checkout can't use this route, however loyal the customer is.

For risky orders, 3-D Secure authentication creates an authentication record you can submit in a later fraud claim. Ask your processor how authenticated transactions are treated in disputes. Refund disputes follow their own logic, which we cover in credit not processed chargebacks.

Decide Which Disputes to Fight With Expected Value

Run each case through one line of math: chance of winning × amount disputed − cost to respond. If the result is clearly positive, fight.

Illustrative: with a $15 response cost and 20% odds on a not-as-described claim, a $50 dispute has an expected recovery of $10. That's less than the cost, so skip it. A $300 dispute at the same odds is worth $60, so fight it. At those odds the break-even is a $75 ticket. Take the odds from your own tracked history for that reason code, not from gut feel.

Accept the chargeback when you made the error (a double charge, a wrong amount, a refund you promised and never issued). Accept it when the customer is worth keeping and the amount is small, and contact them directly instead. Accept it when the reason code calls for evidence you don't have.

Escalating past representment is a separate, steeper decision. The losing side pays the network's arbitration fee. According to Chargeback Gurus, Visa raised its fee from $500 to $600 as part of its April 2025 dispute fee changes. Chargeflow puts Mastercard's fee at $575 when the ruling favors the issuer and notes your acquirer may add its own handling fee.

Here's what that means for an illustrative $400 Visa dispute. If you win arbitration, you recover $400. If you lose, you pay $600 on top of the $400 you've already lost. Break-even odds are 600 ÷ (400 + 600), or 60%, before you count staff time or any acquirer fee. Unless you'd bet on your documentation, don't escalate a dispute that size.

A Won Dispute Still Counts Against Your Chargeback Ratio

This rule trips up many merchants: winning recovers the money but doesn't erase the dispute. Stripe's monitoring program FAQ explains that for the Visa Acquirer Monitoring Program (VAMP), Visa counts the disputes raised in the data month and divides by settled transactions. Outcome doesn't enter into it. Chargeflow's VAMP guide notes that one fraudulent order can count twice, once as a fraud report and once as a dispute. Per chargeback.io, the merchant threshold fell from 2.2% to 1.5% on April 1, 2026, and disputes resolved through a pre-dispute alert never enter the ratio.

So a high win rate protects your revenue but does nothing for your standing in the program. Prevention and pre-dispute resolution do. See what triggers Visa dispute monitoring enrollment and how to calculate your chargeback ratio. Also, don't refund a customer who has already filed a chargeback, or you can pay twice. We explain why in whether to refund a customer who filed a chargeback.

Close the Evidence Gaps That Lose Winnable Cases

The most common loss is a response that argues the merchant's side but ignores the claim the issuer is actually reviewing. A not-received dispute needs delivery proof, and a copy of your refund policy won't help.

Deadlines cause the next most avoidable losses. Chargeback Gurus reports that Visa requires each dispute to be accepted or answered within 30 days of the dispute date. Since April 2025, acquirers also pay higher fees the longer they take within that window. That's why your processor's internal deadline is shorter than the network's, and a late response is an automatic loss.

Other gaps come up repeatedly. Tracking shows "delivered," but to a different address than the order, or with no signature on an expensive item. Refund terms sat in the site footer with no checkbox at checkout. Emails where the customer confirmed receipt were never attached to the order. Or the response was forty pages of screenshots with no summary. Reviewers move fast, so put the two or three documents that answer the reason code first. Our chargeback rebuttal letter template shows the order.

What you keep depends on how you sell. Retail stores need terminal records showing chip or tap entry and receipts that print the return policy. E-commerce stores need AVS and CVV results, IP and device data (which CE 3.0 depends on), delivery confirmation and the order page as the customer saw it. Subscription businesses need the signup screen with renewal terms, renewal reminders, usage after the renewal date and a cancellation log. State law also governs what subscription sellers must disclose; see automatic renewal laws for subscription businesses. That's general information, not legal advice, so confirm your obligations with a qualified attorney.

Log Every Dispute so the Numbers Mean Something

At low volume, a spreadsheet works. Track these fields:

FieldWhy It Matters
Date received and response deadlineCatches late responses before they happen
Network and reason codeWin rates only mean something within a code
Amount disputedFeeds net recovery and expected-value math
Channel (in store, online, recurring)Shows where disputes come from
Fought or accepted, and whyTests your selection rules
Evidence submittedLinks outcomes to specific documents
Final outcome and dollars recoveredProduces win rate and recovery
Staff time spentProduces your true cost per case

Each month, review contested win rate and net recovery by reason code, and count missed deadlines (the target is zero). A cluster of losses in one code usually points to an operational fix, not a better letter. Repeated not-as-described losses point to the product page, while canceled-recurring losses point to the cancellation flow. Our chargeback prevention steps cover those fixes. Book recovered and lost amounts correctly using how to record refunds and chargebacks in your accounting. If volume outgrows the spreadsheet, judge outside help by net recovery, using our guide to comparing chargeback management services.

This week, export the last 90 days of disputes from your processor portal and tag each one with its reason code, your decision and the final outcome. If your processor can't give you reason codes, deadlines and outcomes in a usable format, that's a reporting gap worth raising. If you're comparing providers, you can request a free processing quote from MannyPay, and a specialist will respond within one business day.

Sources

  1. Visa's New Dispute Fee Changes (Chargeback Gurus)
  2. Chargeback Arbitration Process: Steps, Fees and Deadlines (Chargeflow)
  3. Visa Compelling Evidence 3.0: New Dispute Rules for 2026 (Chargebacks911)
  4. Compelling Evidence 3.0 Requirements (cside)
  5. Monitoring Program FAQ (Stripe Support)
  6. Visa Acquirer Monitoring Program (VAMP): Full Guide (chargeback.io)
  7. Visa VAMP 2026: Ratio, Thresholds, Fees and Exclusions (Chargeflow)

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading