Risk & disputes
VAMP Compliance Guide
VAMP is the Visa Acquirer Monitoring Program, Visa’s program for monitoring fraud and disputes across acquirers and their merchants. It combines reported fraud and disputes into a single ratio measured against settled transactions. Merchants stay compliant by keeping that ratio below Visa’s published thresholds, which means preventing fraud, resolving disputes early and watching the figure every month.
Summarize with
Key takeaways
- VAMP replaced Visa’s earlier, separate fraud and dispute monitoring programs in 2025.
- It counts both fraud reports and disputes, so one bad transaction can count in more than one way.
- It applies to acquirers as well as merchants, so your provider has its own reasons to act early.
- Thresholds are set by Visa and have been revised since launch. Always work from the current figures.
- Monitoring monthly, with alerts, is the difference between a correction and a crisis.
What is VAMP?
The Visa Acquirer Monitoring Program is how Visa identifies acquirers and merchants with excessive fraud or disputes. Visa introduced it in 2025 to consolidate its previous monitoring programs into one framework with one ratio.
It matters to merchants because the consequences run downhill. An acquirer whose portfolio approaches a threshold will tighten its rules, and a merchant identified under the program can face fees, a remediation plan or the end of its processing relationship.
How does VAMP monitoring work, step by step?
The program runs on data Visa already receives. Nothing is filed by the merchant, and the sequence repeats each month.
- Issuers report transactions that cardholders say were fraudulent, and cardholders raise disputes.
- Visa counts those reports and disputes for each acquirer and for each merchant.
- It compares the count with settled transactions to produce a ratio.
- Acquirers and merchants whose ratio is above the limit Visa has set, and who meet the program’s other criteria, are identified.
- The acquirer is told and works with the merchant on a plan to bring the ratio down.
- If the ratio stays high, the consequences in Visa’s rules and in the acquirer’s own policy apply.
Two things follow from that sequence. The count is built from what issuers and cardholders report, not from your own records, so your figure and Visa’s can differ. And the conversation reaches you through your acquirer or provider, which is why their reporting matters.
How is the VAMP ratio calculated?
In outline, the ratio adds together two counts for card-not-present Visa transactions in a month and divides by the number of settled Visa transactions in the same month:
- Fraud reports filed by issuers when a cardholder reports a transaction as fraudulent.
- Disputes raised by cardholders, whatever the reason.
Because fraud reports and disputes are counted separately, a single fraudulent sale that is also disputed can add to the numerator twice. That is the feature merchants most often overlook.
Check the current rules
Visa defines exactly what is included and excluded, and has refined this since launch. Use this as an outline and ask your provider for the current definition and thresholds.
Who does VAMP apply to?
It applies at two levels. Acquirers are measured across their whole portfolio. Merchants are measured individually, and the program also includes a separate measure aimed at card testing, where criminals run large numbers of small authorization attempts to find working card numbers.
Businesses that sell card-not-present, take payment before delivery or bill on subscription are the most exposed, because that is where both fraud and disputes concentrate.
Who is responsible for what under VAMP?
Four parties have a part in the program. Knowing which one holds the answer saves time when you have a question.
| Party | What it does | What to ask it |
|---|---|---|
| Visa | Sets the program rules, definitions and thresholds | Nothing directly; its rules reach you through your acquirer |
| Acquirer | Is measured across its portfolio and manages the merchants it identifies | The current thresholds and how your account is counted |
| Payments provider | Gives you reporting, alerts and support | Where you can see your own ratio and its trend |
| Merchant | Controls checkout, fulfillment, refunds and customer service | Which of your own practices produce fraud reports and disputes |
For current figures, your acquirer is the source. Visa’s program rules reach merchants through acquirers and processors, and your provider should pass on what applies to you.
What can a merchant monitor?
You cannot see Visa’s own calculation, but you can see most of what goes into it. Track these signals every month, and more often around a launch or a spike in orders.
| Signal | Where to find it | What it tells you |
|---|---|---|
| Fraud reports | Your provider’s risk reporting | How many sales issuers have flagged as fraudulent |
| Disputes | Your dispute or chargeback report | How many cardholders have challenged a charge, and why |
| Settled Visa transactions | Your settlement or batch reports | The base the counts are measured against |
| Declined authorizations | Your gateway or checkout logs | Bursts of small declines that can indicate card testing |
| Alerts and early refunds | Your dispute tool | How many complaints were settled before a dispute was filed |
| Reason codes | Each dispute record | Which cause to fix first |
Keep the figures side by side for several months. A ratio can rise because fraud and disputes went up or because transaction volume went down, and the remedy is different in each case.
How do merchants stay compliant?
- Know your number. Get your fraud and dispute counts and your Visa transaction count every month, and calculate the ratio yourself.
- Stop fraud at the door. Address and security code checks, velocity limits, and stronger authentication on risky orders reduce fraud reports.
- Block card testing. Rate-limit your checkout, add bot protection, and watch for bursts of small declined authorizations.
- Resolve disputes early. Alerts and pre-dispute tools let you refund before a dispute is filed.
- Fix the causes. Unclear descriptors, slow refunds and renewal surprises generate avoidable disputes. See the chargeback management guide.
- Keep volume honest. Low-quality volume added to dilute a ratio tends to raise it.
A worked example: how would a subscription business respond to a rising ratio?
Picture a subscription business that ships a monthly box and bills a stored card. Its provider’s dashboard shows the combined fraud and dispute ratio rising for a third month, though no one has called about it yet.
The owner does not start with the total. She splits it into its parts and finds that fraud reports are steady while disputes have grown. The reason codes on the new disputes point to canceled or unrecognized recurring charges, not stolen cards.
That tells her where to work. She adds a reminder before each renewal, makes cancellation possible from the account page and checks that the statement descriptor matches the brand on the box. She also switches on alerts, so that a complaint that does reach a bank can be refunded before it is filed as a dispute.
Finally she asks her provider two questions: what the current Visa thresholds are for a merchant like hers, and how her account is counted. With the answers she knows how much room she has, and she keeps watching the monthly figure to see whether the changes worked.
Illustrative
This business is hypothetical and no ratio or threshold is implied. Visa sets and revises the program’s definitions and limits, and your acquirer or provider can give you the current ones.
What mistakes should you avoid?
- Waiting for the letter. By the time an acquirer writes to you, the months being measured are already over.
- Relying on your own count alone. Visa’s figure is built from issuer and cardholder reports, so ask your provider how it compares with yours.
- Refunding without fixing the cause. A refund settles the complaint in front of you and leaves the next one in place.
- Treating fraud and disputes as one problem. Stolen cards and unhappy customers need different fixes, so split the ratio before you act.
- Overlooking small declined attempts. A run of low-value declines can be card testing, which the program measures separately.
What happens if you exceed a threshold?
The acquirer is notified and, in turn, contacts the merchant. Expect a request for a remediation plan, closer monitoring and, if the ratio stays high, fees or termination. Outcomes depend on the acquirer’s own policy as well as Visa’s rules.
The practical point is that action starts before the threshold. A provider that shows you the trend gives you months to respond. One that does not gives you a letter.
What should you ask your acquirer or provider about VAMP?
The current rules live with Visa and your acquirer, not in a guide. Put these questions to your provider and keep the answers with your records.
- What are the current thresholds for a merchant like mine, and when were they last changed?
- Which of my transactions are included in the count, and which are left out?
- Where can I see my fraud reports, disputes and ratio, and how often are they updated?
- How are disputes that I resolve through an alert or a refund treated?
- At what point would you contact me, and what would you ask for?
- What fees or conditions would apply if my account were identified?
- Who do I speak to if I see the trend rising?
How does Lumino help with VAMP?
Lumino’s risk and disputes tools include VAMP monitoring and chargeback alerts in the same dashboard as your payments, so the ratio is something you look at, not something you are told about.
For portfolios and platforms, enterprise risk and compliance covers oversight across many merchants. Lumino cannot guarantee that a merchant stays below a threshold; that depends on the merchant’s own transactions.
How Lumino helps
Which Lumino products help you monitor VAMP?
Risk & Disputes
Risk & Disputes tracks dispute and fraud activity against your sales for each merchant account, and notifies you when a dispute is raised or a ratio approaches a level that needs attention.
Reporting & Analytics
Reporting & Analytics shows transactions, batches and disputes for each merchant ID, so the counts behind your ratio sit in one dashboard instead of several exports.
Enterprise risk and compliance
For platforms and operators with several merchant accounts, enterprise risk and compliance covers oversight across many merchants, with ratios tracked per account and viewed together in one place.
About this guide
This guide is general information, not legal, tax or financial advice. Card network rules and state laws change, and they differ by business type. Check the current rules with your processor or counsel before changing how you price or accept payments.
FAQ
Common questions
What does VAMP stand for?
VAMP stands for Visa Acquirer Monitoring Program. It is Visa’s framework for monitoring fraud and dispute levels across acquirers and their merchants.
Who enforces VAMP?
Visa runs the program and applies it to acquirers, and acquirers apply it to their merchants. In practice a merchant hears about VAMP from its acquirer or payments provider, which may set stricter conditions of its own to protect its portfolio. Ask your provider how it monitors your account. See enterprise risk and compliance.
What is the VAMP threshold?
Visa publishes thresholds for acquirers and for merchants and has revised them since the program launched. We do not reproduce figures here because they change; ask your provider for the current ones.
Does VAMP apply to in-person payments?
The program is focused on card-not-present activity, where fraud and disputes concentrate. Confirm with your provider how your own mix of transactions is treated.
Is VAMP the same as a chargeback ratio?
No. A chargeback ratio counts disputes only. VAMP also counts fraud reports, so it is usually higher than a merchant’s chargeback ratio for the same month.
Does VAMP apply to Mastercard and other card brands?
No. VAMP is a Visa program and counts Visa transactions. Other networks run their own monitoring programs with their own definitions and limits, so a merchant can be inside one program’s limits and outside another’s. Track each brand separately and ask your provider which programs apply to you. The chargeback management guide covers dispute handling in general.
Do refunds count toward VAMP?
A refund on its own is not a dispute or a fraud report, so it is not what the program counts. A refund issued before the customer goes to their bank can stop a dispute from being raised at all. How disputes resolved through alerts or pre-dispute tools are treated is defined by Visa, so ask your provider for the current position. See risk and disputes.
What is a remediation plan?
A remediation plan is a written set of actions a merchant agrees with its acquirer to bring fraud and dispute levels back down. It usually names the causes found, the changes to be made and how progress will be reported. What it must contain is set by the acquirer, so ask for its template. See chargeback protection.
Does VAMP affect small businesses?
It can. Whether a low-volume merchant comes into scope is set by Visa’s current criteria, so ask your provider how your account is assessed. A few disputes move a small merchant’s ratio more than a large one’s, which is why small sellers of large-ticket items should watch it closely. See high-ticket payments.
Summarize with
See where your ratio stands.
Ask for a walkthrough of how Lumino tracks fraud and dispute ratios for each merchant account.