Chargeback / Dispute Response Checklist
Operational checklist for merchants. Integrity-only language. No claims of promised outcomes. Best next step: run a free scan when the packet is still messy, then use the Review Rail examples or start One Case when one packet is ready to fix.
1) Fast checklist (before you submit)
- Confirm deadlines in your payment provider / marketplace portal.
- Respond with a single bundle (fewer attachments, less confusion).
- Keep it factual: dates, what you shipped, what you recorded, what the carrier shows.
- Do not over-claim: avoid “court-proof”, “win promise”, “identity verified”.
2) What to attach
- Evidence Sheet (PDF) — one-page summary + verify link.
- Proof Card (PNG) — quick visual status + receipt id.
- Receipt JSON — portable copy (only if the portal accepts JSON/text).
- Order info — order number, item/SKU, dates, value, shipping service level.
- Carrier artifacts — tracking page screenshots, drop-off receipt, delivery status.
- Message excerpt — customer dispute message and your reply (redact personal data if required).
Tip: if the portal limits attachments, prioritize PDF + carrier proof + order info.
3) What to avoid claiming
- Do not claim certainty: “promised”, “undeniable”, “conclusive proof”.
- Do not claim identity/authorship: “we verified the customer”, “we proved who opened it”.
- Do not claim delivery/condition as proven: integrity evidence ≠ delivery confirmation.
- Do not make legal conclusions: “fraud”, “criminal”, “illegal” (unless you have counsel and a filing).
- Do not upload unnecessary personal data: keep it minimal and relevant.
Use “integrity-only” wording: “tamper‑evident record”, “supports auditability”.
Template generator (local)
Select a reason and platform style, then copy a legally safe template. This is guidance only. No guarantees. No portal integrations.
Integrity-only. No legal advice. No promise of admissibility/court acceptance.
4) Suggested “integrity-only” wording (copy/paste)
Short statement
Attached is a tamper‑evident (integrity‑verified) timeline bundle for this order. It includes a 1‑page Evidence Sheet and a Proof Card with a Verify link. This supports integrity checking (what existed when); it does not prove identity, delivery/condition, or intent.
Timeline framing
We recorded integrity checkpoints under these event names: packed → handed_over → delivered → opened. The carrier tracking screenshots are included as informational references.
Keep your narrative to 5–8 sentences max. Attach the bundle. Let the portal reviewer scan the Verify link.
5) If the dispute is about “empty box / wrong item / used item”
- Attach Packing Proof (photos/video hash + packing checklist version).
- Attach Handover Proof (drop-off receipt + tracking start screenshot).
- If applicable, request an unboxing video and seal the received media hash (Remote Collection).
6) Receiver Preset idea (reason-code ready intake)
To move from a generic tool toward a standard, Vraimony should let the sender choose a Receiver Preset. That changes the intake fields, recommended attachments, and wording order to fit the receiving review lane instead of making the reviewer reconstruct the file manually.
Preset logic
- If receiver = Klarna: prioritize return tracking, warehouse intake, invoice-pause logic, and parcel-level checks.
- If receiver = Shopify / payment processor: prioritize purchase-time policy version, order events, refund traces, and carrier artifacts.
- Always: keep claims minimal, keep evidence joins explicit, and export one decision-ready bundle.
Provider requirements can change. Keep exact portal mappings in the registry/config layer, not buried in support emails or ad-hoc staff habits.
Reality Audit
—