Chargeback Evidence Checklist
A representment is won or lost on the evidence file. This checklist lists what to collect, where to get it and what to leave out.
Evidence checklist
- Order record - full order, line items, agreed price and the delivery promise.
- Proof of delivery - timestamped delivery confirmation, IP or device record, email opened, download or activation event.
- Customer correspondence - every message, in order, with dates and full context.
- AVS and CVV results - the raw response values from the authorisation.
- IP and device - IP address, device fingerprint and country at checkout and at use.
- Account history - prior successful orders and any previous dispute on the same card.
- Descriptor and receipt - the exact descriptor and receipt the cardholder saw.
- Policy evidence - the terms in force at the time of the transaction, with a timestamp.
How this tool works
Disputes are decided on the file, not on the argument. The checklist is organised in the order evidence should be assembled: what was bought, proof it arrived, what the customer said, what the verification returned, who used it, and what the terms allowed. Collecting it in one pass means the representment can be assembled without searching the ticketing system under a deadline.
When to use it
- Prepare a representment without scrambling
- Standardise evidence across the dispute team
- Find the gap in your file before the deadline
- Train support on what to keep
Frequently asked questions
How long should an evidence file be?
Only what is relevant. A long file dilutes the strong evidence.
What is the single most common reason a representment fails?
Proof of delivery that does not match what was ordered.
Should I include the customer's emails?
Yes, in full and in order, with the surrounding context.
Does a good AVS result help?
It helps, but it is not a substitute for proof of delivery.