Organized ecommerce dispute evidence packet on a desk

Merchant dispute response template

Chargeback rebuttal letter template.

Use a concise rebuttal structure before you assemble the full evidence packet: merchant position, transaction facts, timeline, attachment index, and final boundary note.

Use the template Generate a rebuttal Check draft free View example Instant kit - $7 Review this letter - $9 Rebuttal queue - $149

Start with the facts the reviewer can verify.

A rebuttal letter should not argue every detail. It should orient the reviewer to the disputed transaction and point to the evidence that answers the cardholder claim.

Agencies or support teams handling several rebuttal drafts can use the $149 10-pack instead of buying one review at a time.

Team 10-pack - $149
Merchant 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] Merchant position The merchant position is that the attached records support the response to this dispute. The evidence connects the disputed transaction to the order, fulfillment or service record, customer-facing policy context, and 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 merchant asks the reviewer to consider the attached records together. The packet is organized to show what was purchased, how the merchant fulfilled or responded, and how each attachment supports the merchant response to the dispute. 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 the letter short

The rebuttal is a map to the evidence. Avoid long emotional arguments or claims the documents do not prove.

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 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 evidence first, especially delivery, usage, authorization, or refund proof.
  • Remove unnecessary customer personal data before sharing drafts outside your platform workflow.
  • Do not add recovery guarantees, accusations, or platform claims you cannot support.