Skip to content
The ValyrPayMerchant Services

Disputes and monitoring

Visa VAMP explained: the ratio, the thresholds and what to do

Visa’s Acquirer Monitoring Program in plain English: how the VAMP ratio is counted, the 2026 thresholds by region, fees, and how to bring a ratio down.

9 min readUpdated 23 October 202610 sources

Contents9 sections
  1. What VAMP is and why it changed
  2. How the VAMP ratio is calculated
  3. The thresholds
  4. Fees and other consequences
  5. A worked example
  6. How to bring a ratio down
  7. Common misconceptions
  8. What to do next
  9. Sources

What VAMP is and why it changedLink to this section

Card schemes monitor the merchants and acquirers on their networks so that a small number of outliers do not drive up fraud and disputes for everyone. Until 2025 Visa did this through several programmes, most visibly the Visa Dispute Monitoring Program (VDMP) and the Visa Fraud Monitoring Program (VFMP), each with its own measures and remediation processes. In 2024 Visa announced that it would consolidate its fraud and dispute programmes into one acquirer programme, and VAMP took effect on 1 April 2025, with a revised formula and thresholds from 1 June 2025.

Three features distinguish it from what came before:

  • It is built around the acquirer. Visa identifies acquirers whose portfolios exceed its thresholds, and merchants whose own figures exceed the merchant threshold. Either way, the acquirer is the party Visa deals with, and the acquirer passes the consequences on to the merchant.
  • It combines fraud and disputes in a single, count-based ratio. Under the old programmes a merchant could sit comfortably on one measure while failing the other.
  • It watches card testing. A separate enumeration measure flags merchants whose checkouts are being used to test stolen card numbers.

How the VAMP ratio is calculatedLink to this section

Visa’s published formula is:

A few terms first. A fraud report is the record an issuing bank files when its cardholder says a transaction was fraudulent; in Visa’s systems it is a TC40 (TC stands for transaction code). A dispute, also called a chargeback, is the issuer reclaiming the money; it is a TC15. A settled transaction is a completed sale, a TC05. Card-not-present covers online, in-app, mail and telephone orders.

What countsLink to this section

  • Every dispute, whatever the reason. In May 2025 Visa changed the formula “to include all disputes”, fraud and non-fraud alike.
  • Every fraud report. Visa stated at the same time that “all TC40s will be counted”.
  • Both, when a transaction has both. If a cardholder reports a payment as fraud and the issuer then disputes it, that one payment contributes two items to the count. Acquirer documentation states this explicitly.
  • Items that went your way. Winning a dispute does not remove it, and refunding a transaction after it was reported as fraud does not remove the fraud report. The programmes measure what happened, not the outcome.

What is excludedLink to this section

Visa publishes two exclusions, both “contingent on the timing of the data extract”:

  1. Disputes resolved through pre-dispute solutions. Visa’s Rapid Dispute Resolution (RDR), for example, accepts eligible disputes automatically against rules you set, before a full chargeback cycle. A dispute resolved that way does not count. Alerts that you act on before any dispute is filed — such as Verifi’s Cardholder Dispute Resolution Network (CDRN) or Mastercard’s Ethoca Alerts — mean there is never a dispute to count.
  2. Fraud reports that qualify under Compelling Evidence 3.0 (CE3.0). CE3.0 is Visa’s framework for showing that a disputed card-absent “fraud” transaction matches the cardholder’s own earlier, undisputed purchases: broadly, at least two prior transactions on the same card from 120 to 365 days earlier, with matching device or IP information and further identifiers. It can be applied before a dispute through Visa’s Order Insight service, or in your dispute response.

The practical consequence is important: a pre-dispute resolution removes the dispute, but not the fraud report. If the issuer has already filed a TC40, it stays in your count unless it qualifies under CE3.0. Some acquirers describe a broader exclusion in their own materials; if yours does, its figures govern, but Visa’s own wording is that all fraud reports count.

Timing matters too. Exclusions only apply if the resolution is in Visa’s data when it extracts the month, so resolving a dispute within the same calendar month it was raised is the safe course.

Which month things land inLink to this section

Visa compares the fraud reports and disputes it received in a calendar month with the transactions that settled in that month, regardless of when the original sales took place. It reviews each month’s figures in the following month.

The thresholdsLink to this section

MerchantsLink to this section

These apply where your acquirer is not itself identified in the programme.

Visa regionExcessive merchant ratioAnd at least, in the month
Europe (including the UK), United States, Canada, Asia Pacific1.50% from 1 April 2026 (2.20% from June 2025 to March 2026)1,500 counted fraud reports and disputes
Latin America and Caribbean1.50%1,500 counted fraud reports and disputes
Central Europe, Middle East and Africa2.20%150 counted items worth at least USD 75,000

Both conditions must be met. Brazil, Chile and India are outside the global programme; Visa has said their programmes will be announced separately.

The count floor means the programme focuses on larger merchants: at 1.50%, you reach 1,500 counted items at 100,000 settled transactions a month. That is not a reason for smaller merchants to relax. Acquirers apply their own limits, and they answer to Visa for their whole portfolio.

AcquirersLink to this section

An acquirer’s portfolio is Above Standard from a VAMP ratio of 0.50% and Excessive from 0.70%, with the same count floors. Acquirers report an Early Warning level from 0.40%. Visa enforced the Excessive level from the end of the advisory period on 30 September 2025; acquirers report that Above Standard enforcement started on 1 January 2026.

This matters to merchants in a less obvious way. Acquirer documentation describes that when an acquirer is identified, its merchants with a ratio of 0.50% or more and at least five counted items can be charged fees too — far below the Excessive merchant level.

Card testingLink to this section

Separately, Visa flags merchants where enumerated authorisation attempts — automated attempts to test card numbers, approved or declined — reach 20% of all authorisation attempts and at least 300,000 in a month. Visa identifies these attempts with its own models, so merchants cannot calculate the measure themselves. Acquirers report that no fees currently apply to it, but an identified merchant will be asked to fix its controls.

Fees and other consequencesLink to this section

Visa does not publish VAMP fee amounts in its public documents. Acquirers report the following levels, each charged per counted fraud report and dispute in the month — all of them, not just those above the threshold:

WhoWhenReported fee per counted item
MerchantExcessive merchant levelUSD 8
AcquirerExcessive (0.70% and above)USD 8
AcquirerAbove Standard (0.50% to 0.70%)USD 4
Merchant of an identified acquirer0.50% and above, at least five itemsUSD 4 or USD 8, following the acquirer’s level

Fees are assessed on the acquirer, which decides how to pass them on. A first identification within a rolling 12-month period is reported to carry a three-month grace period, during which remediation is expected but fees are not charged.

The fees are rarely the biggest cost. An identified merchant is expected to produce a remediation plan, and Visa may require the acquirer or merchant to deploy specific remediation tools (Visa Rules, 10.4.3.1). If the ratio does not come down, the acquirer may terminate the relationship; identification by VAMP reports is one of the grounds Visa’s rules list, and the acquirer’s file on a terminated merchant must include those reports (10.10.1.1). Termination can lead to a listing on Visa’s Merchant Screening Service, which follows the business and its principals to their next application.

One thing never to do: split your volume across new descriptors or merchant accounts to dilute the ratio. If merchant names, data or performance are altered to circumvent VAMP, Visa may charge the acquirer USD 25,000 per merchant per month and permanently disqualify the merchant and its principals (12.5.3.2).

A worked exampleLink to this section

This example is fictional.

An online retailer in Europe settles 120,000 card-not-present Visa transactions in September 2026. In the same month Visa receives 900 fraud reports and 1,100 disputes on its transactions; 150 of the disputes are resolved through Rapid Dispute Resolution within the month.

  • Counted fraud reports: 900 (none qualified under CE3.0)
  • Counted disputes: 1,100 − 150 = 950
  • Counted items: 1,850
  • VAMP ratio: 1,850 ÷ 120,000 = 1.54%

Both conditions for the 1.50% Excessive merchant level are met. At the reported fee level, the month would cost about USD 14,800 (1,850 × USD 8) once any grace period ends. To get below 1.50% at the same volume, the retailer needs 51 fewer counted items — achievable, but only if it attacks fraud reports as well as disputes, because its RDR rules cannot touch the 900 fraud reports.

How to bring a ratio downLink to this section

Stop fraud before it is capturedLink to this section

Issuers must report fraud on captured transactions, but an authorisation you reverse before capture is not reported. Screening orders before capture, using 3-D Secure authentication where it fits your customers, and reviewing high-risk orders manually all reduce fraud reports at source.

Resolve disputes before they are filedLink to this section

Pre-dispute services remove disputes from the count when they work within the month. They cost money per case and mean refunding, so set the rules carefully. Our guide to chargeback alerts compares Order Insight, RDR, CDRN and Ethoca.

Use Compelling Evidence 3.0Link to this section

It is the only route by which Visa excludes a fraud report from the ratio, and it targets “friendly fraud”: genuine customers disputing their own purchases. It depends on keeping good records of prior transactions — device, IP address, account and delivery details. From 24 October 2026 Visa is expanding where the rule applies, and the framework will support multi-merchant transactions as evidence.

Remove the reasons for disputesLink to this section

Clear statement descriptors, prompt receipts, honest product descriptions, easy cancellation for subscriptions and fast responses to customer contact all cut non-fraud disputes. Visa’s merchant dispute guide sets out practical steps for each dispute category.

Shut down card testingLink to this section

Rate limits, bot detection and challenges on suspicious authorisation patterns protect both your enumeration measure and your fraud figures.

Watch the numbers monthlyLink to this section

Do not wait for your acquirer’s report, which arrives a month after the data. Track your own counts — fraud reports, disputes and settled transactions — every week, and run them through the VAMP calculator.

Common misconceptionsLink to this section

  • “Refunding the customer removes the fraud report.” It does not; the TC40 was filed before your refund.
  • “We won the dispute, so it does not count.” Outcomes are not considered.
  • “RDR makes us safe.” It removes disputes, not fraud reports.
  • “We are below 1,500 items, so VAMP does not apply.” Visa will not identify you as an Excessive merchant, but your acquirer is measured on its whole portfolio and will act on its own limits.
  • “A second merchant account will halve our ratio.” It is treated as circumvention.

What to do nextLink to this section

If your ratio is rising, the earlier you act the more options you keep. The ValyrPay Merchant Services reviews your fraud and dispute mix, identifies which counted items each measure would remove, and helps you put pre-dispute services in place, including enrolment with Visa’s Verifi services. We are not a bank or a payment institution, and Visa and your acquirer decide on identification and fees.

Sources

Each source was read on the date shown. Card-scheme rules and regulations change; check the current edition before relying on a detail.

  1. Visa — Visa Acquirer Monitoring Program Overview (fact sheet 2025) (external site)corporate.visa.com · read 23 October 2026
  2. Visa Perspectives — Introducing the Visa Acquirer Monitoring Program (30 Aug 2024, update of 24 Mar 2025) (external site)corporate.visa.com · read 23 October 2026
  3. Visa Perspectives — Program refresh takes aim at payments fraud (15 May 2025) (external site)corporate.visa.com · read 23 October 2026
  4. Visa Perspectives — Evolving the Visa Acquirer Monitoring Program (9 Oct 2025) (external site)corporate.visa.com · read 23 October 2026
  5. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 (10.4.3.1, 10.10.1.1, 12.5.3.2) (external site)usa.visa.com · read 23 October 2026
  6. Visa Dispute Management Guide for Merchants, October 2026 (external site)usa.visa.com · read 23 October 2026
  7. Stripe Docs — Dispute and fraud card monitoring programs (external site)docs.stripe.com · read 23 October 2026
  8. PayPal — Fall 2025 Release Guide (VAMP section) (external site)paypal.com · read 23 October 2026
  9. Checkout.com — Visa Acquirer Monitoring Program (VAMP) explained (external site)checkout.com · read 23 October 2026
  10. Merchant Risk Council (member blog) — Stricter VAMP ratio thresholds are now in effect (1 Apr 2026) (external site)merchantriskcouncil.org · read 23 October 2026

Keep reading