Mastercard Chargeback Standards — Dispute Resolution & Arbitration

Mastercard Chargeback Standards — Dispute Resolution & Arbitration — 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.

Mastercard Chargeback Standards: 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. second-presentment-evidence-capture · enforced

    The second-presentment supporting documentation is captured as evidence events at transaction time

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

  2. chargeback-response-authority · enforced

    The chargeback response (second presentment / pre-arbitration / acceptance) proceeds only under a recorded…

    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

  3. arbitration-reconstruction-record · enforced

    Arbitration-grade reconstruction: the dispute record is sealed, contestable 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, 21 delegated auditability, 30…

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

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

    (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: The Mastercard Chargeback Standards (the Chargeback Guide) govern the dispute lifecycle on Mastercard transactions: the first chargeback, the merchant's second presentment with supporting documentation, pre-arbitration, and the arbitration case where the network rules on the documented record. The second presentment must carry the documentation that remedies the chargeback reason — order and fulfilment records, authorisation results, proof of delivery, and customer-communication evidence. KYE Protocol™ governs whether the second presentment / case filing may PROCEED — under a named owner's recorded authority, with the supporting evidence captured as evidence events at transaction time, and with the bundle sealed as a signed, hash-bound, WORM-retained, replay-verifiable Evidence Pack™ so the documented record survives pre-arbitration and arbitration scrutiny. KYE™ does not decide whether to fight the dispute, generate the dispute narrative, or judge the dispute outcome (the issuer and Mastercard do). · License: The Mastercard Chargeback Standards are Mastercard's own publications; the KYE™ registry paraphrases each requirement's intent and cites the programme name for mapping purposes only. No Mastercard text is reproduced.

By category

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Second-presentment evidence captured at transaction time11000100%
Named-authority on the chargeback response11000100%
Arbitration-grade reconstruction of the dispute record11000100%
Dispute merits adjudication & strategy100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
mastercard-dispute-rules.second-presentment-evidence-captureThe second-presentment supporting documentation is captured as evidence events at transaction timeenforcedaudit_events: kye.evidence.decision_map.v1, kye.evidence.pack.v1
engines: internal
rule_packs: kye:rule-pack:chargeback-evidence
dictionaries: internal
constitution_refs: constitution/13-RESILIENCE-LOOP.md
mastercard-dispute-rules.chargeback-response-authorityThe chargeback response (second presentment / pre-arbitration / acceptance) 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
mastercard-dispute-rules.arbitration-reconstruction-recordArbitration-grade reconstruction: the dispute record is sealed, contestable 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/21-DELEGATED-AUDITABILITY.md, constitution/30-AUDIT-WORM-RETENTION.md
mastercard-dispute-rules.dispute-merits-adjudicationDispute merits adjudication, fight/accept strategy, and the dispute narrativeout-of-scope(no enforcement cited)

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