Visa VAMP 2026: how to cut your dispute ratio before it costs you

What changed in Visa VAMP for 2026?

The headline change is the threshold. On April 1, 2026, Visa lowered the merchant VAMP ratio threshold from 2.20% to 1.50% across the US, Canada, Europe, Asia Pacific, and Latin America (Visa¹). The Visa Acquirer Monitoring Program launched on June 1, 2025 and replaced the older Visa Dispute Monitoring Program and Visa Fraud Monitoring Program, folding fraud and disputes into one combined ratio. April 2026 ended the grace period and began full enforcement.

That consolidation matters because it changed what counts against you. Under the old programs, fraud and disputes were tracked separately, and a merchant could sit under both individual limits while still running hot overall. VAMP combines them, so a store with moderate fraud and moderate disputes can now cross a single line that neither old program would have flagged. If your acquirer moved you onto VAMP reporting in 2025 and you have not recalculated against the 1.50% number, you are measuring against a threshold that no longer exists.

Enumeration attacks got their own metric too. Visa now asks acquirers to watch a separate VAMP enumeration ratio for card-testing style traffic, so a wave of automated authorization attempts can flag your account even before those transactions turn into disputes. For a Shopify or WooCommerce store, that means card testing is no longer just a nuisance that burns gateway fees; it is a compliance signal.

How is the VAMP ratio calculated?

Your VAMP ratio is the count of fraud reports (TC40 records) plus disputes (TC15 records) divided by your count of settled transactions (TC05 records) over the same period (Visa¹). It is a count-based ratio, not a dollar-based one, so a $4 dispute and a $400 dispute move the number by exactly the same amount. To stay compliant in 2026, that ratio must stay under 1.50%.

Here is the calculation with real numbers. Say you settled 10,000 Visa transactions last month, and in that same month you had 90 disputes and 70 fraud reports. Your VAMP numerator is 90 plus 70, which is 160. Your ratio is 160 divided by 10,000, which is 1.60%. That store is over the 1.50% threshold and would be flagged. To get under the line, it needs to drop the combined count from 160 to below 150, which means removing at least 11 disputes or fraud reports per 10,000 transactions. That is a small, specific, achievable target, and it is why calculating the exact number first matters so much: you are not trying to "reduce fraud," you are trying to remove 11 events.

One trap in the math: fraud reports (TC40) often lag the transaction by weeks, because they are filed when the cardholder or issuer reports the fraud, not when the sale happened. So the ratio you calculate today reflects sales from earlier, and improvements you make now will not show up immediately. Start measuring early and give your changes four to six weeks to move the number.

Which transactions count toward your VAMP ratio?

Three record types drive your ratio, and knowing them tells you exactly where to intervene. TC40 is a fraud report, filed when a cardholder or issuer flags a transaction as fraudulent. TC15 is a dispute, the chargeback itself. TC05 is a settled transaction, your denominator. Both TC40 and TC15 sit in the numerator, so one bad order can hit you twice: a TC40 when fraud is reported, and a TC15 when the dispute posts.

This is why prevention beats everything else. A blocked fraudulent order never becomes a TC40 or a TC15, so it never touches your numerator, and because it was a real attempted sale it also does not shrink your denominator in any way that hurts you. Winning a dispute through representment removes the TC15 from the count once resolved in your favor, which is why fighting disputes is not just about recovering the sale; it directly lowers your VAMP ratio. If you want prevention and verifiable dispute evidence working on every order automatically, that is exactly what RankShield fraud protection for Shopify and WooCommerce is built to do.

The denominator is a lever too, though a gentler one. Because the ratio is fraud-plus-disputes over settled transactions, a store with healthy, growing legitimate sales has more room before the ratio crosses the line than a store with flat volume and the same raw number of disputes. That is not a reason to chase volume recklessly, but it does mean cutting good customers with over-aggressive fraud rules can quietly work against you by shrinking the denominator.

What happens if you exceed the VAMP threshold?

Crossing 1.50% does not switch off your account overnight, but it starts a chain you do not want. Your acquirer is the party Visa holds accountable, so once your ratio breaches the threshold your acquirer faces Visa assessments and pushes that pressure onto your account. In practice that means a monitoring program, a remediation plan, per-dispute fines that stack monthly, and in persistent cases losing your ability to process Visa at all.

The financial exposure compounds because the underlying problem is usually growing while you are in the program. Refund and policy abuse is now the number one fraud threat merchants report, ahead of stolen-card fraud, and 67% of merchants say they have received AI-generated or doctored evidence attached to disputes (MRC 2026²). Account takeover is climbing alongside it, with the reported ATO fraud rate up 37% year over year in the first half of 2026 (Chargebacks911³). So a merchant who lands in VAMP monitoring is often facing rising disputes at the exact moment the program demands they fall. The way out is not to wait for the next reporting cycle and hope; it is to attack the numerator directly.

How do you lower your VAMP ratio fast?

This is the part no vendor announcement covers: what to actually do, in order, when the clock is running. Work these levers top to bottom, because they are sequenced by speed of impact on your VAMP ratio. First, stop the disputes you can see coming: turn on order scoring and hold or cancel the highest-risk orders before you fulfill them, focusing on billing and shipping mismatch, high-velocity attempts from one device or card, and mismatched AVS or CVV results. A fraudulent order you never ship cannot become a TC40 or a TC15.

Second, win representment on disputes worth fighting. Every dispute you win removes a TC15 from your numerator. Fight the ones where you can produce independent, third-party-verifiable evidence: carrier delivery confirmation, geolocated proof of delivery, and identity or device signals from the original order. Networks weight independent evidence above your own internal records, so evidence you can prove beats evidence you simply assert. Third, kill card testing at the edge, because card-testing waves inflate both your fraud reports and your separate enumeration ratio; rate-limit checkout attempts, challenge suspicious sessions, and block automated traffic before it hits your gateway.

Fourth, deflect the disputes that should have been refunds. A meaningful share of disputes are customers who could not find your refund path and went to their bank instead; clear refund and cancellation flows convert some of those would-be TC15 records into ordinary refunds that never touch your ratio. Fifth, instrument every order to produce evidence later. With 67% of merchants now seeing AI-fabricated dispute evidence (MRC 2026²), tamper-evident records of what shipped, when, and to whom are what let you win the disputes that do come. Capture that at the moment of sale, not after the dispute lands.

The reason this sequence works is that it targets the ratio, not a vague sense of "fraud." Prevention keeps events out of the numerator entirely, representment removes events already in it, deflection reroutes events before they count, and instrumentation is what makes representment win. If you have only a few weeks before your acquirer’s next review, run prevention, representment, and card-testing defense first: they move the number fastest, because they act on the disputes and fraud reports still forming right now.

How should you monitor your VAMP ratio?

Calculate your VAMP ratio weekly, not monthly, using a rolling count of the trailing period. By the time a monthly acquirer report flags you, the fraud reports behind it are weeks old and you have lost the window to react before enforcement. A weekly rolling calculation, even in a simple spreadsheet, gives you a trend line and lets you see the ratio climbing toward 1.50% while you still have room to act.

Set an internal warning line below the official threshold. Because TC40 fraud reports arrive late, the number you see today understates where you will actually land once those lagging reports post. Treating 1.20% as your personal ceiling gives you a buffer for that lag. If your rolling ratio crosses your internal line, that is the signal to run the reduction runbook, not the acquirer’s warning email, which arrives after the damage is done. The merchants who never end up in a monitoring program are almost always the ones watching a weekly number, not the ones reading a monthly report.