Visa10.5Fraud

Visa Monitoring Programs

Visa itself has flagged the transaction through one of its monitoring programs (formerly named the Visa Fraud Monitoring Program), because the merchant’s fraud levels were too high. It does not start from a cardholder claim, and the merchant has very limited rights to respond.

Why it happens

  • The merchant’s fraud or dispute ratio crossed a Visa monitoring threshold.
  • A wave of fraud, such as card testing, hit the merchant’s checkout.

What to send to fight it

  1. Proof the same transaction was already disputed under another condition and resolved in the merchant’s favor.
  2. Proof a refund or reversal was already processed for the transaction.
  3. Proof the transaction was not among those identified by the program, provided by the acquirer.

How to prevent it

  • Keep fraud low: use 3-D Secure, velocity limits and fraud screening.
  • Block card testing at checkout with rate limits and bot protection.
  • Track your fraud and dispute ratios every month and act before they reach a threshold.

Summaries written by NoChurn from the networks’ public rules and processor documentation. Networks update their rules and deadlines depend on your processor: check its documentation before you respond.

Other Visa codes

← All reason codes
Sources (3)
  1. Visa Core Rules and Visa Product and Service Rules (24 October 2026) · checked 2026-11-09
  2. Visa Dispute Management Guide for Merchants · checked 2026-11-09
  3. Visa, Evolution of Compelling Evidence: FAQs (October 2022) · checked 2026-11-09
PROMPT

Read https://www.nochurn.sh/llms.txt,
then follow https://www.nochurn.sh/docs/quickstart/
to add NoChurn to this app. Use a test key
(nc_test_…) until I say we go live.

Stop leaking revenue.

  • Free until $300 MRR
  • No card needed
  • Live in 10 minutes
  • Never a cut of what we recover