Copy a short response structure before you submit: case snapshot, merchant position, transaction timeline, evidence references, and neutral closing language.
A useful chargeback response letter is not a long argument. It names the transaction, explains the merchant position, and points the reviewer to attachments that answer the stated claim.
Chargeback response for [store name]
Dispute amount: [amount]
Dispute reason: [item not received / fraud / not as described / credit not processed]
Order or transaction ID: [order ID]
Processor or platform case ID: [case ID]
Response deadline: [date]
Merchant position
The merchant position is that the attached records support the response to this dispute. The evidence connects the disputed payment to the order or transaction record, fulfillment or service record, customer-facing policy context, and relevant merchant communication.
Transaction timeline
- [Date]: Customer placed the order or completed the transaction.
- [Date]: Merchant fulfilled, shipped, delivered, or provided access to the product or service.
- [Date]: Customer communication, refund request, delivery issue, or support follow-up occurred.
- [Date]: Dispute notice received and response deadline confirmed.
Evidence attached
1. Order or transaction record showing the disputed payment.
2. Fulfillment, delivery, usage, or service record tied to the transaction.
3. Customer communication relevant to the stated dispute reason.
4. Policy, product, checkout, refund, or cancellation context in effect at purchase.
5. Any reason-code-specific proof needed to answer the claim.
Response statement
The attached records show what was purchased, how the merchant fulfilled or responded, and how each attachment supports the merchant response to the stated claim. The merchant asks the reviewer to consider the records together with the dispute reason shown in the platform.
Boundary note
This response is based on the attached transaction and evidence records. It is not a guarantee of outcome, legal advice, or platform affiliation.
Keep it short
The response should make the evidence easier to review. Remove emotional language, unsupported claims, and repeated facts.
Match the reason code
A delivered-order response needs different proof than fraud, duplicate charge, not-as-described, or credit-not-processed disputes.
Submit through the platform
Use the payment or commerce platform workflow and deadline. This template is only evidence organization.
Before you submit or send it for review.
Replace placeholders with the exact order, transaction, or dispute details.
Confirm every attachment is readable and tied to the disputed transaction.
Put the strongest reason-specific proof first: delivery, usage, authorization, cancellation, or refund records.
Remove unnecessary customer personal data before sharing drafts outside your platform workflow.
Do not add recovery guarantees, accusations, or platform claims you cannot support.
