What Is VAMP?

VAMP stands for Visa Acquirer Monitoring Program. It is Visa’s framework for monitoring excessive fraud reports and disputes across acquirers, payment facilitators, and merchants.

The important shift is that VAMP brings fraud and chargeback pressure into one operating view. A merchant can no longer treat fraud reports, dispute ratios, and authorization quality as separate problems. For card-not-present businesses, they now roll up into a metric that can affect processing cost, acquirer scrutiny, and the ability to keep scaling safely.

Why Visa Created VAMP

Before VAMP, Visa used separate monitoring programs for fraud and disputes, including VFMP and VDMP. That structure made sense operationally, but it also created fragmented ownership. Fraud teams watched fraud reports. Dispute teams watched chargebacks. Acquirers watched their portfolio risk.

VAMP consolidates that pressure. It gives Visa and acquirers a clearer way to identify merchants or portfolios that generate too many risky or disputed transactions relative to approved volume.

How the VAMP Ratio Works

The VAMP ratio is generally based on fraud reports plus disputes divided by settled Visa transactions during the measurement period.

• TC40 fraud reports: cases where the issuer reports a transaction as fraud.
• TC15 disputes: chargebacks and dispute records, including fraud and non-fraud disputes.
• TC05 settled transactions: the settled transaction count used as the denominator.

In plain English: if too many transactions become fraud reports or disputes, the merchant’s VAMP ratio rises. If the ratio crosses the applicable threshold and the merchant has enough monthly fraud-and-dispute events to qualify for monitoring, the acquirer can face network pressure and pass that pressure down to the merchant.

2026 Threshold Context

As of the 2026 rule phase, public Visa guidance and payment-industry summaries point to a stricter merchant excessive threshold of 1.5% in regions such as the U.S., Canada, EU, and Asia Pacific, with a minimum monthly combined fraud-and-dispute event count. Acquirer thresholds are lower because acquirers are measured at the portfolio level.

The exact commercial impact depends on region, acquirer, merchant category, and contract terms. The practical takeaway is simple: merchants should monitor their fraud reports and disputes before they appear in a monthly acquirer warning.

Why VAMP Matters for Merchants

VAMP matters because it connects fraud prevention, dispute operations, and payment acceptance into one risk-management problem. A business can have strong approval rates but still create too many downstream disputes. It can also reduce fraud too aggressively and create false declines that hurt revenue. The goal is not simply to block more transactions. The goal is to approve the right transactions with enough evidence, authentication, and operational control to defend them later.

This is why VAMP should be owned jointly by payments, fraud, risk, support, and product teams. The metric is downstream, but the causes are usually spread across checkout design, billing descriptors, refund policy, fulfillment quality, fraud models, authentication routing, and customer communication.

How Merchants Can Reduce VAMP Risk

• Monitor fraud reports and disputes together, not in separate dashboards.
• Track disputes by reason code, product, traffic source, BIN, country, issuer, and customer segment.
• Use step-up authentication for higher-risk transactions instead of applying the same friction to every customer.
• Improve billing descriptors, refund flows, subscription reminders, and cancellation UX to reduce avoidable disputes.
• Maintain strong evidence packages for representment, especially delivery proof, customer communication, device signals, and account history.
• Work with the acquirer or processor to understand internal limits, because acquirer thresholds may be stricter than Visa’s merchant threshold.

Relationship to Chargebacks and False Declines

VAMP is closely related to chargeback prevention, but it is not only a chargeback problem. Fraud reports can matter before they become disputes, and non-fraud disputes still contribute to the broader risk picture.

At the same time, merchants should avoid solving VAMP by simply declining more transactions. Overly defensive rules can create false declines, lower conversion, and damage good-customer experience. A better approach is targeted risk decisioning: use model signals, issuer feedback, authentication, tokenization, and post-transaction operations together.

Product Takeaway

VAMP is not just a compliance rule. It is a signal that card-network risk management is becoming more integrated. Fraud, disputes, authorization strategy, customer experience, and acquirer portfolio health are now deeply connected.

The merchants that handle VAMP well will not be the ones that only react after a monthly report. They will be the ones that build early-warning dashboards, investigate root causes quickly, and design payment flows that reduce risk without punishing legitimate customers.

Reference: Visa Acquirer Monitoring Program fact sheet.