Quick Answer:
Visa’s VAMP threshold dropped to 1.5% on April 1, 2026. Merchants who were safe at 2.0% are now in violation territory. If your combined fraud reports (TC40s) and disputes (TC15s) divided by your total Visa sales exceed 1.5%, you face $8-per-transaction fines, account restrictions, or termination.
Your chargeback alert tools won’t save you. RDR, Ethoca, Order Insight, and CDRN still count toward your VAMP ratio. They’re intelligence tools, not shields.
The fix: Prevent fraud before it happens, monitor your TC40 and TC15 reports monthly, set internal thresholds below Visa’s limits, and have a backup processor ready in case your primary account faces restrictions.
Key Takeaways
1. The VAMP threshold dropped 32% overnight — from 2.2% to 1.5% on April 1, 2026. No warning tier. If you’re over, you’re over.
2. One transaction can count TWICE against your ratio. A fraud report (TC40) that escalates into a chargeback (TC15) hits your VAMP ratio as two separate events.
3. Alert tools like RDR, Ethoca, and CDRN do NOT reduce your VAMP ratio. They still count toward it. Use them for intelligence, not protection.
4. Your acquirer’s thresholds are even stricter than Visa’s. Many processors now enforce internal caps of 1.0–1.2% to stay below Visa’s 0.5% acquirer threshold.
5. Compelling Evidence 3.0 is the only mechanism that can remove a TC40 from your VAMP numerator after the fact. If you’re not using it, start now.
What Changed with VAMP on April 1, 2026
If you’re already familiar with what VAMP is and how it works, here’s what’s different now:
| Before (Oct 2025) | Now (April 2026) | |
| Merchant Excessive threshold | 2.2% | 1.5% — a 32% reduction |
| Acquirer Above Standard | 1.0% | 0.5% |
| Acquirer Excessive | N/A | 0.7% |
| Fines per transaction | Started Oct 2025 | $8 per transaction (Excessive), $4 per transaction (Above Standard) |
| Warning tier | None | None — if you’re over, you’re over |
| Regions affected | US, Canada, EU, APAC | Same — all regions except CEMEA |
The practical impact: merchants who were sitting at 1.8% or 2.0% and felt safe are now in violation with no grace period. And because acquirer thresholds dropped even further (to 0.5%), your processor is under intense pressure to manage their portfolio — which means they’ll pass that pressure directly to you.
The Double-Counting Trap That Most Merchants Miss
This is the single most dangerous mechanic in VAMP, and most merchants don’t understand it until it’s too late.
Your VAMP ratio is:
(TC40 fraud reports + TC15 disputes) ÷ Total Visa sales transactions
A single fraudulent transaction can generate both a TC40 (when the issuing bank files a fraud report) and a TC15 (when the customer files a chargeback). That one transaction counts as two events in your VAMP numerator.
It gets worse: if you receive a chargeback alert (from RDR, Ethoca, etc.) and don’t resolve it — allowing it to escalate into a TC15 chargeback — it counts as two fraud alerts toward your VAMP ratio. The alert itself counts, and the chargeback it escalated into counts again.
This double-counting means your effective tolerance is much lower than 1.5%. A merchant processing 10,000 Visa transactions per month can only afford 150 combined TC40 and TC15 events. But if half of those are double-counted, you’re really working with a tolerance of about 100 unique fraud incidents.
Why Your Chargeback Alert Tools Won’t Save You from VAMP
This is the biggest misconception in VAMP compliance. Many merchants assume their alert tools — Rapid Dispute Resolution (RDR), Ethoca, Order Insight, CDRN — protect them from VAMP penalties.
They don’t.
Alerts from these tools still count toward your VAMP ratio. They resolve the dispute, but the TC40 fraud report filed by the issuing bank remains. No alert program can intercept or cancel a TC40 filing. Visa requires issuers to file a TC40 for any transaction the customer claims is fraud — period.
Here’s how to think about these tools under VAMP:
Keep them active. The data they provide is critical for spotting patterns and refining your anti-fraud strategy.
Use them for intelligence, not immunity. Quick action on disputes can prevent escalation from alert to chargeback, which avoids the double-counting trap above.
Don’t let alerts create false confidence. A merchant with Ethoca and RDR active who doesn’t also invest in upstream fraud prevention will still breach VAMP thresholds.
The only tool that can actually remove a TC40 from your VAMP numerator is Compelling Evidence 3.0 — Visa’s enhanced data-sharing framework. When a CE 3.0 representment succeeds, Visa removes the TC40 from the fraud count, and you keep the revenue. But CE 3.0 has strict qualification requirements: you need two prior undisputed transactions on the same payment credentials, aged 120–365 days, with matching data elements.
Your Acquirer Is Under More Pressure Than You
Here’s what most VAMP guides don’t tell you: Visa’s acquirer thresholds are much stricter than merchant thresholds.
Visa set the acquirer “Above Standard” threshold at 0.5% and “Excessive” at 0.7% — far below the merchant threshold of 1.5%. Acquirers exceeding these limits face fines per affected transaction across their entire portfolio.
This creates enormous pressure for processors to proactively restrict or offboard merchants whose individual ratios threaten portfolio compliance. What does that mean for you?
• Your processor may set internal merchant thresholds at 1.0–1.2% — well below Visa’s 1.5%
• You may face restrictions before you actually breach Visa’s threshold
• Low-volume merchants are being dropped first — acquirers are closing accounts with low sales volume to remove the worst ratio offenders
• The first sign of trouble may not be a warning — it may be tighter processing restrictions, account reserves, or a settlement pause
This is why having a backup processor isn’t optional for high-risk merchants under VAMP. If your primary account faces restrictions, you need to keep accepting payments while you resolve the issue.
Your VAMP Compliance Action Plan
Step 1: Know Your Current VAMP Ratio
Calculate your ratio right now. Add your TC40 (fraud reports) and TC15 (disputes) for the last full month, then divide by your total Visa sales transactions.
You won’t find TC40 reports in standard reporting portals — you need to request them from your processor. If your processor won’t share them, that’s a red flag. Push for transparency or consider switching to a provider who gives you access.
To estimate your ratio without TC40 data: add all your dispute and chargeback alerts with fraud-related reason codes, then divide by your total Visa sales. This gives you an approximate VAMP ratio.
Step 2: Set Internal Thresholds Below Visa’s Limits
Don’t aim for 1.5% — aim for 0.9% to 1.0%. This gives you a buffer for seasonal fluctuations, unexpected spikes, and the fact that your acquirer’s internal threshold is probably lower than Visa’s.
Monitor monthly, not quarterly. VAMP is calculated on a per-calendar-month basis. A single bad month can trigger enforcement.
Step 3: Prevent Fraud Upstream
The only way to reduce TC40s is by preventing fraud before it happens. No alert program can intercept a TC40 after the issuing bank files it.
• 3D Secure: Shifts fraud liability to the issuing bank and reduces fraud-related declines
• Velocity checks: Limit the number of transactions from the same card, IP address, or device within a time window
• Device fingerprinting: Identify suspicious devices across multiple transactions
• Block enumeration attacks: Limit failed payment attempts per card and IP. Watch for repeated attempts using the same first six card digits (BIN attacks)
• KYC verification: Verify customer identity on high-ticket or first-time orders
For more fraud prevention strategies, see our guide on reducing credit card decline rates.
Step 4: Stop Double-Counting Before It Happens
When you receive a chargeback alert from Ethoca, RDR, or another tool, resolve it immediately. If you don’t resolve the alert and it escalates into a TC15 chargeback, it counts as two events toward your VAMP ratio.
Fast alert resolution doesn’t reduce your TC40 count, but it prevents the TC15 on top of it. That’s the difference between one count and two.
Step 5: Implement Compelling Evidence 3.0
CE 3.0 is the only mechanism that can remove a TC40 from your VAMP numerator after the fact. When you win a CE 3.0 representment on a Visa reason code 10.4 dispute, Visa removes the TC40 from your fraud count, you keep the revenue, and you avoid the $8 enforcement fee.
CE 3.0 requires two prior undisputed transactions on the same payment credentials, aged 120–365 days. At least two of four data elements must match (user ID, shipping address, IP address, device ID), and at least one must be IP address or device ID.
Step 6: Set Up a Backup Processor
If your primary processor restricts your account due to VAMP concerns, you need to keep accepting payments. A secondary merchant account with a different acquirer gives you uninterrupted processing while you resolve the issue.
This isn’t just a VAMP strategy — it’s a business continuity strategy. Contact DirectPayNet to set up a backup processor before you need one.
Step 7: Monitor Monthly and Act Early
Track your TC40 and TC15 reports every month. Don’t wait for Visa or your processor to notify you — by the time they do, you may already be in the enforcement zone.
Request TC40 data from your processor. If they won’t provide it, engage with a pre-dispute system like Verifi that can surface this data for you.
Who Is Most at Risk Under VAMP
VAMP affects every merchant processing card-not-present Visa transactions, but these business types face the highest risk:
Subscription and recurring billing businesses — higher baseline dispute rates from customers who forget they subscribed or can’t easily cancel.
High-risk industries — supplements, nutraceuticals, CBD, travel, adult, gaming. These categories already face elevated fraud and dispute rates.
High-volume, low-margin businesses — VAMP measures by count, not dollars. A merchant with 50,000 transactions and 750 events is over the threshold, regardless of transaction value.
Merchants with low sales volume — paradoxically, low-volume merchants are at highest risk of ratio spikes. A handful of disputes on 500 transactions creates a much worse ratio than the same disputes on 50,000 transactions.
International merchants — cross-border transactions face higher fraud rates, which directly impacts your TC40 count.
If you’re in any of these categories, your VAMP strategy needs to be active now, not reactive later.
Frequently Asked Questions
As of April 1, 2026, the merchant Excessive threshold is 1.5%. This dropped from 2.2%, a 32% reduction. There is no warning tier — merchants exceeding 1.5% face immediate enforcement including $8-per-transaction fines. For a full breakdown, see our VAMP explainer.
Yes. Alerts from RDR, Ethoca, Order Insight, and CDRN still count toward your VAMP ratio. They help you resolve disputes faster and prevent double-counting, but the underlying TC40 fraud report remains in your numerator. The only tool that can remove a TC40 is Compelling Evidence 3.0.
Add your TC40 (fraud reports) and TC15 (disputes) for the month, then divide by your total Visa sales transactions. Only include Visa transactions. Request TC40 data from your processor — it’s not available in standard reporting portals.
Visa imposes $8-per-transaction fines on merchants exceeding the 1.5% Excessive threshold. Your acquirer may also impose additional restrictions: account reserves, payout delays, processing caps, or account termination. Because acquirer thresholds (0.5%) are stricter than merchant thresholds, your processor may act before Visa does.
Yes. A transaction reported as fraud (TC40) that also results in a chargeback (TC15) counts as two events in your VAMP numerator. Additionally, if you receive a chargeback alert and don’t resolve it, allowing it to escalate into a TC15, that also counts as two events.
CE 3.0 is Visa’s data-sharing framework that allows merchants to prove a disputed transaction was legitimate. A successful CE 3.0 representment removes the TC40 from your VAMP numerator, you keep the revenue, and you avoid the $8 fine. It requires two prior undisputed transactions on the same credentials aged 120–365 days with matching data elements.
Yes, especially if you’re in a high-risk industry. If your primary processor restricts your account due to VAMP concerns, a secondary processor ensures you can still accept payments. DirectPayNet helps merchants set up multi-processor arrangements as both a VAMP mitigation strategy and general business continuity.
Protect Your Processing Before VAMP Catches You
VAMP isn’t coming — it’s here. The threshold already dropped to 1.5% and acquirers are actively tightening their portfolios. Merchants who wait for a warning will find there isn’t one.
DirectPayNet helps merchants stay ahead of VAMP with proactive monitoring, fraud prevention tools, chargeback management, and backup processor setups that keep your payments running even under scrutiny.
