Compliance Metrics & Monitoring
This page is the ratios behind the named network programs - VAMP, ECM, HECM, EFM - and where each line sits. Looking for win rates and costs?
None of these bites on a ratio alone. Each needs a minimum count too, so a scary percentage on low volume can mean nothing at network level.
- Three numbers decide whether a network program comes after you: chargeback ratio, fraud ratio, and enumeration ratio.
- Visa and Mastercard don't calculate the chargeback ratio the same way. Mastercard divides this month's chargebacks by last month's transactions. Visa uses the same month for both.
- Mastercard ECM is 100-299 chargebacks and a 1.50-2.99% ratio. Both halves have to be true, so one without the other tells you nothing.
- Visa's VAMP merchant excessive line is 1.5%, or 2.2% in CEMEA. It only bites at 1,500 combined fraud reports and disputes.
- Set your own alarms at half the network number. You want a month of runway, not a week.
- Neither network publishes any of these figures. Every number below came through an acquirer, so confirm yours with yours.
You can't manage a ratio you see once a month, in an email, after the month closed. This page gets those three numbers onto your own dashboard daily, with an alarm that trips well before your acquirer's does.
Core Compliance Metrics
Three ratios drive every network monitoring program. Track one and ignore the rest, and the other two will blindside you.
Chargeback Ratio
Disputes divided by transactions. Your acquirer watches it. It triggers Mastercard's chargeback program. And it's one of two inputs to Visa's VAMP.
Formula:
Chargeback Ratio = (Chargebacks in Month N) / (Transactions in Month N or N-1) × 100
Where the lines sit: most acquirer contracts treat 0.9% as the concern threshold. That's the number that earns a warning email and a reserve conversation. Visa's own excessive line under VAMP sits higher, at 1.5%. Your contract is what terminates you, so 0.9% is the ceiling that actually matters.
Calculation differences:
- Visa: same-month transactions as the denominator
- Mastercard: prior month (N-1) transactions as the denominator
That gap isn't trivia. Growing volume makes Mastercard's prior-month denominator smaller than Visa's, so identical activity produces a worse Mastercard ratio. It bites hardest after a slow month. Cut spend in June and June's shrunken count becomes July's denominator. July's chargebacks are still arriving from May and June sales. The ratio jumps without a single extra chargeback.
Visa's VAMP folds fraud reports (TC40) and non-fraud disputes (TC15) into one ratio. A clean chargeback number on its own won't keep you out. See Dispute Monitoring.
Fraud Ratio
Confirmed fraud divided by sales. The awkward part: you don't file it. Issuers do, through TC40 reports. So you can be in trouble on a number you never generated and can't see without asking.
Formula:
Fraud Ratio = (Fraud Amount in Month) / (Sales Amount in Month) × 100
Target: below 0.5% for most programs
Where the number comes from:
- TC40 reports (Visa) filed by issuers
- Fraud-reason chargebacks (Mastercard)
- Your own fraud detection system, which will disagree with both
Enumeration Ratio
Card testing. Somebody runs stolen numbers through your checkout to find the live ones. Every attempt lands on your account, not theirs.
Formula:
Enumeration Ratio = (Enumerated Authorizations) / (All Authorizations) × 100
Approvals and declines both count, on both sides of the line. A card-testing run is mostly declines. Measure it against settled transactions and you'd hide it.
Threshold: VAMP enumeration needs both 300,000 enumerated authorizations and a 20% ratio in the same month. Under either number, you're outside the program.
VAMP Ratio (Visa, 2025 onward)
Visa's consolidated number, replacing the old VDMP and VFMP split.
Formula:
VAMP Ratio = (TC40 Fraud Count + Non-Fraud Disputes TC15) / (Settled CNP Transactions)
Under VAMP a fraud dispute can count twice. Once when the issuer files the TC40 fraud notification. Again if a TC15 chargeback follows. Nobody nets them out for you.
Thresholds: merchant excessive is 1.5%, or 2.2% in CEMEA. It only applies once you hit 1,500 combined fraud reports and disputes in a month. Below that count, the ratio can't put you in the program. Details in Dispute Monitoring.
Monitoring Dashboard Components
What to Track
Daily/Weekly Views:
- Chargeback counts by day
- Fraud amounts by day
- Authorization decline rates
- Alert volumes (Ethoca, Verifi)
Monthly Views:
- Chargeback ratio vs. threshold
- Fraud ratio vs. threshold
- VAMP ratio calculation
- Trend comparison (current vs. prior 3 months)
Breakdown Dimensions:
- By reason code (identify root causes)
- By merchant (for acquirers)
- By BIN (for issuers)
- By product type (credit vs. debit)
- By channel (CNP vs. CP)
Alert Thresholds
Set your own alarms below the network's. By the time the network's number trips, you've already had the bad month.
| Level | Trigger | Action |
|---|---|---|
| Green | Below 50% of threshold | Normal monitoring |
| Yellow | 50-75% of threshold | Increased scrutiny, root cause analysis |
| Orange | 75-90% of threshold | Remediation planning, daily monitoring |
| Red | 90%+ of threshold | Emergency response, network notification |
Key Thresholds Reference
Neither Visa nor Mastercard publishes numeric thresholds. Every figure below reached the public through an acquirer. That's true here and on every other site you'll read them on. Treat them as well-sourced and unofficial. Confirm your own limits with your acquirer in writing before you build alerts on them.
| Program | Metric | Threshold |
|---|---|---|
| Visa VAMP (merchants, excessive) | VAMP ratio + count | 1.5% (2.2% in CEMEA) AND 1,500 combined fraud reports + disputes |
| Visa VAMP (acquirers, above standard) | VAMP ratio | 0.5% |
| Visa VAMP (acquirers, excessive) | VAMP ratio | 0.7% |
| Visa VAMP (enumeration) | Count + ratio | 300,000 enumerated transactions AND 20% |
| Mastercard ECM | CB count + ratio | 100-299 AND 1.50-2.99% |
| Mastercard HECM | CB count + ratio | 300+ AND 3.00%+ |
| Mastercard EFM | Transaction count + fraud amount + fraud ratio + 3DS coverage | 1,000+ Mastercard transactions AND $50K+ in fraud claims AND 0.50%+ fraud-to-sales AND 3DS under 50% in regulated markets (10% in non-regulated) |
Every row that says AND means it. A merchant at 4% with 40 chargebacks isn't in ECM. Neither is one with 900 chargebacks at 0.4%.
EFM is the strictest of the lot. It takes four conditions at once, not two. Most summaries print the money and the ratio and drop the other two. The transaction floor is what keeps small merchants out of it entirely. The 3DS test is the one you control directly: get your coverage above the line and you're out of scope no matter what the fraud number does.
Early Warning Systems
Proactive Monitoring
Set internal thresholds at 50% of network limits:
- Visa VAMP: alert at ~0.75%
- Mastercard ECM: alert at ~0.75% and 50 chargebacks
Monitor velocity, not just absolute numbers:
- Week-over-week change percentage
- Month-over-month trajectory
- Seasonal adjustment factors
Flag anomalies:
- MIDs/BINs with sudden increases
- New merchants with unusual patterns
- Specific reason codes spiking
Review Cadence
| Situation | Review Frequency |
|---|---|
| Normal operations | Weekly compliance review |
| Approaching 50% threshold | Twice-weekly review |
| Approaching 75% threshold | Daily review |
| Above 90% threshold | Multiple daily reviews |
Issuer-Specific Metrics
If you're a merchant, skip this section. It's written for card issuers, and none of it shows up on a merchant statement.
Dispute Initiation Rate
How often your cardholders dispute transactions.
Dispute Initiation Rate = (Disputes Initiated) / (Total Transactions) × 100
Higher rates may indicate:
- Fraud targeting your cards
- Poor merchant partnerships
- Cardholder education needs
Fraud Loss Rate by BIN
Split fraud losses by BIN to find the problem products.
Fraud Loss Rate = (Fraud Losses) / (Sales Volume) × 100
TC40 Filing Compliance
Issuers file TC40s for fraud claims. Those filings land on somebody else's ratio. Track:
- Filing timeliness
- Filing completeness
- Filing accuracy
Visa Issuer Monitoring Program (VIMP)
- Monitors issuer-side fraud and dispute rates for CNP
- Includes dispute-to-transaction and fraud-to-sales ratios
- Regional minimum volume thresholds apply
Acquirer/Merchant Metrics
Portfolio-Level Monitoring
For acquirers managing multiple merchants:
| Metric | Calculation | Target |
|---|---|---|
| Portfolio VAMP ratio | Aggregate across all MIDs | Below 0.3%, well under the 0.5% above-standard line |
| At-risk merchant count | MIDs above 75% threshold | Zero |
| MATCH additions | New listings per quarter | Minimize |
Individual Merchant Tracking
| Metric | Frequency | Action Trigger |
|---|---|---|
| Chargeback ratio | Daily | Above 0.5% |
| Fraud ratio | Weekly | Above 0.25% |
| VAMP ratio | Daily | Above 0.75% |
BRAM/VIRP Status
Track registration and compliance status for high-risk merchants:
- Registration current?
- Monitoring reports filed?
- Any violations flagged?
Reporting Cadence
| Frequency | Report Type | Audience | Content |
|---|---|---|---|
| Daily | Alert/exception report | Operations | Threshold breaches, anomalies |
| Weekly | Trend summary | Risk managers | Ratio trends, reason code analysis |
| Monthly | Full compliance report | Leadership, regulators | All metrics, program status |
| Quarterly | Program review | Board, examiners | Strategic view, remediation status |
Monthly Report Components
-
Executive Summary
- Overall compliance status (Green/Yellow/Red)
- Key metric trends
- Notable events
-
Metric Detail
- Chargeback ratio with trend
- Fraud ratio with trend
- VAMP ratio calculation
- Breakdown by segment
-
Program Status
- Current network program enrollments
- Remediation plan progress
- Upcoming threshold changes
-
Action Items
- Required responses
- Recommended improvements
- Timeline commitments
Building Your Dashboard
Essential Views
Real-Time (refreshed hourly):
- Current day chargeback count
- Current day fraud alerts
- Authorization decline rate
Daily Summary:
- Rolling 30-day chargeback ratio
- Rolling 30-day fraud ratio
- Comparison to same period prior month
Trend Analysis:
- 90-day trend chart
- Projection to month-end
- Threshold overlay
Data Sources
| Data Type | Source | Frequency |
|---|---|---|
| Chargebacks | Processor reports, network files | Daily |
| Transactions | Authorization logs | Real-time |
| TC40s | Visa reporting | Daily |
| Fraud claims | Internal systems | Real-time |
| Alert resolutions | Ethoca, Verifi | Daily |
Where This Breaks
You build the dashboard on your own transaction count. Your gateway's count and your acquirer's settled count won't match. Refunds, partial captures, voids and declines all get treated differently. Build the ratio off the acquirer's settled count. Reconcile your gateway to that, not the other way round.
You use one denominator for both networks. Mastercard's prior-month denominator and Visa's same-month denominator turn one month of activity into two different ratios. A single "chargeback ratio" tile is wrong for at least one network. Usually it's wrong low for Mastercard.
Chargebacks get counted on the date they're worked, not the date they're received. Networks count by received date. Clear a backlog in one week and your internal number spikes in a month the network calls quiet. Or it stays flat in a month the network calls bad.
Fraud looks fine because you're measuring your own fraud. Your ratio comes from TC40s that issuers filed, not from the fraud your rules caught. Ask your acquirer for the raw TC40 feed. If they can't provide it, that's a real gap in what you can see. Raise it before you need it.
Next Steps
Setting up compliance monitoring?
- Track core metrics - Chargeback, fraud, enumeration ratios
- Build your dashboard - Real-time, daily, trend views
- Set alert thresholds - 50/75/90% of network limits
Approaching thresholds?
- Check key thresholds - VAMP, ECM, EFM limits
- Increase review cadence - Daily at 75%, multiple daily at 90%
- Follow remediation playbook - Emergency response
Building early warning systems?
- Set internal alerts at 50% - Catch problems early
- Monitor velocity not just absolutes - WoW and MoM changes
- Establish reporting cadence - Weekly, monthly, quarterly
Tracking compliance is just one piece. See also: Payments Metrics · Fraud Metrics · Chargeback Metrics · Operations Metrics
See Also
- Dispute Monitoring Programs - VAMP, ECM thresholds and remediation
- Fraud Metrics - Fraud-specific KPIs
- Chargeback Metrics - Chargeback-specific measurements
- Chargeback Prevention - Reducing ratios proactively
- Monitoring Thresholds - Network program detail
- Zero Point Nine Panic - Crisis response
- Reduce Chargebacks Fast - Emergency playbook
- Chargeback Alerts - Deflection tools
- Benchmarks - Industry standards
- Processor Reporting Checklist - Data requirements
- Alerts Configuration - Monitoring setup
- Network Programs - VAMP, ECM details