Visa Compelling Evidence 3.0 (CE3.0)

Visa Compelling Evidence 3.0 (CE3.0) — 100% of in-scope requirements covered.

4 requirements · 3 in scope (3 enforced) · 1 out-of-scope (outside KYE™’s authority layer). The 100% is weighted over the in-scope base.

Visa Compelling Evidence 3.0 (CE3.0): requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. evidence-set-capture · enforced

    The CE3.0 qualifying evidence set is captured as evidence events at transaction time

    Audit events: kye.evidence.decision_map.v1, kye.evidence.pack.v1, kye.evidence.tool_call.v1 · Rule packs: kye:rule-pack:chargeback-evidence · Constitution: 13 resilience loop

  2. representment-bundle-integrity · enforced

    The representment bundle is signed, hash-bound, WORM-retained and replay-verifiable

    Audit events: kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.replay.proof.v1 · Rule packs: kye:rule-pack:chargeback-evidence · Constitution: 13 resilience loop, 30 audit worm retention

  3. representment-authority · enforced

    The representment decision proceeds only under a recorded named-authority decision

    Audit events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1 · Rule packs: kye:rule-pack:chargeback-evidence · Constitution: 12 purpose permission

  4. dispute-outcome-adjudication · out-of-scope

    Dispute outcome adjudication, fight/accept strategy, and the dispute narrative on the merits

    (no enforcement cited)

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

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

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Qualifying evidence set captured at transaction time11000100%
Representment bundle integrity (signed · hash-bound · WORM)11000100%
Named-authority on the representment decision11000100%
Dispute outcome adjudication & narrative on the merits100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
visa-ce30.evidence-set-captureThe CE3.0 qualifying evidence set is captured as evidence events at transaction timeenforcedaudit_events: kye.evidence.decision_map.v1, kye.evidence.pack.v1, kye.evidence.tool_call.v1
engines: internal
rule_packs: kye:rule-pack:chargeback-evidence
dictionaries: internal
constitution_refs: constitution/13-RESILIENCE-LOOP.md
visa-ce30.representment-bundle-integrityThe representment bundle is signed, hash-bound, WORM-retained and replay-verifiableenforcedaudit_events: kye.evidence.pack.v1, kye.replay.context_seal.v1, kye.replay.proof.v1
engines: internal, internal
rule_packs: kye:rule-pack:chargeback-evidence
constitution_refs: constitution/13-RESILIENCE-LOOP.md, constitution/30-AUDIT-WORM-RETENTION.md
visa-ce30.representment-authorityThe representment decision proceeds only under a recorded named-authority decisionenforcedaudit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1
engines: internal, internal
rule_packs: kye:rule-pack:chargeback-evidence
constitution_refs: constitution/12-PURPOSE-PERMISSION.md
visa-ce30.dispute-outcome-adjudicationDispute outcome adjudication, fight/accept strategy, and the dispute narrative on the meritsout-of-scope(no enforcement cited)

Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE Protocol™.