Visa Reason Code 10.4 (Fraud, Card-Absent): How to Win It

If you sell online, Visa reason code 10.4 is the chargeback you will see more than any other. It is Visa’s card-absent fraud code, and despite the alarming name, most 10.4 disputes are not criminal fraud at all — they are friendly fraud, and they are winnable.

This guide explains what 10.4 means, why it dominates ecommerce chargebacks, the exact evidence that wins it (including Compelling Evidence 3.0), the time limits, and how to decide whether to fight or accept.

What Visa reason code 10.4 means

Visa reason code 10.4, Fraud — Card-Absent Environment, applies when a cardholder claims they did not authorize a transaction made without the physical card present. That covers virtually all ecommerce: online orders, phone orders, and any card-not-present sale.

The claim behind the code is simple: “I did not make this purchase.” Sometimes that is literally true — a stolen card number used online. But far more often, the cardholder did make the purchase and is disputing it anyway, whether because they forgot it, did not recognize the descriptor, a family member used the card, or they are trying to get something for free. That last category is friendly fraud, and industry data shows it drives well over half of all chargebacks and is the fastest-growing type.

10.4 sits in Visa’s fraud category (category 10). For how it fits alongside every other Visa code, see the Visa chargeback reason codes guide.

Why 10.4 is the #1 ecommerce fraud code

Two things make 10.4 the most common dispute online merchants face:

1. It is the default bucket for disputed card-not-present transactions. When a cardholder tells their bank they do not recognize or did not authorize an online charge, 10.4 is the natural fit.
2. It absorbs friendly fraud. A customer who wants their money back but cannot honestly claim the item was defective or undelivered can claim they never authorized the charge. That routes straight to 10.4.

The upshot: a large share of your 10.4 disputes involve customers who genuinely made the purchase. That is exactly why 10.4 is so winnable — if you can prove the real cardholder transacted, the fraud claim collapses.

The evidence that wins a 10.4 dispute

Winning 10.4 comes down to one thing: proving the genuine cardholder made and benefited from the purchase. Here is the evidence, roughly in order of power.

1. Prior undisputed transaction history (CE 3.0) — the strongest

Visa’s Compelling Evidence 3.0 (CE 3.0) is purpose-built for 10.4, and it is the most powerful tool you have. It lets you defeat the fraud claim by showing a history of prior undisputed transactions from the same cardholder that share identifiers with the disputed one.

Qualifying data points include:

• IP address
• Device ID or fingerprint
• Account login / customer ID
• Shipping or delivery address

The core idea: if this same customer previously made purchases from the same device, IP, or delivery address — and never disputed them — that is compelling evidence the disputed transaction is also legitimate. When your evidence meets Visa’s CE 3.0 criteria (typically two or more prior transactions sharing qualifying data points, made a set number of days before the disputed one), liability shifts back to the issuer. This has turned many previously unwinnable friendly-fraud disputes into wins.

The catch is that you need this historical data captured, linked to the customer, and retrievable the moment a dispute arrives. If you cannot connect the disputed order to the customer’s prior activity, you cannot invoke CE 3.0.

2. AVS and CVV match

If the Address Verification Service (AVS) matched and the CVV was correct at checkout, submit it. A full AVS/CVV match is strong evidence the person had the physical card and knew the billing address — hard to reconcile with a “someone stole my number” claim.

3. IP address and device data

An IP address that geolocates to the cardholder’s known location, or a device previously used on their account, directly ties the transaction to the genuine customer.

4. Delivery confirmation to the cardholder’s address

Carrier tracking showing the item was delivered to the cardholder’s verified address — ideally with signature confirmation — is powerful. Someone committing true fraud rarely ships to the real cardholder’s home.

5. Customer communications and account activity

Emails, login records, account creation tied to the cardholder, and any post-purchase interaction (support requests, reviews, repeat logins) all reinforce that the real customer was engaged with the order.

For the general framework behind assembling and presenting this, see how to win a chargeback dispute.

Time limits for 10.4

Two clocks apply:

• Cardholder filing window: generally 120 days from the transaction date for a 10.4 fraud claim.
• Merchant response window: roughly 20 to 30 days at the network level, but your processor’s internal deadline is shorter and is the one that governs your case. Submit well before it — a missed deadline forfeits the dispute automatically, no matter how strong your CE 3.0 evidence is.

Fight or accept? A quick decision guide

Not every 10.4 is worth fighting, but most are. Use the signals in the transaction to decide.

When several genuine-fraud signals stack up (mismatched AVS, brand-new customer, delivery to an unrelated address, foreign IP), the transaction may in fact be criminal fraud, and accepting avoids throwing good time after a loss. But when the signals point to friendly fraud — which is the majority of 10.4s — fight, because the evidence to win almost certainly exists in your own records.

The bottom line

Visa 10.4 is the ecommerce merchant’s most common chargeback, and its scary “fraud” label hides the fact that most instances are winnable friendly fraud. The path to winning is clear: prove the genuine cardholder transacted, leaning first on prior undisputed transaction history under CE 3.0, backed by AVS/CVV, IP and device data, and delivery confirmation.

The hard part is having all of that captured, linked to the customer, and ready the instant a 10.4 lands — especially the prior-transaction history CE 3.0 depends on. DisputeDash detects each 10.4 the moment Visa reports it, automatically assembles the CE 3.0 history and supporting evidence, builds the rebuttal, and submits before the deadline — so you win the disputes you deserve to win without racing the clock.