Visa 10.5 - Visa Fraud Monitoring Program (VFMP)
- VFMP was retired on 31 March 2025 and folded into VAMP on 1 April 2025. Nobody is enrolled in it today
- The dispute condition still exists and is still numbered 10.5. Visa retired the program behind it
- If your acquirer says you're in a fraud monitoring program, it's VAMP, and the numbers are different
- Everything below the overview describes the retired program. It's kept for anyone reading an old notice or an old runbook
Visa retired the Fraud Monitoring Program as a program and folded it into VAMP (Visa Acquirer Monitoring Program) on 1 April 2025. Nobody is enrolled in VFMP today, and no VFMP fine has been assessed since then. The name survives only on this dispute condition, which is still numbered 10.5.
If your acquirer has told you that you're in a fraud monitoring program, it's VAMP, and the numbers are different. See Network Programs Reference for what's live: 1.5% merchant excessive, a 1,500 combined fraud-and-dispute floor, and per-dispute fees rather than the monthly assessments below.
Everything on this page below the overview describes the retired program. It's kept for anyone reading an old notice or an old runbook.
Disputes arising from VFMP compliance violations. Issuers could file under this code while the program ran.
Overview
Issuers filed this code against merchants sitting in Visa's Fraud Monitoring Program. The trigger was either a missed program requirement or a fraud transaction out of an enrolled account.
When This Code Applies
- The merchant was enrolled in VFMP
- The transaction was fraudulent and came from that merchant
- The merchant missed a VFMP compliance requirement
- The fraud rate blew past the program thresholds
VFMP Thresholds
Historical. These applied until 31 March 2025 and apply to nobody now. VAMP replaced them with a single combined fraud-and-dispute ratio.
Standard VFMP Thresholds
| Tier | Fraud Basis Points | Fraud Transactions |
|---|---|---|
| Early Warning | 65 bps AND | 75 transactions |
| Standard | 90 bps AND | 100 transactions |
| Excessive | 180 bps AND | 1,000 transactions |
VFMP Timeline
Also historical. VAMP charges per dispute instead: US$8 per CNP dispute at merchant excessive, not a flat monthly assessment.
| Stage | Consequence |
|---|---|
| Month 1-4 | Identification, remediation required |
| Month 5-8 | $25,000/month fines |
| Month 9+ | $75,000/month fines |
| Month 12 | Card acceptance termination possible |
Conditions for Valid Dispute
Issuer Must Verify
- The merchant was enrolled in VFMP at the time
- The transaction itself was fraudulent
- The filing landed inside the program timeframes
Merchant Situation
- You were already under enhanced monitoring
- Your representment options were thin
- Every dispute you filed drew extra scrutiny
Representment Options
Once you were in the program, you didn't have many moves.
1. Transaction Was Authorized
Evidence required:
- Strong authentication proof (3DS with ECI 05)
- Cardholder correspondence
- Device/IP matching prior purchases
2. Fraud Prevention Was Applied
Evidence required:
- Fraud screening records
- 3DS attempt logs
- Declined transaction history showing controls
3. Exit VFMP Status
Getting the fraud rate under the thresholds beat winning cases. Prevention mattered more than representment.
Prevention Strategies (VFMP Exit Focus)
Immediate Actions
- Enable 3DS 2.0 - Get liability shift on all transactions
- Tighten fraud scoring - decline more of the borderline orders
- Review product/pricing - some products attract fraud and have to go
- Velocity limits - cap orders per customer, per card and per IP
Monitoring
- Daily fraud review - Don't wait for monthly reports
- Track basis points - Know your real-time fraud rate
- Dispute categorization - know where your fraud is coming from
Customer Verification
- Enhanced verification - confirm the order by phone or email
- Delivery confirmation - require a signature on every delivery
- New customer friction - make first-time buyers clear a higher bar
Win Rate Expectations
Representment during VFMP was an uphill fight:
| Defense Type | Expected Win Rate |
|---|---|
| 3DS fully authenticated | 70-85% |
| Strong prior relationship | 40-60% |
| Standard evidence | 15-30% |
Reality: spend the effort on prevention, not on representment.
Exiting VFMP
Exit Requirements
- Fraud rate below thresholds for 3 consecutive months
- Evidence that you'd closed the compliance gaps
- Your acquirer confirming you're out
Exit Strategy
- Aggressive fraud blocking - accept fewer of the risky orders
- 3DS on everything - push the liability shift as far as it goes
- Product review - pull the items that keep attracting fraud
- Customer segmentation - whitelist the customers you already trust
Common Mistakes
- Ignoring VFMP enrollment - hope isn't a strategy
- Continuing normal operations - if nothing changes, the fraud rate doesn't either
- Fighting all disputes - Waste of resources during VFMP
- No root cause analysis - you'll be back in the program
Related Codes
- 10.1 - EMV Counterfeit
- 10.2 - EMV Non-Counterfeit
- 10.3 - Other Fraud Card Present
- 10.4 - Card Not Present Fraud
Next Steps
In VFMP program?
- Immediately implement 3D Secure
- Set up dispute alerts to reduce dispute count
- Review fraud rules → Tighten velocity checks
- Follow the Reduce Chargebacks Fast playbook
Get out of VFMP:
- Reduce fraud ratio below thresholds for 3 consecutive months
- Work with processor on remediation plan
- Consider temporarily blocking high-risk transactions