Visa Compelling Evidence 3.0 (CE3.0): Qualifying Criteria, Evidence Requirements, and What Changed

Compelling Evidence 3.0 (aka CE3.0 or CE3) is Visa's name for the prior-transaction history test under Dispute Condition 10.4 (Other Fraud – Card-Absent Environment): if the same payment credential was used in two earlier undisputed transactions, matched to the disputed one on device or IP data plus one more element, the dispute can be invalidated or defeated at pre-arbitration.¹

What has to be true about the prior transactions to qualify?

Two things have to be true: the same payment credential was used in two prior transactions the issuer never reported as fraud, and those transactions fall inside a 120-to-365-day window before the current dispute.¹

Broken into its parts:

Two of those conditions carry detail worth stating outright: a fraud report only disqualifies a prior transaction when it lands before the current dispute's processing date, and the 120-day floor is waived when the prior transactions were Original Credit Transactions rather than purchases.¹

What evidence has to be submitted to match the prior transactions?

The disputed transaction and the two prior transactions have to share device ID or device fingerprint, or IP address, plus at least one more matching element from a fixed list, and Visa specifies the exact format each element has to meet.¹

The rule requires a detailed description of the merchandise or services purchased across all three transactions, plus proof of a match on:

Device ID and device fingerprint count as one element, not two. Visa treats them as the same type of data; an acquirer can't submit both and call it two matches.¹ A submission built on "device ID matched, and so did device fingerprint" still needs a genuinely separate second element to qualify.

The base requirement is device ID/fingerprint or IP, plus one more.

The rule's own structure reads as: (device ID/fingerprint, OR IP address) AND at least one additional element from the remaining list. A submission that matches only a login ID and a delivery address, with no device or IP data at all, does not meet the test as written.

The character floors are where otherwise-qualifying cases fail in practice. Visa requires at least 15 characters. A 12-character string doesn't qualify as a device ID under the rule, regardless of how confident the match is.

Is CE3.0 used to invalidate a dispute, or to win pre-arbitration?

CE3.0 works two different ways depending on when it's used: grounds to call a dispute invalid before it's answered, or supporting documentation in a pre-arbitration attempt after an issuer has already rejected the first response.¹

The qualifying test (the prior-transaction history, the matching elements, the format requirements) is the same either way; the pre-arbitration version just restates it as certification alongside the attempt rather than a standalone ground. Pre-arbitration also allows two other paths that have nothing to do with prior-transaction history: evidence that a merchant credit or reversal wasn't addressed, or the broader "compelling evidence" standard that covers all 17 evidence types across all three fraud conditions.² CE3.0 is one narrow slice of that broader standard, built specifically around purchase history rather than delivery proof, digital-goods logs, or the other evidence types.

What changed with CE3.0 vs earlier compelling evidence standards?

The pre-CE3.0 standard isn't publicly documented. Visa's Core Rules describe CE3.0 only as the current version of this rule: the 18 April 2026 edition contains no reference to a "CE 1.0" or "CE 2.0" and no version history for the rule's evolution.³ If a documented predecessor exists — an earlier, looser matching test, or a different day-count floor — it sits in an acquirer bulletin or a Visa Business News item rather than the rulebook.

What the rulebook does document as a defined change is the October 2026 expansion below; that one is tier-1 sourced and dated.

What changes on October 24, 2026?

Starting 24 October 2026, the two prior transactions no longer have to be with the same merchant: they can be spread across one or more merchants, as long as the acquirer only submits transaction data it processed itself.³

Today, both prior transactions have to sit with the same merchant relationship. After the change, they can span multiple merchants under the same acquirer. Everything else about the test (the 120-to-365-day window, the fraud-reporting exclusion, the matching-element list, the format floors) carries forward unchanged.¹ Since the acquirer's submission is still limited to data it processed itself, the practical reach depends on how much of a cardholder's history sits with the same acquiring relationship; a large acquirer processing for many merchants gets more out of this than a merchant on a small, single-relationship acquirer.

Visa frames the change as reducing friendly fraud by widening what counts as prior undisputed history.³

How does Order Insight deliver CE3.0 evidence to the issuer?

Order Insight is the product name for the pre-dispute channel that carries CE3.0-type transaction evidence to the issuer while a cardholder is still questioning a charge, before a formal dispute is filed.⁴ It's a Verifi product. Verifi is a Visa company, but Order Insight is not something Visa's own rulebook names or governs directly. How the issuer's system actually behaves when it receives that evidence (acceptance rates, response times, integration mechanics) comes from Verifi/Visa product material and industry reporting, same as on the companion pages.

What happens when CE3.0 evidence is accepted vs rejected, and what's the VAMP consequence?

When an issuer accepts CE3.0 evidence, the dispute is resolved without becoming a chargeback and the associated fraud report is cleared from the numerator of the merchant's Visa Acquirer Monitoring Program (VAMP) ratio; when it's rejected, the dispute proceeds normally and both the fraud report and the dispute record remain in that numerator.⁵

A transaction can generate both a TC40 fraud report (filed the moment a cardholder tells their bank a charge is fraudulent) and a TC15 dispute record (filed when the dispute is formally opened), and both count in the VAMP ratio independently.⁶ Tools like Rapid Dispute Resolution and CDRN remove the TC15 side by resolving the dispute before it's filed, but leave the TC40 standing. CE3.0 evidence, submitted and accepted through a channel like Order Insight, is the only mechanism that reaches both records on the same transaction. It resolves whether the transaction was fraudulent, not just whether a dispute gets filed.⁵

If the evidence is rejected, it means the issuer isn't satisfied the matching elements establish undisputed prior use. The dispute runs its normal course: response, and if needed, pre-arbitration under the CE3.0 pre-arbitration path. A rejected CE3.0 submission at the invalid-dispute stage isn't wasted, either, since the same evidence and matching elements can be resubmitted as pre-arbitration documentation under §11.7.5.6 if the first attempt fails.

What to do with this

Check your dispute date against the 120-to-365-day window before pulling evidence. A prior transaction six weeks old doesn't qualify no matter how clean the match is. A prior transaction from fourteen months ago doesn't either.

Audit your checkout logs for device ID length before you need them. If your device ID field is shorter than 15 characters or your fingerprint is under 20, that data doesn't meet Visa's format regardless of how confident the match is. This is a data-capture fix, not a dispute-response fix, and it has to happen before the transaction, not after.

Don't submit both device ID and device fingerprint expecting two matches. They count as one element under the rule. Plan for a genuine second match (login ID, delivery address, or IP) from the start.

Track which of your acquiring relationships will benefit from the October 24, 2026 multi-merchant change. If a meaningful share of your customers' undisputed history sits with other merchants on the same acquirer, the expansion is worth building toward now.

Route CE3.0-eligible transactions to whatever pre-dispute channel your provider offers before assuming the dispute-response path is the only option. Evidence accepted before a formal dispute is filed clears the fraud report; evidence submitted only after the fact still has to go through response or pre-arbitration.

Related

• What Counts as Compelling Evidence for a Visa Dispute?
• Does Rapid Dispute Resolution (RDR) Remove Chargebacks from Your VAMP Ratio?
• TC40 vs TC15: What Counts Where in Your VAMP Ratio
• Chargeback Glossary

Sources

1. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, §11.7.5.3 "Dispute Condition 10.4: Other Fraud – Card-Absent Environment – Invalid Disputes," Table 11-28, Rule ID 0030254, pp.699–705, and footnotes 1–9 on p.704; §11.7.5.6 "Dispute Condition 10.4: Other Fraud – Card-Absent Environment – Pre-Arbitration Processing Requirements," Table 11-31, Rule ID 0030257, pp.706–708. Country/Region: All. visa-rules-public.pdf ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

2. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, §11.7.5.6, Table 11-31, p.706, listing CE3.0 alongside credit/reversal evidence and a reference to §11.5.1 "Use of Compelling Evidence," Rule ID 0030221, p.677, the broader 17-item standard covering Dispute Conditions 10.1, 10.3, and 10.4. ↩

3. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, Summary of Changes, "Updates to Compelling Evidence 3.0 for Dispute Condition 10.4: Other Fraud – Card-Absent Environment," effective 24 October 2026, p.48. This is the only occurrence of the name "Compelling Evidence 3.0" or "CE3.0" in the document; it names §11.7.5.3 (Rule ID 0030254) and §11.7.5.6 (Rule ID 0030257) as the rules impacted. ↩ ↩² ↩³

4. Not published by Visa. Order Insight appears zero times in the 18 April 2026 Visa Core Rules. It is a Verifi product name (Verifi has been a Visa company since 2019); its role as a delivery channel for CE3.0-type evidence comes from Verifi/Visa product documentation and industry reporting, not the Core Rules. ↩

5. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, §11.7.5.3 Table 11-28 (Rule ID 0030254) and §11.7.5.6 Table 11-31 (Rule ID 0030257), pp.699–708. The rule text establishes the evidentiary mechanism, not the VAMP outcome. For the VAMP-clearing consequence see the next footnote. ↩ ↩²

6. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, §10.4.3.1 "Visa Acquirer Monitoring Program (VAMP)," Rule ID 0029286, p.633, establishing the VAMP program's existence and count-based structure; §1.9.4.3 "Issuer Fraud Activity Reporting," Rule ID 0002389, p.139, establishing that fraud reporting fires independent of dispute status. The Core Rules do not state the VAMP-clearing consequence, but Visa does publish it: the Visa Acquirer Monitoring Program fact sheet (accessed August 2026) states under "VAMP Ratio has additional criteria" that the ratio "Excludes TC 40 fraud qualified for Compelling Evidence 3.0, contingent on the timing of the data extract." Tier 2 — a Visa-published fact sheet rather than the rulebook — and the data-extract timing caveat is Visa's own wording, worth keeping in any restatement. ↩