Winning a chargeback does not fix your ratio: it recovers the money, but the dispute still counts toward Visa VAMP and Mastercard ECM. Both programs measure how well you prevent disputes, not whether you win them β so a merchant with a high win rate and a high dispute rate is still a merchant heading for a monitoring program. The remediation is to lower the count, not just to win cases.
Winning a chargeback recovers the disputed amount, and that matters β revenue recovered is real money, and a strong representment operation pays for itself. But it does not remove the dispute from the month it posted in, because monitoring programs count disputes when they arrive and do not recalculate for representment outcomes. Stripe's own documentation states the point plainly for its merchants: monitoring programs ignore dispute outcomes and refunds. They measure prevention, not litigation skill. A merchant who wins 80% of its disputes and still posts 200 a month is, to Visa and Mastercard, a merchant posting 200 disputes a month.
That split β revenue vs ratio β is the whole strategy problem in one sentence. Fighting cases is a revenue operation: it recovers money already at risk. Lowering the ratio is a prevention operation: it stops disputes from posting at all. A merchant that only does the first will keep winning cases while drifting toward a program threshold, and will discover the problem in a monthly report rather than in time to fix it. Run both, but never confuse them.
Visa's Acquirer Monitoring Program (VAMP) counts fraud reports plus disputes, not wins and losses. Since April 1, 2026, the published merchant tier is Excessive at a ratio of 1.5% β TC40 fraud reports plus TC15 non-fraud disputes, divided by settled card-not-present transactions β once the merchant generates at least 1,500 fraud reports and disputes in the month, for merchants in the US, Canada, Europe, Asia-Pacific and Latin America group. Both conditions must hold in the same month. A dispute that you later win still entered that month's TC15 count when it posted, and winning it does not take it back out.
Note also what VAMP counts that a raw chargeback ratio does not: fraud reports count even when they never become chargebacks, so the ratio Visa computes can run higher than your own chargeback ratio. That is why the first question to your acquirer is always what its VAMP count actually is, not what your own spreadsheet says β and why a merchant can be in VAMP trouble while believing its "chargeback rate" looks fine.
Mastercard's Excessive Chargeback Program counts first-presentment chargebacks, and does not recalculate for representment outcomes either. ECM trips at 100 or more chargebacks in a month with a chargeback-to-transaction ratio of 1.5% or more; HECM, the severe tier, at 300 or more and 3.0% or more. Both conditions in the same month β but the ratio itself is computed differently from Visa's: Mastercard divides this month's first-presentment chargebacks by last month's transactions. A quiet sales month therefore raises next month's official ratio on the same chargeback count, and seasonal sellers feel it first.
The worked example from this site's monitoring guide makes the trap concrete: 120 chargebacks this month on 10,000 transactions this month is 1.20% on Visa's basis, but 1.50% on Mastercard's basis if last month had 8,000 transactions β exactly on the ECM line, with nothing about the disputes having changed. Winning half of those 120 cases changes your revenue. It changes neither month's count, and it changes no program outcome at all.
The narrow exceptions that can keep a dispute out of the count all act before the dispute posts, not after you win it. Disputes resolved through pre-dispute solutions β alerts and pre-dispute resolution that turn a complaint into a refund before a chargeback is filed β never post as chargebacks, so they never enter the count. That is the mechanism behind RDR for Visa and behind Ethoca-style alerts for Mastercard: a refund issued in the pre-dispute window is a refund, not a dispute, and the ratio never sees it. Fraud that qualifies for Visa's Compelling Evidence 3.0 can also be excluded, subject to timing and evidence rules β but again, the exclusion is a pre-dispute mechanism, not a prize for winning a fight.
Everything else about a win is financial, not programmatic. Processor fees generally stay charged even when you win β on Stripe's US standard pricing, for example, the $15 dispute received fee is not returned on a win, though the $15 countered fee is β and the staff time spent assembling evidence is spent whether the case is won or lost. Price wins accordingly: a win is worth the recovered amount minus the unrecovered fee and the staff cost, and it is worth nothing at all against the ratio.
Lower the count by working the inflow, in the order merchants usually feel it. Fix the billing descriptor so customers recognize the charge. Turn on pre-chargeback alerts so a refund replaces a dispute before it posts. Make cancellation painless and send renewal reminders. Read reason codes monthly and fix the product, page or traffic source behind each cluster. And check your position monthly, not quarterly: run your figures through the Chargeback Ratio Calculator and the Merchant Monitoring Program Checker, which runs VAMP, ECM/HECM and the SMMP signals against one month's figures.
Keep fighting the cases worth fighting β the Fight-or-Refund Decision Calculator prices each one, and the Chargeback Cost Calculator shows the full cost of a loss β but budget the two operations separately. The fight operation's target is revenue recovered. The prevention operation's target is disputes posted. Only the second number moves your ratio, and only the second number keeps you out of a monitoring program. A merchant who wins every case and still posts too many disputes is a merchant who will learn this distinction from an acquirer letter instead of from this guide.
Your win rate does not appear in any program ratio. Your monthly count does β run it now.
The short answers to the questions merchants ask most about wins and ratios.
No. Visa VAMP and Mastercard ECM count disputes when they post, and neither recalculates for representment outcomes. Winning recovers revenue; it does not remove the dispute from the month's count.
Since April 1, 2026, the merchant Excessive tier is a ratio of TC40 fraud reports plus TC15 non-fraud disputes to settled card-not-present transactions reaching 1.5%, with at least 1,500 fraud reports and disputes in the month.
ECM trips at 100 or more chargebacks in a month with a ratio of 1.5% or more; HECM, the severe tier, at 300 or more and 3.0% or more. Mastercard counts first-presentment chargebacks and divides this month's chargebacks by last month's transactions.
Only preventing a dispute from posting: pre-dispute resolution and alerts that turn a complaint into a refund before it becomes a chargeback, plus qualifying Compelling Evidence 3.0 fraud exclusions for Visa, subject to timing.
Yes. Processor dispute fees generally stay charged even on a win β on Stripe, for example, the $15 received fee is not returned β and the staff time spent fighting is spent whether you win or lose.
Tools and guides for ratios, monitoring programs and fight decisions.
Sources (checked October 28, 2026): This site's guides/merchant-monitoring-programs-explained.html and guides/chargeback-ratio-explained.html (VAMP 1.5% / 1,500 since April 1, 2026, TC40 + TC15 over settled card-not-present transactions; ECM 1.5% / 100+, HECM 3.0% / 300+, first-presentment chargebacks over last month's transactions; winning disputes does not lower the ratio; pre-dispute solutions and Compelling Evidence 3.0 as the exclusions, subject to timing; the 120-on-10,000 vs 8,000 worked example). Chargeflow, "Visa VAMP 2026: Ratio, Thresholds, Fees and Exclusions" (monitoring programs ignore dispute outcomes and refunds; Visa counts a dispute in the month it receives it; only qualifying pre-dispute resolutions and Compelling Evidence 3.0 fraud are excluded). Fraudio, "Visa VAMP: Complete Guide" (winning a chargeback at representment does not reduce the ratio, because the chargeback has already counted). Stripe pricing and fees via this site's Chargeback Cost Calculator (verified October 2026): $15 received fee not returned on a win; $15 countered fee returned on a win. No program fee amounts and no single exit-month figure are stated in this guide: published fee schedules vary by source and acquirer agreement, and published exit patterns disagree, so your acquirer's notice governs both.