Visa VAMP & your dispute ratio

VAMP is Visa’s Acquirer Monitoring Program — the program that flags merchants and acquirers with too many disputes and fraud reports. In 2025 it absorbed Visa’s older programs (the Dispute Monitoring Program and Fraud Monitoring Program) into a single ratio. This page explains what it measures and, honestly, what DisputeDash can and can’t do about it.

What VAMP measures

VAMP watches one count-based ratio on your card-not-present Visa transactions:

VAMP ratio = ( Fraud reports (TC40) + Disputes (TC15) ) ÷ Settled transactions (TC05)

A few things that matter:

It’s a count, not a dollar amount. Every dispute is one tick in the numerator, regardless of size.
It’s outcome-blind. A dispute you go on to win still counts. The only disputes that stay out of the ratio are the ones that are never filed.
A fraud report (TC40) that later becomes a chargeback (TC15) is counted on both sides.

Thresholds and timing


Enrollment floor	Applies once you clear ~1,500 applicable CNP transactions in a month
Excessive threshold	2.2%, tightening to 1.5% on April 1, 2026
Enforcement	Live since October 2025 (fines roughly $8 per dispute at excessive levels)

Visa also tracks a separate enumeration ratio for card-testing / BIN-attack traffic (for merchants with 300,000+ enumerated authorizations) — a different problem from ordinary disputes.

The honest part: representment doesn’t lower your ratio

DisputeDash’s core job is representment — winning back the money on chargebacks that have already been filed. That’s real revenue you’d otherwise lose, and it’s worth doing regardless of VAMP.

But because a filed dispute is counted the moment it exists, winning it does not remove it from your VAMP ratio. Anyone who tells you their win rate will fix your VAMP standing is glossing over how the ratio is calculated.

What actually moves the ratio is a smaller numerator — fewer disputes and fraud reports getting filed. That’s a prevention and root-cause problem.

How DisputeDash helps

The tool for the ratio is Radar, which reads your dispute stream nightly and surfaces what’s driving the count, each finding with a recommended action:

Fraud spikes — a jump in fraud-coded chargebacks flagged early, so you can tighten rules or pause a SKU before the ratio climbs. Fewer TC40s and TC15s at the source.
Repeat disputers — the same customer filing across your brands, so you can blacklist them workspace-wide and cut off the next dispute before it’s filed.
Rate and driver monitoring — chargeback-rate and win-rate signals per processor, product, and reason code, showing where the count is climbing and why (a broken integration, a problem product, a fraud pattern) while there’s still time to act.
Subscription friction — recurring-billing disputes spiking on a plan or rebill cycle, pointing at unclear messaging or a hard-to-find cancellation flow so you can fix the cause.

The goal is the same one VAMP cares about: fewer disputes filed in the first place.

In short

VAMP counts disputes, won or lost — the ratio is about volume, not outcomes.
Representment protects revenue but doesn’t lower the ratio (still worth doing — see Compelling Evidence 3.0).
Radar is the VAMP tool — it finds and helps you cut the causes so fewer disputes get filed.