Free tool Β· For Business Β· For merchants

Visa CE 3.0 Evidence Readiness Checker


This one is for merchants, not cardholders. It answers one question before peak season: can the data your checkout already captures actually support a Visa CE 3.0 defence for a 10.4 card-absent fraud dispute β€” or would the packet fail on a field you never logged? Answer for a representative order history, and it audits each CE 3.0 condition as pass or fail. It is not the consumer-side Visa Fraud Dispute Checker, which answers a cardholder's question; this audits a merchant's data capture.

Rules checked October 29, 2026. Primary sources, linked inline in the first section below: Stripe's Visa CE 3.0 documentation, Chargeflow's CE 3.0 guide to the Visa Core Rules, April 18, 2026 edition, and Visa's CE 3.0 Acquirer Readiness document. Visa's rulebooks are not public; confirm your route with your acquirer. This is a self-check, never a Visa determination.

Can your checkout data defend a CE 3.0 case?

Everything is counted in your browser and never sent anywhere. This checker asks for no card numbers, account numbers or merchant IDs β€” never enter those into any checker. Answer about what your checkout captures today, not what you plan to capture.

Device ID and device fingerprint together count as ONE matching element, never two β€” even if both qualify.

Your processor may apply its own window β€” Stripe states 120–364 days. Ask your processor which window its field checks enforce; this audit tests Visa's 120–365-day rule.

At pre-arbitration, an acquirer may submit only transaction data it accepted and processed. Multi-merchant history from another acquirer's merchants cannot be submitted by your acquirer.

The rules, in one view

What CE 3.0 actually tests


Primary sources for everything on this page: Stripe's Visa CE 3.0 documentation (10.4 scope, two priors, main/secondary elements, device ID + fingerprint not a valid combination); Chargeflow's CE 3.0 guide (Visa Core Rules, April 18, 2026 edition, sections 11.7.5.3 and 11.7.5.6 β€” the October 24, 2026 expansion, the same-acquirer limit, Chile excluded); Visa's CE 3.0 Acquirer Readiness document (one-submission limit); and Pulse CRM's analysis of the October 24, 2026 change (purchase-order-number alternative, pre-arbitration footnote). All checked October 29, 2026.

ConditionWhat Visa requires
Dispute typeVisa 10.4, Other Fraud β€” Card-Absent Environment only
Prior transactionsAt least 2, same card or associated credential (from Oct 24, 2026), none reported as fraud
Age of priorsMore than 120 and no more than 365 calendar days before dispute processing
Matching elementsAt least 2 of: IP address, device ID/fingerprint, login ID, full delivery address β€” one must be IP or device
Device ID / fingerprintDevice ID 15+ characters in clear text; fingerprint 20+ characters from 2+ properties; together they count as ONE element
Same acquirer (pre-arbitration)Acquirer may submit only data it accepted and processed
SubmissionsOne attempt per dispute β€” an incomplete attempt burns the remedy

Want the full story, with the sources?

The companion article works through each check with examples, the October 24, 2026 expansion and its limits, and the two questions to put to your acquirer in writing. Read it here: Visa CE 3.0 evidence readiness guide for merchants.

Read: Visa CE 3.0 evidence readiness guide

Checker questions

For a Visa 10.4 card-absent fraud dispute, two prior undisputed transactions on the same card or an associated credential, each more than 120 and no more than 365 days before dispute processing, sharing at least two matching elements with the disputed transaction, one of which must be the IP address or the device ID/fingerprint.

No. From the October 24, 2026 rule change, device ID and device fingerprint count as similar elements β€” one category, not two. A qualifying pair needs IP or device plus a different element such as login ID or a full delivery address.

Only in a limited way. For disputes processed on or after October 24, 2026, priors may come from one or more merchants, but at pre-arbitration an acquirer may submit only transaction data it accepted and processed. Priors held only by a different acquirer cannot be submitted by your acquirer.

Once per dispute. Visa's acquirer readiness guidance states a CE 3.0 submission may be attempted only once; an incorrect or incomplete attempt is declined and the remedy is lost for that dispute.

Sources (checked October 29, 2026): Stripe β€” Visa Compelling Evidence 3.0 disputes documentation; Chargeflow β€” Visa Compelling Evidence 3.0 (CE3.0): Rules and 2026 Changes, citing Visa Core Rules April 18, 2026, sections 11.7.5.3 and 11.7.5.6; Visa β€” Compelling Evidence 3.0 Acquirer Readiness (visa.com PDF); Pulse CRM β€” Visa's Compelling Evidence 3.0 Changes on 24 October; Checkout.com β€” Visa Compelling Evidence 3.0 Overview. Visa's rulebooks are not public; figures are as published in these processor and rules summaries and can change.

General information only β€” not legal or financial advice. Whether a CE 3.0 defence succeeds depends on your acquirer's submission route and Visa's validation, which no checker can see. This checker applies the published rules to the answers you entered. Never enter a card number, account number or merchant ID into any checker.

Built by Chargeback Clock β€” Meet the Founder.

← Back to homepage Β· For Business