What Visa reason code 10.4 means
The issuer files 10.4 when a cardholder reports a card not present transaction as unauthorized. The card was not physically used, so Visa looks at whether the merchant authenticated the buyer and whether the purchase matches the cardholder's history. Some are true fraud from stolen card data, many are friendly fraud by the cardholder or a family member.
Typical triggers for a 10.4 chargeback
-
Stolen card details used on your checkout without 3D Secure.
-
A family member or employee used a saved card without telling the cardholder.
-
The cardholder does not recognize your statement descriptor and assumes fraud.
-
A subscription renewal the cardholder forgot about, reported as unauthorized instead of canceled.
-
Account takeover, where someone logged in to a real customer's account and placed an order.
Time limits for Visa 10.4
The cardholder typically has 120 days from the transaction date to dispute. Your response window is much shorter and is set by your processor, often between 7 and 21 days. In Stripe the exact deadline appears as the evidence due date on the dispute. Missing it means the dispute is lost automatically, whatever evidence you hold.
Evidence that wins a 10.4 dispute
-
Proof of 3D Secure authentication for the transaction, which in many cases shifts fraud liability to the issuer.
-
AVS and CVV match results from the authorization.
-
The customer IP address, device and location, and how they match previous orders.
-
Login history showing the account was used after the purchase.
-
Delivery confirmation to the cardholder's billing address, or download and usage logs for digital goods.
-
Compelling Evidence 3.0 data, at least two prior undisputed transactions 120 to 365 days old with matching IP or device plus another identifier.
-
Customer emails or support conversations that confirm the order.
What to avoid when you respond
-
Do not send a generic letter that only says the order was legitimate. Issuers need data, not opinions.
-
Do not refund after the dispute is opened, because the money is already pulled and you can lose twice.
-
Do not miss the deadline while you wait for one more document.
How to prevent Visa 10.4 chargebacks
-
Turn on 3D Secure for risky orders, or for all orders if your dispute rate is climbing.
-
Use a clear statement descriptor with your brand name and a support contact.
-
Send renewal reminders before subscription charges.
-
Watch early fraud warnings and consider refunding when a refund costs less than the expected chargeback.
How 10.4 appears in Stripe
Stripe shows Visa 10.4 disputes with the reason fraudulent, and the network reason code field on the dispute carries 10.4. NoChargeback reads both, pulls 3D Secure, AVS, CVV, IP and customer history from the charge, and fills the matching Stripe evidence fields for you. Read more on Stripe chargeback protection and Compelling Evidence 3.0.
Rebuttal letter opening for Visa 10.4
We are responding to the dispute filed under Visa reason code 10.4. The transaction was authorized by the cardholder: it passed 3D Secure authentication, the AVS and CVV checks matched, and the purchase was made from an IP address and device used in earlier undisputed orders on the same account. The evidence below confirms the cardholder received and used the purchase.
Can a merchant win a Visa 10.4 chargeback?
Yes. Merchants win 10.4 disputes when they show authentication, matching customer data and proof that the cardholder received or used the purchase. Compelling Evidence 3.0 data and 3D Secure results are the strongest proof.
Does 3D Secure protect me from 10.4 chargebacks?
In many cases a successfully authenticated 3D Secure transaction moves fraud liability to the issuer, so the dispute is either blocked or easier to win. Check your processor's rules for exemptions.
Should I refund a 10.4 dispute?
Not after the dispute is filed, because the funds are already withdrawn. Refunding before a dispute, when an early fraud warning arrives, can be cheaper than the chargeback fee and keeps the dispute out of your ratio.