Visa Reason Code 10.5: Visa Fraud Monitoring Program

What Visa reason code 10.5 means

Reason code 10.5 is unusual. Most chargebacks are triggered by a cardholder’s complaint about a specific transaction. A 10.5 is triggered by Visa’s own fraud monitoring: the issuer may raise it when Visa has notified the issuer that the transaction was identified by Visa’s fraud monitoring program, and the issuer hasn’t already successfully disputed the same transaction under another code.

In practice, that means the merchant’s overall fraud performance drew Visa’s attention, and fraud-reported transactions became chargeable for that reason alone. The evidence that would normally win a fraud claim, such as delivery proof or customer history, generally doesn’t apply.

10.5 is an allocation code, like the rest of category 10.

Program change: Visa replaced its separate fraud monitoring program (VFMP) and dispute monitoring program (VDMP) with the Visa Acquirer Monitoring Program (VAMP), effective April 1, 2025. The 10.5 code still appears on Visa’s code list and on processor notices. How identification under VAMP translates into 10.5 dispute rights is set by Visa’s current rules, so confirm the details with your acquirer. Our VAMP guide covers the program itself.

Common causes

• A fraud ratio high enough to put the merchant in Visa’s monitoring program
• Card-testing attacks that push a burst of fraud reports onto your merchant account
• Weak checkout screening in high-risk verticals
• A sudden spike in stolen-card orders, such as after a promotion goes viral on fraud forums

Evidence that wins a 10.5 dispute

The remedies are narrow. Ask your processor what it will accept before preparing a response.

1. Proof of a prior credit: the refund or reversal record, with amount, date and reference number, showing you credited the transaction before the dispute was raised.
2. Proof the transaction falls outside the program’s scope, if your acquirer confirms the issuer’s claim of identification is wrong.
3. Accurate transaction records matching the dispute: amount, date, card and order ID.

Compelling evidence of cardholder participation, including the prior-transaction approach Visa allows under CE 3.0 for 10.4, is not the remedy for a 10.5.

How to prevent 10.5 chargebacks

Prevention here means preventing fraud, because the code exists only for merchants whose fraud levels triggered monitoring.

• Watch your fraud-to-sales ratio monthly, not just your dispute count. See what a good chargeback ratio is.
• Block card testing with rate limits, CAPTCHA on checkout and velocity rules.
• Use 3-D Secure on risky orders and AVS/CVV checks on all of them.
• Refund suspicious orders before they ship, and before they turn into fraud reports.
• If your acquirer warns you about VAMP standing, treat it as urgent.

Should you fight or accept?

Accept in almost every case. Unless you can show a prior refund, there is usually no evidence that changes the outcome, and each failed response adds cost.

Fight only when you have proof you already credited the cardholder, or your acquirer confirms the dispute was raised in error. Then put your energy into the fraud controls that get you out of monitoring.