← Chargeback Evidence Packet Builder
Search for “chargeback evidence checklist” and you get one list: order confirmation, proof of shipment or delivery, and a log of correspondence with the customer. Sellers bookmark that list and reuse it for every dispute that arrives, because it is free and it looks thorough. It is thorough for exactly one kind of dispute — merchandise not received — and silent about the other six reason codes a processor can post.
The card networks route a dispute under a reason code, and the reason code is the question a reviewer is actually deciding. This tool keeps a separate required-evidence set for each of the seven reasons it models, because a generic list answers only the delivery question and has no entry for the others.
| Dispute reason | A generic checklist's usual four | What it is missing for this reason |
|---|---|---|
| Merchandise not received | Order, shipping proof, correspondence, receipt | Close enough — this is the case the generic list was written for. |
| Fraudulent transaction | Order, shipping proof, correspondence, receipt | AVS/CVV verification result and the billing-to-shipping address match — the actual question is authorization, not delivery. |
| Merchandise not as described | Order, shipping proof, correspondence, receipt | The product listing as shown at purchase and the terms accepted at checkout — the question is what the buyer was shown, not whether it arrived. |
| Subscription canceled | Order, shipping proof, correspondence, receipt | The signup terms and the cancellation record — there is no shipment in a subscription dispute at all. |
| Credit not processed | Order, shipping proof, correspondence, receipt | The refund or cancellation record itself — the question is whether a promised credit was issued, which shipping proof cannot answer. |
| Incorrect amount | Order, shipping proof, correspondence, receipt | The order total as originally agreed and the checkout terms — shipping proof says nothing about the price. |
| Duplicate transaction | Order, shipping proof, correspondence, receipt | Nothing extra, but two full order-and-payment pairs, one per charge — a single shipping record does not show two distinct purchases. |
That is why a seller who reuses one checklist across reasons keeps attaching shipping proof to a fraud dispute — a record that answers a question nobody asked — while the AVS/CVV result the reviewer actually needed never makes it into the packet. This tool's checklist changes with the reason code you pick, so the gap it flags is the gap for that reason, not a copy-pasted generic one.
It is deliberately still just a checklist and a draft, not a submission service: nothing you type leaves your browser, there is no account, and it does not connect to your processor. The only thing it changes from a printed or bookmarked checklist is that it asks the reason first and tailors the list to it, and marks anything you have not checked off as a gap rather than letting a stale, wrong-reason list read as complete.
The card networks group disputes into reason codes, and each reason code asks a different question. “Merchandise not received” asks whether the goods arrived, so it is carried by the order, payment authorization, fulfillment record, and delivery tracking. “Fraudulent transaction” asks whether the cardholder authorized the purchase at all, so it is carried by the payment authorization, the AVS/CVV verification result, the billing-to-shipping address match, and delivery to that verified address. A generic checklist built around receipts, shipping proof, and a correspondence log answers the first question and has nothing for the second — it does not mention AVS/CVV verification anywhere, because that record only matters for a fraud claim.
Sometimes, by coincidence, for the reasons whose required records happen to overlap with what a generic list already covers — order and payment records appear in most of them. It reliably fails on the reasons that need something a generic list was never written to ask for: AVS/CVV verification for fraud, the accepted terms and cancellation record for a canceled-subscription dispute, or the product listing as shown at purchase for a not-as-described dispute.
No. This page compares against the generic method of using a single downloaded or bookmarked chargeback checklist for every dispute, not any specific company or product.
Open the Chargeback Evidence Packet Builder and pick the dispute reason first — the checklist below it is the one built for that reason, not a generic one.