What changed
VAMP consolidated fraud and disputes into a single monitoring framework, replacing the separate legacy programmes that allowed each to be managed by a different team with a different threshold. That structural point was covered when the programme launched. What has changed since is that Visa is now publishing outcomes.
The October 2025 update introduced a minimum monthly VAMP count of 1,500 fraud-plus-dispute transactions. That threshold determines whether an entity's ratio is actionable at all — a low-count portfolio can produce a mathematically alarming ratio from a handful of events.
In March 2026, Visa reported that the issuer VAMP ratio declined by more than 10 percent quarter over quarter, and attributed more than $30 million in issuer operational savings in a single quarter to reduced downstream dispute handling. Both figures are Visa's own, describing network-level performance.
Why it matters
The reported ecosystem improvement is the signal merchants should read most carefully. When aggregate performance improves, the distribution tightens — and entities that have not improved become more visible relative to their peers rather than less. A ratio that looked unremarkable against last year's distribution may not look that way against this one.
The consolidated framework also ends a long-standing organizational arrangement. When fraud and disputes were monitored separately, it was possible for a fraud team to hit its target while dispute performance deteriorated, and for neither team to own the combined number. Under VAMP the combined number is the number. There is no version of this that works with two independent teams and two independent dashboards.
The minimum count matters for interpretation rather than for safety. A portfolio below the count threshold is not necessarily healthy; it is simply not yet actionable. Growth alone can move an entity across that line with no change in underlying behaviour, which is why forecasting matters more than current-state reporting.
VAMP has moved from policy to operating reality. The question is no longer whether organizations are ready — it is whether their data shows readiness before their acquirer asks.
Who is affected
- Merchants. Especially those with growing volume, seasonal peaks or a ratio within visible distance of a threshold.
- Acquirers. Portfolio-level exposure aggregates merchant behaviour, which is why acquirer intervention typically arrives before formal network escalation.
- Fraud and dispute leaders. Two functions, one measured outcome. Separate targets are now structurally misaligned with how performance is assessed.
- Finance and executive teams. Threshold breach carries commercial consequence — remediation cost, pricing pressure and, at the extreme, processing continuity risk.
MerchantGo analysis
The practical lesson from the first operating cycles is about sequence. Merchants generally do not learn about a VAMP problem from Visa. They learn about it from their acquirer, who sees portfolio contribution earlier and has commercial reason to act before network escalation. By the time that conversation happens, the merchant is responding to someone else's data with a remediation timeline they did not set.
Avoiding that position requires forward-looking reporting. A retrospective monthly ratio tells leadership where the business was. What leadership needs is a projection: given current fraud and dispute trajectory, expected volume and known seasonality, where does the ratio land in sixty and ninety days, and what is the confidence interval around that number.
Dispute deflection is the highest-leverage lever because it operates before the dispute is counted. Order-status transparency, clear billing descriptors, responsive service before the customer calls the issuer, and structured pre-dispute resolution all reduce the numerator directly. Representment, by contrast, arrives after the count in most framings — valuable financially, less so for ratio management.
Compelling Evidence 3.0 remains underused relative to its eligibility footprint. Merchants with a qualifying history of prior undisputed transactions frequently have the data required and simply have not operationalized the workflow into their dispute process.
Underlying all of it is a data problem. Most merchants cannot produce a combined fraud-plus-dispute ratio at the level VAMP measures without assembling it manually from two systems. That reconciliation gap is the real readiness question — not whether the team understands the programme.
What leaders should do now
- 01Produce the combined ratio internally, monthly. Reconcile fraud and dispute counts to the definition the programme uses. If it takes a manual exercise to produce, that is the first thing to fix.
- 02Forecast, don't report. Give executives a sixty- and ninety-day projected ratio with assumptions, not a retrospective figure that arrives after decisions were needed.
- 03Merge fraud and dispute governance. One owner, one target, one forum. Separate teams with separate KPIs cannot manage a consolidated measure.
- 04Prioritize deflection over litigation. Invest first in the controls that prevent a dispute from being filed, then in winning the ones that are.
- 05Operationalize Compelling Evidence 3.0. Codify eligibility checks and evidence assembly into the standing dispute workflow rather than handling qualifying cases ad hoc.
- 06Model your own growth. Volume changes can move an entity across the minimum count threshold without any change in behaviour. Know in advance when that happens.