The Visa Fraud Monitoring Program (VFMP) was retired on March 31, 2025 and replaced by VAMP — the Visa Acquirer Monitoring Program. VAMP consolidates fraud and non-fraud disputes into a single unified ratio with a 1.5% dispute ratio threshold. Confirm your current monitoring status directly with your acquirer.
What Visa Reason Code 10.5 Means
Visa reason code 10.5 is historically titled Visa Fraud Monitoring Program (VFMP), but as of April 2025 it is associated with VAMP — the Visa Acquirer Monitoring Program, which replaced both VFMP and VDMP. Unlike most chargeback codes that represent individual cardholder disputes, 10.5 is a compliance program code. It signals that Visa has placed your merchant account into its compliance monitoring program due to excessive fraud or dispute ratios.
Under VAMP, issuers are permitted to file chargebacks on fraudulent transactions using this code with reduced documentation requirements. This means you receive more chargebacks, faster, with less evidence attached — a deliberate mechanism to increase financial pressure on merchants with elevated fraud or dispute rates.
Receiving a 10.5 chargeback is a symptom of a larger problem. Fighting individual 10.5 disputes without simultaneously reducing your overall fraud rate will not resolve your VAMP enrollment and will not stop the chargebacks from continuing. Contact your acquirer immediately upon receiving any 10.5 dispute to understand your VAMP status and remediation requirements.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Visa | 10.5 | Visa Fraud Monitoring Program | This page |
| Mastercard | GMAP | Global Merchant Audit Program | MC's equivalent compliance program; different thresholds |
| Amex | N/A | Amex Fraud Monitoring | Amex handles compliance internally without a specific chargeback code |
| Discover | N/A | Discover Fraud Monitoring | Similar internal program; disputes use standard codes |
Common Trigger Scenarios
- Dispute rate exceeds VAMP threshold. Your combined fraud and non-fraud dispute ratio surpassed 1.5% for a monitoring period, prompting VAMP enrollment through your acquirer.
- Compromised card data from your environment. A data breach or skimming incident at your locations has resulted in many fraudulent transactions being traced back to your merchant ID, driving your fraud ratio up sharply over a short period.
- High-risk product categories with endemic fraud. Merchants selling gift cards, gaming credits, digital goods, or high-value electronics see elevated baseline fraud rates. Without strong fraud prevention controls, VAMP enrollment is a recurring risk.
- Fraudulent orders slipping through weak fraud screening. Inadequate velocity checks, no address verification, or disabled 3DS authentication allows bad actors to transact freely until the combined dispute ratio climbs high enough to trigger VAMP enrollment.
- New merchant account with rapid fraud spikes. New MIDs sometimes attract fraudsters testing cards. An early fraud spike before prevention controls are calibrated can trigger VAMP during the account's first months of operation.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From transaction processing date |
| Merchant Response Window | 30 days | Per individual dispute; processor deadline may be shorter |
| VAMP Remediation Period | 12 months | After enrollment; must achieve compliant ratios to exit |
| Fine Escalation | Month 4+ | Visa begins issuing fines if ratios remain non-compliant after initial remediation period |
Evidence You Will Need
For individual 10.5 chargeback representments, the evidence strategy depends on the specific transaction. For the program itself, you need a documented remediation plan.
- Authorization data showing the transaction was approved and completed legitimately — AVS results, CVV match, 3DS authentication if applicable
- Fraud screening records showing the transaction passed your fraud tools (velocity checks, device fingerprinting, fraud score) at time of processing
- Delivery or fulfillment confirmation for the specific disputed transaction, to the extent applicable
- Cardholder communication records if any post-transaction contact occurred that implies cardholder knowledge of or participation in the purchase
- Remediation plan documentation for your acquirer showing the steps you are taking to reduce fraud rates — this is essential for VAMP compliance discussions even though it does not affect individual dispute outcomes
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the specific evidence requirements for VAMP-related chargebacks, how to structure your representment when 3DS authentication was used, and the remediation documentation your acquirer needs to see.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- Treating 10.5 like any other fraud chargeback. Standard representment arguments that work for 10.4 disputes often fail for 10.5 because the VAMP context affects reviewer bias. Arguing individual transactions without acknowledging or addressing the program context leaves important persuasion on the table.
- Ignoring the VAMP enrollment while fighting individual disputes. You can win every representment and still lose your merchant account. The program-level problem must be resolved through fraud and dispute rate reduction, not just dispute responses.
- Weak or absent fraud prevention controls. If your fraud screening consists of basic AVS checks with no velocity limits, device fingerprinting, or 3DS, you will continue generating fraudulent transactions faster than you can dispute the resulting chargebacks.
- Delay in contacting your acquirer. Your acquirer is your first line of support for VAMP issues. Merchants who engage their acquirer proactively with a remediation plan fare significantly better than those who do nothing until fines arrive.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide includes VAMP-specific representment strategies, the remediation plan format acquirers want to see, and the fastest paths to exiting the monitoring program.
Get the step-by-step winning strategy →Response Framework Overview
- Confirm legitimacy of the specific transaction. Start with authorization data, fraud screening results, and any delivery confirmation for the individual disputed transaction.
- Demonstrate fraud prevention controls were active. Show that your fraud tools evaluated this transaction and returned an acceptable risk score before authorization.
- Reference 3DS or additional authentication if used. If the transaction was authenticated through 3DS2, this shifts liability to the issuer and is your strongest individual defense.
- Note any cardholder interaction. Post-purchase contact, order confirmation delivery, or account login activity can support the transaction's legitimacy.
- Separately address program-level remediation. Provide your acquirer with a fraud mitigation plan even if not formally requested — it signals good faith and can influence program escalation decisions.
Prevention Tips
- Implement 3DS2 authentication for card-not-present transactions. 3DS-authenticated transactions shift fraud liability to the issuer. If your fraud rate is primarily CNP fraud, 3DS adoption is the single highest-impact change you can make.
- Deploy multi-layered fraud screening. Layer velocity checks, device fingerprinting, IP reputation scoring, and machine learning fraud scores. Single-factor fraud screening is insufficient for any merchant above minimal transaction volumes.
- Monitor your dispute ratio monthly before Visa does. Set up internal reporting to track your combined fraud-and-dispute ratio each month. Catching a rising ratio early gives you time to act before VAMP enrollment.
- Establish a clear escalation path with your acquirer. Your acquirer should be a partner in dispute monitoring. Regular check-ins, especially if your dispute rate trends upward, allow for early intervention before Visa-level enforcement.
Frequently Asked Questions
What triggers enrollment in the Visa Fraud Monitoring Program?
VFMP was retired on March 31, 2025 and replaced by VAMP — the Visa Acquirer Monitoring Program. VAMP consolidates fraud and non-fraud disputes into a single ratio with a 1.5% threshold. Merchants previously enrolled in VFMP transitioned into VAMP monitoring through their acquirer.
Can I dispute individual 10.5 chargebacks?
Yes, each 10.5 chargeback is an individual dispute that can be represented. However, fighting individual chargebacks without addressing the underlying fraud rate will not resolve your VAMP enrollment. The chargebacks are a symptom; the elevated ratio is the disease. You need to address both simultaneously.
How long does VFMP enrollment last?
VAMP uses a 1.5% dispute ratio threshold. This unified metric combines both fraud and non-fraud disputes. Exceeding 1.5% triggers a structured escalation path: penalty fees, increased reserve requirements, higher processing rates, and potentially account termination for persistent violators.
Do 10.5 chargebacks count against my chargeback ratio separately?
Under VAMP, all disputes - including those carrying reason code 10.5 - count toward your unified VAMP ratio. VAMP combines fraud and non-fraud dispute volumes into one metric. Outcomes are irrelevant: a dispute you win counts the same as one you lose.