Key takeaways
- Compelling Evidence 3.0 applies only to Visa dispute condition 10.4, the card-absent "I didn't make this purchase" fraud claim, not to cancelled subscriptions, items not received or other networks' disputes.
- You need two earlier transactions on the same card or a linked credential, not reported as fraud, processed more than 120 and no more than 365 days before the dispute.
- The disputed and earlier transactions must share an IP address or a device ID or fingerprint, plus one more match: the login ID, the full delivery address, or the other of IP and device.
- Since October 24, 2026 the history can come from one or more merchants, limited to data your acquirer processed, and the invalid-dispute rules now also spell out, as the pre-arbitration rules already did, that device ID and device fingerprint can't count as two matches.
- CE 3.0 is decided at checkout: the public IP, device data, login ID and address have to be stored in Visa's formats at the time of each order and kept for over a year.
- Fraud reports that qualify for CE 3.0 are one of only two exclusions Visa names in its VAMP ratio, while an ordinary representment win gets the money back but leaves both the fraud report and the dispute in the count.
Compelling Evidence 3.0 (CE 3.0) is Visa's rule for beating a fraud claim from a cardholder who did make the purchase. When a customer tells their bank "I didn't make this purchase" about an online or phone order (Visa dispute condition 10.4), you can answer with their own history: two earlier transactions on the same card, not reported as fraud, processed 120-365 days before the dispute, that match the disputed order on IP address or device plus one more identifier. When the criteria are met, Visa's rules treat the fraud dispute as invalid.
Two things decide whether you can use it. The data must have been captured at checkout, because you can't rebuild an IP address or device fingerprint months later. And the rules changed on October 24, 2026, so much of what is written about CE 3.0, parts of Visa's own merchant guide included, is out of date. This guide works from the Visa Core Rules and Visa Product and Service Rules, edition dated 24 October 2026.
What Compelling Evidence 3.0 is, and the one dispute it covers
Visa introduced CE 3.0 for pre-arbitration attempts processed on or after April 15, 2023, to fight what it calls first-party misuse: cardholders reporting fraud on transactions they authorized, better known as friendly fraud.
Condition 10.4, Other Fraud, Card-Absent Environment, is the dispute in which the cardholder denies authorizing or taking part in an online, phone or mail order. The issuer must report the fraud to Visa before disputing, and has 120 calendar days from the transaction processing date to file. When the CE 3.0 criteria are met, the dispute is invalid and the issuer keeps the loss.
| Dispute | Visa condition | Does CE 3.0 apply? |
|---|---|---|
| "I didn't make this purchase" on an online, phone or mail order | 10.4 | Yes, if the criteria are met |
| Chip, counterfeit or other card-present fraud | 10.1-10.3 | No |
| Flagged by a Visa monitoring program | 10.5 | No |
| Not received, or not as described | 13.1, 13.3 | No |
| Charged after cancelling a subscription | 13.2 Cancelled Recurring | No |
| Mastercard, American Express or Discover disputes | Each network's own rules | No, CE 3.0 is Visa only |
Mastercard handles first-party fraud claims under its own rules and programs, so ask your processor what applies to those cards.
The CE 3.0 requirements as of November 2026
For disputes processed on or after October 24, 2026, Visa's rules (sections 11.8.5.3 and 11.8.5.6) require:
- Two earlier transactions on the same card or a credential associated with it, such as a token, "at one or more Merchants".
- No fraud reports on them that reached Visa's fraud reporting system before the dispute processing date. Ask your acquirer about edge cases.
- The right window: each processed more than 120 calendar days before the dispute was submitted and no more than 365 days before its processing date. The window counts back from the dispute, not from the purchase.
- A detailed description of what was bought in the disputed transaction and in both earlier ones.
- A data match, set out below.
Say a dispute is processed on November 19, 2026 (a hypothetical date). Qualifying earlier transactions fall roughly between November 19, 2025 and July 21, 2026, so a loyal customer whose other orders were in September and October 2026 would not qualify.
The data match
At least two data elements must match, and one must be the IP address or a device identifier. Call that one the anchor. Data that misses Visa's format doesn't count.
| Data element | Can it be the anchor? | Format Visa requires |
|---|---|---|
| IP address | Yes | The cardholder's public IP address, in clear text, IPv4 or IPv6 |
| Device ID | Yes | An identifier the cardholder can verify, such as an IMEI; at least 15 characters, clear text |
| Device fingerprint | Yes | Built from at least 2 software or hardware properties; at least 20 characters; may be hashed |
| Login ID | No | The ID used to authenticate the cardholder at the time of purchase; clear text, a value they recognize |
| Full delivery address | No | Street, city, state or province, postal code and country; clear text |
So IP address plus login ID works, and so does device fingerprint plus delivery address. Login ID plus delivery address doesn't, because neither is an anchor.
What doesn't count
- A store pickup location. Visa doesn't treat a merchant location as a delivery address.
- A checkout email or phone number, unless you use it to authenticate the customer as part of the purchase.
- Device ID and device fingerprint together. Visa calls them "similar data elements", so only one can be supplied.
- A proxy or load balancer IP in place of the customer's public IP address.
Some history counts that merchants assume won't. Visa's guide says earlier orders you later refunded can still count, and so can recurring charges that relate back to an earlier customer-initiated purchase. The 120-day minimum doesn't apply when the earlier transactions were Original Credit Transactions, such as payouts pushed to the card.
What changed on October 24, 2026
The Visa Rules print both versions side by side. The old text covers disputes processed through October 23, 2026.
| Rule | Through October 23, 2026 | From October 24, 2026 |
|---|---|---|
| Earlier transactions | Same payment credential, such as a card number or token (Visa's guidance: prior activity with your business) | Same card or a linked credential such as a token, at one or more merchants |
| Data the acquirer may submit | No separate limit stated | Only transaction data that acquirer accepted and processed |
| Device ID and fingerprint | Listed separately in the invalid-dispute criteria | Similar data elements: one or the other, never both |
| Login ID | The login on the merchant's site or app | Also logins with an agentic payment provider |
| Purchase order number in place of a description (invalid-dispute check) | Visa Secure, ECI 7 with a CAVV | Also Visa Token Service and Visa Intelligent Data Exchange (IDX) data |
The cross-merchant change doesn't give you other merchants' customer records. Your acquirer may submit only transaction data it processed, so a first-time buyer at your store might now qualify on history elsewhere, but don't plan around it: ask your processor what it can match. An agentic payment provider, in Visa's terms, is an app the cardholder uses to search for and buy products on their behalf.
Visa's own Dispute Management Guide for Merchants, dated October 2026, still describes prior activity "with your business", and says the Rules prevail where the two differ.
How a CE 3.0 defense works
You reach CE 3.0 through your acquirer or processor, by one of two routes.
- Before a dispute. Verifi's Order Insight lets merchants share order details with the issuer before a dispute is created. In its 2026 dispute services announcement, Visa said an April 2026 update lets merchants use CE 3.0 within Order Insight, and counted 106 million disputes globally in 2025, up 35% since 2019. If you don't use Order Insight, Visa says to ask your acquirer.
- After a dispute. Your acquirer sends the CE 3.0 data in its pre-arbitration attempt, due within 30 calendar days of the dispute processing date. The issuer has 30 days to respond, and arbitration must be filed within 10 days of that response. Your processor's deadline to you is shorter, and Visa warns that a missed window can lose even a strong case.
Industry sources also report that Visa now qualifies some US transactions for CE 3.0 automatically from Visa Secure data, for a fee. We couldn't find this in Visa's public rules, so ask your processor whether it applies to you and what it costs. CE 3.0 doesn't require 3-D Secure, a separate defense covered in our guide to 3-D Secure.
When a 10.4 arrives
- Confirm it is a Visa 10.4.
- Find the most recent eligible earlier transactions, and check with your acquirer that they carry no fraud reports.
- Pull an anchor plus at least one more matching element for all three transactions, in Visa's formats.
- Describe each purchase specifically, not with generic labels.
- Send it before your processor's deadline, and ask whether it goes in as CE 3.0 or as ordinary compelling evidence.
Even then, Visa says CE 3.0 guarantees no particular outcome.
A worked example
Say an online outdoor gear store (hypothetical) gets a 10.4, processed November 19, 2026, on a $240 tent. The buyer logged in to the same account for every order, and has two earlier orders on the same card, boots in February and a backpack in June 2026, shipped to the same address and never disputed or reported as fraud. The store records the public IP address on every order, and all three came from the same one.
That is an anchor plus two matches (login ID and delivery address), so with clear descriptions the criteria are met. Had the store never recorded IP addresses or device data, it would have no anchor and no CE 3.0 case, however many emails matched.
When CE 3.0 won't help, and what to use instead
Visa's guide says CE 3.0 is generally less likely to apply to first-time purchases, thin or inconsistent history, and anything that isn't a 10.4. Guest checkout gives it less to work with, and an annual plan may never have two charges inside the window. Subscription disputes are often filed as cancelled recurring (13.2), which CE 3.0 doesn't reach; see subscription billing without triggering chargebacks.
Classic compelling evidence
Visa's older compelling evidence list (Table 11-7) still applies to 10.4 and asks for less history. Useful items include:
- Delivery to an address that received an AVS match of Y or M, with no signature needed (item 3).
- For digital goods, a description, the date provided and 2 or more items from a list that includes IP address, device ID and a verified customer profile (item 4).
- Three or more of login ID, delivery address, device ID or fingerprint, email, IP address and phone number used in an undisputed transaction (item 10). Here a plain email counts.
- Undisputed payments for the same goods or service (item 12), or for recurring charges, a contract, proof of use and an earlier undisputed transaction (item 13).
The catch: with classic evidence the issuer can still decline, and if contact details match its records, it must go back to the cardholder for an explanation. Met CE 3.0 criteria make the dispute invalid instead. More in chargeback representment: how to fight and win.
| Defense | What it relies on | Result when met |
|---|---|---|
| CE 3.0 | Two earlier transactions in the window, not reported as fraud, with an anchor plus one match | The 10.4 is invalid |
| Classic evidence, item 10 | 3 or more elements from an undisputed transaction; a plain email counts | Issuer may decline, but must recheck with the cardholder if contact details match |
| Visa Secure (3DS) | ECI 5, or attempted ECI 6, with the CAVV in the authorization | The 10.4 is invalid, except in excluded categories |
Other facts that make a 10.4 invalid
Under Table 11-29, a 10.4 is invalid on, among others:
- A 3DS-authenticated transaction with ECI 5 and the CAVV, or an attempted one with ECI 6 and a CAVV (not on non-reloadable prepaid cards).
- A transaction with CVV2 present, a result of N (no match), and an approval anyway.
- A transaction approved on a credential the issuer had already reported for fraud.
- A credential on which the issuer had filed more than 35 disputes in the previous 120 days.
On US domestic e-commerce, 3DS gives no 10.4 protection to merchant category codes 4829, 5967, 6051 (non-financial institutions such as currency and digital-asset sellers), 6540, 7801, 7802 and 7995. CE 3.0 has no such list: Visa said in 2023 that every merchant category VisaNet supports can use it.
When it really is a stolen card or a taken-over account, CE 3.0 isn't the tool. Visa rule 10.4.4.3 requires you to try to withdraw the goods or services after a fraud dispute, and to re-authenticate the cardholder after an account takeover.
Build the CE 3.0 evidence trail at checkout
Every element CE 3.0 uses has to be recorded when each order happens. A dispute can arrive 120 days after a purchase and lean on orders placed up to 365 days before the dispute.
- Accounts for repeat buyers. Store the login ID on each order in clear text.
- The customer's public IP address on every order, in clear text, not a CDN, proxy or load balancer address.
- One device identifier: a fingerprint of at least 20 characters built from at least 2 device properties, or a device ID the cardholder can verify, such as an IMEI, of at least 15 characters in clear text.
- The full delivery address, including postal code and country.
- Specific descriptions, such as "men's waterproof hiking boots, size 10" rather than a SKU.
- At least 13 months of records, since an earlier transaction can be 365 days older than the dispute.
- A consistent billing descriptor. Visa's 2023 matching guidance: keep the leftmost characters (or those left of a "*") the same, and make sure your processor gives each transaction a unique acquirer reference number (ARN).
- Renewals linked to the first purchase. Visa said in 2023 that the first customer-initiated transaction's IP address can carry over to later recurring charges, so keep it.
Developers: ask your processor which of these fields it stores for each payment, and whether it can submit CE 3.0 data for you.
CE 3.0 and your Visa monitoring ratio
The Visa Acquirer Monitoring Program (VAMP) ratio is fraud reports (TC40) plus disputes (TC15), divided by settled card-not-present transactions (TC05). Every 10.4 starts with a fraud report, so one fraud dispute can count twice.
The VAMP fact sheet names just two exclusions: disputes resolved through pre-dispute solutions, and fraud reports that qualified for Compelling Evidence 3.0, both contingent on the timing of Visa's data extract. An ordinary representment win gets the money back, but both items still count. When CE 3.0 qualifies, the fraud report comes out of the ratio, though a filed dispute stays in; both stay out only when a pre-dispute solution such as Order Insight resolves the case first.
Visa's thresholds apply to a merchant through its acquirer, so ask your acquirer which figure applies to your account, and get it in writing. Our chargebacks hub explains how ratios and monitoring programs work.
How Flux fits
CE 3.0 runs through the card network and your acquirer. If you process with Flux, ask the team how dispute evidence, CE 3.0 included, is handled for your account. Around it, Flux gives you:
- Fraud screening. Flux fraud detection scores each transaction as it comes in and flags or blocks the risky ones before they settle, using rules you control.
- Customer history. Customer profiles show every payment, refund and saved method for a customer in one place, all tokenized.
- 3-D Secure on card payments through hosted checkout, payment links and invoices, on every card payment or only riskier ones. Its liability shift covers eligible fraud chargebacks only.
- Dispute handling: Flux tells you about each chargeback by email and in the portal, whose Chargebacks page holds the deadline, the evidence and the response, and chargebacks are among the 16 detailed reports. With hosted fields, your checkout page can also add its own device fingerprint and checkout session ID to each payment's chargeback evidence record.
- A person who knows your account. Flux tells you where your ratio is going before the network does, and a real person reviews every application.
This guide explains Visa's rules as of November 2026. It isn't legal advice: confirm what applies to your account with your processor, and talk to your attorney about your own situation. Questions: sales@fluxpayments.com.
Frequently asked questions
What is Visa Compelling Evidence 3.0?
A Visa dispute rule, in effect since April 2023, that lets a merchant answer a card-absent fraud dispute (condition 10.4) with the cardholder's own purchase history. If two earlier transactions not reported as fraud, processed 120 to 365 days before the dispute, match the disputed one on IP address or device plus one more identifier, and each purchase is described, the fraud dispute is invalid.
What are the requirements for Compelling Evidence 3.0?
Two earlier transactions on the same card or a linked credential that the issuer didn't report as fraud, processed more than 120 and no more than 365 days before the dispute, plus a detailed description of each purchase. The transactions must match on IP address or a device ID or fingerprint, plus at least one more element: login ID, full delivery address, or the other of IP and device.
Does Compelling Evidence 3.0 apply to Mastercard?
No. It is a Visa rule for Visa 10.4 disputes. Mastercard, American Express and Discover run their own dispute rules, so ask your processor what applies to those cards.
Does CE 3.0 work for subscription chargebacks?
Only when the subscriber files a fraud claim. Visa notes that subscription disputes are often classified as cancelled recurring, which CE 3.0 doesn't cover, and an annual plan may not have two charges inside the 365-day window.
What changed in Compelling Evidence 3.0 in October 2026?
For disputes processed on or after October 24, 2026, the qualifying history can come from the same card or a linked credential such as a token, at one or more merchants, limited to data the same acquirer processed. The invalid-dispute rules now also spell out, as the pre-arbitration rules already did, that device ID and device fingerprint can't count as two separate matches, and login IDs for agentic payment providers now count.
Does CE 3.0 help my VAMP ratio?
Partly. When CE 3.0 qualifies, the fraud report comes out of Visa's VAMP count, subject to the timing of Visa's data extract, but a dispute that was already filed still counts. Only a CE 3.0 case resolved through a pre-dispute solution, such as Order Insight, keeps both out.
Related reading
Fighting fraud disputes on online sales?
Flux gives you fraud rules you control, customer profiles with transaction history, a Chargebacks page in the portal with each dispute's deadline, evidence and response, and a person who knows your account.
Get Started