Visa · Chargeback reason codes
Visa 10.5 chargeback: Visa Fraud Monitoring Program explained
Checked
Visa reason code 10.5, Visa Fraud Monitoring Program (Visa Monitoring Programs in the current rules), lets an issuer charge back a transaction that Visa flagged through a merchant monitoring program. The bank has 120 days from the date of Visa's monitoring report. It can be filed even after you won an earlier dispute on the same payment, and the only answers are an unaccounted refund or an invalid dispute. Prevention means keeping fraud and dispute rates low.
- Category
- Fraud (monitoring program)
- Time limit for the bank to file
- 120 days from the date of the Visa Monitoring Program report
- Time limit to respond
- Your processor's deadline (on Stripe usually 7–21 days); under Visa rules the acquirer must answer within 30 days of the dispute processing date
- Typical evidence
- Only a refund the issuer ignored, or proof the dispute is invalid
- Can it be prevented?
- Yes: keep fraud and dispute ratios below monitoring thresholds
- Who usually wins
- Almost always the cardholder; Stripe says 10.5 has no recourse to remedy
What PlatformDTC does
PlatformDTC watches the store's dispute rate hourly against Visa's monitoring line and Stripe's intervention line, and its Settings → Automation screen checks that each link keeping it down is working: early fraud warnings arriving and being refunded, refunds landing before the bank files, and disputes answered.
What it means
Visa told the issuer that this transaction was identified by a Visa monitoring program, and the issuer has not won it under another code. It is the one Visa code an issuer may file on a transaction that was already disputed.
Why customers file it
The merchant is in a Visa fraud or dispute monitoring program because its ratios crossed Visa's thresholds.
Evidence that wins
Visa allows only two answers. Cardholder withdrawal does not apply.
- Proof of a refund the issuer did not account for
- Proof the dispute is invalid
How to prevent it
- Track your fraud and dispute ratios monthly
- Use 3-D Secure, AVS and CVV2 on card-absent payments
- Refund early fraud warnings quickly and stop billing reported cards
- Work with your acquirer on a remediation plan if you are notified
For developers
On Stripe the dispute object arrives with reason "fraudulent" and the card network's own code in payment_method_details.card.network_reason_code; listen for charge.dispute.created and read evidence_details.due_by for the deadline.
Stripe lists 10.5 under fraudulent and notes these disputes have no recourse to remedy.
Frequently asked questions
- Can I win a 10.5?
- Rarely. Visa allows only a refund the issuer did not account for or an invalid dispute as answers.
- How do I avoid 10.5 chargebacks?
- Stay out of Visa's monitoring programs by keeping fraud and dispute ratios low with 3-D Secure, card checks, fast refunds of early fraud warnings and clear billing.
Sources
Related
- 10.4 — The cardholder says they did not make an online, phone or mail order purchase.
- 11.2 — The sale was completed even though the authorization was declined.
- 11.3 — No valid authorization was obtained, or the transaction was presented late.
- 12.2 — The transaction was processed with the wrong code, such as a credit processed as a sale.
- 12.3 — The transaction was processed in a different currency than the one shown to the cardholder.
- 12.4 — The charge was posted to a card number that does not match the cardholder's account.
- 12.5 — The cardholder was charged a different amount than they agreed to.