Visa VAMP program: What merchants need to know about the new fraud thresholds
Today we are talking about the Visa VAMP program and why merchants need to pay close attention to how fraud alerts and chargebacks are now being measured.
Visa’s monitoring programs have always influenced how merchants manage fraud and disputes. But the Visa VAMP program introduces several important changes that directly affect fraud ratios, fee exposure, and how fraud signals are counted across the ecosystem.
In this episode I break down what merchants need to know about the Visa monitoring program rollout, how VAMP chargeback thresholds work, and why some merchants are already seeing enforcement actions tied to activity from earlier months.
The biggest change is how fraud alerts and chargebacks are now combined into a single ratio. That shift has real consequences for merchants trying to manage fraud ratios and avoid monitoring programs.
Understanding the Visa VAMP program is critical for ecommerce merchants, acquirers, and fraud teams preparing for the next wave of dispute activity.
What you’ll hear in this episode
- How the Visa VAMP program combines TC40 fraud alerts with chargebacks in a single monitoring ratio
- Why VAMP chargeback thresholds create new compliance pressure for merchants
- What Visa fraud monitoring fees mean when a TC40 alert later becomes a chargeback
- How descriptor-level fraud monitoring can create unexpected fraud attribution issues
- Why processor-specific fraud ratios matter for merchant fraud ratio management
- How merchants can plan for potential holiday chargeback spike planning
You should listen to this episode if you
- Manage fraud or chargebacks for an ecommerce merchant affected by the Visa VAMP program
- Work with acquirers or payment processors handling VAMP compliance for merchants
- Track TC40 fraud alerts and want to avoid TC40 chargeback double counting
- Need better strategies for chargeback prevention under VAMP
- Want to understand merchant VAMP fee math and dispute exposure
If you liked this episode, be sure to subscribe and review the podcast on iTunes, Spotify, YouTube, or wherever you listen to podcasts. It really helps with getting the word out.
Episode notes & key takeaways
How the Visa VAMP program changes fraud monitoring
Let’s reset the room for a moment.
The Visa VAMP program changes how fraud signals are measured by combining two previously separate metrics.
TC40 fraud alerts and chargebacks are now counted together in the same fraud monitoring ratio.
That means merchants who previously managed these metrics separately now face a combined risk profile. If both alerts and disputes accumulate, merchants may reach monitoring thresholds much faster than before.
These VAMP chargeback thresholds determine whether a merchant falls into monitoring programs that trigger additional oversight and potential penalties.
Understanding TC40 alerts and dispute fee exposure
TC40 fraud alerts represent transactions where the issuing bank identifies fraud before or during the dispute process.
Under the Visa VAMP program, these alerts now carry direct financial implications.
Each fraud instance can generate an $8 monitoring fee. If the transaction later becomes a chargeback, that exposure can double.
This creates what many merchants call Visa dispute fee exposure.
When alerts and disputes are counted together, merchants must carefully track how fraud alerts evolve into disputes.
Descriptor-level monitoring and fraud attribution risks
Another important element of the Visa VAMP program is descriptor-level fraud monitoring.
Descriptors represent the merchant name that appears on a customer’s card statement.
If descriptors are reused or shared across businesses, fraud activity may be attributed incorrectly. This creates descriptor mismatch fraud risk, where one merchant’s fraud signals impact another merchant’s ratios.
For merchants working with multiple brands, marketplaces, or payment entities, validating descriptors becomes an essential part of fraud ratio management.
Preventing double counting and managing fraud ratios
One operational challenge merchants must address is TC40 chargeback double counting.
If a fraud alert is followed by a chargeback, merchants risk having both events counted within their monitoring ratio.
That is why refund reconciliation for TC40s becomes important.
If merchants issue refunds after receiving fraud alerts but before disputes are filed, they can sometimes reduce chargeback exposure and prevent unnecessary ratio inflation.
Accurate reconciliation processes are essential for managing fraud ratios under the new monitoring rules.
Planning for VAMP enforcement and holiday disputes
The Visa VAMP program also introduces stricter portfolio monitoring at the acquirer level.
Acquirer portfolio thresholds currently sit around 0.7 percent and are expected to drop to 0.5 percent in April 2026\.
These acquirer risk monitoring rules mean processors must monitor the combined fraud activity of their merchants.
For merchants, this creates additional pressure from payment partners to reduce fraud ratios.
Looking ahead, merchants should also prepare for the typical holiday chargeback spike planning that occurs every year.
Disputes from holiday purchases often appear weeks later, which means January and February can produce sudden increases in fraud ratios.
The key takeaway from this episode is simple.
The Visa VAMP program changes the math behind fraud monitoring.
Merchants need to track fraud alerts, chargebacks, descriptors, and refunds more closely than ever before.
Understanding how these metrics interact will help merchants reduce monitoring risk, avoid unnecessary fees, and improve chargeback prevention under VAMP.
