Visa VAMP 2025: What Every Online Merchant Needs to Know

In October 2025, Visa collapsed two long-running monitoring programmes — VDMP and VFMP — into a single unified framework called VAMP, the Visa Acquirer Monitoring Programme. The change tightened the chargeback threshold and made it significantly harder for merchants to stay compliant. If your dispute rate is anywhere above 0.7%, you need to understand how VAMP works before it starts costing you money.

What Is Visa VAMP?

VAMP stands for Visa Acquirer Monitoring Programme. Launched on 1 October 2025, it replaced two separate programmes that had been running for years: the Visa Dispute Monitoring Programme (VDMP), which tracked chargeback rates, and the Visa Fraud Monitoring Programme (VFMP), which tracked fraud rates. VAMP merges both into a single metric and a single enforcement framework.

The programme operates at the acquirer level — meaning Visa formally monitors and fines your acquiring bank, not you directly. In practice, this distinction matters very little: acquirers immediately pass every fine down to the merchants responsible, often with an additional service surcharge on top. For day-to-day compliance purposes, treat VAMP as a direct merchant obligation.

Visa reviews performance monthly. Each calendar month, your combined chargeback-and-fraud rate is calculated, compared against the programme thresholds, and if you breach them you receive a notification — typically via your acquirer — within the first two weeks of the following month. The clock for remediation starts from that notification, not from when the breach occurred.

VAMP vs VDMP vs VFMP — What Changed

Under the old structure, VDMP monitored chargebacks only, with a threshold of 1.0% of monthly transactions. VFMP monitored fraud transactions separately, with its own threshold and its own fine schedule. A merchant could breach VDMP without breaching VFMP, and vice versa. Compliance teams learned to manage the two metrics independently.

VAMP eliminates that separation. Both chargeback and fraud disputes now count towards a single rate, and there is a single set of thresholds. This consolidation was deliberate: Visa wanted to close the gap where merchants managed down one metric while allowing the other to drift. Under VAMP, any strategy that reduces chargebacks but ignores fraud — or vice versa — is incomplete.

The other critical change is the threshold itself. VDMP triggered at 1.0%. VAMP triggers at 0.9%. That single decimal point has pushed thousands of merchants who were previously operating safely into the Standard monitoring tier. A business processing 1,000 transactions per month now breaches the threshold at just 9 disputes, compared to 10 under VDMP. For high-volume merchants, the practical impact is even larger.

VAMP Thresholds and Fines

VAMP uses four tiers. Each tier triggers a different level of Visa's enforcement response, and the consequences escalate quickly once you pass the Standard threshold.

One calculation detail that catches merchants out: your chargeback rate for VAMP purposes is chargebacks filed in month M ÷ transactions processed in month M–1. Visa uses the prior month's transaction volume as the denominator, not the current month's. This means a sharp drop in sales (seasonal dip, failed campaign, etc.) can push your rate above threshold even if your absolute chargeback volume stays flat. Monitor both the numerator and the denominator.

How Acquirers Pass Fines to Merchants

Visa issues the fine to your acquirer. The acquirer is the entity with a direct contractual relationship with Visa, so that is where the liability formally sits. In practice, every acquirer passes 100% of VAMP fines to the merchant whose account triggered the breach. The fine appears as a line item on your monthly statement — often labelled something like "Visa monitoring programme assessment" or "dispute programme fee" — which is easy to overlook if you aren't watching your statements carefully.

Most acquirers also add their own surcharge on top of the Visa fine. This varies by acquirer, but a common structure is the Visa fine plus a flat processing fee (ranging from $500 to $2,000/month depending on the acquirer) plus a per-dispute fee for every dispute filed above the threshold. By the time all three components are combined, the Excessive tier can cost a merchant $15,000–$20,000/month in total programme-related fees, even before the direct cost of lost disputes.

Merchants in the Excessive tier often have no idea they are being fined until month two or three, when the charges have already compounded. If your chargeback rate is above 1.5%, call your acquirer's risk team today and ask specifically whether you are currently in any Visa monitoring programme. Do not wait for them to contact you.

The 5 Fastest Ways to Lower Your Chargeback Rate

Reducing your VAMP rate requires reducing the number of disputes that count against you. Here are the five tactics with the highest near-term impact, roughly in order of speed and leverage.

1. Win your existing chargebacks

Every dispute you win is a dispute that still counted in the numerator when it was filed — but winning means the underlying transaction is not reversed, which reduces your net loss on each case. More importantly, fighting every illegitimate chargeback builds a documented pattern that issuers and acquirers take note of. For Visa 10.4 (fraud — card-absent environment) disputes, use Visa Compelling Evidence 3.0 if you have prior transaction data from the same device fingerprint and IP address. CE 3.0 has among the highest win rates of any dispute response strategy available to e-commerce merchants today.

2. Refund before the chargeback is filed

A refund costs you the transaction amount. A chargeback costs you the transaction amount plus the dispute fee, plus it counts against your VAMP rate. If a customer contacts you to complain and you can see the claim might escalate to a dispute, issue the refund immediately. This is not a loss — it is an arbitrage. You are trading a certain cost (the refund) for a larger certain cost (the chargeback + VAMP impact) that you would otherwise incur anyway. Train your customer service team to escalate potential dispute scenarios for rapid refund review, rather than following a standard complaint resolution timeline.

3. Use Visa Order Insight

Visa Order Insight connects your transaction metadata — merchant name, item description, order confirmation number — directly to the issuing bank's dispute portal. When a cardholder calls their bank to say "I don't recognise this charge," the issuer can show them the full order detail before filing a dispute. A significant proportion of "I don't recognise this" cases are resolved without a dispute ever being filed. Order Insight integration is available through most major payment platforms and PSPs at no additional cost. If your acquirer or payment processor supports it, enabling it should be a priority.

4. Implement RDR (Rapid Dispute Resolution)

Rapid Dispute Resolution (RDR), administered by Verifi (a Visa subsidiary), allows you to set automatic refund rules for disputes before they are formally filed as chargebacks. For low-value transactions, this is often the right trade-off: the refund is issued automatically, the dispute never becomes a chargeback, and your VAMP rate is unaffected. RDR is configurable — you can set rules by transaction amount, product category, dispute reason code, and more. Many merchants set a threshold of $50–$75: disputes under that amount trigger an automatic refund; disputes above it are reviewed manually.

5. Fix your billing descriptor

"I don't recognise this charge on my statement" is the single most common reason cardholders file fraud disputes — and a large proportion of those disputes are filed against perfectly legitimate transactions. The merchant's billing descriptor appeared as an unfamiliar string of characters (a legal entity name, a payment processor reference, or an abbreviation the customer has never seen) and the cardholder assumed fraud. Your billing descriptor should include your brand name exactly as it appears in your marketing, plus a customer support phone number or website. Most acquirers allow you to set a soft descriptor per transaction; use it. This is a five-minute change that can meaningfully reduce your dispute rate within a single billing cycle.

Visa CE 3.0 — Your Highest-Impact Tool for 10.4 Chargebacks

Visa reason code 10.4 — Fraud, Card-Absent Environment — is the most common VAMP contributor for e-commerce merchants. A 10.4 chargeback means the cardholder claims they did not authorise the transaction, and because the card was not physically present, the standard liability shift to the issuer does not apply (unless 3DS authentication was used). The default outcome in an uncontested 10.4 dispute is a merchant loss.

Visa Compelling Evidence 3.0 (CE 3.0), introduced in 2023 and now widely adopted, changes that calculus. CE 3.0 allows merchants to dispute a 10.4 chargeback by demonstrating that the same device fingerprint and IP address made at least two prior non-disputed transactions within the past 120–365 days. If you can show that this "fraudulent" transaction came from a device that has successfully transacted with your business before — without ever triggering a dispute — the liability shifts back to the issuer.

For merchants who have been collecting device fingerprint and IP data at the point of checkout (which most modern payment stacks do by default), CE 3.0 is the single most powerful tool available to reduce VAMP rate from 10.4 disputes. Win rates for well-documented CE 3.0 submissions are consistently above 70%, versus below 30% for standard fraud dispute responses.

→ Full CE 3.0 guide

What to Do If You're Already in VAMP

If you've received a VAMP notification, or you suspect you're close to the threshold, here is the step-by-step response:

1. Request your dispute rate breakdown from your acquirer. Ask for a breakdown by reason code and by week, not just the monthly aggregate. You need to know whether your disputes are dominated by 10.4 fraud, 13.1 (merchandise not received), 13.2 (recurring billing disputes), or something else — because each root cause has a different solution.
2. Identify the dominant reason code. In most cases, one reason code accounts for 50–70% of your VAMP exposure. Address that one first. Spreading effort across all reason codes equally is less effective than eliminating the primary driver.
3. Address the root cause of the top reason code specifically. 10.4 fraud → CE 3.0 and Order Insight. 13.1 not received → delivery confirmation processes and logistics integration. 13.2 recurring → clearer subscription disclosures and easy cancellation flows. Generic chargeback reduction tactics are less effective than targeted fixes.
4. Submit a remediation plan to your acquirer within 30 days. Most acquirers require a written remediation plan when you enter the Standard or Excessive tier. Submit it proactively — before they ask — and make it specific: what you are changing, when, and what rate reduction you expect. A credible plan buys goodwill with your acquirer's risk team.
5. Review your rate weekly, not monthly. Monthly review cycles are too slow. By the time you see a spike in your monthly report, you're already three weeks into the next reporting period. Most payment dashboards expose dispute data in real time or with a 48-hour lag — use it. Set a weekly internal target of 0.15% disputes per week (equivalent to approximately 0.6% monthly), which gives you a buffer before the 0.9% VAMP threshold.
6. Use outsourced dispute management if you don't have in-house capacity. The window for responding to Visa disputes is 30 days. Missing that window means an automatic loss. If your team is stretched, or if you're fighting disputes inconsistently, that inconsistency is costing you winnable cases and keeping your rate elevated.

When to Consider Outsourcing

If you are already in VAMP — or approaching 0.7% — you need every legitimate dispute won. That requires submitting a strong, well-evidenced response to every case before the deadline, without exception. In practice, in-house teams often fall short in three ways: they miss deadlines because disputes come in at unpredictable times and nobody is specifically accountable; they submit weak evidence because building a compelling rebuttal requires expertise in Visa's dispute reason codes and chargeback frameworks; and they skip disputes they believe are unwinnable, which is almost always the wrong call.

Dedicated dispute management teams — whether in-house or outsourced — achieve consistently higher win rates precisely because the work is their only function. They know the reason code frameworks, they never miss deadlines, and they have experience identifying winning angles on cases that look weak on first review.

The economics are straightforward. At $10 per case, outsourcing costs $100 for every ten disputes. If outsourcing wins just one additional case per month that your in-house team would have lost — on an average transaction value of $150 — the service pays for itself entirely from that single recovered transaction. For merchants in the Excessive tier paying $10,000/month in VAMP fines, the math becomes even starker: a service that lowers your rate back below the Excessive threshold eliminates the fine entirely.

→ ChargeMate outsourcing — $10/case

Conclusion

Visa VAMP is the most significant change to card scheme dispute compliance in years, and the tighter 0.9% threshold means merchants who were previously safe under VDMP may find themselves in a monitoring programme for the first time. The fines escalate fast — from warning to $10,000/month to $25,000/month to card acceptance termination within a handful of months — so the window to act is narrow once a breach occurs.

The most effective response is to monitor your dispute rate weekly (not monthly), address your top reason code specifically, and make sure every legitimate dispute is responded to with strong evidence before the 30-day deadline. If you don't have the capacity to do that consistently in-house, outsourcing the function is almost always cheaper than absorbing the fines.