Visa merchant monitoring has no single program name. In Visa’s public guide it is a stack of requirements on the acquirer. Two touch the merchant’s website. One measures fraud and disputes.
Run it: website cloaking checker covers the website check VARS recommends; VAMP ratios need your own payment data. Visa figures as of 20 Nov 2026.
VAMP in numbers
| acquirer | merchant (US, EU, Canada, Asia Pacific) | merchant (Latin America) | merchant (CEMEA) | |
|---|---|---|---|---|
| ratio, Excessive | 70 bps | 150 bps from 1 Apr 2026 (220 before) | 150 bps | 220 bps |
| ratio, Above Standard | 50 bps | n/a | n/a | n/a |
| monthly count of fraud and disputes | 1,500; CEMEA 150 and USD 75,000 | 1,500 | 1,500 | 150 and USD 75,000 |
| enumeration | ratio ≥ 2,000 bps (20%) and ≥ 300,000 enumerated authorizations |
Ratio = fraud reports (TC40) plus disputes (TC15), divided by settled transactions (TC05), on card-not-present. Source: Visa VAMP fact sheet, effective 1 June 2025. Enumeration is the pattern card testing leaves: card testing attack.
The four parts
Visa’s Ecosystem Risk Programs guide (October 2024) lists them: Visa Acceptance Risk Standards (VARS), the Visa Integrity Risk Program (VIRP), Visa Monitoring Programs, and the Account Information Security Program (Visa).
| part | what it does to merchant monitoring |
|---|---|
| VARS | portfolio monitoring from onboarding to termination; website checks |
| VIRP | controls for high integrity risk merchants: prohibited merchants list |
| Visa Monitoring Programs | thresholds on fraud and disputes: VAMP |
| account security | card data protection, not monitoring |
What VARS says about the website
Control AACQ.C8.1: acquirers “must adopt a risk management-focused monitoring strategy for their Merchants, beginning with successful onboarding and continuing until partnership termination”, to catch fraud, collusion, credit issues, disputes, AML, and brand-damaging and illegal activity.
Recommended controls for illegal transactions:
- web crawling tools, if needed
- regular review of transaction data for unusual patterns
- verify each merchant website: it sells only what was declared, and has a checkout and a way to take payments
- look for mismatched merchant names and MCCs, and suspicious connections to the URL and backlinks
Source: same guide. At onboarding Visa recommends web crawling, negative news scanning and beneficial owner research.
What VAMP measures
VAMP ratio = fraud reports plus disputes, divided by settled transactions, on card-not-present transactions. An acquirer is Above Standard at 50 basis points or more, Excessive at 70 or more. Excessive merchant thresholds, from Visa’s fact sheet: Asia Pacific, Canada, EU and US 220 basis points, reduced to 150 on 1 April 2026, with at least 1,500 fraud and dispute cases a month. Latin America 150. CEMEA 220, with at least 150 cases and USD 75,000 (Visa VAMP overview).
VAMP counts disputes and fraud. It does not read websites. A merchant can sit under every ratio and still be a hidden seller.
Where our check fits
The website part is the part a ratio cannot see: what the site sells, and whether it shows reviewers a different page than customers. Website cloaking checker · merchant monitoring. Mastercard’s side: BRAM.
Related
Transaction laundering · MATCH list (Visa: Terminated Merchant File) · PayFac
See also: merchant descriptor · MCC mismatch · for payment processors