Chargeback ratio explained (it is not one number)
"Chargeback ratio" sounds like one number. It is not.
Visa runs one calculation for its own monitoring program. Mastercard runs a different one, on a different denominator and a different clock. And the processor or acquirer actually holding your money often runs a third figure, on its own window, that can flag your account before either network does. I have watched a merchant sit comfortably under Visa's threshold and get a risk email from their processor the same week. Neither number was wrong. They were not measuring the same thing.
What is a chargeback ratio?
Strip it down and a chargeback ratio is disputes measured against some volume of transactions, expressed as a percentage or basis points, used to decide whether a merchant is disputing too much relative to what it processes. That is the entire part everyone agrees on.
Everything past that sentence is decided separately by whoever is doing the counting: what counts as a dispute, what it is divided by, over what window, and whether a case you won gets subtracted back out. At least three parties count independently. The card network runs its own program. Your acquirer often layers its own contractual threshold on top, usually tighter and enforced sooner. And some processors, PayPal is the clearest public example, run an entirely separate ratio for their own account-risk decision, with no reference to whether you have crossed a network threshold at all.
Visa's VAMP ratio, the one most people mean by default
Visa's is a count, not a dollar figure: fraud reports (TC40) plus disputes (TC15), divided by settled card-not-present transactions (TC05), evaluated monthly. The excessive-merchant line sits at 150 basis points (1.5%) in most regions as of April 1, 2026, with a floor of 1,500 combined events a month before the ratio applies at all. Visa's 2026 VAMP thresholds breaks the full regional table down, including the acquirer-level thresholds that sit well below the merchant line. Worth naming here: VAMP is a 2025 consolidation. The Visa Dispute Monitoring Program and Visa Fraud Monitoring Program, VDMP and VFMP, that a lot of chargeback content still describes as Visa's active framework were folded into VAMP and are no longer the program your acquirer is enforcing. If a page you are reading names either one as current, the page is stale.
Mastercard's ratio runs on a one-month lag
Mastercard's Excessive Chargeback Program counts differently in a way that trips people up. According to PayPal's Braintree documentation on card brand monitoring programs, checked July 22, 2026, the ratio is chargebacks received in a given month divided by sales processed in the prior month, not the same month. A merchant flagged for June chargebacks is being measured against May's volume.
The thresholds pair a ratio with a raw count, both required at once. The Excessive Chargeback Merchant tier triggers at 100 to 299 chargebacks in the month and a ratio of 1.50% to 2.99%. Cross 300 chargebacks and 3.00% and it escalates to the High Excessive tier. The lag matters operationally: a slow sales month ahead of a normal dispute month can push the ratio over the line with dispute behavior unchanged, and growing volume in the current month does nothing to help this month's number, since the denominator is already fixed to the month before.
The number your processor actually watches
This is the layer most chargeback content skips, and it is the one that reaches merchants first in practice.
Some processors run no ratio of their own. Stripe is the clean example. Per Stripe's own documentation on dispute and fraud monitoring programs, checked July 22, 2026, Stripe does not operate an independent program. It relays network monitoring data monthly and notifies you if a network places you in one. But Stripe is explicit about a gap worth knowing: some disputes where you carry no liability do not appear in your Stripe dashboard or API responses, and are not charged to you, yet monitoring programs still include them in what they report to the network. Your dashboard number and the number a network is actually acting on are not guaranteed to match.
Other processors run their own separate ratio, enforced directly, with no network trigger required. PayPal is the clearest public case. Its dispute rate, per PayPal's own help documentation, checked July 22, 2026, is dollar-weighted rather than count-based: the disputed amount of item-not-received and not-as-described claims, divided by net sales, over the trailing three calendar months. Cross 1.5% with more than 100 transactions in that window and PayPal charges a High Volume Dispute Fee, independent of anything Visa or Mastercard is separately calculating on the same transactions.
That is the same fact this site has argued about Visa's ratio, stated here in a processor's own words about its own separate number: winning a chargeback does not fix your dispute ratio either, and it does not fix a processor's dispute rate.
How the ratios compare
| Ratio | Counts | Divided by | Window | 2026 threshold | Who enforces it |
|---|---|---|---|---|---|
| Visa VAMP | TC40 fraud + TC15 disputes | Settled card-not-present transactions | Same calendar month | 150 bps most regions, from April 1, 2026, with a 1,500-event floor | Visa, through your acquirer |
| Mastercard ECM / HECM | Chargebacks received | Sales processed the prior month | One-month lag | 1.50-2.99% and 100+ chargebacks (ECM); 3.00%+ and 300+ (HECM) | Mastercard, through your acquirer |
| PayPal dispute rate | Dollar amount disputed (item not received, not as described) | Net sales dollars | Trailing 3 calendar months | 1.5%, once over 100 transactions in the window | PayPal directly |
| Stripe and most processors | No independent ratio; relays the network's own figures | Whatever the relevant network uses | Whatever the relevant network uses | Not independently published | The network, via your processor's notice |
Read the denominator column twice. A count-based ratio and a dollar-weighted one can move in opposite directions on the same batch of disputes. A store with a few large clean transactions looks better on a dollar-weighted number than it does on a count, because the clean dollars are doing more diluting than the clean orders are.
The honest part
I want to be precise about what a merchant can actually verify here. You can approximate Visa's or Mastercard's ratio from your own data, and how to calculate your VAMP ratio walks through doing that. You generally cannot reconstruct a processor's undisclosed internal risk threshold the same way. Stripe does not publish one. Your acquirer's contractual limit lives in an agreement you may not have reread since you signed it.
That leaves one reliable move, and it is not a calculation. Ask your acquirer and your processor separately, in writing, three questions: what ratio do they calculate for your account, over what window, and what is their own internal action threshold, as distinct from the network's published one. Acquirers frequently set a tighter internal line than Visa or Mastercard requires, because they carry the network's risk before it ever reaches you.
Frequently asked questions
Is the chargeback ratio the same across Visa, Mastercard, and my processor?
No. Visa's VAMP ratio counts fraud reports and disputes against settled transactions in the same month. Mastercard's ECM ratio counts chargebacks against the prior month's sales. Processors like PayPal can run a separate, dollar-weighted dispute rate on their own window. A merchant can be under one threshold and over another at the same time.
Are VDMP and VFMP still Visa's active chargeback programs?
No. Visa consolidated the Visa Dispute Monitoring Program and the Visa Fraud Monitoring Program into the Visa Acquirer Monitoring Program (VAMP) in 2025. Content that still names VDMP or VFMP as Visa's current framework is describing a retired structure.
Does winning a chargeback remove it from any of these ratios?
Not that we found documented anywhere. Visa's exclusion list does not include disputes that were won. PayPal states its high-volume dispute fee does not depend on case outcome. A dispute is counted at filing or creation, and resolving it in your favor recovers the money without pulling the entry back out of the ratio.
Which ratio should I watch first?
Whichever one your acquirer or processor tells you, in writing, that they act on internally. That figure is frequently tighter and reached sooner than the network's own published threshold, since your acquirer or processor is managing its own risk on your account before a network ever gets involved.
The test I'd run: pull last month's dispute count and dollar total, then ask your acquirer and your processor, separately, what ratio each is holding you to and over what window. If the two answers disagree, manage to the stricter one. It is the one that will act first.