VAMP (Visa Acquirer Monitoring Programme)

VAMP represents a structural simplification of Visa's acquirer monitoring architecture. For years, acquirers and merchants had to manage compliance separately under VDMP (which tracked dispute ratios) and VFMP (which tracked fraud ratios), each with separate thresholds, remediation timelines, and fee schedules. VAMP merges these into a single metric and shifts the compliance relationship to sit primarily between Visa and the acquirer.

The Unified VAMP Ratio

The VAMP ratio is calculated as:

(Fraud (TC40) + Disputes (TC15)) / Settled transactions (TC05)

Key components:

Disputes: Confirmed chargebacks initiated by cardholders, counted at the transaction level.

TC40 reports: Fraud reports filed by issuers through the Visa TC40 process when a cardholder reports fraud. These are included in VAMP whether or not they result in a formal dispute, which means a merchant can be contributing to VAMP exposure through issuer-reported fraud even when cardholders do not formally file chargebacks.

Enumeration: Card-testing attacks (high-velocity low-value authorisation attempts against a merchant's payment endpoint) are tracked separately under Visa's enumeration ratio rather than inside the core VAMP ratio, reflecting Visa's view that merchants who are being enumerated against create network-level risk.

Exclusions: Disputes resolved through pre-dispute solutions (such as Visa RDR) and TC40 fraud that qualifies for Compelling Evidence 3.0 are excluded from the ratio, contingent on timing.

Thresholds and Enforcement

Visa sets acquirer-level thresholds — Above Standard at ≥50 bps (0.50%) and Excessive at ≥70 bps (0.70%) — and a merchant excessive threshold of ≥220 bps (2.2%) in AP, Canada, the EU, and the U.S., reducing to ≥150 bps (1.5%) from 1 April 2026. Breaching these exposes the acquirer to fines and programme fees assessed by Visa. Confirm current thresholds with your acquirer or Visa representative, as Visa periodically revises them.

The 1,000-transaction minimum means low-volume merchants are excluded from the programme, focusing enforcement on material transaction volumes.

Acquirer-Level Enforcement

Because VAMP enforcement sits at the acquirer level, acquirers are incentivised to proactively manage merchant-level ratios rather than waiting for Visa to intervene. In practice, acquirers now have contractual mechanisms (reserve requirements, merchant-level surcharges, and offboarding rights) that they deploy based on per-merchant VAMP contribution analysis — merchants do not deal with Visa directly on VAMP.