A chargeback response pack is the evidence submitted to contest a disputed payment: proof the order was placed, proof it was delivered, the customer communication, and your published terms. The deadline is short and fixed, so the work is assembly rather than investigation, and the common failure is starting late rather than having a weak case.
When to use it
Start the day the dispute notification arrives. The deadline is set by the card scheme rather than by you, and a strong response submitted after it is worth nothing.
Run it even on cases you expect to lose. Patterns across disputes are how you find a product description that misleads, a delivery route that fails, or a fraud problem you have been absorbing.
The template
Assemble, attach, submit. Do not spend the time deciding whether it is worth contesting until the pack is ready.
CHARGEBACK RESPONSE Order: [number] Amount: [ ] Reason given: [ ] Notified: [date] RESPONSE DEADLINE: [date] Owner: [name] 1. THE ORDER EXISTS AND THEY PLACED IT [ ] Order confirmation, with timestamp [ ] Billing and shipping address as entered [ ] IP and device details, if available [ ] Account history: previous orders from this customer 2. THEY RECEIVED IT [ ] Tracking showing delivery, with date and location [ ] Proof of delivery or signature, if the carrier provides it [ ] Dispatch confirmation sent to them 3. THEY KNEW WHAT THEY WERE BUYING [ ] Product page as it appeared, including description and images [ ] Refund and returns policy, as published at the time [ ] Terms shown at checkout 4. WHAT WAS SAID [ ] All customer messages, in full, in order [ ] Anything offered and whether it was accepted 5. SUBMIT [ ] Short covering summary: what was ordered, delivered, and said [ ] Everything above attached [ ] Submitted before the deadline [ ] Outcome recorded for pattern-spotting Outcome: [ ] Date: [ ]
How to adapt it
- Put the deadline at the top and in your calendar. It is the only field that invalidates everything else.
- Keep the covering summary to a short paragraph. Whoever reviews it is working through a queue, and a clear three-sentence account of what happened is read in full where two pages are skimmed.
- Capture the product page as it appeared. If the description has changed since the order, the current page is not evidence of what they bought.
- Record outcomes even when you lose. Three disputes citing the same product description is a listing problem, not a fraud problem, and only the record shows it.
Why it is this short
The pack is a checklist rather than a guide because there is no judgement in it. The evidence a scheme accepts is fixed, and the job is gathering it before a date.
It also does not ask whether to contest. That decision takes longer than assembling the pack, and it is better made with the pack in front of you than instead of it.
Common questions
How long do you have to respond to a chargeback?
It is set by the card scheme and the window is short. Check the exact date on the notification and put it in a calendar, because a strong response submitted late is worth nothing.
What evidence helps most in a chargeback?
Proof of delivery with a date, the order record showing what was bought, and the customer communication. Together they address the three most common reasons given.
Should you contest every chargeback?
Assemble the pack first and decide after. Deciding first usually takes longer than the assembly, and the pack is what the decision should be based on.
Why record the outcome of disputes you lose?
Because patterns are invisible case by case. Several disputes naming the same product usually mean a listing that misleads rather than customers who defraud.