In April 2025, Visa rolled out a consolidated acquirer monitoring framework called VAMP — the Visa Acquirer Monitoring Program. The updated VAMP replaced the previous structure of separate programs that had governed dispute and fraud thresholds for merchants and acquirers, pulling them into a single unified framework with revised metrics and enforcement mechanisms.

For most standard merchants, VAMP operates invisibly in the background — their acquirer manages compliance and nothing in their day-to-day processing changes. For high-risk merchants, particularly those whose chargeback or fraud ratios run close to threshold levels, understanding what VAMP measures and how it differs from the previous program structure matters for protecting their processing relationships.

What VAMP Replaced

Before April 2025, Visa operated two separate monitoring programs that addressed different sides of the dispute and fraud problem:

The Visa Dispute Monitoring Program (VDMP) tracked chargeback ratios at the merchant level. Merchants whose monthly chargeback ratio exceeded 0.9% entered an Early Warning status, and merchants exceeding 1.8% entered Standard status with associated fines. The program measured chargebacks as a percentage of total transaction count.

The Visa Fraud Monitoring Program (VFMP) ran in parallel, tracking fraud-to-sales ratios. Merchants who generated excessive fraud relative to their processing volume were flagged under this program separately from their chargeback ratio performance.

VAMP consolidates both programs into a single framework. The most significant change is the introduction of a unified metric that combines disputes and enumeration activity (card testing) under one measurement umbrella, giving Visa and acquirers a more holistic view of a merchant's risk profile rather than tracking disputes and fraud through disconnected channels.

The New VAMP Ratio: What It Measures

The VAMP ratio is calculated differently from the old VDMP chargeback ratio. Under VAMP, the numerator includes both disputes (chargebacks) and enumeration transactions — fraudulent attempts to validate stolen card numbers through small test charges. The denominator is total Visa transaction count for the month.

This combined metric is the key conceptual shift. Previously, a merchant could have an elevated fraud rate from card testing attacks while keeping their chargeback ratio clean, and the two programs tracked those problems separately. Under VAMP, a card testing attack that generates significant enumeration volume affects the VAMP ratio directly, not just through any subsequent chargebacks the fraudulent cards generate.

For ecommerce merchants whose checkout pages have been targeted by card testing — a common attack where fraudsters run thousands of small transactions to validate stolen card numbers — this change means gateway-level fraud screening that catches enumeration attempts has become even more important. Enumeration activity that was previously an annoyance and a gateway cost is now a metric that directly affects your standing under Visa's monitoring framework.

The thresholds under VAMP are set at the acquirer level rather than publishing fixed merchant-level numbers in the same way the old programs did. Your acquirer receives VAMP reporting and is responsible for managing the merchants in their portfolio within Visa's acceptable parameters. What this means practically is that your acquirer's risk management team has more direct incentive to address VAMP ratio contributors in their merchant portfolio — which means merchants generating elevated dispute or enumeration volume are more likely to hear from their processor about it.

What VAMP Means for High-Risk Merchants Specifically

High-risk merchants already operating close to dispute thresholds need to understand a few practical implications of the VAMP framework:

Card testing attacks now affect your VAMP ratio directly. If your checkout page has been hit by enumeration attacks — visible in your gateway as a sudden spike of small-dollar authorizations from many different cards, often declining on CVV or AVS — those transactions are now contributing to your VAMP ratio calculation. Configuring velocity limits, CVV verification requirements, and transaction amount minimums in your gateway fraud screening to catch card testing before those transactions authorize is now a direct ratio management measure, not just fraud loss prevention.

Acquirers have increased visibility and motivation to act. The consolidated VAMP reporting gives acquirers a cleaner view of which merchants are driving their portfolio's risk metrics. Merchants who were previously below the threshold on chargebacks but generating fraud volume may find their processor more proactive about risk reviews under VAMP than they were under the old separate-program structure.

The dispute component still matters. VAMP doesn't eliminate dispute ratio monitoring — it incorporates it. Chargebacks still count in the VAMP numerator. The prevention measures that reduce chargebacks under the old framework continue to apply: clear billing descriptors, pre-charge reminders for subscriptions, chargeback alert interception, and responsive customer service that resolves complaints before they escalate to disputes.

Load balancing across multiple accounts still provides ratio management benefit. Distributing transaction volume across multiple merchant accounts under gateway load balancing means that dispute and enumeration events are distributed across accounts rather than concentrated in one. This keeps each account's VAMP ratio below threshold levels even when aggregate dispute volume is elevated. For high-risk merchants doing meaningful volume, this architectural approach remains one of the most effective ratio management tools available.

A note on thresholds: Visa has not published the specific VAMP ratio thresholds that apply to merchants in the same public-facing way the old VDMP numbers were communicated. The thresholds are managed at the acquirer level. Your processor can tell you what VAMP metrics they monitor for your account and what levels trigger a review. If you don't know your current VAMP standing, that's a conversation worth having with your processor.

Protecting Your Processing Relationship Under VAMP

The practical steps for high-risk merchants who want to stay in good standing under the updated framework are an extension of the chargeback and fraud management practices that have always been important, now with the addition of enumeration prevention as an explicit priority.

Audit your fraud screening rules for enumeration coverage. Card testing attacks have patterns: many small-dollar transactions from different cards in a short window, high decline rates, frequent CVV failures. If your current iSpy fraud rules aren't specifically configured to flag and block this pattern, review and tighten them. Velocity limits by IP address, by card BIN range, and by transaction amount are the most direct controls.

Monitor your VAMP ratio proactively. Don't wait for your processor to notify you. Ask your processor what dispute and fraud metrics they report on for your account under VAMP, what the thresholds are that would trigger a review, and how frequently the reporting updates. Proactive monitoring gives you time to address trending problems before they become account-level issues.

Keep chargeback prevention infrastructure current. Alert interception through Ethoca and Verifi networks, clear billing descriptors, subscription pre-charge reminders, and easy cancellation all reduce the dispute component of your VAMP ratio. Our full chargeback prevention guide covers the complete prevention framework for ecommerce merchants.

Have a backup processing relationship. This is true under any monitoring framework, but VAMP's more consolidated enforcement mechanism gives acquirers cleaner data to act on. Merchants whose VAMP ratios are elevated are more likely to face proactive action from their processor under the new framework. Having a second merchant account in place before that happens keeps your processing running regardless of what one acquirer does. For help establishing a backup processing relationship or reviewing your current fraud and chargeback management setup, apply with CyoGate.