If your institution issues cards, processes them, or runs a fintech card program, you’ve likely heard about Visa’s Acquirer Monitoring Program (VAMP), even if fraud monitoring, not disputes, is technically someone else’s desk. That’s by design. VAMP folded two previously separate programs, the Visa Dispute Monitoring Program and the Visa Fraud Monitoring Program, into a single ratio that treats fraud claims and non-fraud disputes as one combined signal, with a threshold that tightened to 1.5% earlier this year.
On October 24, 2026, the program expands again, widening how Visa’s Compelling Evidence rules identify related fraudulent activity across multiple merchants. For a dispute operations team, that’s worth understanding even if fraud monitoring sits with a different department, because the same underlying shift, treating fraud and disputes as one connected data set instead of two, applies just as much to how your own case management should work.
What VAMP Actually Merged
Before VAMP, fraud and disputes were tracked separately, each carrying its own threshold. Under the current 1.5% VAMP ratio, that separation is gone. A fraud claim (a transaction the cardholder says they never authorized) and a non-fraud dispute (a transaction they authorized but disagree with, such as a billing error, a service issue, or goods not received) now count toward the same combined number. Cross that ratio, and there are real financial consequences for the acquiring side of the transaction.
What Changes on October 24
Today, Visa’s Compelling Evidence 3.0 rules generally look for a pattern within a single merchant: has this cardholder made prior, undisputed purchases at this exact business. Starting October 24, 2026, that scope expands to include transactions across differentmerchants, as long as they share a linked payment credential, meaning additional tokens tied to the same underlying card. In practice, fraud pattern detection stops looking at one storefront in isolation and starts looking at the cardholder’s broader transaction footprint.
The Blind Spot This Creates for Issuers and Program Banks
Visa’s rule is written for the acquirer side of the transaction, but the pressure travels. When a change like this expands what counts as pattern evidence, it also raises the stakes on the reason code your team assigns at intake. A claim that should have been coded as “fraud,” or the reverse, a cardholder dispute miscoded as fraud, doesn’t just risk resolving that one case incorrectly. It risks feeding the wrong number into a ratio your network and acquiring partners are watching closely.
Most dispute platforms weren’t built with that connection in mind. They were built to close individual cases quickly, not to make sure a fraud claim gets classified as accurately, and as consistently, as a billing dispute filed the same week by a different analyst.
Where a Unified Platform Earns Its Keep
This is the same architecture question Dispute Advantage was built around: a case isn’t just resolved, it’s classified, documented, and tracked in a way that holds up if it’s ever looked at again, whether that’s an examiner, a card network, or an acquiring partner asking why the numbers moved. Consistent reason-code logic at intake, full evidentiary documentation, and a single audit trail across every case, regardless of whether it starts as a fraud claim or a billing dispute, means an institution isn’t relying on individual analyst judgment to keep those categories straight case by case.
What This Means If You’re Evaluating Dispute Technology
Card network rules will keep evolving. VAMP itself has changed twice in the past year and a half. The systems that hold up aren’t the ones built around today’s specific thresholds. They’re the ones built so fraud and dispute data live in one place, classified consistently from the moment a case is opened. That’s what lets an institution adapt when the rules change again, without rebuilding the plumbing every time Visa does.
Is your team confident every fraud claim and every dispute is coded the same way, no matter which analyst opens the case?
Learn more about Dispute Advantage and how APS helps issuing banks, processors, and fintech program managers keep fraud and dispute data consistent across a card network rule set that keeps shifting.
