What is Compelling Evidence 3.0 and does it work against 10.4?

CE3.0 is a Visa framework that lets merchants defeat a 10.4 dispute by proving an established relationship with the cardholder. You need two undisputed transactions on the same card that are between 120 and 365 days old and share at least two data elements with the disputed order, one of which must be device ID or IP address. When the criteria are met, liability moves back to the issuer, and qualifying disputes can even be blocked pre-chargeback through Order Insight.

Does 3-D Secure stop 10.4 chargebacks?

A fully authenticated 3DS transaction generally shifts fraud liability to the issuer, so a 10.4 filed against it is invalid and should be reversed on representment. It does not stop non-fraud disputes, and attempted or data-only flows may not carry the same protection. It also does nothing for the TC40 fraud report if the issuer still records one, so 3DS is a liability tool more than a reputation tool.

Most of my 10.4 disputes are friendly fraud. Is it worth fighting them?

Yes, and 10.4 is the code where fighting pays best. Friendly fraud collapses when you show delivery to the cardholder's verified address, usage of the product after purchase, or a CE3.0 transaction history. Wins also feed back into issuer behavior over time, since Visa tracks merchant representment outcomes. Just remember that winning the reversal does not remove the transaction from fraud-ratio calculations, so prevention still matters more than recovery.

Visa · Fraud

Reason code 10.4: Other Fraud - Card-Absent Environment

The cardholder claims they did not authorize a card-not-present transaction, making this the standard fraud chargeback for ecommerce, mail order, and telephone order sales. It covers both true third-party fraud, where stolen card credentials were used, and friendly fraud, where the actual cardholder disputes a purchase they made. For online merchants, 10.4 is usually the single highest-volume fraud code.

Issuer filing window

120 days from the transaction processing date

Merchant response window

typically 20-30 days to respond, depending on the acquirer

Why 10.4 chargebacks happen

Stolen card credentials from a data breach or phishing attack were used to place an order on your site.
The cardholder made the purchase but failed to connect the descriptor on their statement to your brand.
A family member, often a child, placed the order on the account holder's card without them knowing.
The customer experienced buyer's remorse and found that claiming fraud was faster than requesting a refund.
Bots validating stolen card numbers pushed small authorizations through your checkout and some settled before you caught them.

How to fight a 10.4 chargeback

Build a Compelling Evidence 3.0 case if you can: two prior undisputed transactions on the same card, between 120 days and 365 days old, sharing at least two matching data elements with the disputed transaction such as device ID, IP address, shipping address, or customer account login.
Check whether the transaction was fully authenticated with 3-D Secure; a successful 3DS authentication generally shifts fraud liability to the issuer and invalidates the dispute.
Submit AVS and CVV2 match results together with carrier confirmation of delivery to the billing address you verified.
Provide evidence of post-purchase engagement, such as digital product logins, subscription usage, app activity, or support conversations from the cardholder after the sale date.
Include the device fingerprint, IP geolocation, and email history showing consistency with the cardholder's known profile.
Respond inside the pre-dispute window through Order Insight or Verifi CDRN where available, since deflecting the case before it becomes a chargeback keeps it off your dispute ratio.

How to prevent 10.4 chargebacks

Enable 3-D Secure on higher-risk segments of your traffic to move fraud liability to issuers, balancing the friction against conversion.
Run layered fraud screening: AVS, CVV2, velocity limits, device fingerprinting, and BIN-country versus IP-country checks.
Use a billing descriptor that clearly names your brand and includes a customer service phone number.
Deploy rate limiting and CAPTCHA on checkout to shut down card-testing runs before they settle.
Enroll in Verifi Order Insight so issuers can show cardholders your order details at the moment they call to dispute.
Send an order confirmation and a shipping notification from a recognizable sender so the purchase stays fresh in the customer's memory.

High-risk merchant angle

This is the code that pushes high-risk merchants over Visa's monitoring thresholds, because every 10.4 arrives with a TC40 fraud report behind it, and under VAMP (the Visa Acquirer Monitoring Program that replaced VFMP and VDMP in April 2025) those TC40s are combined with non-fraud disputes into a single ratio against settled card-not-present transactions. Cross the excessive line, 1.5% in most regions as of April 2026 with a 1,500 combined monthly count floor, and enforcement fees begin, issuers can gain the 10.5 dispute right, and your acquirer starts asking hard questions, so managing 10.4 volume is direct MID-preservation work. For merchants running multiple MIDs with load balancing, watch per-MID ratios rather than the blended number; one hot MID can breach while the portfolio average looks fine. CE3.0 is especially valuable for subscription and repeat-purchase models because the prior-transaction history it requires is exactly what your billing model produces, and CE3.0-qualified outcomes are currently the main remedy that removes qualifying fraud from the VAMP count as well.

Frequently asked questions

What is Compelling Evidence 3.0 and does it work against 10.4?: CE3.0 is a Visa framework that lets merchants defeat a 10.4 dispute by proving an established relationship with the cardholder. You need two undisputed transactions on the same card that are between 120 and 365 days old and share at least two data elements with the disputed order, one of which must be device ID or IP address. When the criteria are met, liability moves back to the issuer, and qualifying disputes can even be blocked pre-chargeback through Order Insight.
Does 3-D Secure stop 10.4 chargebacks?: A fully authenticated 3DS transaction generally shifts fraud liability to the issuer, so a 10.4 filed against it is invalid and should be reversed on representment. It does not stop non-fraud disputes, and attempted or data-only flows may not carry the same protection. It also does nothing for the TC40 fraud report if the issuer still records one, so 3DS is a liability tool more than a reputation tool.
Most of my 10.4 disputes are friendly fraud. Is it worth fighting them?: Yes, and 10.4 is the code where fighting pays best. Friendly fraud collapses when you show delivery to the cardholder's verified address, usage of the product after purchase, or a CE3.0 transaction history. Wins also feed back into issuer behavior over time, since Visa tracks merchant representment outcomes. Just remember that winning the reversal does not remove the transaction from fraud-ratio calculations, so prevention still matters more than recovery.

Related Visa codes