Payment network monitoring has historically been fragmented. Merchants and acquirers navigated separate programs for fraud, disputes, enumeration and excessive activity. Each had its own thresholds, definitions and remediation paths.
VAMP changes that. Visa's Acquirer Monitoring Program brings these signals under one framework — with clearer accountability and less room for ambiguity.
VAMP replaces a patchwork of thresholds with a single view of portfolio health.
What VAMP Changes
- Unified evaluation of fraud and dispute activity
- New definitions for reportable enumeration behavior
- Explicit acquirer accountability for merchant portfolio performance
- Standardized remediation pathways and timelines
- Increased data granularity in ongoing reporting
What has not changed
Network expectations around merchant behavior — clear descriptors, appropriate fraud controls, honest representation of goods and services — remain unchanged. VAMP simply makes deviations visible earlier.
Why Legacy Metrics Are Not Portable
Merchants comfortable with prior monitoring thresholds should not assume their existing metrics translate directly. Definitions, denominators and inclusion rules have shifted. A portfolio that appeared healthy under legacy programs may present differently under VAMP.
The right response is not panic — it's recalibration. Re-baseline every metric against VAMP definitions before drawing conclusions.
Preparing for VAMP
- Re-baseline current metrics using VAMP methodology.
- Align fraud and dispute teams under one performance view.
- Formalize communication protocols with your acquirer.
- Ensure executive visibility into monitoring posture.
- Document remediation plans before they are needed.