payment nerds logo
Payment Nerds Blog (Single) Gradient Background
Home » Blog » VAMP Thresholds in 2026 Explained: Above Standard vs. Excessive

Post contents

Free Quote

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

VAMP Thresholds in 2026 Explained: Above Standard vs. Excessive

a man pressing against the bridge of his nose in frustration in front of a computer
written by:
Sean Marchese

The Visa Acquirer Monitoring Program (VAMP) gives Visa and acquirers a way to monitor fraud, disputes, and enumeration activity. For merchants, the most important question is how close are we to a threshold?

The thresholds for Visa VAMP 2026 will have an impact on merchants in relation to their fees, reserves, processing limits, and more – especially for ecommerce, subscription, and high-risk merchants.

Why Merchants Need VAMP Threshold Monitoring

The Visa Acquirer Monitoring Program does not just look at chargebacks. The ratio used by VAMP divides the number of fraud and dispute reports for merchants by the total number of settled Visa transactions.

Merchants can create risk in various ways. Fraud transactions, non-fraud disputes, disputes due to incorrect billing statements, recurring payment issues, and issues related to card and payment testing can all contribute to a merchant creating risk for VAMP.

Above Standard vs Excessive VAMP Thresholds

Both of these are escalations of the fraud-and-dispute ratio. Above Standard means the ratio exceeds Visa’s standard. Excessive means the ratio is even more serious and more likely to prompt action by the acquiring company or processor.

Merchants may find themselves in trouble with their processor before they run into trouble with their acquiring company. The acquiring company may monitor the merchant’s portfolio and take steps to reduce issues with high fraud and dispute rates within it.

Who Should Monitor Visa VAMP Thresholds

Businesses that rely on Visa card-not-present transactions should find this guide most useful.

The Visa Acquirer Monitoring Program (VAMP) is of most interest to the following types of merchants:

  • High-risk ecommerce websites
  • Businesses that take subscriptions
  • Card-not-present merchants
  • Merchants that sell CBD, vape products, nutraceutical, adult, travel, dating and digital products
  • SaaS, coaching and online education companies
  • Merchants experiencing rising instances of fraud and chargebacks
  • Merchants using chargeback alert software, 3DS and fraud detection software
  • Businesses that are reviewing visa acquirer monitoring program vamp thresholds
  • Merchants seeking to understand visa vamp chargeback thresholds 2026

If your business uses Visa for card-not-present transactions, you should consider the VAMP program as part of your monthly business review.

Visa Acquirer Monitoring Program (VAMP) Thresholds Compared

The thresholds below are the key concepts merchants need to understand. Exact interpretation should always be confirmed with the merchant’s acquirer or processor because regional rules, processor policies and internal risk limits can be stricter than the public network threshold.

Threshold Area Applies To 2026 Threshold Concept Why It Matters
Above Standard Acquirer portfolio VAMP ratio of 50 bps or higher Signals elevated portfolio risk and may lead processors to tighten merchant expectations
Excessive Acquirer portfolio VAMP ratio of 70 bps or higher Indicates more serious portfolio exposure and can create pressure on high-ratio merchants
Excessive Merchant Individual merchants Regional merchant thresholds apply Merchants over the limit may face fees, remediation, reserves or account review
AP, Canada, EU and U.S. Merchant Threshold Merchants in those regions Reduced to 150 bps on April 1, 2026 Makes it easier for merchants to be flagged if fraud and disputes rise
Enumeration Threshold Authorization activity Enumeration ratio and transaction-count criteria apply Card-testing attacks can create risk even when completed sales look normal

The most important takeaway is that merchants should not wait until they hit Excessive. A merchant operating near the line may already face pressure from the processor because the acquirer is managing its overall portfolio.

Best Tools for VAMP Threshold Management

The right support depends on whether the merchant needs a processor-fit strategy, dispute alerts, fraud prevention, chargeback analytics, or gateway controls.

Provider Or Tool Best Fit For Key Strength Main Tradeoff
Payment Nerds High-risk and card-not-present merchants needing Visa Acquirer Monitoring Program (VAMP) strategy, processor guidance and account-stability support Connects VAMP thresholds to merchant accounts, gateways, fraud controls, chargebacks and underwriting risk More consultative than a standalone chargeback tool
Verifi Merchants that need Visa dispute prevention and pre-dispute workflows CDRN and RDR can help resolve disputes before they become formal chargebacks Requires careful rule setup to avoid over-refunding
Ethoca Merchants that want issuer-to-merchant fraud and dispute alerts Alerts can help stop fulfillment, issue refunds or prevent escalation Coverage and workflow fit vary by merchant setup
Chargeback Gurus Merchants needing chargeback strategy and VAMP education Strong chargeback prevention, representment and Visa Acquirer Monitoring Program (VAMP) guidance Does not replace processor or merchant-account fit
Midigator Merchants that need analytics and dispute workflow visibility Useful reporting, chargeback analytics and representment support Works best when internal payment data is clean
Signifyd Ecommerce merchants focused on fraud decisioning and chargeback protection Fraud screening and chargeback protection options Fit depends on product category, traffic source and risk profile
Gateway Fraud Tools Merchants using NMI, Authorize.Net or similar gateways Velocity controls, AVS, CVV, 3DS and bot controls can reduce upstream risk Requires ongoing tuning to avoid false declines

Payment Nerds is usually the strongest fit when the merchant needs to connect the Visa Acquirer Monitoring Program (VAMP) threshold exposure to the processor fit and merchant-account stability. Software tools can help, but the processor relationship still matters when thresholds are approached.

How VAMP Impacts Chargeback Operations

VAMP will change chargeback operations, as merchants will have to monitor both chargebacks and fraud. The dispute team may not be aware of fraud chargebacks (TC40) whilst focusing on chargebacks (TC15). The fraud team may miss fraud when they are only monitoring for suspicious orders.

The best chargeback operation will bring together fraud, customer support, fulfillment, the gateway, and chargebacks into a single review. Any product, campaign, affiliate, descriptor, or subscription plan that poses a threat to the merchant must be identified before the payment processor does.

How to Stay Below Visa VAMP Thresholds

Build a weekly Visa Acquirer Monitoring Program (VAMP) dashboard to track the following metrics: TC40 fraud reports, TC15 disputes, settled Visa transactions, refunds, authorization declines, chargeback alerts, 3DS performance and gateway error and enumeration rates.

Identify the source of the ratio. Some merchants need enhanced fraud rules. Others need better control over billing descriptors, refunds, delivery and cancellation communications, marketing and campaign cleanups, affiliate accounts or bot activity.

VAMP Compliance Costs Explained

VAMP costs can include fees, costs related to chargebacks and chargeback losses, remedial costs, increases in the reserve amount required of merchants, the reduction of the amount of Visa transactions that can be processed by the merchant, costs related to implementing anti-fraud tools, and the time and costs related to upgrading the technology and staff necessary to handle VAMP and its requirements.

The larger of these costs is usually the instability of the merchant’s accounts with their Visa processors. If the processors lose confidence in the merchant, they may hold the merchant’s funds, require higher reserves from the merchant, or terminate the merchant’s account with the processor altogether. Thus, managing thresholds is a matter of protecting revenue, not simply cleaning up non-compliant merchants.

Common VAMP Threshold Mistakes

The biggest mistake people make is treating VAMP thresholds as a monthly math problem. While the ratio is important to understand, it is even more important to understand the root cause behind the ratio. Merchants should understand which products or channels are creating this threat.

Another of the biggest mistakes is treating Excessive as the only threshold that matters. Threats to merchants can arise from pressures on acquiring banks that exceed the standard threshold. Processors may limit certain merchants before they reach their thresholds to protect their existing merchants and customer base.

Key Features of Visa Acquirer Monitoring Program (VAMP) Thresholds

VAMP Ratio Calculation

The VAMP ratio is a simple calculation that divides the number of fraud and chargeback reports by the number of settled Visa transactions. For instance, a business with 40 fraud reports, 35 chargebacks and 5,000 settled Visa transactions has a VAMP ratio of 75 divided by 5,000, or 1.5%. This ratio may determine whether a merchant has a general discussion with its processor or if it faces a more serious review.

Above Standard Portfolio Monitoring

Above Standard pertains to the portfolios of acquiring banks, not the merchants themselves. When a bank’s portfolio reaches the 50 basis point threshold for the VAMP ratio, it is considered to be above standard. While the merchants may not notice, the acquiring bank’s processors may begin to take more drastic measures with these merchants to contain the problem.

Excessive Portfolio Monitoring

An acquiring bank’s portfolio is categorized as Excessive when it reaches the higher threshold for the VAMP ratio. At this level, the acquiring bank’s processor may take more drastic measures to reduce the risk of the merchants with that acquiring bank. A business may be looked at for this reason if their VAMP ratio is high, as the processor must protect the acquiring bank’s portfolio from excessive exposure to these risks.

Excessive Merchant Thresholds

Each merchant has its own VAMP threshold limits, but only if the acquiring bank is not already Above Standard or experiencing Excessive conditions with its other merchants. Visa publishes a fact sheet with the thresholds for each region of the company, such as the 150 basis point limit for AP, Canada, EU and U.S. merchants as of April 1, 2026. Therefore, to understand the visa vamp thresholds 2026, a merchant should be aware of its region, number of transactions, fraud and chargebacks, and the acquiring bank’s own limits.

Enumeration Thresholds

Enumeration Thresholds Another component of the VAMP ratio is the enumeration ratio. This measures the number of suspected enumeration transactions divided by the total number of authorization transactions for a given merchant. Enumeration occurs when bots attempt to use a variety of different credit cards on a merchant’s website. Enumeration differs from the fraud and chargeback ratios because bots may create thousands of failed authorizations for a merchant that result in no sales.

Processor-Level Limits

A merchant’s processor may have additional limits to the VAMP ratio that are more restrictive than the thresholds that Visa has published for each region and category of merchant. This is done to ensure that the acquiring bank does not have one high-risk merchant dragging the rest of the merchants in that acquiring bank’s portfolio to the Attention or Excessive limits. A merchant should aim to maintain a VAMP ratio that not only meets the official threshold but satisfies the acquiring bank’s and processor’s internal limits, as well.

FAQs About Visa VAMP Thresholds

Q: What are Visa VAMP thresholds?
A: Thresholds under the Visa Acquirer Monitoring Program (VAMP) allow Visa to monitor acquirers and merchants for fraudulent or disputed transactions.

Q: What are the Visa VAMP thresholds for 2026?
A: The thresholds for acquirer portfolios under the VAMP program will be set at Above Standard at 50 bps and Excessive at 70 bps for merchants in AP, Canada, the EU, and the U.S. The threshold for Excessive merchants will be reduced to 150 bps effective April 1, 2026.

Q: What is Above Standard under the Visa Acquirer Monitoring Program (VAMP)?
A: The category of acquirer portfolios with Above Standard thresholds will have a VAMP ratio of 50 bps or higher. Merchants in these portfolios may feel the impact of this threshold, as their processor must implement fraud-prevention measures to protect the acquirer’s portfolio.

Q: What is Excessive under the Visa Acquirer Monitoring Program (VAMP)?
A: The category of acquirer portfolios with Excessive thresholds will have a VAMP ratio of 70 bps or higher. Individual merchants under these acquirers may have different thresholds for being classified as having Excessive fraud and dispute activity.

Q: How is the VAMP ratio calculated?
A: The VAMP ratio is calculated by taking the number of fraud and dispute reports for an acquirer’s merchants divided by the total number of settled Visa transactions for those merchants. Visa considers the number of fraud reports (TC40 records), the number of disputes (TC15 records) and the total number of settled transactions (TC05 records) for each merchant to calculate this ratio.

Q: Are Visa VAMP chargeback thresholds 2026 the same as old chargeback ratios?
A: The thresholds under VAMP for chargebacks are not the same as the old chargeback ratios, as VAMP considers both fraud and chargeback ratios. Merchants are required to monitor both of these categories.

Q: What is the enumeration threshold?
A: Enumeration thresholds for merchants are used to detect bots performing card testing on those merchants’ cards. The enumeration threshold is the number of enumerated transactions divided by the total number of authorization transactions for those merchants. Additionally, there is another threshold that considers the total number of transactions by those merchants to determine whether they have serious instances of card-testing activity.

Q: Can my processor set a stricter threshold than Visa?
A: Yes, a merchant’s processor may set a threshold that is more restrictive than the threshold Visa has set. Additionally, the acquirer for a merchant may have a threshold that is more restrictive than Visa’s threshold, as they are responsible for the fraud activity of the merchants within their portfolio.

Conclusion

The thresholds of the Visa Acquirer Monitoring Program (VAMP) are more than a compliance number for a merchant’s payment network. These thresholds can indicate to a merchant the level of fraud, disputes, enumeration and confidence that their processor has in the merchant’s business. In 2026, merchants should be aware of the difference between thresholds above the standard, excessive, and those of their regional merchants before it becomes a problem for their merchant account.

Payment Nerds can assist with merchants with high levels of fraud and card-not-present transactions to review their VAMP thresholds, monitor for fraud and disputes, and to reduce their chargebacks and improve their gateway controls – all to protect their merchant account from becoming a problem due to high thresholds.

About the Author

Sean Marchese

Sean Marchese, MS, RN, is a Senior Writer for Payment Nerds, specializing in secure payment solutions, fraud prevention, and high-risk merchant services. With over a decade of experience in regulated industries, Sean simplifies complex payment processing challenges, helping businesses optimize their strategies and improve revenue.

hands using a laptop

Subscribe to our newsletter

hands using a laptop

Stay informed with the latest insights, updates, and exclusive offers—subscribe to our newsletter today!

By clicking Sign Up you’re confirming that you agree with our Privacy Policy.

Join the Team

Payment Nerds is here to serve you! With a real person waiting to take your call or answer your email, you only need to let us know how we can help.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Max. file size: 50 MB.