What Is VAMP? The Visa Acquirer Monitoring Program Explained

If you sell online in a high-risk vertical, few acronyms matter more to your processing stability right now than VAMP. The VAMP Visa Acquirer Monitoring Program is Visa’s unified framework for watching fraud and disputes across acquirers and the merchants they board. It replaced Visa’s older, separate dispute and fraud monitoring programs with a single metric, and it changed how acquirers look at every merchant in their portfolio. This guide explains what VAMP is, how the ratio works, why it hits high-risk merchants hardest, and what you can do to stay well clear of the line.

What is the VAMP Visa Acquirer Monitoring Program?

VAMP is Visa’s risk monitoring program that combines fraud and dispute activity into one score. Historically, Visa ran two parallel programs: one for disputes and one for fraud. A merchant could look acceptable in one and problematic in the other, and the thresholds and timelines were handled separately.

VAMP consolidated these into one view. Instead of asking “how many chargebacks does this merchant have?” and separately “how much fraud is reported?”, it asks a single question: how much of this merchant’s card-not-present volume is turning into fraud reports or disputes?

The name is important. It is an acquirer monitoring program. Visa measures acquirers at the portfolio level and expects them to manage the merchants they board. In practice, that means your acquirer is now under direct pressure to identify and act on merchants who push its overall numbers up.

How the VAMP ratio is calculated

At its core, the VAMP ratio compares problem transactions to good ones. Broadly, it counts:

• Fraud reports (TC40s): transactions that issuers report to Visa as fraudulent, whether or not the cardholder ever files a dispute.
• Disputes (TC15s): chargebacks initiated by issuers, across fraud and non-fraud reason codes.
• Settled card-not-present transactions: the denominator, representing your legitimate online sales volume for the period.

The key shift is that a single fraudulent transaction can count against you twice: once when the issuer reports it as fraud and again if it becomes a dispute. Under the old programs, many merchants focused only on chargebacks and largely ignored fraud reports. Under VAMP, fraud reports carry real weight, even on transactions that never become a chargeback.

Visa publishes thresholds for both acquirers and merchants, along with minimum count requirements, and these have been tightened in phases since the program launched. Because the exact figures and enforcement dates vary by region and have been revised more than once, always confirm the current numbers with your acquirer rather than relying on a figure you read in a forum.

Why VAMP matters so much for high-risk merchants

High-risk merchants tend to operate in verticals with higher natural dispute rates: subscriptions and continuity offers, nutraceuticals, travel, digital goods, online education, and similar categories. VAMP raises the stakes for these businesses in several ways.

Acquirers become more conservative

Since acquirers are measured at the portfolio level, a handful of noisy merchants can drag the whole book toward a threshold. The rational response for an acquirer is to tighten underwriting, raise reserves, or exit merchants whose ratios trend upward, sometimes before those merchants ever reach a published limit.

Fraud reports are no longer “invisible”

Friendly fraud and true fraud alike now feed the ratio through TC40 reporting. A merchant with modest chargebacks but heavy fraud reporting can still find itself in trouble.

Consequences cascade

Exceeding VAMP thresholds can lead to fines passed down by the acquirer, higher rolling reserves, remediation plans, and in severe cases MID termination. A terminated MID can also make it harder to secure new processing elsewhere.

Practical steps to keep your VAMP ratio under control

Managing VAMP is less about a single tactic and more about running a disciplined payments operation. The merchants who do well typically focus on these areas:

• Track your ratio per MID, weekly. Don’t wait for a monthly statement or an acquirer email. Monitor fraud reports, disputes, and settled volume for each MID so you can see trends early.
• Use pre-dispute alerts and resolution tools. Visa-ecosystem tools that let you resolve or refund a transaction before it becomes a formal dispute can help keep disputes out of the count. Discuss which options are available through your acquirer.
• Tighten fraud screening at checkout. Velocity rules, 3-D Secure where it makes sense, device and IP checks, and BIN-level controls reduce fraudulent orders before they turn into TC40s.
• Make billing descriptors and receipts crystal clear. Many “fraud” claims are cardholders who simply don’t recognize a charge. A recognizable descriptor and a support contact reduce confusion.
• Fix subscription friction. Clear trial terms, renewal reminders, and an easy cancellation path cut down on disputes from customers who feel trapped.
• Refund proactively. A quick refund is almost always cheaper than a dispute plus its impact on your ratio.
• Distribute volume responsibly. Spreading traffic across multiple MIDs is common in high-risk processing, but it must be done transparently and within your acquirers’ rules. Load balancing is not a substitute for fixing the underlying dispute drivers.

Building visibility: the operational side of VAMP

The biggest challenge most merchants face is not knowing the rules but seeing their own data clearly. Disputes, alerts, refunds, and fraud reports often live in different gateway dashboards and acquirer portals, and reconciling them by hand is slow and error-prone.

This is where a centralized view across MIDs pays off. Resub is a payments and CRM platform built for high-risk merchants, designed to bring MID management, chargebacks, and rolling reserves into one place so teams can spot a deteriorating ratio before their acquirer does. Whatever stack you use, the principle is the same: one source of truth for every MID, reviewed on a fixed cadence.

What to review in a weekly VAMP check-in

• Fraud reports and disputes by MID, product, and traffic source
• Top dispute reason codes and how they changed week over week
• Alert and refund outcomes, and how many disputes they prevented
• Any offer, funnel, or affiliate change that correlates with a spike

Common misconceptions about VAMP

“I’m fine because my chargeback rate is low.” Not necessarily. Fraud reports count too, so a low chargeback rate alone doesn’t guarantee a healthy VAMP ratio.

“Only Visa cares about this.” Visa runs VAMP, but your acquirer enforces it, and other card networks maintain their own monitoring programs. Good dispute hygiene helps across all of them.

“I’ll deal with it when I get a warning.” By the time a warning arrives, the data behind it is already weeks old. Acquirers may also act on their own internal limits well before Visa’s thresholds.

Conclusion

The VAMP Visa Acquirer Monitoring Program changed the rules of the game by merging fraud and disputes into a single ratio and making acquirers accountable for their whole portfolio. For high-risk merchants, that means less tolerance for noisy MIDs and more scrutiny of fraud reports that used to fly under the radar. The merchants who thrive under VAMP treat it as an operating discipline: they measure per MID, prevent disputes before they’re filed, screen fraud at checkout, and keep a clear, consolidated view of their payments data. Do that consistently, and VAMP becomes a manageable metric rather than an existential threat to your processing.

Related reading: VAMP explained · payment orchestration vs chargeback tools