Visa VAMP 2026: 1.5% Threshold for High-Risk Merchants
Quick answer: Visa's Acquirer Monitoring Program (VAMP) tightened its "excessive" dispute-and-fraud threshold from 2.2% to 1.5% on April 1, 2026, and pairs it with an $8 fee on every disputed or fraudulent card-not-present transaction once you cross it. Mastercard runs a parallel program that can flag a merchant at as few as 100 disputes and a 1.5% ratio. High-risk categories with structurally higher dispute rates, like subscriptions, forex, and adult, get pushed toward the line faster than average retail. Because ePayVista settlement is final the moment a customer pays, there's no reversible transaction sitting on your books for a chargeback to unwind, so there's no VAMP ratio building against you in the first place.
If a processor or acquirer has mentioned VAMP, BRAM, or an "excessive" flag on your account this year, or you're evaluating high-risk processors and keep seeing the term, here's what actually changed, what it costs, and what removes the exposure entirely.
What is Visa VAMP?
VAMP, the Visa Acquirer Monitoring Program, is Visa's current system for tracking fraud and disputes at the merchant and acquirer level. It replaced two older, separate programs, the Visa Dispute Monitoring Program (VDMP) and the Visa Fraud Monitoring Program (VFMP), by combining fraud reports (TC40 data) and non-fraud disputes (TC15 data) into a single ratio measured against total settled transactions.
The point of the merge is that Visa no longer cares whether a bad transaction was disputed as fraud or disputed as "I didn't recognize this charge" or "I want my money back." Both count against the same number now, and that number determines whether your acquirer, and by extension you, land in the "excessive" tier.
What changed on April 1, 2026?
The threshold got tighter, and the fine got more expensive:
- Excessive threshold: 1.5%, down from 2.2% at VAMP's original launch, for merchants in North America, the EU, and Asia Pacific. CEMEA merchants remain at the looser 2.2% for now.
- $8 per transaction, charged on every fraudulent or disputed card-not-present transaction for merchants and acquirers sitting in the excessive tier. This fee has applied since October 1, 2025, and now bites at a lower ratio.
- No early-warning buffer. Earlier versions of Visa's monitoring gave acquirers a heads-up tier before "excessive." The current single-tier structure doesn't.
Mastercard runs its own, separate Excessive Chargeback Merchant program alongside this. It can flag a merchant with as few as 100 disputes and a 1.5% ratio, and it calculates that ratio on a lag, this month's chargebacks against last month's sales, which means a slow sales month can push your ratio up even if your actual dispute count hasn't moved at all.
Who actually feels this?
The rule technically applies to acquirers, who are the ones Visa and Mastercard hold accountable. In practice, acquirers pass the consequence straight down to the merchants driving their ratio up:
| VAMP / Mastercard mechanic | What it means for a flagged merchant |
|---|---|
| Ratio calculation | Fraud + non-fraud disputes ÷ settled transactions (Visa); this month's disputes ÷ last month's sales (Mastercard) |
| Threshold | 1.5% (Visa, NA/EU/APAC); 1.5% at 100+ disputes (Mastercard) |
| Fee | $8 per disputed or fraudulent card-not-present transaction once excessive |
| Who pays first | The acquirer, contractually, then the merchant via reserves, fees, or termination |
| Typical merchant response | Higher rolling reserve, transaction holds, or account closure to protect the acquirer's own standing |
High-risk categories are structurally closer to the line before anything goes wrong. Subscription and negative-option billing generates disputes from customers who forgot they signed up. Forex and trading platforms see deposits disputed after a losing trade, not a processing error. Adult content carries elevated friendly-fraud rates. None of that is fraud in the way Visa's fraud reporting was originally built to catch, and it counts against the ratio exactly the same as if it were.
How processors respond to a VAMP flag
If your account (or your acquirer's whole portfolio) crosses the threshold, the standard playbook looks like this:
- Reserve increase. A bigger percentage of every sale gets held back to cover expected fines and disputes.
- Transaction holds or velocity limits. Some processors cap volume while you work the ratio back down.
- Chargeback alert services. Tools like real-time dispute alerts let you refund a transaction before it becomes a formal chargeback, so it doesn't count against the ratio, at the cost of the refund itself.
- Non-renewal or termination. If the ratio doesn't improve, or the acquirer decides the portfolio risk isn't worth it, the account gets closed rather than fixed.
All of these are reactive fixes to a mechanism that's still in place. None of them remove the ratio itself, they just try to keep you under it.
How is ePayVista structurally different?
VAMP exists to measure disputes against card-network merchant transactions, because a card payment is reversible by design, that's what makes a chargeback possible in the first place. ePayVista changes what happens after the customer pays, not the threshold you have to stay under.
Customers still pay by card at checkout, exactly like today. From there, the payment settles through our managed, non-custodial settlement layer, our rails, and lands in an account only you control. Because that settlement is final the moment it happens, there's no reversible balance sitting with a processor for a customer or issuing bank to claw back later, which means there's no dispute event to feed into a VAMP or Mastercard excessive-chargeback ratio in the first place.
| Traditional card-network merchant account | ePayVista | |
|---|---|---|
| VAMP / BRAM exposure | Ratio tracked against every settled transaction | No card-network merchant account carrying a dispute ratio |
| Response to rising disputes | Reserve increase, holds, possible termination | Nothing to escalate |
| $8-per-dispute fee risk | Applies once flagged "excessive" | Not applicable |
| Customer checkout | Card | Card, unchanged |
| Approval | Underwriting review | Setup, about 5 minutes |
Verticals watching this closest
Dispute-monitoring programs hit hardest where dispute rates already run structurally high:
- Forex & trading - deposits disputed after a losing trade look identical to a legitimate dispute in Visa's data, pushing ratios up regardless of fraud intent.
- Gaming & iGaming - blanket high-risk classification plus dispute-prone deposit patterns compound the exposure.
- Supplements & nutra - subscription and free-trial billing is one of the highest-dispute business models in the VAMP data, by design.
- Adult - elevated friendly-fraud rates keep these merchants closer to the line even with clean operations.
For the broader cost picture beyond disputes, see the high risk merchant account cost guide. If chargeback abuse specifically, not VAMP mechanics, is the immediate problem, see chargeback fraud in high-risk merchant accounts and how a no-chargeback processor works.
How switching actually works
- Install the WooCommerce plugin. About 5 minutes; Shopify support is in beta.
- Connect your settlement account. The account only you control, where settled funds land.
- Keep taking card payments as normal. Customers check out exactly like before; nothing about their experience changes.
FAQ
Does ePayVista report a VAMP ratio to Visa?
No. VAMP tracks disputes against a card-network merchant account. ePayVista settlement finalizes into an account only you control, so there's no reversible merchant-account transaction for that ratio to be built on.
If I already have a VAMP flag on an existing processor, does switching fix it?
Switching new volume to ePayVista stops adding to that ratio going forward. It doesn't erase a flag already on record with your existing acquirer for past transactions; that follows its own resolution timeline with that processor.
Can I run ePayVista alongside a processor that's watching its dispute ratio?
Yes. Many merchants shift volume gradually while managing an existing account's standing, rather than switching everything at once.
Is this the same thing as a chargeback fee?
No. A chargeback fee is a flat charge per dispute from your processor. VAMP is Visa's program-wide monitoring system that can trigger reserve increases, per-transaction fines, or termination once your ratio crosses the threshold.
What's the catch on the flat 1%?
None. One flat rate, deducted automatically as funds settle. No reserve, no monthly fee, no gateway fee, and no dispute ratio to manage.
Stop managing a ratio built for reversible transactions
VAMP and Mastercard's excessive-chargeback program exist to police disputes on card-network merchant accounts, and 2026's tighter threshold means high-risk categories hit the line faster than ever. Reserve increases and alert services manage the ratio. Removing the reversible transaction removes the ratio.
Download the WooCommerce plugin and start taking card payments with no reserve, no dispute ratio, flat 1%, settled into an account only you control.
ePayVista helps legal high-risk merchants accept card payments and receive settled funds into an account they control, for a flat 1%, with no chargebacks and no freezes. Setup is a WooCommerce plugin, not an underwriting application.
Stop renting your revenue.
Install the WooCommerce plugin, connect your payout account, and get paid in about 5 minutes. Flat 1%. No freezes.
Download the WordPress plugin