VAMP is live. Your margin for error just shrank.
New threshold, stacking penalties, no pause in the window. Built for subscription merchants running 10+ MIDs.
Key facts
- Threshold: 1.5% — New "excessive" VAMP ratio threshold for merchants. Cross it and enrollment begins.
- Warning: 0.9% — "Above standard" warning tier. Your acquirer will likely act before Visa does.
- Penalty: $10 — Per-dispute fee applied by most acquirers once you're above threshold.
- Multiplier: 2× — Fraud-related disputes now count twice under the VAMP formula (TC40 + dispute).
- Effective: APR 1, 2026 — Already counting. Your ratio is already being measured.
What changed
VAMP replaced VDMP and VFMP on April 1, 2026.
- Threshold: 1.5%, with a 0.9% warning tier.
- Fraud disputes: Counted twice in the ratio.
- RDR: No longer deflects TC40s.
- Acquirers: Being measured too — passing tighter limits down to merchants.
How it compares
| Framework | VDMP + VFMP (separate programs) | VAMP (unified) |
|---|---|---|
| Excessive threshold | 1.5% dispute ratio | 1.5% VAMP ratio |
| Warning tier | VDMP early warning notice | "Above standard" at 0.9% |
| Penalty structure | Flat fines + enrollment | Per-dispute fees + enrollment |
| Fraud disputes | Counted once | Counted twice (TC40 + dispute) |
| RDR deflects TC40 | Yes | No |
| Measurement window | Calendar monthly | Monthly rolling [VERIFY] |
| Termination trigger | After sustained excessive status | Same — but you reach it faster |
The details
Visibility — Can you see your dispute ratio per MID, per funnel, daily?
Visibility is the load-bearing pillar. Every other pillar rests on it. If your data is stale or aggregated above the MID level, you are making decisions on yesterday's shadow.
- Real-time dispute data at the MID level
- Refresh cadence measured in hours, not days
- Drill-down by BIN, processor, campaign, and affiliate
- Automatic alerts when any MID crosses 0.9%
Prevention — Do you have deflection tools in place — and do you know which ones are working?
Under VAMP, prevention gets harder: RDR no longer deflects TC40s. That makes it more important to audit what you're actually deflecting vs. what you're paying for.
- Ethoca and/or Verifi CDRN alerts active
- RDR configured with the new VAMP rules in mind
- Alert effectiveness audited monthly
- BIN blocking based on historical dispute rates
Response — Can you represent disputes inside the window, with evidence that holds?
VAMP tightened thresholds. It didn't change representment mechanics. But it did raise the cost of losing a representment case.
- Representment SLA tracked per MID
- CE3.0 evidence workflows in place
- Loss reason analysis fed back into prevention
Reporting — Do you have a weekly cadence that's documented, reviewed, and acted on?
The merchants who survive VAMP aren't the ones with the best dashboard. They're the ones with the shortest gap between "signal" and "action."
- Weekly dispute review meeting on the calendar
- Documented action list with named owners
- Board-level visibility on VAMP ratio trajectory
Recovery — Can you reconcile disputes back to their source — offer, affiliate, agent?
This is the pillar most merchants don't have. Disputes are usually treated as a cost of doing business. Under VAMP, they're a direct input to your survival — and that means you need to know which part of your business is generating them.
- Dispute-to-source attribution (affiliate, offer, funnel)
- Affiliate-level profitability view net of disputes
- Offer-level chargeback accounting
- Feedback loop to marketing and acquisition
Scenarios
The campaign that ran hot for 11 days
A sweepstakes merchant running 100+ MIDs was reviewing disputes in monthly processor reports. A new campaign went live in early April and started generating disputes at 1.8% — above the new VAMP excessive threshold. They didn't notice for 11 days.
Moved to hourly MID-level monitoring with automatic alerts when any MID crossed 0.9%.
Cut time-to-detection from 11 days to under 2 hours. The campaign was paused before the MID enrolled in "above standard."
The alerts that weren't alerting
A telehealth subscription merchant running 25 MIDs suspected their Ethoca alerts weren't fully firing but had no way to audit it.
Audited alert performance MID-by-MID across 90 days of data and identified roughly 20% of purchased alerts that weren't deflecting anything.
Recovered five figures per month in alert spend — and redirected the budget toward RDR reconfiguration now that TC40 deflection no longer works under VAMP.
The two affiliates generating 60% of disputes
A beauty subscription merchant couldn't tell which affiliates were driving disputes because affiliate-level dispute data wasn't reconciled to source.
Cross-mapped dispute data to affiliate source at the BIN × MID level.
Found two affiliates generating 60% of disputes while producing 22% of revenue. Cut them. Dispute rate dropped 0.4% within 30 days — moving them from "above standard" back to "safe."
Frequently asked questions
What is VAMP?
VAMP is the Visa Acquirer Monitoring Program. It replaced VDMP and VFMP on April 1, 2026, consolidating fraud and dispute monitoring into a single, stricter framework.
What's the new VAMP threshold for merchants?
The "excessive" merchant threshold is 1.5% VAMP ratio. A warning tier — "above standard" — kicks in at 0.9%. Your acquirer may enforce tighter internal thresholds.
What's the difference between VAMP and VDMP/VFMP?
VDMP and VFMP were separate programs — one for disputes, one for fraud. VAMP unifies them, adds a per-dispute fee structure, and makes fraud disputes count twice in the ratio calculation.
How is the VAMP ratio calculated?
VAMP ratio = (fraud disputes + non-fraud disputes) ÷ total settled transactions, measured across a rolling window. Fraud-related disputes are counted twice because they appear in both the TC40 report and the dispute record.
What counts as a fraud dispute?
Disputes filed under fraud-related reason codes (primarily 10.4 and related). These trigger the TC40 report in addition to the dispute itself — which is why they count twice.
What's the measurement window?
Monthly rolling under current guidance.
Does VAMP apply worldwide?
Yes, VAMP is a global Visa program. Regional thresholds may vary — the numbers on this page reflect North America.
What's the per-dispute penalty?
Most acquirers pass through a fee of approximately $10 per dispute once you're above threshold. This is in addition to any Visa-direct fines at the "excessive" tier.
Can my MID be terminated under VAMP?
Yes. Sustained "excessive" status is a termination trigger under most acquirer agreements. VAMP didn't change this — it just made it easier to reach.
Is there a warning tier before "excessive"?
Yes. "Above standard" triggers at 0.9% and usually results in acquirer intervention — not Visa fines, but increased scrutiny, higher reserves, or tightened internal limits.
Does VAMP apply to refunds or only disputes?
Only disputes. Refunds don't count toward your VAMP ratio. But if you're using refunds to avoid disputes, you're treating the symptom, not the cause.
How does VAMP interact with my acquirer's own rules?
Acquirers are also being monitored under VAMP — their portfolio threshold is 0.3%. Most acquirers are responding by tightening internal limits on their merchants well below Visa's public numbers. Your acquirer's limit is usually the one that matters first.
What happens if I hit "excessive" status?
Enrollment in the program, per-dispute fees, required remediation plan, increased reserves, and — if sustained — MID termination or MATCH list placement.
What should I do first?
Confirm three things: (1) the true current dispute ratio of every MID in your portfolio, refreshed at least daily; (2) which of your prevention tools are actually deflecting disputes; (3) whether you can attribute disputes back to source (affiliate, offer, funnel). If any answer is "no" or "I don't know," start there.
Do I need a fraud prevention tool, an analytics tool, or both?
Both. Prevention tools deflect what they can. Analytics tells you what's getting through, why, and where. Under VAMP, you can't run one without the other.
How fast can I bring my dispute ratio down?
Depends on the root cause. If one bad campaign or affiliate is driving a spike, you can move 30–50 bps inside 30 days. If the issue is structural (product, billing model, customer expectation), it takes longer. Either way: you have to see the cause before you can fix it.
What data do I need to be tracking daily?
At minimum: dispute ratio per MID, alert effectiveness per MID, BIN-level decline and dispute rates, and attribution of disputes to affiliate, offer, or funnel.
Does RDR still work under VAMP?
Yes — for non-fraud disputes. No — for TC40/fraud-related disputes. That's the change that's catching the most merchants off-guard.
How does Beast Insights help with VAMP compliance?
We give you the five pillars covered on this page in a single product: hourly MID-level visibility, alert auditing, dispute attribution, BIN-level intelligence, and routing recommendations grounded in cross-merchant network data. Compliance isn't a feature — it's what the product was built to produce.
Do I need to change processors to use Beast Insights?
No. Beast Insights is a layer that sits on top of your existing CRM and processor stack. We integrate with Sticky.io, CheckoutChamp, and major processors. You don't move your money; we read the data.
How long does onboarding take?
Most subscription merchants running 10–50 MIDs are fully onboarded inside two weeks. Larger portfolios (100+ MIDs) take longer because of integration volume, not complexity.
Can I get a VAMP readiness score without booking a demo?
Yes. The readiness score linked at the top of this page is self-serve. A walkthrough is available if you want one, but it's not required.
What's the minimum MID count to make Beast Insights worthwhile?
10+ MIDs. Below that, the complexity usually doesn't justify the product. Above that, the math works quickly.