How Beast connects
  1. 01Connect read-only, over the API
  2. 02Live in days, on your own data
  3. 03Turn routing on when you choose
See how it connects
Don’t see part of your payment stack? Request itPartner with Beast All integrations

EFFECTIVE APRIL 1, 2026 — LIVE NOW

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.

  • 100+subscription brands
  • $60M+monthly volume analyzed
  • $1B+transaction dataset

Last updated November 5, 2026

Reviewed by Shalin Rabadia, Founder, Beast Insights

Key facts

VAMP is the Visa Acquirer Monitoring Program. It replaced VDMP and VFMP in 2025, consolidating fraud and dispute monitoring into a single, stricter framework, and on April 1, 2026 its excessive merchant threshold dropped from 2.2% to 1.5%.

  • ThresholdVisa's VAMP fact sheet: cut from 2.2% on April 1, 2026 in the US, Canada, Europe and Asia Pacific (Latin America was already at 1.5%; CEMEA stays at 2.2%). Verify with your acquirer.

    1.5%

    New "excessive" VAMP ratio threshold for merchants. Cross it and enrollment begins.

  • MinimumVisa's minimum monthly VAMP count in the US, Canada, Europe, Asia Pacific and Latin America (CEMEA: 150 and USD 75,000). Your acquirer can still act below it.

    1,500

    Fraud reports plus disputes in a month before Visa can flag a merchant on the ratio.

  • PenaltyReported Visa fee for excessive merchants, cut from $10. Your acquirer's fee schedule may differ.

    $8

    Fee per fraud report or dispute once a merchant is identified as excessive, usually passed through by the acquirer.

  • MultiplierUnder VAMP, fraud-coded disputes appear in both the TC40 report and the dispute record.

    2×

    Fraud-related disputes now count twice under the VAMP formula (TC40 + dispute).

  • EffectiveThe 1.5% merchant threshold took effect April 1, 2026. VAMP itself replaced VDMP and VFMP in 2025.

    APR 1, 2026

    Already counting. Your ratio is already being measured.

5-Minute Briefing

What changed.

3a · VAMP in 60 seconds

VAMP replaced VDMP and VFMP in 2025. On April 1, 2026, its merchant line dropped to 1.5%.

What changed

01Threshold
1.5%, down from 2.2%, once a merchant has 1,500 fraud reports and disputes in a month.
02Fraud disputes
Counted twice in the ratio.
03RDR
No longer deflects TC40s.
04Acquirers
Being measured too — passing tighter limits down to merchants.

3b · Side-by-side comparison

Before VAMP → VAMP in 2026.

How it compares

  • High-impact change
  • Meaningful change
  • Housekeeping
DimensionBefore VAMP (VDMP + VFMP)VAMP in 2026
Housekeeping: Framework VDMP + VFMP (separate programs) VAMP (unified)
High-impact change: Excessive threshold VDMP: 0.9% standard, 1.8% excessive (disputes only) 1.5% VAMP ratio (2.2% until March 31, 2026)
Meaningful change: Minimum count Separate counts per program 1,500 fraud reports + disputes a month
High-impact change: Warning tier VDMP early warning notice None for merchants; acquirers are flagged from 0.5%
Meaningful change: Penalty structure Flat fines + enrollment Per-dispute fees + enrollment
High-impact change: Fraud disputes Counted once Counted twice (TC40 + dispute)2×
High-impact change: RDR deflects TC40 Yes NoGONE
Housekeeping: Measurement window Calendar monthly Monthly
Meaningful change: Termination trigger After sustained excessive status Same — but you reach it faster
Meaningful change: Card testing Not measured by VDMP or VFMP Enumeration ratio: 20% with 300,000+ enumerated attemptsNEW

3c · Who this applies to

Built for subscription operators with multiple MIDs.

VAMP applies to every Visa-accepting merchant. But the pressure lands hardest where dispute rates are naturally elevated:

  • Nutraceutical subscriptions
  • Telehealth subscriptions
  • Digital and streaming subscriptions
  • Sweepstakes and skill-based gaming
  • Skin, beauty, and wellness subscriptions
  • Any MCC flagged as higher-risk by your acquirer

If your business runs recurring billing across multiple MIDs, this page was built for you.

3d · What hasn't changed

Useful to know — because not everything is now on fire.

  • The definition of a legitimate dispute
  • Chargeback reason codes
  • Representment windows and evidence standards
  • CE3.0 compliant evidence — still deflects friendly fraud
  • Your acquirer relationship — still matters more than your direct Visa relationship

Calculator

What VAMP actually costs your business.

Enter three numbers. See your exposure in dollars.

%
$

Your VAMP status

Caution

1.20%
SafeCautionExcessive
0.5%1.5%

Headroom is shrinking. Tighten alert effectiveness and review MIDs this week.

Monthly

$29.4K

600 disputes/mo, under the 1.5% line

Annual

$352.8K

12-month exposure

Acquirer alert

9 d

Estimated time to intervention

Want these numbers as a PDF for your CFO or board?

We'll prep a clean one-pager with your inputs and send it over.

Send me the report

Methodology: Visa's VAMP thresholds (a 1.5% excessive line since April 1, 2026, counted from 1,500 fraud reports and disputes a month) and the reported $8 fee per fraud report or dispute for an excessive merchant. Your acquirer's limits and fee schedule may differ. Last updated November 5, 2026.

Self-Assessment

Seven questions. One verdict.

Answer each one. Watch your readiness score and projected VAMP exposure update in real time.

  1. 01

    MID portfolio

    Do you have 10 or more active MIDs?

    Single-MID exposure — every dispute lands in one place.

  2. 02

    Daily MID visibility

    Can you see your dispute ratio, per MID, updated at least daily?

    You learn about VAMP-tier risk after the acquirer does.

  3. 03

    Ratio well under 1.5%

    Is every MID's VAMP ratio comfortably under 1.5%, with room for your acquirer's tighter limit?

    You're close to Visa's line, and your acquirer's own limit usually bites first.

  4. 04

    Alert effectiveness

    Do you use pre-dispute alerts (Ethoca, Verifi) — and do you know which ones are actually deflecting?

    You're paying for alerts without knowing which ones work.

  5. 05

    Dispute attribution

    Can you reconcile disputes back to the specific funnel, offer, or affiliate that generated them?

    Disputes are anonymous — you can't fix the source.

  6. 06

    Weekly review cadence

    Do you have a weekly dispute review cadence with documented actions and owners?

    No accountability loop — issues compound silently.

  7. 07

    Headroom for tightening

    If Visa tightened thresholds by another 0.3% tomorrow, would you still be safe?

    No buffer. The next policy change puts you over the line.

The Beast Insights Approach

Fly blind. Hand the controls to a black box. Or sit in the cockpit.

When VAMP is live and your margin for error is pennies, you have three options.

01

Flying Blind

Spreadsheets & billing-platform exports

You learn about VAMP drift in next month's acquirer report. By then, you may already be over your acquirer's limit.

Data latency
Days to weeks
MID granularity
Manual joins, always stale
Drift detection
After the fact
Cross-merchant intel
None

02

Black Box

Autopilot routing tools

Decisions happen — somewhere, by something. You find out when your acquirer calls.

Data latency
Hidden from you
Root cause
The tool decides
Action ownership
The tool, without your input
Transparency
Opaque

03Recommended

Cockpit

Beast Insights

Every MID lit up, every drift caught early, every action yours — with the dollar impact attached.

Data latency
Hourly refresh
MID granularity
Every MID, BIN, combo
Action ownership
You, with $-impact recs
Cross-merchant intel
$1B+ network dataset

"Beast Insights turns the light on for your business."

— Rob, telehealth subscription operator, 25+ MIDs

The Cockpit Model

Five pillars of VAMP readiness.

VAMP compliance isn't a single tool or a single report. It's a system. These are the five pillars every subscription merchant running 10+ MIDs needs in place — and how to know if yours are load-bearing or decorative.

The details

Pillar 1 · 01

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.

What good looks like

  • 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 well before any MID nears 1.5%

Pillar 2 · 02

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.

What good looks like

  • 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

Pillar 3 · 03

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.

What good looks like

  • Representment SLA tracked per MID
  • CE3.0 evidence workflows in place
  • Loss reason analysis fed back into prevention

Pillar 4 · 04

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."

What good looks like

  • Weekly dispute review meeting on the calendar
  • Documented action list with named owners
  • Board-level visibility on VAMP ratio trajectory

Pillar 5 · 05

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.

What good looks like

  • Dispute-to-source attribution (affiliate, offer, funnel)
  • Affiliate-level profitability view net of disputes
  • Offer-level chargeback accounting
  • Feedback loop to marketing and acquisition

Real Scenarios

What VAMP looks like in practice.

From operators running the exact playbook this page describes.

Scenario 01

The campaign that ran hot for 11 days

  1. The problem

    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.

  2. What they changed

    Moved to hourly MID-level monitoring with automatic alerts when any MID crossed an internal 0.9% alert line.

  3. The result

    Cut time-to-detection from 11 days to under 2 hours. The campaign was paused before the MID reached Visa's excessive line.

Scenario 02

The alerts that weren't alerting

  1. The problem

    A telehealth subscription merchant running 25 MIDs suspected their Ethoca alerts weren't fully firing but had no way to audit it.

  2. What they changed

    Audited alert performance MID-by-MID across 90 days of data and identified roughly 20% of purchased alerts that weren't deflecting anything.

  3. The result

    Recovered five figures per month in alert spend — and redirected the budget toward RDR reconfiguration now that TC40 deflection no longer works under VAMP.

Scenario 03

The two affiliates generating 60% of disputes

  1. The problem

    A beauty subscription merchant couldn't tell which affiliates were driving disputes because affiliate-level dispute data wasn't reconciled to source.

  2. What they changed

    Cross-mapped dispute data to affiliate source at the BIN × MID level.

  3. The result

    Found two affiliates generating 60% of disputes while producing 22% of revenue. Cut them. Dispute rate dropped 0.4% within 30 days, back under their acquirer's limit.

More scenarios, as we verify them

We add customer outcomes here as they report them back.

Every scenario on this page is anonymized with the customer's consent. If you're running a VAMP playbook that's working — or not working — we want to hear about it.

Share your outcome

FAQ

Questions we get every week.

24 questions across 4 categories.

Thresholds & Rules

What is VAMP?

VAMP is the Visa Acquirer Monitoring Program. It replaced VDMP and VFMP in 2025, consolidating fraud and dispute monitoring into a single, stricter framework, and on April 1, 2026 its excessive merchant threshold dropped from 2.2% to 1.5%.

What's the new VAMP threshold for merchants?

The "excessive" merchant threshold is a 1.5% VAMP ratio, down from 2.2% on April 1, 2026 (CEMEA stays at 2.2%). It applies once a merchant has 1,500 or more fraud reports and disputes in a month. There is no separate warning tier for merchants, and your acquirer may enforce tighter internal limits.

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 = (TC40 fraud reports + TC15 disputes) ÷ TC05 settled card-not-present transactions, counted each month. Fraud-related disputes are counted twice because they appear in both the TC40 report and the dispute record. Disputes resolved through pre-dispute tools, and fraud that qualifies for Compelling Evidence 3.0, are left out.

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. Visa compares each month's fraud reports and disputes with that month's settled transactions.

Does VAMP apply worldwide?

Yes, VAMP is a global Visa program. The 1.5% merchant threshold applies in the US, Canada, Europe, Asia Pacific and Latin America; CEMEA stays at 2.2%, counted from 150 fraud reports and disputes and USD 75,000.

What is the VAMP enumeration ratio?

VAMP's card-testing measure: enumerated authorization attempts, approved and declined, as a share of all authorization attempts. Visa expects acquirers to keep merchants below an enumeration ratio of 20% with 300,000 or more enumerated attempts in a month, separately from the VAMP ratio.

Penalties & Consequences

What's the per-dispute penalty?

Visa's fee for an excessive merchant is reported at $8 per fraud report or dispute, cut from $10, and most acquirers pass it through. Check your acquirer's fee schedule: many add their own charges.

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"?

Not for merchants. "Above standard" is an acquirer tier: a 0.5% VAMP ratio across the acquirer's portfolio, with "excessive" at 0.7%. That is why acquirers often set internal limits for merchants well below 1.5%, and why the usual first step is acquirer intervention: increased scrutiny, higher reserves, or tightened 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 monitored under VAMP too: a portfolio is "above standard" at a 0.5% VAMP ratio and "excessive" at 0.7%. 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.

Preparation

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.

Beast Insights Specifics

How does Beast Insights help with VAMP compliance?

We give you the analytics behind the five pillars 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 the payment stack you already use. 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.

Work with subscription merchants? Join the Beast partner program

Find out if your business is ready for VAMP.

Get a readiness score in under 15 minutes. Uses your real data, not a sales script.

No credit card. No auto-renewing anything. Real data, not sales theater.