Small business owner reviewing online orders on a laptop next to shipping boxes
Pillar page

Chargeback Monitoring Programs Explained

What chargeback monitoring programs are, which thresholds trigger them, how Visa VAMP and Mastercard ECP work in 2026, and what Shopify merchants need to do before a notice arrives.

DE

DisputeDesk Editorial

Oct 6, 2026
21 min read
English

01What a chargeback monitoring program is, and the numbers that matter

A chargeback monitoring program is a formal network mechanism that tracks a merchant's chargeback or fraud ratio every calendar month and imposes escalating fines, mandatory remediation, and ultimately termination risk when that ratio stays above a published threshold. Visa, Mastercard, and American Express each run their own version. The programs are not optional, and the consequences flow through your acquirer to you — Shopify merchants included.

1.5%
Visa VAMP Excessive line
from 1 April 2026 (US, Canada, EU, Asia-Pacific)
1,500
fraud + dispute events
the monthly floor before VAMP's merchant program applies
100 · 300
chargebacks: ECM · HECM
on top of a 1.5% / 3.0% ratio at Mastercard
3 months
below the line to exit
Mastercard's rule; Visa has no fixed count

The cards below cover every major program. Where a figure is not published by the network, that is noted plainly.

Visa VAMP — Excessive
What triggers it
Ratio ≥ 1.5% (US/CA/EU/APAC from 1 Apr 2026; CEMEA 2.2%)
How the ratio is calculated
(TC40 fraud reports + TC15 disputes) ÷ settled CNP transactions
Minimum floor
1,500 fraud + dispute events per month
Cost
Reported $8 per fraud report or dispute, billed through acquirer
How you exit
Through acquirer remediation; no fixed month count in public fact sheet
Mastercard ECM
What triggers it
≥ 100 chargebacks AND ratio ≥ 1.50% (150 bps)
How the ratio is calculated
This month's chargebacks ÷ prior month's Mastercard transactions × 10,000
Minimum floor
100 chargebacks in the month
Cost
$0 month 1; $1,000 month 2–3; $5,000 months 4–6; escalates to $100,000/month at month 19+
How you exit
Three consecutive months below ECM threshold
Mastercard HECM
What triggers it
≥ 300 chargebacks AND ratio ≥ 3.00% (300 bps)
How the ratio is calculated
Same as ECM
Minimum floor
300 chargebacks in the month
Cost
$0 month 1; $1,000 month 2; $2,000 month 3; $10,000 months 4–6; escalates to $200,000/month at month 19+; plus $5 per chargeback above 300 from month 4
How you exit
Three consecutive months below ECM threshold
Mastercard EFM
What triggers it
Reported: ≥ 1,000 e-commerce transactions, ≥ $50,000 in fraud chargebacks, fraud chargeback ratio ≥ 0.50%
How the ratio is calculated
Fraud-reason chargebacks only; prior-month denominator
Minimum floor
1,000 e-commerce transactions
Cost
Reported; confirm with your processor
How you exit
Below EFM threshold; if both EFM and ECM apply in the same month, only EFM assessment is charged
American Express
What triggers it
Reported: ratio above 1% for three consecutive months
How the ratio is calculated
Not published in detail; Amex goes straight to chargeback without an inquiry stage
How you exit
Not published; contact your Amex relationship or processor
Discover
What triggers it
No published program
How you exit
N/A — processor internal limits apply

02Who is actually enrolled: your acquirer, not you

Visa and Mastercard hold the acquirer responsible, not the merchant. Both networks measure at the Merchant ID (MID) level — the acquirer-assigned identifier that appears in the clearing record — and they assess the acquirer for noncompliance. The acquirer then passes the fines, the remediation requirements, and the reputational pressure down to the merchant. That chain matters because it shapes everything about how a notice arrives, what it says, and how much room you have to respond.

The number in a notice is always last month's ratio. Network data flows through clearing and settlement, gets aggregated, and is reported on a monthly cycle. By the time your acquirer forwards the placement notice — whether by email, through your payment provider's dashboard, or through Shopify's own notification path — the ratio that triggered it describes a month that has already ended. The disputes that drove it have long since been filed. That lag is not a technicality; it means the ratio you are running right now could already be worse than the one in the letter, or it could have improved, and you will not know which for another month.

Acquirers and processors also run their own internal monitoring lines, and those lines are almost always tighter than the network thresholds. An acquirer may flag a merchant internally well below the Visa VAMP Excessive threshold of 1.5%, because the acquirer itself faces network-level consequences if its aggregate portfolio ratio climbs too high. Visa's acquirer-level Above Standard threshold is 0.5% (enforced from 1 January 2026), and the acquirer Excessive threshold is 0.7%. An acquirer carrying a merchant at 1.2% is already absorbing portfolio risk before that merchant ever crosses the formal merchant program line. The practical result: a processor can impose reserves, reprice your rates, or restrict your processing volume based entirely on its own internal risk model, with no network program involved at all.

03Are you big enough to be enrolled? The arithmetic most guides skip

Most articles on chargeback monitoring programs skip the volume question entirely, which leaves small merchants convinced they are one bad month away from a Visa enforcement action when they are nowhere near the scope threshold. The honest answer requires a little arithmetic.

Visa VAMP's merchant program only applies once a merchant has at least 1,500 fraud reports plus disputes in a single month. That floor counts events — TC40 fraud reports and TC15 disputes combined — not transactions. To generate 1,500 events, you need enough volume that 1,500 of your orders are generating fraud reports or disputes. At a 1.5% ratio, that means 100,000 settled card-not-present transactions in the month. At a 3% ratio, still 50,000. At 5%, still 30,000.

Mastercard ECM requires both a ratio of at least 1.50% and at least 100 chargebacks in the calendar month. To reach 100 chargebacks at exactly 1.5%, you need roughly 6,667 prior-month Mastercard transactions. That is a much lower bar than Visa — but it is still a bar, and a merchant running 500 Mastercard transactions a month who has 20 chargebacks is at a 4% ratio without being anywhere near the 100-chargeback floor.

Ratio you are runningVisa: monthly settled CNP transactions needed to reach the 1,500 floorMastercard ECM: prior-month Mastercard transactions needed to reach 100 chargebacks
1.5%100,000about 6,700
3%50,000about 3,300
5%30,0002,000

Most small Shopify stores — a few hundred to a few thousand orders a month — are below both of those floors. The formal Visa VAMP merchant program will not apply to them, and Mastercard ECM is unlikely to apply unless their chargeback rate is extremely high and their Mastercard volume is concentrated. That is the honest answer to the question most merchants are actually asking when they search this topic.

04Visa VAMP in detail

The Visa Acquirer Monitoring Program (VAMP), which took effect 1 April 2025, replaced five earlier Visa fraud and dispute programs — including the Visa Dispute Monitoring Program (VDMP) and the Visa Fraud Monitoring Program (VFMP) — and consolidated 38 separate remediation processes into one. An advisory period ran from 1 April 2025 through 30 September 2025. Enforcement of the Excessive merchant tier began after that, from 1 October 2025.

The ratio and formula

The VAMP ratio
TC40 fraud reports + TC15 disputes
settled card-not-present transactions (TC05)

The VAMP ratio is calculated as: (TC40 fraud reports + TC15 disputes) divided by settled card-not-present transactions (TC05). Card-present transactions are excluded entirely. One important wrinkle: a single order can generate both a TC40 fraud report and a TC15 dispute, and if it does, it counts in both the numerator components. That means a merchant with a high rate of fraud-that-becomes-a-dispute can see its event count climb faster than its raw dispute count would suggest.

The 1,500 floor

A merchant is only measured under the formal VAMP merchant program once it has at least 1,500 fraud-plus-dispute events in a month. The 1,500 is a count of events, not transactions. A merchant with 90,000 settled CNP transactions and 1,500 events is right at the floor. A merchant with 40,000 settled CNP transactions and 1,200 events is below the floor regardless of what ratio that produces — the formal program does not apply that month, though the acquirer's own risk team may still act on the ratio.

The 1.5% threshold and the 2025–2026 timeline

The Excessive merchant threshold was 2.2% at launch. It stepped down to 1.5% (150 basis points) from 1 April 2026 for merchants in the US, Canada, the EU, and Asia-Pacific. CEMEA remains at 2.2%. There is no warning tier for merchants — one Excessive line, and crossing it while above the 1,500 floor puts the merchant in scope. Reported: a first-time breach within a rolling twelve months gets a three-month delay before enrollment begins; confirm the current application of that provision with your acquirer.

What is excluded and what that means

Two categories of disputes are excluded from the VAMP ratio: disputes resolved through Compelling Evidence 3.0 (CE 3.0), and disputes stopped by pre-dispute tools. Disputes resolved through Rapid Dispute Resolution (RDR) and through dispute alerts such as Verifi CDRN and Ethoca Alerts are reported as not counting toward the ratio. This exclusion is operationally significant: it means that a merchant close to the 1.5% line has a lever that actually moves the ratio, not just the dispute outcome. A dispute that is filed and then won does not come off the ratio. Only prevention — stopping the dispute before it is filed, or qualifying it under CE 3.0 — keeps it out of the count.

Cost and tiers

There is no merchant warning tier under VAMP — the program goes straight to Excessive. The reported fee is $8 per fraud report or dispute, billed through the acquirer. At 1,500 events, that is $12,000 in a single month. The fee is charged per event, so the cost scales with the count: 2,000 events would be 2,000 × $8 = $16,000 in a month. Acquirers may pass through additional surcharges on top of the network fee; confirm the exact pass-through structure with your processor.

05Mastercard ECP and EFM in detail

Mastercard's Excessive Chargeback Program (ECP), defined in the Mastercard Security Rules and Procedures, Merchant Edition (August 2026), section 8.3.1, runs on a different clock and a different formula than VAMP. The two programs are not interchangeable, and a merchant can be in one without being anywhere near the other.

ECM and HECM thresholds

ECM
Excessive Chargeback Merchant
100+ chargebacks
AND
ratio ≥ 1.50% (150 bps)
both conditions, in the same month
HECM
High Excessive Chargeback Merchant
300+ chargebacks
AND
ratio ≥ 3.00% (300 bps)
both conditions, in the same month

Excessive Chargeback Merchant (ECM): at least 100 chargebacks received in the calendar month AND a ratio of at least 150 basis points (1.50%). High Excessive Chargeback Merchant (HECM): at least 300 chargebacks AND at least 300 basis points (3.00%). Both conditions must be met simultaneously — a merchant with 150 chargebacks at a 1.2% ratio is not ECM; a merchant with 80 chargebacks at a 2.5% ratio is not ECM either. The program is measured per MID, and Mastercard assesses the acquirer for noncompliance.

The prior-month denominator

Mastercard basis points
chargebacks received this month
Mastercard transactions last month
× 10,000

This is where Mastercard's formula diverges from intuition. The ratio uses this month's chargebacks in the numerator and last month's transaction count in the denominator. A large sales month inflates the denominator for the following month's ratio calculation, which makes that following month look artificially safe — even if disputes from the big sale are already arriving. The danger arrives one month later, when the sale's disputes are still coming in against a normal-sized denominator. A Black Friday or BFCM spike in November produces a low December ratio (big November denominator) and a potentially dangerous January ratio (normal December denominator, but November's disputes still arriving). Shopify merchants who run seasonal promotions should map this two-month lag explicitly.

Fine schedule

Monthly fine by consecutive month above the threshold
Linear scale, USD. ECM vs HECM.
ECMHECM
$0$50k$100k$150k$200k$1k$1kMonth 2$1k$2kMonth 3$5k$10kMonths 4–6$25k$50kMonths 7–11$50k$100kMonths 12–18$100k$200kMonth 19+
Consecutive months in programECM fine (per month)HECM fine (per month)
Month 1$0$0
Month 2$1,000$1,000
Month 3$1,000$2,000
Months 4–6$5,000$10,000
Months 7–11$25,000$50,000
Months 12–18$50,000$100,000
Month 19 onward$100,000$200,000

Source: J.P. Morgan Payments, Mastercard Excessive Chargeback Program guide (rev. 12/2019), reproducing Mastercard's fine structure. Amounts can change; confirm current figures with your acquirer.

Issuer recovery assessment

From the fourth month in the program, a separate issuer recovery assessment applies: $5 per chargeback above 300 chargebacks in the month. A merchant with 500 chargebacks in month four pays (500 − 300) × $5 = $1,000 in issuer recovery on top of the monthly fine. This assessment is in addition to, not instead of, the fine.

What Mastercard can require after six months

After a merchant has been ECM or HECM for six months — consecutive or not — Mastercard may advise the acquirer on an action plan and may require the acquirer to undergo a Franchise Management Program Customer Risk Review at the acquirer's own expense. That last clause matters: the acquirer is paying for the review, which means the acquirer has a strong incentive to terminate the merchant before reaching that point rather than absorb the cost and reputational exposure.

Exit

To exit ECP, the merchant's MID must be below the ECM threshold for three consecutive months. The status resets automatically; a later breach is treated as a first-time breach and the fine clock restarts at month one.

EFM

The Excessive Fraud Merchant (EFM) program targets e-commerce fraud specifically. Reported trigger: at least 1,000 e-commerce transactions, at least $50,000 in fraud chargebacks, and a fraud chargeback ratio of at least 0.50%. EFM counts fraud-reason chargebacks only, not all chargebacks. If a MID is noncompliant under both EFM and ECM in the same month, only the EFM assessment applies — the two programs do not stack. EFM thresholds are reported by processors; the Mastercard rulebook points to a separate monitoring manual, so confirm current figures with your acquirer.

06Worked examples

VisaVisa example A: at the line
Ratio 1.67%1,500 eventsExcessive$12,000 that month

A merchant settles 90,000 card-not-present transactions in a month and has 650 fraud reports (TC40) plus 850 disputes (TC15), for 1,500 total events. Ratio = 1,500 ÷ 90,000 = 1.67%. That is above the 1.5% Excessive threshold and exactly at the 1,500-event floor, so the merchant is Excessive. At the reported $8 per event: 1,500 × $8 = $12,000 for that month.

VisaVisa example A — prevention variant
Ratio 1.38%1,240 eventsOut of scope

Same merchant, same month. But 260 of the 850 disputes were stopped by Rapid Dispute Resolution or dispute alerts before they were filed, and so are excluded from the ratio. Disputes counted = 590. Total events = 650 + 590 = 1,240. Ratio = 1,240 ÷ 90,000 = 1.38%. That is under 1.5% and also under the 1,500-event floor, so the merchant is not in scope at all that month. The lesson: at this volume, pre-dispute tools do not just reduce the ratio — they can move a merchant entirely out of the program's scope.

VisaVisa example B: high ratio, below the floor
Ratio 3.00%1,200 eventsBelow the floor: not in scope

A merchant settles 40,000 card-not-present transactions and has 500 fraud reports plus 700 disputes, for 1,200 events. Ratio = 1,200 ÷ 40,000 = 3.00% — double the Excessive threshold. But 1,200 events is below the 1,500 floor, so the formal VAMP merchant program does not apply that month. The acquirer's own risk team may still act on a 3% ratio, and almost certainly will.

MastercardMastercard sales-spike example

A merchant's baseline is 10,000 Mastercard transactions a month. An October promotion produces 20,000 transactions. Chargebacks received: October 40, November 140, December 150, January 60.

The October sale, month by month
Bars: chargebacks received. Ratio = that month's chargebacks ÷ the previous month's transactions.
050100150100-chargeback floor40Oct20,000 txns · sale monthration/a140Nov10,000 txnsratio0.70%Looks safe150Dec10,000 txnsratio1.50%ECM60Jan10,000 txnsratio0.60%Clear
  • November ratio: 140 ÷ 20,000 (October's transactions) = 0.70% with 140 chargebacks. Below both the 1.50% threshold and the 100-chargeback floor — safe, because October's large transaction count inflates the denominator.
  • December ratio: 150 ÷ 10,000 (November's transactions) = 1.50% with 150 chargebacks. Both conditions met: the merchant becomes an Excessive Chargeback Merchant for the first time in December. To have stayed out, it would have needed 149 or fewer chargebacks (1.49%).
  • January ratio: 60 ÷ 10,000 (December's transactions) = 0.60% with 60 chargebacks. Back below both limits.

The lesson: the October promotion's disputes arrived two months after the sale, against a normal denominator, and that is what triggered ECM — not the month of the sale itself.

MastercardMastercard six-month fine total
$17,000 in finesbefore any processor surcharge

A merchant stays at the ECM level for six consecutive months, with fewer than 300 chargebacks each month (so no issuer recovery applies). Fine total: month 1 $0 + month 2 $1,000 + month 3 $1,000 + months 4, 5, and 6 at $5,000 each = $17,000 in network fines before any processor surcharge or reserve adjustment.

07American Express and Discover

American Express operates its own dispute process and does not use the Visa or Mastercard network rails. The reported excessive chargeback threshold is above 1% for three consecutive months, at which point Amex may contact the merchant or acquirer directly. Amex goes straight to chargeback without a pre-dispute inquiry stage, which means disputes arrive faster and with less warning than on the Visa or Mastercard networks. The specific fine structure and remediation requirements are not published; contact your Amex relationship manager or processor for current program details.

Discover has no published chargeback monitoring program. Processors commonly use an informal rule of thumb of around 1% or roughly 100 chargebacks a month as an internal trigger, but that is a processor convention, not a Discover document. If you process meaningful Discover volume and your chargeback rate is elevated, the risk is an internal processor action rather than a formal network program.

08What happens if you stay in: from first notice to termination and MATCH Pro

The Mastercard fine escalation in practice

Month one in ECM costs nothing in fines — but it is not free. The acquirer is now aware, the clock has started, and the three-consecutive-months exit clock has not. Month two brings a $1,000 fine. Month three, another $1,000. By month four the fine jumps to $5,000 per month and stays there through month six. A merchant that enters ECM in January and cannot get below the threshold until June has paid $17,000 in fines by the time it exits — and that is at the ECM level, with fewer than 300 chargebacks. At HECM, the same six months costs $33,000 in fines ($0 + $1,000 + $2,000 + three months at $10,000), plus the issuer recovery assessment from month four onward.

After six months in the program — consecutive or not — Mastercard may advise the acquirer on an action plan and can require a Franchise Management Program Customer Risk Review at the acquirer's expense. At that point the acquirer's incentive to terminate the merchant becomes very strong, because the acquirer is absorbing both the fine pass-through risk and the cost of the review.

Termination, reserves, and repricing

Acquirer termination is the acquirer's decision, not the network's. Networks do not directly terminate merchant accounts; they pressure acquirers through fines and program requirements, and acquirers act. The practical path looks like this: notice arrives, remediation plan is requested, fines begin accumulating, the acquirer reprices the account or imposes a rolling reserve to offset its exposure, and if the ratio does not improve, the acquirer terminates the MID. Repricing and reserves can happen at any point in that sequence — they do not require a formal network program to be in place.

MATCH Pro

MATCH Pro — Mastercard Alert To Control High-risk Merchants — is a mandatory database that acquirers must check before signing any new merchant. If an acquirer terminates a merchant and a listed reason applies, it must add the merchant to MATCH Pro within five calendar days of the earlier of the termination decision or the merchant's own notice of departure.

The two reason codes most relevant to chargeback monitoring are Reason Code 04 (Excessive Chargebacks) and Reason Code 05 (Excessive Fraud).

RC 04
Excessive Chargebacks
Mastercard chargebacks over the previous three months exceeded 1.5% of Mastercard sales transactions in that month, and the chargebacks totalled at least $5,000.
RC 05
Excessive Fraud
Fraud-to-sales dollar volume of 8% or more over the previous three months, and 10 or more fraudulent transactions of $5,000 or more in that period.

A listed merchant can request removal from the acquirer that entered the listing. No lawyer is required. The request must include the merchant name, address, the principal owner's first and last name, and the website URL if applicable. Mastercard can remove a listing that was entered in error.

09How to get out: what moves each ratio and what does not

The levers that actually reduce a monitoring program ratio split into three categories, and conflating them is where most remediation plans go wrong.

Keeps disputes out of the ratio
Levers that keep disputes out of the Visa VAMP ratio

Pre-dispute tools — Verifi CDRN alerts, Ethoca Alerts, and Rapid Dispute Resolution — stop a dispute before it is filed as a TC15. Because the dispute never reaches the filed stage, it is excluded from the VAMP ratio. At the volume levels where VAMP applies, this is the single highest-leverage operational change available. A merchant running 90,000 CNP transactions a month and stopping 260 disputes through RDR or alerts can move from Excessive to out-of-scope entirely, as the worked example above shows.

Compelling Evidence 3.0 (CE 3.0) is a Visa rule that lets a merchant answer a fraud dispute (condition 10.4) with proof of two earlier undisputed transactions: each settled 120 to 365 days before the dispute, not reported as fraud, and matching the disputed transaction on at least two data elements, one of which must be the IP address or the device ID or fingerprint. The other can be the customer account login or the full delivery address. A dispute that qualifies under CE 3.0 is excluded from the VAMP ratio. Not every fraud dispute qualifies, and the evidence assembly is specific; it is not a general-purpose tool.

Reduces disputes upstream
Levers that reduce fraud and disputes upstream

These do not change how a filed dispute is counted, but they reduce the number of disputes that get filed in the first place. Strong authentication — 3DS2 with liability shift, AVS and CVV checks, velocity rules — reduces unauthorized transaction disputes. Clear billing descriptors reduce "I don't recognize this charge" disputes. Proactive post-purchase communication (shipping confirmations, delivery notifications, easy return instructions) reduces not-received and not-as-described disputes. Refunding a transaction before the customer disputes it means no chargeback is ever filed, so nothing is counted on either network.

Fulfillment speed and carrier reliability matter more than most merchants expect. A dispute filed because an order was 18 days late is a real chargeback that counts against the ratio. Switching to a carrier with better tracking and fewer delivery failures is a ratio-reduction strategy, not just a customer service improvement.

Does not move the number
Things that do not move the number

Winning a filed dispute does not remove it from the Visa VAMP ratio or the Mastercard chargeback count. The event was counted when it was filed. A merchant that fights every dispute and wins 70% of them has the same ratio as a merchant that accepts every dispute — the wins do not come off the numerator. This is the most operationally consequential fact in chargeback management, and it is the one most often misunderstood. Dispute responses matter for revenue recovery and for demonstrating good-faith remediation to an acquirer, but they do not directly reduce a monitoring program ratio.

Exit conditions

Mastercard requires three consecutive months below the ECM threshold. The status resets automatically; no acquirer action is required. A later breach restarts the clock at month one. Visa's public fact sheet gives no fixed number of months to exit; remediation runs through the acquirer, and the timeline depends on the acquirer's own remediation program structure. If you are in VAMP, ask your acquirer explicitly what the exit criteria look like in their program — the network document does not specify it.

10If you sell on Shopify

Shopify merchants interact with chargebacks through the Disputes list in their Shopify admin, which surfaces individual disputes as they arrive. That list is useful for tracking and responding to disputes, but it does not show your VAMP ratio or your Mastercard ECM status. The ratio that networks and acquirers monitor is calculated by the acquirer from network clearing data — not from your Shopify order count. Any ratio you calculate yourself from the Disputes list is an approximation, and it will differ from the acquirer's number for several reasons: timing differences in when disputes clear, the treatment of fraud reports (TC40s) that never become visible disputes, and the specific transaction types included in the denominator.

If a monitoring program notice is coming, it will arrive through Shopify or your payment provider — not directly from Visa or Mastercard. Shopify Payments merchants will typically see it through their payment provider communications. Third-party gateway merchants will receive it through their gateway or acquirer. The notice will reference last month's ratio, not the current one.

Flash sales and BFCM create the exact Mastercard denominator distortion described in the worked example above. A Shopify merchant who runs a significant November sale should map the two-month lag: November's large transaction count makes December's ratio look safe, but January's ratio — when November's disputes are still arriving against a normal December denominator — is the month to watch. Build that projection in October, before the sale, not in January when the disputes are already filed.

A monthly routine
  1. 1Open the Disputes list in your Shopify admin.
  2. 2Count the disputes received this calendar month.
  3. 3Compare that count with last month's order volume.
  4. 4Watch the trend, not only the line.
You do not need to hit a network threshold for the trend to matter — your processor's internal risk team is watching the same numbers, and they act earlier than the network programs do. A ratio climbing from 0.4% to 0.7% over three months is a signal worth acting on before it becomes a notice.
11 · DisputeDesk

How DisputeDesk handles this for Shopify merchants

Syncs your disputesBuilds the evidence packEstimates your ratios nightly

DisputeDesk is built for Shopify merchants. It connects to your store, syncs disputes automatically, and builds an evidence pack for each dispute. Based on your automation settings, it sends the evidence through Shopify so disputes do not sit unanswered until the deadline — the deadline scramble that quietly costs merchants winnable cases and recoverable revenue.

Each night, DisputeDesk calculates your estimated Visa VAMP and Mastercard ECM ratios from your Shopify data and shows how close each is to its line, and your monthly digest email flags it when you are approaching Visa’s VAMP line. These are calculated estimates — only your acquirer has the official number — but they give you a working view of your trend before a notice arrives, not after.

Where a Visa fraud dispute qualifies, DisputeDesk builds Compelling Evidence 3.0 style evidence. CE 3.0 is one of the routes that keeps a dispute out of the Visa VAMP ratio entirely, not just a response that might win. Answering every dispute on time with the right evidence recovers revenue and removes the operational scramble. You stay in control through your automation settings.

To see your current estimated ratios and get disputes off your plate, connect your Shopify store to DisputeDesk.

Connect your Shopify store
Sources and last verified
  • Visa Acquirer Monitoring Program fact sheet (2025) and Visa Perspectives program updates
  • Mastercard Security Rules and Procedures, Merchant Edition (August 2026)
  • J.P. Morgan Payments, Mastercard Excessive Chargeback Program guide (rev. 12/2019), reproducing Mastercard's fine structure
  • Merchant Risk Council VAMP guidance (2026)
Last verified 5 October 2026.

Key Takeaways

Visa VAMP's Excessive threshold is 1.5% from 1 April 2026, but only merchants with at least 1,500 fraud-plus-dispute events a month are in scope — roughly 100,000 settled CNP transactions at that ratio.
Mastercard ECM uses last month's transaction count as the denominator, so a big sales month makes the following month look safe — and the month after that dangerous.
Winning a filed dispute does not remove it from your Visa VAMP ratio. Only prevention tools (RDR, dispute alerts, Compelling Evidence 3.0) keep a dispute out of the count.
Most small Shopify stores are below the network floors, but processors run tighter internal limits that can trigger reserves and account reviews well before any network program applies.
The Disputes list in your Shopify admin is a useful approximation, not the official ratio — that number lives with your acquirer.

FAQ

What is a chargeback monitoring program?
A formal network program that tracks a merchant's chargeback or fraud ratio each month and imposes fines, remediation requirements, or termination risk when the ratio exceeds a published threshold.
What is the Visa VAMP threshold in 2026?
1.5% (150 basis points) for merchants in the US, Canada, EU, and Asia-Pacific from 1 April 2026. CEMEA remains at 2.2%. A merchant must also have at least 1,500 fraud-plus-dispute events in the month to be in scope.
Does the VAMP 1,500 minimum count transactions or disputes?
It counts fraud reports (TC40) plus disputes (TC15) — events, not transactions. A single order can generate both a fraud report and a dispute and count twice.
What are the Mastercard ECM and HECM thresholds?
ECM: at least 100 chargebacks AND a ratio of at least 1.50% (150 basis points). HECM: at least 300 chargebacks AND at least 3.00% (300 basis points).
How is the Mastercard chargeback ratio calculated?
Chargebacks received this calendar month divided by the number of Mastercard transactions in the preceding month, multiplied by 10,000 to express in basis points.
How long does it take to get out of a monitoring program?
Mastercard requires three consecutive months below the ECM threshold. Visa's public fact sheet gives no fixed month count; exit runs through acquirer remediation.
Do chargeback alerts and Rapid Dispute Resolution count toward my ratio?
For Visa VAMP, disputes stopped by pre-dispute tools such as Verifi CDRN, Ethoca Alerts, and Rapid Dispute Resolution are reported as excluded from the ratio. Mastercard's ECP counts all chargebacks received regardless of how they were resolved.
If I win a dispute does it come off my ratio?
No. A filed dispute counts toward the Visa VAMP ratio and the Mastercard chargeback count even if the merchant wins it. Only prevention keeps a dispute out of the Visa ratio.
What is MATCH Pro and how do merchants end up on it?
MATCH Pro is Mastercard's mandatory database of terminated merchants. An acquirer that terminates a merchant for excessive chargebacks (Reason Code 04) or excessive fraud (Reason Code 05) must add the merchant within five calendar days.
Can my processor put me in monitoring before I hit a network threshold?
Yes. Most processors and acquirers run internal risk limits that are tighter than the network floors. They can impose reserves, reprice, or restrict processing before any formal network program applies.
Is my small Shopify store big enough to be put in a monitoring program?
Probably not by the networks directly. Visa VAMP requires roughly 100,000 settled CNP transactions a month at a 1.5% ratio to hit the 1,500-event floor. Mastercard ECM requires at least 100 chargebacks. Most small stores never reach those floors — but their processor's internal limits are a real and separate risk.

Disclaimer

This content is for informational purposes only and does not constitute legal advice.

Automate Your Chargeback Responses

DisputeDesk automatically tracks deadlines, collects evidence, and generates winning responses so you never miss a deadline again.