Answer a Chargeback With the Evidence Issuers Actually Weigh — Free
Paste the dispute and the evidence you hold, and see which disputed dollars are backed by a named evidence type — and which sit bare before the issuer's deadline.
The proof surface
Issuers read packets by evidence vocabulary — transaction record, delivery proof, correspondence — not by narrative; indexing the reader's own exhibits against those types exposes the dollars still uncovered while there is time to cover them.
Why the flat version breaks
Sending narrative, not exhibits
A cover letter that explains feelings loses to a packet that names transaction record, delivery proof and correspondence.
Missing the rebuttal window
The issuer's deadline is measured in days and does not extend for weekends or your bookkeeper's holiday.
Double-refunding yourself
A chargeback plus a refund on the same order is a self-inflicted loss the processor will not unwind.
How to work the evidence packet
The disputed dollars, the order reference and the filing date, one line per exhibit.
Every exhibit is checked against transaction record, delivery proof, correspondence or logs.
Gather the named type for whatever sits uncovered — the packet names it exactly.
Send the indexed packet, and keep the countdown from printing your rebuttal date.
What the packet replaces
| Question | Before | On the packet |
|---|---|---|
| Is the response strong | screenshots in a zip file | every exhibit checked against a named type |
| Which dollars are bare | nobody knows until the loss | the uncovered balance ruled above the index |
| What to gather next | 'more evidence' | the specific missing type for the specific bare dollars |
The packet indexes what you paste; the card network's own reason-code rules remain the authority on what counts.
Run it on the samples, right here
FIRST-LOAD
Data note: Everything runs in this browser tab on the evidence packet: your disputed dollars and the exhibits that cover them stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a stapled evidence packet
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the ready-to-mail packet, and holds your drafts on this device — one free run, then $ 12 one-time for the layer that keeps filing.
The packet index and the uncovered total are free. The paid layer keeps one packet per dispute, prints the issuer-ready response, and tracks the rebuttal deadline.
Open the chargeback evidence packet companionBoundary
This evidence packet works only on the dispute and exhibit lines you paste you paste. It does not decide who wins the dispute, does not submit to the processor for you, and does not interpret card-network reason codes. The figures describe what you supplied, not what is true in the world. Confirm anything you plan to act on with your payment processor's dispute team, and an accountant for recurring-loss patterns before you rely on it.
What this is built on
- Every figure comes from the dispute and exhibit lines you paste you paste; nothing is looked up, scraped or asserted as verified.
- Method: every exhibit line is matched against named evidence types you supplied; disputed dollars whose lines name no type are totalled as uncovered and ranked for gathering
- Sample values are labelled samples — illustrative by design, not your data and not a quotation of any organisation's policy.
Before: the merchant forwarded screenshots and hoped. After: they see $312 of the disputed $715 names no evidence type and gather exactly those items, because the packet indexed their own case.