Menu

Building a Visa CE3.0 Eligibility Matcher: Data Model, Rules, Edge Cases
📰

Building a Visa CE3.0 Eligibility Matcher: Data Model, Rules, Edge Cases

DEV Community: backend·Jarrod Wright·about 2 hours ago
#5MxNBpRC
#devtobackend#devto#dev#match#none
Reading 0:00
15s threshold

Visa's Compelling Evidence 3.0 (CE3.0) rule can stop a card-absent fraud dispute (reason code 10.4) when the merchant shows that the same card made earlier, undisputed purchases with matching identifiers. Most coverage frames this as a disputes-team topic. In practice, whether you qualify is decided months earlier by your checkout, logging, and data-retention code.

If your system didn't capture a stable device ID or a normalized shipping address at purchase time, you can't produce it later. This article treats CE3.0 as an engineering problem. It covers what to store, how to normalize it, how to write the matcher, and where implementations commonly break.

For the business context, the dispute lifecycle, and recent rule changes, see this overview of Visa Compelling Evidence 3.0 .

The rule, restated as a spec

Here are the commonly described qualification criteria, written the way you'd hand them to an engineer:

Scope: the disputed transaction is a Visa card-absent dispute under reason code…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.