Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Enterprise merchants reduce chargeback ratios by stopping avoidable disputes and fraud before they are filed. Then they measure results the way Visa and Mastercard do. Winning a dispute later brings back money, but it does not remove the chargeback from your ratio. A high chargeback ratio can lead to fines and, in the worst case, loss of card processing.
Written by Chargeflow Experts. Updated 12 November 2026.
“Disputes divided by sales” is not how every program works. Stripe’s network-monitoring guidance shows that VAMP counts fraud reports and disputes together, with some exclusions. Mastercard uses a different month for its sales count.
Confirm the account scope, the top and bottom of the ratio, the month and the chargeback thresholds with your acquirer. No single percentage is safe for everyone. Never swap the official monthly report for a blended average across all accounts.
| Workstream | What It Improves | Measure Separately |
|---|---|---|
| Fulfillment and billing fixes | Complaints you could have avoided. | Dispute counts for those reasons. |
| Fraud review | Exposure to stolen-card and account-takeover fraud. | Fraud reports, approvals and good orders blocked. |
| Pre-dispute resolution | Cases refunded before a chargeback is filed. | Confirmed outcome and whether it left the count. |
| Representment | Money won back on fought cases. | Recovered funds, costs and pending cases. |
| Reporting controls | Accurate numbers and early warnings. | Data age, matching and status per account. |
Each network counts different events and uses a different month for sales. This table shows how the main programs work in 2026.
| Program | What is counted (top) | Divided by (bottom) | Flags you at |
|---|---|---|---|
| Visa VAMP | TC40 fraud reports + TC15 disputes received in the month. A payment in both reports counts twice. | Settled Visa card-not-present sales in the same month. | 1.5% and 1,500+ events in the US, Canada, EU, Asia Pacific and Latin America (since 1 April 2026). CEMEA: 2.2%, 150 events and USD 75,000. |
| Mastercard ECM | Chargebacks received this month, whatever the outcome. | Mastercard sales from the previous month. | 1.5% to 2.99% and 100 to 299 chargebacks. |
| Mastercard HECM | Same as ECM. | Same as ECM. | 3% and 300+ chargebacks. |
| Mastercard EFM | Fraud chargebacks (4837 and 4863) this month. | Ecommerce sales from the previous month. | 0.50%, USD 50,000 in fraud and 1,000+ ecommerce sales, with low 3D Secure use. |
Sources: Visa’s VAMP fact sheet and Stripe’s monitoring guidance. To test your own numbers, use the VAMP calculator or our guide to chargeback ratio calculation.
Why chargeback ratios matter: Mastercard fines start in month 2 of ECM at USD 1,000 and climb to USD 100,000 a month after 19 months. HECM fines reach USD 200,000, plus USD 5 per chargeback over 300.
You leave a Mastercard program only after 3 months in a row below the line. Mastercard’s new GMAP program replaces ACMP on 1 April 2027, and acquirers report that its ratio floor will tighten each year after that.
Split disputes by reason, product, sales channel, shipping path and account. Compare each count with its sales volume. Look for shipping failures, billing errors, cancel problems and hacked accounts. Do not assume every spike is friendly fraud.
Match each chargeback prevention control to its cause. Use delivery controls, renewal controls and repeat-pattern review to assign clear fixes.
These steps change what the networks count, not just how you report it:
Use each program’s own rules
Money won back and counted events are separate
Filed dispute and recovery
A fast evidence response can win the money back, but the dispute still happened. Stripe’s guidance says Mastercard counts chargebacks whatever the outcome. Check each program’s exclusions. Do not assume a win or refund takes a case out.
Eligible early resolution
For early refunds, see the chargeback-alerts guide. Confirm the outcome and how it was reported before you call a case prevented.
Disputes show up weeks after the sale, so track early signs too: shipping exceptions, failed cancels, fraud warnings and rising complaints.
Set your own alert levels well below the network lines, for example at two thirds of the threshold. Keep the official monthly view per account. If your acquirer asks for a fix plan, list the actions, owners, dates and results.
Use account-level reporting and multi-processor controls. Chargeflow’s dispute analytics show trends by account. To reduce chargeback losses on cases that do get filed, use chargeback automation that scales with transaction volume. Chargeflow Automation answers each case and charges only on recovered disputes.
Hypothetical Visa month
Count the events first, then check status
Counted fraud and disputes
10060 TC40 fraud reports + 40 TC15 disputes.
Settled sales
10,000Settled TC05 sales in the same month.
Example ratio
1%100 ÷ 10,000 × 100, after exclusions.
This is math only. At 1% and 100 events, this account is below both the 1.5% ratio and the 1,500-event minimum. Region, account scope and timing still matter. The Mastercard example below uses a different month.
Visa’s fact sheet defines this combined count. Read the VAMP guide next to your acquirer’s official notice.
Mastercard example: 100 chargebacks in September divided by 20,000 Mastercard sales in August gives 0.5%. Stripe’s ECP guidance confirms the previous-month sales count. Do not compare this number directly with the same-month Visa ratio. See the Mastercard Excessive Chargeback Program guide for the full rules.
Winning chargebacks does not lower a monitoring ratio. Mastercard counts chargebacks whatever the outcome, and Visa counts TC15 disputes when they are received. Only steps taken before a dispute is filed, like pre-dispute refunds, take cases out.
There is no universal safe chargeback ratio for every enterprise. Visa flags merchants at 1.5% with 1,500 events in most regions, and Mastercard at 1.5% with 100 chargebacks, but processors can set stricter limits.
No, do not track only the portfolio average of your chargeback ratio. Visa and Mastercard flag single accounts, so an average can hide one account that is crossing the line.
Enterprises measure dispute rates the way each network does. Visa VAMP divides TC40 fraud reports plus TC15 disputes by settled sales in the same month. Mastercard divides this month’s chargebacks by last month’s sales.
A high chargeback ratio is one that crosses a network line. That means 1.5% for Visa VAMP with 1,500+ events in most regions, or 1.5% for Mastercard ECM with 100+ chargebacks. Many acquirers act well before those levels.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.
Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.
Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.
Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..
Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.
Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.
Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.
Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.