What every effective response has in common
Before looking at the examples, it is worth understanding why some responses succeed and others fail. A reviewer at a bank or card network is not reading your response looking for the full story of your business. They are checking whether your evidence directly contradicts the dispute claim.
The responses that work share these characteristics:
- They address the specific reason code rather than providing a general account of the transaction.
- They lead with facts, not emotion. The tone is professional and neutral throughout.
- They include an evidence index so the reviewer can navigate the pack quickly.
- They are concise. Two pages of focused, labelled content beats ten pages of everything.
- They reference the merchant's own policies: shipping, returns, and any relevant terms.
Use these as starting points
The examples below are illustrative. They use placeholder order details. Replace all bracketed values with your actual order data and adapt the facts to your specific situation before submitting.
Example 1: Item not received
The item not received dispute is the most common in ecommerce. The customer is claiming the parcel never arrived. Your response needs to establish that the item was shipped and delivered to the address the customer provided at checkout.
Item not received -- full response example
What makes this response effective
- It leads with the delivery confirmation fact in the opening summary.
- The tracking record includes the delivery address, confirming it matches the order address.
- It notes that the customer did not contact the merchant before the dispute, which is relevant context.
- The evidence index maps directly to the attached files.
- The conclusion restates the key fact clearly and makes a specific request.
Example 3: Item not as described
The item not as described dispute is where the customer claims the product they received was different from what was advertised. Your response needs to demonstrate that what you sold matched your listing, and ideally that the customer did not raise the issue with you before filing the dispute.
Item not as described -- full response example
What makes this response effective
- It directly addresses the dispute claim by comparing the product listing to the item shipped.
- It includes the specific listing language that covers natural variation, which is directly relevant to this type of dispute.
- It notes clearly that the customer did not contact the merchant before filing, which is important context.
- The return policy is included to show the customer had a route to resolution available.
What to attach with each example
The evidence index in each example tells you exactly what to attach. Here is a quick reference by reason code:
- Item not received: order confirmation, tracking history (full timeline), delivery confirmation, order and shipping emails, shipping policy.
- Unauthorised transaction: order confirmation, transaction record, Shopify fraud analysis screenshot (AVS, CVV, IP), tracking with delivery to billing address, order confirmation email.
- Item not as described: order confirmation, product photos, product listing screenshot at time of purchase, customer communication history (or documented absence of contact), return policy.
Name every file clearly before uploading: 01_order_confirmation.pdf, 02_tracking_screenshot.png. Match the file names to the exhibit numbers in your response letter.
Dispute response review checklist
Before submitting your response
- Reason code identified and response addresses it specifically
- All placeholder text replaced with actual order details
- Evidence index complete and matches attached files
- Files named consistently and numbered
- Response under two pages
- Tone is professional and factual throughout
- Shipping policy and return policy included
- Submission deadline confirmed and met
DisputeDesk generates these responses automatically
DisputeDesk pulls your order data from Shopify, prefills the response form with the correct details, and generates a formatted draft matched to your reason code. You review, adjust, and export a submission-ready PDF.
Build your evidence pack with DisputeDesk
DisputeDesk helps ecommerce merchants organise chargeback evidence and draft customer responses in minutes.
Disclaimer
DisputeDesk is not a law firm. Outputs and templates from DisputeDesk should be reviewed before use. Merchants are responsible for their own customer communications and dispute submissions. Nothing on this page constitutes legal advice.
Frequently asked questions
Can I copy these examples exactly for my dispute?
The structure is designed to be reused, but you must replace all placeholder values with your actual order details. A response submitted with test data or placeholder text will fail. Read through the entire response before submitting and confirm every factual statement matches your records.
What if my situation does not match any of these examples exactly?
Use the closest matching example as a structure and adapt the facts section to your situation. The core format -- summary, transaction details, fulfilment record, evidence index, policies, conclusion -- applies to every reason code. The middle section needs to address your specific dispute claim.
How long should the examples be when I adapt them?
Aim for two pages or fewer. The examples above are on the longer side for illustration purposes. In practice, cut any section that does not add relevant evidence for your specific dispute. A tighter, more focused response is generally more effective.
Should I mention that the customer filed the chargeback without contacting me?
Yes, where it is true and relevant. For item not received and item not as described disputes, the absence of prior customer contact is useful context. It shows you had no opportunity to resolve the issue before the dispute was filed. State it factually without sounding accusatory.
Do I need a cover letter separate from the response letter?
No. The response letter itself acts as the cover document. It contains the summary, facts, evidence index, policies, and conclusion. You do not need a separate cover page. Keep everything in one clear, structured document.
Does submitting a well-written response guarantee a win?
No. The outcome depends on the card network, the issuing bank, the reason code, and the strength of your evidence. These examples give you the best structure for a strong submission, but no response format or tool can guarantee a specific outcome. DisputeDesk does not guarantee chargeback results.