Skip to main content

Monitoring & Remediation

Last updated . Copy page as text

TL;DR
  • Know the published lines. Visa's U.S. excessive test is 1.5% with 1,500 fraud reports and disputes, when the acquirer condition applies. Stripe describes dispute activity above 0.75% as excessive. Shopify can enroll at 1.5% over 90 days on its NDRP inclusive rate. PayPal charges its high volume fee at its own 1.5% dispute ratio with more than 100 sales in the prior three full calendar months. Each metric differs (who publishes what)
  • Watch the trend, get your processor's own limit in writing, and respond to a warning today
  • Mastercard: both count AND ratio must be met (ECM is 100-299 chargebacks AND 1.50-2.99%; HECM is 300+ AND 3.00%+)
  • Exit differs by program: Mastercard ECP/EFM sources say three consecutive compliant months. VAMP sources disagree on one versus three; get your applicable conditions in writing
  • Termination risk: use the conditions in your agreement and notice. A program month isn't a universal closure deadline
  • This page covers how to monitor and respond. For exact thresholds, fees, and timelines, see Network Programs Reference.

This page teaches you how to monitor your dispute ratios and what to do when they're trending in the wrong direction. For the complete threshold tables, fee schedules, and month-by-month escalation timelines, see Network Programs Reference.

What to Do as Your Ratio Rises​

NOT PUBLISHED Universal healthy, danger or crisis bands. Use your processor's limit and the published program lines below.

What you're seeingWhat to do
Stable figures below your limitKeep monitoring counts and ratios. Check the reporting period
A rising ratio or dispute countStart free prevention fixes. Find the cause before you reach the limit
Approaching your processor's own limitFix descriptor and support problems. Review 3DS and alerts against the dispute causes
A warning or breach noticeConfirm its metric and deadline. Use the crisis playbook and reduce chargebacks fast
Low-Volume Warning

At low transaction counts, a single bad month can spike your ratio. 5 chargebacks on 1,000 transactions = 0.5%. Read the counts beside the rate. A rolling average can help you see the trend, but it doesn't replace the reporting period your processor or network uses.

Programs at a Glance​

NetworkProgramKey TriggerDetails
VisaVAMP (replaced VDMP + VFMP, April 2025)U.S.: at least 1.5% AND 1,500 combined fraud reports and disputes, when the acquirer isn't Above Standard or Excessive. CEMEA: at least 2.2%, 150 events AND USD 75,000, with the same acquirer conditionFull regional scope
MastercardECP (ECM/HECM tiers)ECM: 100-299 chargebacks AND 1.50-2.99%. HECM: 300+ AND 3.00%+Full thresholds
AmexInternal monitoringNo published number. Amex acts when your volume is "considered disproportionate"Details
DiscoverInternal monitoringNo published number. "Excessive returns or Disputes, as determined by us in our sole discretion"Details

For exit, use the program-specific sourced conditions. Three consecutive months is the reported Mastercard ECP/EFM rule, not a rule for every network program.

Calculating Your Rates​

Program Ratios​

Visa VAMP % = (TC40 Fraud Reports in Month N + TC15 Disputes in Month N) / Settled CNP VisaNet Transactions in Month N x 100
Mastercard ECP % = First Mastercard Chargebacks Received in Month N / Mastercard Sales Transactions in Month N-1 x 100

VAMP has extract-dependent exclusions. Use the VAMP formula and exclusions and Mastercard formula sources. A chargebacks-only same-month rate isn't either program's full calculation.

Want the room left under each line? Work out your headroom with both formulas and your processor's limit.

Important Notes​

  • Transaction counts matter. Low-volume merchants can hit ratio thresholds quickly.
  • Both metrics. Many programs require both ratio AND count thresholds.
  • Month matters. VAMP uses same-month fraud reports plus disputes over settled CNP VisaNet transactions. Mastercard ECP uses this month's first chargebacks over last month's Mastercard sales count.

Warning Signs​

Leading Indicators​

Monitor these to catch problems early:

IndicatorWarning LevelAction Level
Chargeback ratioRising toward your processor's limitApproaching or breaching that limit; confirm the deadline
EFM fraud-chargeback count ratio0.35% (example internal alert)Check all applicable EFM entry tests, including the Australia exception
Dispute trendUnexplained rise on comparable salesA rise that would cross your processor's written limit or a program threshold before your next review
Customer complaintsIncreasingSpiking

EFM isn't triggered by one fraud percentage. Its count ratio, fraud-chargeback amount, prior-month sales count and 3DS usage tests apply together. Network Programs gives the sourced figures, Australia's different lines and provider equality differences. The 0.35% warning level is an example internal setting, not a network line or a promise of a month to react. Set your chargeback alerts against your processor's limit. Published provider lines differ; they don't establish one cutoff for everyone.

Don't borrow another merchant's alert levels. Check which program applies, how it counts fraud and disputes, and what your processor requires.

Red Flags​

  • Chargeback ratio approaching your processor's limit
  • Fraud-chargeback count ratio approaching the applicable EFM line; check its other tests and regional conditions
  • Month-over-month increases
  • New fraud patterns emerging
  • Customer service complaints spiking

Remediation Requirements​

Use the deadline in your notice. Braintree's September 2025 VAMP update says 15 days from notification. Nuvei asks its merchants for findings and a plan within ten calendar days. Those aren't a shared deadline for every program. Sources and scope. Ask: "What must I send, who gets it, and by which date?"

What Networks Want to See​

  1. Root cause analysis - Why are chargebacks occurring?
  2. Remediation plan - Specific actions with timelines
  3. Progress reporting - Regular updates
  4. Evidence of improvement - Declining metrics
  5. Compliance commitment - Ongoing monitoring

Typical Remediation Actions​

AreaActions
Fraud Prevention3DS implementation, enhanced scoring, velocity rules
Customer ExperienceClear descriptors, easy cancellation, better support
OperationsFaster refunds, delivery confirmation, dispute response
PoliciesClear terms, visible disclosures, proper consent

Prevention Strategies​

Immediate Actions​

  1. Enable fraud tools - 3DS, AVS, CVV
  2. Review refund policies - Make refunds easier
  3. Improve response time - Customer service SLAs
  4. Implement alerts - Ethoca, Verifi for pre-disputes

Long-term Solutions​

  1. Improve descriptors - Clear merchant names
  2. Order confirmations - Email with charge preview
  3. Delivery confirmation - Tracking and signature
  4. Review sales practices - No aggressive tactics
  5. Train customer service - Dispute prevention focus

Alert Services​

ServiceFunction
Verifi CDRNPre-dispute alerts for Visa
EthocaPre-dispute alerts for Mastercard
RDR (Rapid Dispute Resolution)Auto-resolve disputes

For how alerts affect program ratios, see Prevention Tool Impact.

Next Steps​

Checking your program status?

  1. Review threshold tables - Know exactly where the lines are
  2. Watch warning signs - Act before breach
  3. Calculate your program ratios - Check the numerator and reporting months

Already in a program?

  1. Follow remediation requirements - What networks want
  2. Implement prevention strategies - Get below thresholds
  3. Review fee escalation timelines - Understand urgency

Preventing program entry?

  1. Monitor leading indicators - Early warning metrics
  2. Enable alert services - Ethoca, Verifi
  3. Review prevention strategies - Reduce disputes proactively

See Also​

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.