Visa Acquirer Monitoring Program (VAMP): What Every Merchant Needs to Know

VAMP replaced two separate Visa monitoring programmes in October 2025, tightened the chargeback threshold, and created a unified enforcement framework that moves faster and fines harder than what came before. If your dispute rate is above 0.7%, you need to understand this programme thoroughly.

What Is the Visa Acquirer Monitoring Program?

The Visa Acquirer Monitoring Programme (VAMP) is Visa's unified dispute and fraud monitoring system, launched on 1 October 2025. It replaced two previously separate programmes: the Visa Dispute Monitoring Programme (VDMP), which tracked chargeback rates, and the Visa Fraud Monitoring Programme (VFMP), which tracked fraud rates independently. Under VAMP, both metrics feed into a single monitoring framework with a single set of thresholds and a single fine schedule.

Despite the name, VAMP formally operates at the acquirer level — Visa monitors and fines your acquiring bank, not your merchant account directly. In practice this distinction changes nothing for merchants: acquirers immediately pass every fine and every compliance requirement to the merchant responsible for the breach. The liability is yours; the acquirer is simply the conduit.

VAMP calculates your dispute rate monthly. Each calendar month, Visa tallies your total chargebacks and fraud disputes, divides by the prior month's transaction volume, and compares the result against programme thresholds. If you breach a threshold, your acquirer receives a notification in the first two weeks of the following month. The remediation clock begins from that notification, not from the breach itself.

VAMP vs VDMP vs VFMP: What Changed

To understand VAMP's significance, it helps to understand what it replaced. VDMP triggered at 1.0% monthly chargeback rate — merchants at 0.95% could operate indefinitely without entering the programme. VFMP monitored fraud separately, with its own threshold and its own escalation track. Merchants could manage the two metrics independently, sometimes letting one drift while managing the other.

VAMP collapses that separation. Both chargebacks and TC40 fraud disputes now count toward a single rate. There is no longer a benefit to reducing one while ignoring the other. A 0.5% chargeback rate combined with a 0.5% fraud rate puts you above the Standard threshold when combined, even though neither rate alone would have triggered VDMP or VFMP separately.

The threshold itself tightened. VDMP's trigger was 1.0%. VAMP's Standard tier triggers at 0.9%. A merchant processing 1,000 transactions per month can now absorb only 8 disputes before breaching, compared to 9 under VDMP — a 12% reduction in headroom. At higher volumes the absolute difference is larger and operationally significant.

EU merchants face a more severe change: VAMP applies a 0.5% dispute threshold in European regions, compared to the 0.9% global standard. This reflects Visa's stricter approach to CNP fraud in EU markets under PSD2 regulatory pressure. EU merchants who were operating comfortably under VDMP may find themselves above VAMP's threshold without any change in their actual dispute volumes.

VAMP Thresholds and Fines

VAMP uses four tiers. Each tier triggers a different enforcement response, and the consequences escalate sharply between tiers.

One calculation detail that catches merchants out: the denominator for your VAMP rate is the prior month's transaction volume, not the current month's. If your sales drop sharply in month M — seasonal dip, marketing pause, site outage — while chargebacks from month M-1 arrive in month M, your apparent rate can spike even though your dispute volume is unchanged. Monitor both the numerator and denominator independently.

How Acquirers Pass VAMP Fines to Merchants

Visa issues fines to your acquiring bank. The acquirer, in turn, passes the full fine to the merchant whose account triggered the breach. The fine appears on your monthly processor statement, often labelled as a "dispute programme assessment," "monitoring programme fee," or similar. Easy to overlook; impossible to reclaim.

Most acquirers add their own charges on top of the Visa fine. A typical structure includes: the Visa fine itself, plus a flat acquirer processing fee ($500–$2,000/month depending on the acquirer), plus a per-dispute fee for every dispute filed above the threshold. At the Excessive tier, the combined cost can reach $15,000–$20,000/month before accounting for the direct cost of lost disputes themselves.

Merchants in the Excessive tier frequently discover this months in — when the fines 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.

What Triggers VAMP Entry

Merchants enter VAMP monitoring when their combined dispute and fraud rate exceeds a tier threshold in a given calendar month. The most common root causes:

• High friendly fraud rate — legitimate cardholders disputing valid transactions. Accounts for 60–80% of all chargebacks at most merchants. Unclear billing descriptors are the single largest trigger for unintentional friendly fraud.
• Subscription billing disputes — recurring charges disputed as unauthorised or cancelled. Common for SaaS, streaming, and box subscription businesses without robust renewal communication.
• CNP fraud attacks — stolen card credentials used on your platform, generating TC40 fraud disputes. A targeted fraud campaign can spike your rate in a single week.
• Fulfilment problems — delivery delays, lost shipments, or product quality issues driving "goods not received" and "not as described" disputes in volume.
• Transaction volume drops — the same absolute chargeback count produces a higher rate when transaction volume falls. Seasonal slowdowns or marketing pauses can push previously safe ratios above threshold.

How to Calculate Your VAMP Rate

The VAMP rate calculation:

The prior-month denominator is the critical detail. If you process 10,000 transactions in April and receive 100 chargebacks plus fraud disputes in May, your VAMP rate for the May review period is 100 ÷ 10,000 = 1.0% — which exceeds the Standard threshold. Visa uses April's transaction count, not May's.

Use our VAMP Ratio Calculator to check your current position in real time.

The Five Fastest Ways to Lower Your VAMP Rate

1. Win your existing chargebacks

Every won dispute reduces your net loss but — importantly — does not remove the chargeback from your ratio. What winning does is reduce the ongoing count by eliminating the pattern: merchants who contest every legitimate dispute show issuers and acquirers that disputes get fought, which subtly reduces subsequent dispute filing behaviour. For Visa 10.4 fraud disputes, Visa's Compelling Evidence 3.0 framework allows you to shift liability to the issuer if you can demonstrate two or more prior undisputed transactions from the same device and IP within the past 365 days. CE 3.0 win rates consistently exceed 70% for well-documented submissions — the highest win rate of any dispute response strategy available to e-commerce merchants.

2. Proactively refund before chargebacks are filed

A refund prevents a chargeback from entering the network entirely — it never becomes a dispute count, never affects your ratio, and costs only the transaction amount (not the chargeback fee plus ratio impact). When a customer contacts you to complain about an order and the claim looks like it might escalate, issue a refund immediately. Chargeback alert services (Verifi, Ethoca) extend this model systematically: they notify you when a cardholder contacts their bank, giving you a 24–72 hour window to refund before the formal dispute is filed.

3. Fix your billing descriptor

"I don't recognise this charge" is the most common reason cardholders file disputes — and most of those disputes are against perfectly legitimate transactions. The cardholder saw a legal entity name, a payment processor prefix, or an abbreviated string they didn't recognise, assumed fraud, and called their bank. Update your billing descriptor to your exact brand name as it appears in your marketing, plus a customer support phone number. This change takes minutes at your processor and typically reduces unrecognised-charge disputes by 15–25% within a billing cycle.

4. Enable 3D Secure 2.0 on high-risk transactions

Transactions authenticated via 3DS2 shift fraud liability from merchant to issuer. If a 3DS-authenticated transaction is subsequently disputed as fraud, the chargeback goes to the issuing bank — not your ratio. Enabling 3DS2 on Stripe, Shopify Payments, or your payment gateway (typically a configuration change, not a development project) eliminates merchant liability for an entire category of disputes. Frictionless 3DS — where the cardholder sees no challenge screen — shifts liability just as effectively as step-up authentication.

5. Implement Visa Order Insight

Order Insight connects your transaction metadata 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 your merchant name, product description, and order confirmation number before filing a dispute. A significant proportion of potential disputes are resolved at this stage — the cardholder recognises the transaction once they see the details. Order Insight integration is available through most major payment platforms at no additional cost.

If You Are Already in VAMP: Step-by-Step Response

If you have received a VAMP notification from your acquirer, or if you have calculated that your current rate exceeds the threshold, act immediately:

1. Request a dispute breakdown from your acquirer. Ask for the data by reason code and by week for the past 90 days. You need to know whether the primary driver is fraud (10.4), goods not received (13.1), subscription disputes (13.2), or something else — because each has a different solution.
2. Address the dominant reason code first. One reason code typically accounts for 50–70% of your VAMP exposure. Targeting that code first produces faster ratio improvement than spreading effort evenly across all dispute types.
3. Submit a written remediation plan to your acquirer within 30 days. Most acquirers require this when you enter Standard or Excessive tier. Submit it proactively, before they ask. Include specific actions, timelines, and expected rate improvements. A credible plan earns goodwill with your acquirer's risk team and demonstrates you understand the programme.
4. Track your rate weekly, not monthly. Monthly reviews are too slow — by the time you see a spike in your monthly report, you're already three weeks into the next review period. Most payment dashboards expose dispute data with a 24–48 hour lag. Set a weekly internal target of 0.65% (Standard) or 0.35% (EU) to give yourself a buffer.
5. Ensure every dispute is responded to before the 30-day Visa deadline. Missed deadlines are automatic losses that keep your ratio elevated while also costing you the transaction amount. If your team doesn't have the capacity to respond consistently to every case, outsourcing is the correct solution.

VAMP and the Chargeback Reason Code Framework

Understanding which Visa reason codes contribute most to your VAMP rate helps focus remediation:

• 10.4 (Other Fraud — Card-Absent): The most common fraud-coded CNP dispute. Without 3DS authentication, merchants bear full liability. With CE 3.0, liability can shift to the issuer. Enabling 3DS2 prevents future 10.4 liability entirely on authenticated transactions.
• 13.1 (Merchandise/Services Not Received): The most common consumer dispute at physical goods merchants. Carrier tracking and delivery confirmation are the primary evidence. Signature confirmation eliminates the dispute category entirely for orders above the threshold.
• 13.2 (Cancelled Recurring Transaction): Subscription disputes. Prevented by renewal reminders, documented consent at sign-up, and one-click cancellation flows.
• 13.3 (Not as Described): Product quality and description disputes. Detailed product specifications, photos, and order confirmation records win these consistently when the description was accurate.

The Visa VAMP reason code page provides full detail on the programme and links to individual reason code guides.

Regional VAMP Thresholds

VAMP thresholds differ by geographic region. The difference between the EU threshold and the global standard is the most significant:

• US / Canada: 0.9% Standard threshold
• EU: 0.5% Standard threshold — reflects the stricter fraud environment under PSD2 and SCA requirements
• APAC / CEMEA: 0.9% Standard threshold

EU merchants who are predominantly serving EU cardholders face more than double the threshold sensitivity of their US counterparts. A 0.8% dispute rate is standard-tier safe in the US but significantly above the EU threshold. EU merchants should use the EU-specific values in the VAMP calculator to evaluate their position accurately.

When to Outsource Chargeback Management

Managing chargebacks in-house while in or near VAMP requires: tracking every dispute deadline across potentially hundreds of cases per month, building correct evidence packages for each reason code, writing network-compliant rebuttal letters, and submitting everything before the 30-day Visa window closes. In-house teams with competing priorities consistently miss deadlines on a subset of cases, lose winnable disputes, and keep their ratio elevated longer than necessary.

The economics of outsourcing at $10 per case are compelling once you account for the full cost of in-house management. A team member spending 3 hours per dispute at $50/hour costs $150 per case in internal time — 15× the outsourcing cost. For merchants in the Excessive tier paying $10,000/month in VAMP fines, any service that lowers the rate back below the Excessive threshold pays for itself immediately from the fine reduction alone.

Conclusion

VAMP is the most significant change to Visa's dispute monitoring framework in years. The tighter 0.9% threshold (0.5% in the EU), the unified dispute-plus-fraud calculation, and the faster fine escalation make it a more serious compliance requirement than VDMP ever was. Merchants who were previously safe under VDMP may now find themselves in Standard monitoring without any increase in absolute dispute volumes — simply because the threshold moved.

The response is systematic: monitor your rate weekly, address your dominant reason code specifically, make sure every legitimate dispute gets a response before the 30-day deadline, and use the prevention tools available to you (3DS2, Order Insight, billing descriptor clarity, renewal communication). If your in-house capacity isn't sufficient to do this consistently, outsourcing is almost always cheaper than absorbing VAMP fines.