Visa 10.5: Visa monitoring programme (your business is enrolled in a VFMP)
The network's own name for this condition: Visa Monitoring Programs
What the cardholder is actually claiming
The transaction was flagged because your business was enrolled in a VFMP monitoring programme, which allows the issuer to dispute transactions under the programme's rules.
The response window, and the arithmetic
- Network window
- 30 calendar days
- Counted from
- the dispute date on your notice
- Last day to respond
- dispute date + 30 days
- Worked example
- notice dated 22 November 2026 → respond by 22 December 2026
Visa gives the merchant 30 days to respond at each dispute phase. Your payment processor usually sets an earlier cut-off. Visa's October 2026 Core Rules retitled 10.5 from "Visa Fraud Monitoring Program" to "Visa Monitoring Programs", so older notices may use the previous name.
These are calendar days, not business days: a weekend or public holiday inside the window still counts towards it. Because the network window is the outer limit and your processor usually sets an earlier cut-off, treat the earlier of the two dates on your paperwork as your real deadline.
The builder dates this for you from the dispute date you enter — open it with Visa 10.5 selected.
The evidence checklist (4 items)
Each item carries the weight the published evidence list gives it for this code, and where to get it from your own systems.
- 01
Record that this transaction was already disputed and accepted
Decisive · answers the claim directlyVisa allows a response to a 10.5 only where the issuer has already disputed the transaction and you have already accepted that dispute — in other words, a duplicate.
Where to get it: Find the earlier case number and the accepted response in your processor's dispute list, and export both.
- 02
Proof you already credited the cardholder for this transaction
Decisive · answers the claim directlyThe other route Visa allows: you have already issued a credit offsetting the transaction being disputed.
Where to get it: Export the credit confirmation with date, amount and reference number from your processor.
- 03
Acquirer enrolment records for the monitoring programme
Strong · strongly supports the answerShows which monitoring programme applies and from what date, which is what the case is really about.
Where to get it: Ask your acquirer for the programme notice and the enrolment record for your merchant ID.
- 04
Documented fraud-prevention controls (3-D Secure, velocity checks)
Strong · strongly supports the answerVisa's own evidence list for 10.5 asks for documented fraud-prevention controls alongside the enrolment records.
Where to get it: Export the 3-D Secure settings and velocity rules from your payment stack as a dated screenshot.
What tends to decide these cases
The published evidence list for Visa 10.5 marks 2 items as decisive — the ones that answer the claim itself rather than supporting it:
- Record that this transaction was already disputed and accepted
Visa allows a response to a 10.5 only where the issuer has already disputed the transaction and you have already accepted that dispute — in other words, a duplicate.
- Proof you already credited the cardholder for this transaction
The other route Visa allows: you have already issued a credit offsetting the transaction being disputed.
Below those, Acquirer enrolment records for the monitoring programme, Documented fraud-prevention controls (3-D Secure, velocity checks) are strong supporting items — worth attaching, but not a substitute for the decisive ones.
The claim here is specific: The transaction was flagged because your business was enrolled in a VFMP monitoring programme, which allows the issuer to dispute transactions under the programme's rules. So the question being decided is whether that is true, not whether the customer is unhappy. Evidence that speaks to the claim carries the case; a general account of good service does not.
Rebut does not publish win rates and does not predict an outcome. What it does is tell you, from the checklist you can actually fill, how thin or complete your file is.
Questions merchants ask about Visa 10.5
- What does Visa 10.5 mean?
- Visa calls this condition "Visa Monitoring Programs". The transaction was flagged because your business was enrolled in a VFMP monitoring programme, which allows the issuer to dispute transactions under the programme's rules.
- How long do I have to respond to a Visa 10.5 chargeback?
- Visa gives the merchant 30 days to respond at each dispute phase. Your payment processor usually sets an earlier cut-off. Visa's October 2026 Core Rules retitled 10.5 from "Visa Fraud Monitoring Program" to "Visa Monitoring Programs", so older notices may use the previous name.
- What evidence do I need to answer Visa 10.5?
- The published evidence list for Visa 10.5 has 4 items. The 2 that answer the claim directly: Record that this transaction was already disputed and accepted; Proof you already credited the cardholder for this transaction. Everything else supports that answer rather than replacing it. Each item on the page says where to get it from your own systems.
- Does Rebut guarantee the outcome of a Visa 10.5 dispute?
- No. Rebut does not publish win rates and does not predict an outcome. It checks the file you actually hold against the published evidence list for this code, shows which decisive items are missing, and writes the rebuttal letter for you to submit.
Sources
The evidence list above was last reviewed on 8 November 2026; the response window is the merchant window the network publishes. Where a network keeps its full rulebook behind a merchant login, the network's own public page is cited rather than a third-party summary. Networks revise their rules, so confirm both against the notice from your processor before you submit.
Build the rebuttal for this code
Opens the builder with Visa 10.5 already selected. Enter the dispute date and order value, tick the evidence you hold, and you get the dated deadline, the ranked gaps and a filled-in letter. No account, no email.
Open the builder with Visa 10.5 selectedRelated Visa codes
- 10.4Fraud — card not present (customer says they never bought it)
- 12.5Incorrect amount (customer says they were charged a different figure)
- 12.6.1Duplicate processing (customer says they were charged twice)
- 13.1Goods or services not received (customer says nothing arrived)
