• Visa VAMP is the card network's combined fraud and dispute monitoring program for merchants and acquirers.
• On April 1, 2026, the merchant excessive threshold dropped from 2.2% to 1.5%.
• The VAMP ratio adds reported fraud to total disputes, divided by total settled card-not-present transactions.
• Enrolled merchants are assessed $8 per fraudulent or disputed transaction.
• Dispute alerts, stronger authentication, and TC40 visibility pull a rising ratio back down fastest.

You can run a clean business and still land in trouble with your card network. That is the uncomfortable reality behind Visa VAMP, the program that decides whether your fraud and dispute levels are acceptable enough to keep processing.

For most of last year, merchants had a 2.2% ceiling to work with. On April 1, 2026, that ceiling moved to 1.5%. If your business was sitting comfortably at 1.8%, it is now over the line without a single thing changing in how you operate.

This guide covers what the program measures, how the ratio is calculated, what enforcement costs, and the practical steps that keep you under the limit.

Visa VAMP, short for the Visa Acquirer Monitoring Program, is a single framework that tracks both fraud and disputes for merchants and the acquiring banks that process their transactions.

Before VAMP, those lived in separate systems. Fraudulent transactions were tracked under one monitoring program and chargebacks under another. VAMP folded them together, consolidating five fraud and dispute programs into one and collapsing 38 remediation processes into a single path.

The practical effect is that you can no longer treat fraud and disputes as unrelated problems. A rise in either one moves the same number, and that number decides whether you get enrolled in monitoring.

Your VAMP ratio is the sum of reported fraudulent transactions and total disputes, divided by your total settled transactions. Only card-not-present transactions count toward it.

Two data feeds drive the number. Fraud comes from TC40 reports, which issuing banks file when a cardholder reports a transaction as fraudulent. Disputes come through as TC15 records.

Here is the part that catches merchants off guard. A fraud report and the chargeback that follows it are both counted, so a single incident can hit your ratio twice.

TC40 reports are also easy to miss. When the amount is small, an issuer may credit the customer directly instead of filing a chargeback. You never see a dispute, but the fraud report still lands in your ratio.

The merchant excessive threshold is now 1.5%, down from 2.2% as of April 1, 2026.

Acquirers face tighter limits still. Their excessive threshold sits at 0.7% and their above standard threshold at 0.5%, with enforcement on the latter beginning January 1, 2026. That matters to you because acquirers under pressure pass scrutiny straight down to the merchants in their portfolio.

Breaching the threshold does not trigger instant enrollment. A first violation inside a rolling twelve-month window earns a three-month grace period. Stay above the line after that and you get enrolled, at which point you are assessed $8 per fraudulent or disputed transaction. Stack that on top of normal chargeback fees, lost goods, and staff time, and a modest dispute volume gets expensive fast.

The goal is straightforward. Keep fewer disputes from entering the system, and resolve the ones that do before they become chargebacks.

Start with visibility. Track your ratio at the merchant ID level and integrate TC40 data so you are not guessing. Real-time alerts as you approach the threshold buy you time to act.

Then tighten the front door. Address verification and CVV matching filter out low-effort attempts. 3-D Secure adds issuer-backed authentication and can shift liability away from you. Machine learning models catch patterns static rules miss, such as device inconsistencies or card testing.

On the dispute side, chargeback prevention alerts let you refund a dispute before it becomes a chargeback, which keeps it out of your ratio entirely. Order Insight resolves confusion-driven disputes by giving issuers full transaction detail. Rapid Dispute Resolution auto-refunds eligible low-value transactions. Compelling Evidence 3.0 defeats certain fraud claims using historical transaction data, blocking both the dispute and the fraud report.

Tools like Kumaa Guard automate the alert and dispute response side so your team is not chasing every case by hand. Because the VAMP calculation overlaps heavily with your chargeback ratio, the fundamentals of keeping that number low apply directly here. The same goes for card-not-present fraud controls, since CNP transactions are the only ones VAMP counts.

Finally, look at root causes. Unclear billing descriptors, slow customer service, and confusing refund policies generate disputes that never needed to happen