Every month a large number of high‑risk merchants are caught off guard when their acquirer informs them that their VAMP ratio has crossed the threshold. What begins as a subtle drift in disputes or fraud soon results in fines, payout reserves or even termination of Visa processing rights.
Visa’s Acquirer Monitoring Programme (VAMP), introduced 1 April 2025, sets the VAMP ratio limit for merchants at 1.50% for now. On 1 January 2026 that limit falls to 0.90% globally.
These tighter controls are not theoretical. In recent revisions Visa included both fraud alerts (TC40) and non‑fraud disputes (TC15) in the ratio calculation. Missing even one element or misunderstanding what counts can push a business past “Excessive” status.
Below are six critical alerts within acquirer monitoring programmes that every high‑risk merchant must observe. Recognising them in time can protect account stability and prevent severe financial consequences.
Critical Alerts in VAMP that High‑Risk Merchants Need to Watch For
Here are key alerts you should monitor closely. These are specific warning signs that your business is approaching or exceeding thresholds set by Visa’s Acquirer Monitoring Programme (VAMP). Each alert indicates risk, and acting early can prevent penalties or worse.
1. Rising VAMP Ratio from Combined Disputes and Fraud
Under VAMP Rules, merchants are measured by a ratio that combines fraud alerts (TC40) and non‑fraud disputes (TC15) over the number of settled card‑not‑present transactions. It’s easy to misjudge because each of those components behaves differently. A small uptick in either without mitigation can move your ratio above permitted levels.
- Why it sneaks up: TC40s can include fraud alerts even before they become chargebacks. If you rely solely on chargeback counts, you may vastly underestimate your risk.
- What to watch: look at each month’s numbers, see if the fraud alerts or non‑fraud disputes have increased independently; plot trends for both separately before they get combined.
2. Persistent or Growing Enumeration / Card‑Testing Attacks
VAMP includes enumeration ratio as a separate metric. Enumeration means unauthorised attempts to verify card credentials via repeated small authorisation or CVV attempts. Many merchants see authorisations failing silently; those failures might still count if tagged as enumeration by Visa’s detection.
- Why this matters: high enumeration indicates vulnerabilities in your authorisation / anti‑bot systems. Even if you reject invalid attempts, if they are “enumerated” you get flagged.
- What to monitor: daily logs of authorisation failures, look specifically for patterns (same IPs, same card prefixes, rapid attempts). If your gateway or acquirer provides enumeration alerts or intelligence (Visa’s Account Attack Intelligence, etc.), use those.
3. Sudden Spikes in Non‑Fraud Disputes (TC15)
These disputes are for reasons other than fraud: services not delivered, items damaged, misdescriptions, etc. A rise in TC15s signals operational problems, customer service gaps, or fulfilment/logistics issues. Often overlooked until combined with fraud they push you past thresholds.
- Why non‑fraud issues cause damage: they are easier for customers to win disputes, often because the merchant failed somewhere in delivery, description, or refund policy. Even though not fraud, under VAMP they contribute fully.
- What to watch: frequent repeat cause codes in TC15 disputes (for example “item not as described”, “product not delivered”); customer complaints before disputes; return/refund policies and how clearly they are communicated.
4. Failures or Delays in Dispute / Fraud Remediation
Once disputes or fraud alerts occur, what you do with them matters as much as what occurs. Slow responses, poor evidence, incomplete investigations allow small issues to fester and often lead to escalation or chaining (e.g. unresolved disputes turning into more serious disputes or even chargebacks).
- Why it becomes critical: unresolved or mishandled disputes not only cost more but also show a pattern that Visa or acquirers may see as negligence. That raises the risk profile.
- Things to track: time taken to respond to disputes/fraud alerts; quality and completeness of response (do you include full shipping/tracking, product images, customer correspondence?); frequency of escalated cases because initial evidence was weak.
5. Crossing Minimum Volume / Count Triggers
Even if your ratios look passable, volume matters. VAMP requires a minimum number of combined dispute + fraud events or settled transaction counts for monitoring and enforcement to kick in. Once you cross that volume threshold, even a slightly elevated ratio becomes dangerous.
- Why volume is deceptive: with low transaction numbers some volatility is expected; but once volume is large, even small slack in operations or fraud detection creates meaningful risk.
- What to monitor: monthly counts of TC40 + TC15; transaction volume trends; whether your processed volume is growing (which may trigger stricter enforcement).
6. Acquirer / Card Scheme Notifications or Early Warning Flags
Merchants often discover problems only when their payment acquirer or scheme contacts them. But there are earlier signs: notices from your processor that your account is “above standard”, warnings about increasing dispute counts, requests for extra fraud mitigation, requests to update billing descriptors, or being asked for more documentation. Ignoring these is dangerous.
- Why this alert is critical: It often means you’re already on the radar. At that point your margin for error is small; small slip-ups could trigger a penalty or worse.
- What to watch: any formal warning letters/emails; unexpected demands from processor for customer support improvements or dispute policy changes; descriptor or merchant name inconsistencies flagged by acquirer.
Also Read: How to Avoid Termination Under VAMP Guidelines
Conclusion
Monitoring critical alerts is essential for high-risk merchants operating under Visa’s Acquirer Monitoring Programme (VAMP). These alerts serve as early indicators of potential issues, allowing merchants to address problems proactively before they escalate into significant penalties or account terminations.
By staying vigilant and addressing these alerts promptly, merchants can maintain compliance with VAMP’s thresholds and ensure the continued health of their payment processing relationships. It’s crucial to understand that VAMP’s enforcement is not just about meeting the minimum requirements but about fostering a culture of continuous improvement and risk management.
For high-risk merchants, this means regularly reviewing transaction data, implementing robust fraud prevention measures, and maintaining clear communication with acquirers. By doing so, merchants can navigate the complexities of VAMP effectively and sustain their operations without disruption.
