Skip to content
NoChargeback

Visa reason code 10.5 and the Visa fraud monitoring program

Visa reason code 10.5 (Visa Fraud Monitoring Program) means Visa identified your merchant account in its fraud monitoring program and the issuer is charging back a fraudulent transaction on that basis. Unlike most fraud codes, 10.5 is generally not contestable through representment. The real work is checking that the code was applied correctly and bringing your fraud level down.

Draft my evidence See pricing

Read and dispute permissions only. We never move your money.

What Visa reason code 10.5 means

Visa monitors merchants whose fraud levels exceed its thresholds. Once a merchant is identified and has passed the early stages of the program without fixing the problem, issuers can file 10.5 for fraud reported on that merchant's transactions, without the cardholder needing to claim anything further. Visa has been consolidating its fraud and dispute monitoring programs into the Visa Acquirer Monitoring Program (VAMP), and the exact rules for 10.5 depend on your region and your acquirer.

Typical triggers for a 10.5 chargeback

  • Card testing attacks that push many small fraudulent authorizations through your checkout.
  • A wave of stolen card orders on high resale goods such as electronics, gift cards or tickets.
  • Weak or disabled fraud screening after a checkout or platform change.
  • Fraud reports (TC40 data) piling up even when cardholders never file a chargeback.

Time limits for Visa 10.5

Issuers can file 10.5 for transactions in the period when your account is identified in the program. Your processor still sets a response window, often between 7 and 21 days, and you should use it to check the code. Program timelines and fees are set by Visa and your acquirer.

What to check before you accept a 10.5 dispute

Representment is generally not available for 10.5. You can still challenge a dispute that does not meet the conditions of the code.

  • Whether the transaction date falls inside the period in which Visa identified your account.
  • Whether the same transaction was already disputed under another reason code.
  • Whether you issued a refund or credit before the dispute was filed.
  • Whether the transaction was a Visa transaction processed on the identified merchant account at all.

If none of these apply, accepting the dispute and spending the time on prevention is usually the better use of resources.

What to avoid when you respond

  • Do not send a long letter with 3D Secure and delivery proof for a valid 10.5. The code does not depend on that evidence.
  • Do not ignore program notices from your acquirer. Fees and higher reserves follow quickly.

How to prevent Visa 10.5 chargebacks

  • Track your fraud and dispute ratio daily with a chargeback ratio monitor, alerting well before Visa thresholds.
  • Turn on 3D Secure for risky orders to shift fraud liability where it applies.
  • Stop card testing with rate limits, CAPTCHA on checkout and blocks on repeated declines from one device or IP.
  • Refund orders flagged by early fraud warnings before they become chargebacks.
  • Use Ethoca alerts and Visa RDR to resolve fraud claims before they count against you.

How 10.5 appears in Stripe

Stripe shows 10.5 disputes with the reason fraudulent, and the network reason code field on the dispute carries 10.5. NoChargeback flags the code as monitoring program related, checks dates and duplicates against your other disputes, and shows your ratio against Visa thresholds with alerts at 70 and 90 percent. See Stripe chargeback protection.

Rebuttal letter opening for Visa 10.5

We are responding to the dispute filed under Visa reason code 10.5. This transaction does not qualify under the fraud monitoring program: a full refund was issued to the cardholder before the dispute was filed, as shown in the attached refund record.

Draft my evidence

Can a merchant fight a Visa 10.5 chargeback?

Generally not on the merits. You can challenge it only when the code was applied wrongly, for example the transaction falls outside the program period, was already disputed or was refunded first.

How does a merchant get into the Visa fraud monitoring program?

By exceeding Visa fraud thresholds measured on reported fraud. Card testing and stolen card orders are the usual causes.

How do I leave the Visa fraud monitoring program?

Bring your fraud level below the threshold and keep it there for the period your acquirer and Visa require, using authentication, screening and early refunds.