Code10.4TypeFraudFiling window120 daysMonitoringFraud + dispute (VAMP)What does Visa 10.4 mean?
The cardholder told their bank they didn't make or approve a card-not-present charge. That covers real fraud with stolen card details, and it covers a real customer who looked at a statement line, didn't recognize it, and picked “I don't recognize this charge.”
Because it is coded as fraud, 10.4 does double damage: the issuer files a fraud report on the transaction, and the dispute follows. Both sides of your VAMP ratio feel it.
What causes a 10.4 chargeback?
- Stolen card details used at your checkout - true fraud.
- A rebill weeks after signup, under a statement name the customer didn't connect to you.
- A family member who used the card, with the cardholder disputing honestly.
- A customer who regretted the purchase and found the fraud button easier than the refund email.
Why do subscription businesses get 10.4?
For a subscription business, most 10.4 disputes start as recognition failures, not theft. The customer signed up under your brand name, then months later a statement line shows a name they don't recognize, and the bank's app offers a one-tap fraud claim.
That is why the cheapest 10.4 prevention is a statement line that matches your checkout brand. The disputes caused by confusion are the only ones you can delete entirely.
Can a chargeback alert stop 10.4?
Alerts stop the chargeback, but the fraud report still counts.
When the cardholder calls their bank, RDR and CDRN catch the dispute and you can refund before it becomes a chargeback, which keeps it out of the VAMP dispute count. But a 10.4 claim also generates a fraud report, and that report counts on VAMP's fraud side whether or not the alert saved the dispute. Alerts contain the damage. Only fixing recognition and screening stops it.
Alerts are one of the two levers here. See how RDR, CDRN and Ethoca work together, and check where your ratio stands before the letter checks it for you.
How do you respond to a 10.4 dispute?
You win 10.4 by proving the cardholder authorized the charge or participated in the purchase. This is also the one code where Visa's Compelling Evidence 3.0 applies. Send:
- AVS and CVV match results from the authorization.
- The device fingerprint, IP address, and account login used for the purchase.
- Usage records: the customer accessed the product after the charge they claim is fraud.
- Under Compelling Evidence 3.0: two prior undisputed transactions, 120 to 365 days old, matching the disputed one on data points like device ID and IP address. Qualifying evidence shifts liability back to the issuer.
- 3D Secure authentication data, if the charge was authenticated - authenticated fraud claims are generally the issuer's liability, not yours.
Your processor sets your response deadline, usually 20 to 30 days from the chargeback.
How do you prevent 10.4?
- Fix the statement line first. A recognizable descriptor deletes the confusion disputes, which are most of a subscription business's 10.4 volume.
- Send a renewal reminder before each rebill, so the charge is expected before it appears.
- Use 3D Secure on risky or high-value charges. Authenticated transactions shift fraud liability to the issuer.
- Keep AVS and CVV checks on, and hold obviously mismatched orders for review.
The cardholder gets 120 days to file. You usually get 20 to 30 days to respond. And the dispute counts the day it files, win or lose, which is why prevention beats response.
FAQ
Is reason code 10.4 always real fraud?
No. It covers true fraud with stolen card details, but for subscription businesses a large share of 10.4 disputes are real customers who didn't recognize a rebill on their statement and chose the fraud option. The bank cannot tell the difference. Your descriptor and evidence can.
What is Compelling Evidence 3.0?
A Visa rule for fighting 10.4 friendly fraud. If you can show two prior undisputed transactions from the same cardholder, 120 to 365 days old, matching the disputed charge on data points like device ID and IP address, liability shifts back to the issuer. It applies only to 10.4.
Does 3D Secure protect me from 10.4?
Largely, yes. When a charge is authenticated with 3D Secure, fraud liability generally shifts to the issuer, so a 10.4 claim on that charge is the bank's problem rather than yours. The trade-off is checkout friction, which is why many merchants reserve it for risky charges.
Do alerts stop 10.4 from counting in VAMP?
Partly. An alert lets you refund before the dispute becomes a chargeback, which keeps it out of the VAMP dispute count. But a 10.4 claim also files a fraud report, and fraud reports count on VAMP's fraud side regardless. Alerts contain 10.4. Descriptors and screening prevent it.
Checked against Visa's Dispute Management Guidelines (June 2024) and Visa's Compelling Evidence 3.0 rules. Last reviewed August 28, 2026.
