KYE Chargeback Evidence™ — the representment evidence that wins is the evidence you can prove.
Merchants lose winnable representments because the evidence was never captured when the transaction ran — and AI agents now issue refunds and accept liability with no recorded authority. KYE Chargeback Evidence™ governs the authority and evidence of the card-dispute flow: who authorised the refund, the representment, or the liability acceptance; the dispute evidence trail (order record, delivery confirmation, AVS/CVV result, customer communications) captured as hash-bound evidence events at transaction time; and the representment bundle sealed as a signed, WORM-retained, replay-verifiable Evidence Pack™ — the qualifying evidence set Visa Compelling Evidence 3.0 representments turn on, in cryptographically provable form. KYE Protocol™ governs whether the dispute action may proceed and proves it — it does not decide whether to fight a dispute, auto-generate dispute narratives, judge the dispute outcome, or do fraud scoring.
The dispute is decided on the record — and the record is made at transaction time, not after the chargeback arrives.
Dispute-management tools fight chargebacks; none of them make the merchant's evidence provable. Four facts converge:
- Visa Compelling Evidence 3.0 is an evidence-set standard. A CE3.0 remedy turns on recorded facts — two-plus prior undisputed transactions on the same credential, two-plus matching identifiers (device, IP, shipping address, account ID), delivery confirmation. If those facts were not captured when the transactions ran, the representment has nothing to stand on.
- The submitted bundle must survive challenge. In pre-arbitration and arbitration the documented record is everything. KYE Chargeback Evidence™ seals every representment bundle as a signed, hash-bound, WORM-retained Evidence Pack™ — verifiable offline, derivable from published keys alone.
- AI agents now move dispute money. Refund bots, auto-accept rules, and support copilots issue credits and accept liability. KYE™ records the named authority on every refund above threshold, every representment, and every liability acceptance — and refuses the silent write-off.
- This is a governance wedge, not a dispute-management engine. KYE Protocol™ does not compete with the dispute-management platform, the fraud engine, or the card network. It governs the action boundary they feed — the named-authority + transaction-time evidence + sealed Evidence Pack™ + contestability layer the dispute ecosystem currently lacks (complement-not-compete).
Survives the issuer, the network, the arbitration panel, and the auditor — captured at transaction time, sealed, and derivable from public keys alone.
- Evidence captured when it exists. The order record, delivery confirmation, AVS/CVV authorisation result, and customer-communication trail are captured as timestamped, hash-bound evidence events at transaction time — the CE3.0 qualifying set, with the honest gap enumerated when a field is missing.
- Refunds are authority-bound. Every refund or credit an AI agent issues above threshold maps to a recorded named-authority decision — the agent, the artefact, the action, and the named owner who authorised it. No recorded authority, no refund.
- Representment is a recorded decision. The decision to fight maps to a named authority before submission; the decision to accept liability is a recorded, contestable decision with a reconstruction route — no silent AI write-offs.
- Replay-provable Evidence Pack™. Every submitted bundle is sealed — evidence events + authority decisions + assembly basis under a context seal, hash-bound over canonical JSON, signed, WORM-retained — reconstructable and valid at T=0, verifiable offline by the issuer, the network, or a regulator.
- Regulatory perimeter included. Bound to Reg E (12 CFR 1005.11), Reg Z (12 CFR 1026.13), PSD2 SCA & unauthorised-transaction liability (Arts. 72-74, 97), Visa Compelling Evidence 3.0, and the Mastercard Chargeback Standards — each with a 90-day attestation cadence.
A standalone dashboard plus a Stripe App wrapper — every consequential dispute action authority-bound and evidenced.
One coherent spine governs three specializations — refund-authority, representment-evidence, and liability-acceptance — with no parallel packs. The standalone dashboard assembles and verifies Evidence Packs; the Stripe App wrapper listens to the dispute webhooks and assembles the pack from the dispute data plus the merchant's evidence.
- 1 — Dispute arrives. A chargeback lands (via the Stripe App wrapper's dispute webhooks, or entered in the dashboard). The governed transaction already carries its evidence events, captured when it ran.
- 2 — Authority check. The Action Admissibility™ Gate verifies the named authority on the proposed action — fight (representment), refund, or accept liability — under the §25 Edge Governance Safety Floor. No recorded authority = no action.
- 3 — Evidence assembled, gaps honest. The Evidence Pack™ assembler binds the order, delivery, AVS/CVV, and comms evidence events to the dispute, evaluates the Visa CE3.0 checklist, and enumerates exactly which qualifying fields are present and which are missing — honestly, never inflated.
- 4 — Pack sealed + submitted. The runtime emits kye.purpose.request.v1 + kye.purpose.admissibility.v1 + kye.evidence.decision_map.v1 + kye.evidence.pack.v1 + kye.replay.context_seal.v1 in lockstep, seals the bundle with a real SHA-256 over canonical JSON, retains it WORM, and submits the evidence through the card-network channel — reconstructable when challenged.
Bound to the dispute, error-resolution, and card-network evidence perimeter.
The app binds the canonical KYE™ artefact set to the dispute / chargeback perimeter. Every claim resolves to a control row on the bound framework — the five regimes are consumed by the rule pack, never re-mapped (honest scope: KYE™ maps only the authority / evidence slices, and cedes the dispute strategy, the narrative, the fraud scoring, and the outcome to the merchant, the dispute-management provider, and the card network).
| Framework | Control area | Coverage |
|---|---|---|
| Reg E (12 CFR 1005.11) | Named-authority on the provisional credit / refund, investigation evidence record, written-determination contestability | partial |
| Reg Z (12 CFR 1026.13) | Named-authority on the account correction, billing-dispute evidence record, written-explanation reconstruction | partial |
| PSD2 Arts. 72-74 + 97 | SCA evidence captured at transaction time, refund authority, Article 72 burden-of-proof bundle integrity | partial |
| Visa Compelling Evidence 3.0 | Qualifying evidence set captured at transaction time, representment bundle integrity, representment authority | partial |
| Mastercard Chargeback Standards | Second-presentment evidence capture, chargeback-response authority, arbitration-grade reconstruction | partial |
Honest scope. KYE Protocol™ governs the authority, evidence, integrity, and contestability of the dispute flow at the action boundary — whether the refund / representment / liability acceptance may proceed and how the evidence came into existence, so the submitted bundle is provable when challenged. It does not decide whether to fight a dispute, auto-generate dispute narratives, judge the dispute outcome, or do fraud scoring. Partial coverage means the bound surface satisfies the authority / evidence slice of the control area when paired with the merchant’s own dispute judgment. KYE™ complements the dispute-management ecosystem and the card networks — it does not compete with them.
A standalone app, distributed where the disputes are — your dashboard plus the Stripe App wrapper.
KYE Chargeback Evidence™ is a §68 sector product with Starter, Growth, and Enterprise commercial tiers; the Stripe App wrapper installs against the merchant’s own payment account with dispute scopes only. Commercial distribution is value-based, qualification-gated, and disclosed under NDA to qualified applicants.