Visa Compelling Evidence 3.0 (CE3.0)
Visa Compelling Evidence 3.0 (CE3.0) — 75% covered.
4 requirements · 3 enforced · 0 designed · 0 advisory · 0 deferred.
Source: Visa Compelling Evidence 3.0 (effective April 2023) defines the qualifying evidence a merchant must present to remedy a card-absent fraud dispute (reason code 10.4): two or more prior undisputed transactions on the same payment credential within a window, with at least two matching core data elements between the disputed and prior transactions (device ID / fingerprint, IP address, shipping address, customer account / login ID), plus supporting evidence such as delivery confirmation and product / service description. KYE Protocol™ governs whether the representment may PROCEED — under a named owner's recorded authority, with the qualifying evidence captured as evidence events at transaction time, and with the representment bundle sealed as a signed, hash-bound, WORM-retained, replay-verifiable Evidence Pack — which is exactly the provable evidence set CE3.0 representments turn on. KYE does not decide whether to fight the dispute, generate the dispute narrative, or judge the dispute outcome (the issuer and Visa do). · License: The Visa Rules and Compelling Evidence 3.0 requirements are Visa's own publications; the KYE registry paraphrases each requirement's intent and cites the programme name for mapping purposes only. No Visa text is reproduced.
By category
| Category | Reqs | Enforced | Designed | Advisory | Deferred | Coverage |
|---|---|---|---|---|---|---|
| Qualifying evidence set captured at transaction time | 1 | 1 | 0 | 0 | 0 | 100% |
| Representment bundle integrity (signed · hash-bound · WORM) | 1 | 1 | 0 | 0 | 0 | 100% |
| Named-authority on the representment decision | 1 | 1 | 0 | 0 | 0 | 100% |
| Dispute outcome adjudication & narrative on the merits | 1 | 0 | 0 | 0 | 0 | 0% |
Every requirement → the KYE™ artefact that enforces it
| ID | Title | Status | KYE™ enforcement |
|---|---|---|---|
visa-ce30.evidence-set-capture |
The CE3.0 qualifying evidence set is captured as evidence events at transaction time | enforced | audit_events: kye.evidence.decision_map.v1, kye.evidence.pack.v1, kye.evidence.tool_call.v1engines: internalrule_packs: kye:rule-pack:chargeback-evidencedictionaries: internalconstitution_refs: constitution/13-RESILIENCE-LOOP.md |
visa-ce30.representment-bundle-integrity |
The representment bundle is signed, hash-bound, WORM-retained and replay-verifiable | enforced | audit_events: kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.replay.proof.v1engines: internal, internalrule_packs: kye:rule-pack:chargeback-evidenceconstitution_refs: constitution/13-RESILIENCE-LOOP.md, constitution/30-AUDIT-WORM-RETENTION.md |
visa-ce30.representment-authority |
The representment decision proceeds only under a recorded named-authority decision | enforced | audit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1engines: internal, internalrule_packs: kye:rule-pack:chargeback-evidenceconstitution_refs: constitution/12-PURPOSE-PERMISSION.md |
visa-ce30.dispute-outcome-adjudication |
Dispute outcome adjudication, fight/accept strategy, and the dispute narrative on the merits | out-of-scope | (no enforcement cited) |