Chargeback Ratio Monitoring: Formulas, Thresholds, Workflow

Last updated: October 30, 2026

The chargeback rate in your gateway report is probably not the number Visa or Mastercard uses. Your dashboard might divide lost disputes by sales dollars for the month. The networks count disputes, sometimes fraud reports too, against transaction counts, and Mastercard uses last month’s transactions as the denominator. Same business, three different ratios.

That gap is how merchants get surprised by a letter from their acquirer. They were watching a number. Just not the right one.

This guide explains chargeback ratio monitoring the way the networks do it. We’ll cover how Visa and Mastercard calculate ratios, the thresholds in force as of late 2026, why you should track every MID on its own, and how to build an early warning workflow with alerts that gives you time to act. It’s written for dispute leads, risk managers, and finance teams. Where it helps, we’ll point out what Midcove does in this process and what still sits with your processor and alert providers.

What is chargeback ratio monitoring? It’s tracking disputes against transactions for each merchant account, using the same formulas card networks use, so you can see trouble before you cross a program threshold. Visa’s VAMP and Mastercard’s Excessive Chargeback Program each use their own formula and limits.

How chargeback ratios are calculated

At the simplest level, a chargeback ratio is disputes divided by transactions over a period. The details are where it gets tricky. Each network decides what counts on top, what counts on the bottom, and which month each belongs to. If you need a refresher on the dispute lifecycle itself, start with how chargebacks work.

Visa: the VAMP ratio

Since 2025, Visa monitors card-not-present merchants through the Visa Acquirer Monitoring Program (VAMP). According to Visa’s VAMP fact sheet, the ratio is count-based:

VAMP ratio = (TC40 fraud reports + TC15 disputes) ÷ TC05 settled transactions

TC40s are fraud reports that issuers file, whether or not the cardholder disputes. TC15s are disputes. A fraudulent transaction that’s both reported and disputed can be counted twice. Disputes resolved through certain pre-dispute tools, and fraud reports that qualify under Compelling Evidence 3.0, are excluded. Visa counts disputes and transactions in the same calendar month. Our deep dive on Visa VAMP covers the program in full.

Mastercard: the Excessive Chargeback Program ratio

Mastercard’s ratio is simpler on top but shifts the bottom:

Mastercard ratio = chargebacks received this month ÷ transactions from the previous month

The previous-month denominator matters a lot for seasonal businesses. A slow month followed by a busy one makes your ratio look worse than your real experience, because this month’s disputes are divided by last month’s smaller volume.

What the networks ignore

Three things your internal reports might include, but monitoring programs generally don’t:

• Dispute outcomes. A chargeback you won still counts. Networks measure how many disputes you get, not how many you win.
• Refunds after the fact. Refunding after a chargeback is filed doesn’t remove it from the count.
• Dollar amounts. The core ratios use counts, so a $9 dispute weighs the same as a $900 one.

A worked example: one merchant, two ratios

Take a summer camp registration platform. May is quiet; June brings the enrollment rush. Here’s what one month looks like through each network’s lens.

On Visa, the platform sits right at the 1.5% merchant threshold with a count above the 1,500 minimum. On Mastercard, 620 chargebacks against May’s slow volume puts it over 1.5% with more than 100 chargebacks. Its own dashboard, dividing lost disputes by June sales dollars, showed something under 1%.

Same business. Two programs flagging it. One internal report saying all was fine.

Current Visa and Mastercard thresholds

These are the main merchant-level thresholds as published by Visa and reproduced by major processors, current as of October 2026. Networks update programs, and your acquirer may apply stricter internal limits, so confirm with your processor before relying on them.

Visa also scores acquirers on their whole portfolio, with acquirer thresholds of 0.5% and 0.7%. That’s why some acquirers watch merchants far below 1.5%. A merchant at 0.9% may be adding to an acquirer’s portfolio problem, even if it’s under the merchant line.

What happens when you cross

Under VAMP, merchants identified as Excessive face fees per dispute and fraud report, widely reported at $8 each, usually passed through by the acquirer. Under Mastercard’s program, Stripe’s summary of card network monitoring programs shows fines rising the longer you stay in, and you exit after three consecutive months below threshold. Beyond fines, acquirers can require remediation plans, add reserves, or close the account.

Why chargeback ratio monitoring must be per MID

Networks identify merchants at the account level. Visa, for example, ties monitoring to the descriptor and acquirer. So if you run three MIDs, you have three ratios that matter, not one.

A combined number hides the account that’s in trouble. Consider a software company with an annual plan MID running at 0.3% and a monthly plan MID at 1.4%. The blended rate looks safe. The monthly plan’s MID is a few bad weeks from a program.

Don’t try to fix this by shifting clean volume onto the hot account, or by moving risky sales elsewhere. Card network rules prohibit spreading volume to mask dispute levels. Fix the cause on the account where it lives.

Building an early warning workflow

The goal of chargeback ratio monitoring is time. Network numbers arrive a month late. If you wait for your acquirer’s letter, the damage is already a month old.

Set internal levels below the network limits

Here’s a sample tier system. Tune it to your acquirer’s own warning levels.

The weekly monitoring routine

1. Pull month-to-date transaction counts per MID, split by card brand.
2. Pull disputes received month to date per MID, also by brand.
3. Calculate each brand’s ratio using its own formula, including Mastercard’s previous-month denominator.
4. Add any TC40 fraud reports your processor shares to the Visa numerator.
5. Project the month-end ratio based on the pace so far.
6. Break disputes down by reason code: fraud, not received, not as described, subscription cancelled, unrecognized.
7. Assign one fix per top reason, with an owner and a date.

Reason codes tell you where to act. Lots of fraud codes point to filters and card testing. “Not recognized” points to descriptors. “Cancelled recurring” points to billing reminders and an easier cancel flow. Our guide on how to reduce chargebacks has fixes for each.

Common monitoring mistakes

• Using dollar-based rates. The core network ratios are count-based. A dollar rate can look half as bad as the real one.
• Counting only lost disputes. Every dispute received counts, won or lost.
• Ignoring fraud reports. On Visa, TC40s sit in the numerator even when no dispute follows.
• Using the wrong month. Mastercard’s denominator is last month’s volume, which hurts after a slow month.
• Blending accounts. Chargeback ratio monitoring at the company level misses the one MID that’s slipping.

Pre-dispute alerts and how they affect ratios

Alerts are the other half of early warning. Services such as Mastercard’s Ethoca and Visa’s Verifi tools (including Rapid Dispute Resolution and Order Insight) let issuers notify you, or resolve a case automatically, before a formal chargeback is filed.

Under VAMP, disputes resolved through qualifying pre-dispute tools don’t count toward the ratio. Refunding in response to an alert can stop a dispute from being filed at all. Two caveats, though. A fraud report (TC40) may still be filed even if no dispute follows. And alerts cost money per case, so they’re best for merchants with meaningful dispute volume.

Enrollment usually runs through your processor or an alert provider, not through your CRM. Ask your acquirer which programs your MIDs are eligible for.

What to use for monitoring

The official numbers come from your acquirer and the networks. Your job is to estimate them early and act. That requires counts per MID, per brand, per month, plus dispute details by reason.

Midcove’s chargeback management pulls disputes from your MIDs on NMI, Authorize.Net, Stripe, and PayPal into one queue, with real-time alerts on new cases, deadline tracking, evidence upload, and win-rate reporting. Its reporting tools show volume, chargebacks, and refunds per MID side by side, and export to a spreadsheet where you can apply the Visa and Mastercard formulas above.

To be clear about scope: Midcove doesn’t replace Ethoca or Verifi alerts, and it doesn’t see TC40 fraud reports your processor hasn’t shared. Treat any in-house ratio as an estimate, and reconcile it with your acquirer’s monthly figures.

Key Takeaways

• Visa’s VAMP ratio counts fraud reports plus disputes against same-month settled transactions; Mastercard divides this month’s chargebacks by last month’s transactions.
• As of October 2026, the Visa merchant Excessive threshold is 1.5% with at least 1,500 fraud and disputes in most regions.
• Mastercard ECM starts at 100 chargebacks and 1.5%; HECM at 300 and 3%.
• Monitor every MID separately; blended rates hide the account at risk.
• Set internal warning levels well below network limits and review weekly.
• Pre-dispute alerts can keep disputes out of the count, but fraud reports may still land.

Frequently Asked Questions

How do you calculate a chargeback ratio?

Divide the number of chargebacks by the number of transactions for the same account and period. Visa’s VAMP adds fraud reports to the top and uses same-month settled transactions. Mastercard divides this month’s chargebacks by the previous month’s transactions. Calculate each network separately, per MID.

What is an acceptable chargeback ratio?

Network thresholds start at 1.5% for Visa VAMP and Mastercard ECM, but that’s a limit, not a target. Many acquirers start asking questions well below 1%. A practical goal is to stay under about 0.5% per MID, and to investigate any account trending upward.

What is the Visa chargeback threshold in 2026?

Under VAMP, the merchant Excessive threshold dropped from 2.2% to 1.5% on April 1, 2026, for the US, Canada, Europe, and Asia Pacific, with a minimum of 1,500 fraud reports plus disputes per month. Latin America already used 1.5%. CEMEA has its own levels, so confirm with your acquirer.

What is Mastercard’s Excessive Chargeback Merchant threshold?

Mastercard identifies an Excessive Chargeback Merchant at 100 or more chargebacks in a month with a ratio of 1.5% or higher, using the previous month’s transactions as the denominator. The High Excessive level starts at 300 chargebacks and 3%. Fines increase the longer a merchant stays in the program.

Do refunds lower your chargeback ratio?

Refunds don’t reduce disputes already filed. Refunding early can prevent a dispute from being filed in the first place, which keeps it out of the count. Refunding in response to a pre-dispute alert works the same way. A refund after a chargeback lands does nothing for the ratio.

Do won chargebacks still count toward the ratio?

Yes. Monitoring programs count disputes in the month they’re received, regardless of outcome, because waiting for every decision would take months. Winning a dispute recovers the revenue, but it does nothing for your ratio. That’s why prevention and early resolution matter more for program risk than representment win rates.

How often should I check chargeback ratios?

At least weekly for each MID, and daily for any account in a “watch” range. Network figures arrive about a month late, so your own month-to-date estimate is the only early signal. Project month-end ratios from the current pace so you can act before the month closes.

Are chargeback ratios measured per merchant account or per business?

Generally per merchant account. Visa ties monitoring to the descriptor and acquirer, and Mastercard calculates per merchant. A business with several MIDs has several ratios. One account can enter a program while the others are healthy, so track each one.

Watching the number that counts

Good chargeback ratio monitoring means using the networks’ math, not your gateway’s default report. Count disputes and fraud reports the way Visa does, use last month’s volume for Mastercard, and do it for every MID on its own, split by card brand. Then set warning levels well below the network limits, review weekly, and act on reason codes before the month closes.

The thresholds will keep moving; Visa’s drop to 1.5% this year is the latest example. A routine that tracks each account’s real ratio holds up regardless, because it’s built on the same counts the networks use. Midcove gives you one queue for disputes across your MIDs and per-account reporting to feed that routine, while the official numbers stay with your acquirer.