Build Visa Compelling Evidence 3.0 (CE3.0) evidence to reverse a 10.4 card-absent fraud dispute under Visa Claims Resolution
domain: payments-disputes · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the dispute was filed under Visa reason code 10.4 (Other Fraud - Card-Absent Environment); CE3.0 only applies to this reason code.
Pull two prior undisputed, non-fraud-reported transactions from the same cardholder that are between 120 and 365 days older than the disputed transaction (the 120-day floor doesn't apply if the prior transactions were original credit transactions).
Match at least two data elements across all three transactions, and ensure at least one of the two matches is IP address, device ID, or device fingerprint rather than only softer fields like name or shipping address.
Submit the qualifying evidence either pre-dispute via Verifi's Order Insight during the Visa Resolve Online pre-dispute window, or post-dispute/pre-arbitration through your acquirer if the pre-dispute window was missed.
If validated, expect the chargeback to reverse; note it affects your dispute ratio even though your fraud ratio is unaffected.
Where Visa Secure (3DS) or Visa Data Only was used on the transaction, check whether Visa's automatic CE3.0 qualification already covers it before manually assembling evidence.
Known gotchas
CE3.0 is specific to reason code 10.4 — using it to contest other fraud or non-fraud reason codes won't work and wastes evidence-submission effort.
Matching only soft data points (e.g., name and address) without an IP/device-based match fails the criteria, since one of the two matches must be IP, device ID, or fingerprint.
Missing the pre-dispute Order Insight window means you must catch it at the post-dispute/pre-arbitration stage instead — track both deadlines separately.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?