Chargeback Letter: Merchant Template and Evidence Checklist

A chargeback letter is the merchant’s written explanation of why a disputed payment should stand. It connects the cardholder’s claim to transaction records and supporting evidence. Usually, this narrative belongs within the response submitted through your payment processor, alongside the required documents; it is not a separate letter you must send after responding.

A useful letter is specific, factual, and easy to check. Start with the actual claim, identify the amount under dispute, and explain what each attachment establishes. For the broader process, see our guide to how chargebacks work.

Check the Case Before Writing

Open the dispute in the processor’s dashboard and confirm the response deadline, time zone, reason, disputed amount, and required evidence fields. Read the cardholder’s explanation as well as the chargeback reason code. A delivery complaint and an unauthorized-payment claim need different answers, even when they concern the same order.

Decide whether the available facts support contesting the case. If the customer was charged incorrectly or a promised refund was never completed, escalating the operational problem may be more appropriate than defending the payment. Use your dispute handling procedures to assign that decision to an accountable owner.

Follow the submission rules for your processor. For example, Stripe’s official dispute response guidance says a submitted response cannot be edited and issuers do not review external links. Prepare the complete evidence package before final submission.

What to Include in a Chargeback Letter

Merchant Chargeback Letter Template

Replace every bracketed field below with verified case information. Remove sections that do not apply. If your processor separates the narrative into several fields, distribute the same facts across those fields rather than uploading duplicate explanations.

Re: Dispute [case ID], transaction [transaction ID], order [order ID]

Disputed amount: [amount and currency]

The cardholder reports [neutral summary of the claim]. We contest [amount and currency] because [specific reason supported by the records below].

On [date], [relevant transaction or service event]. On [date], [relevant fulfillment, cancellation, or customer communication event]. These records address the claim because [explain the connection without assumptions].

Attachment A: [record name], showing [specific fact]. Attachment B: [record name], showing [specific fact]. Attachment C: [record name], showing [specific fact, if relevant].

Refund or adjustment status: [none, pending, completed, or other verified status], with [amount, date, and reference where relevant].

Based on these records, we request reversal of [amount and currency] of the disputed debit. The supporting documents are included in the response package.

Match the Explanation to the Claim

For merchandise not received, identify the promised delivery details and the actual fulfillment record. A warehouse label proves a label was created; it does not establish delivery. Explain any split shipment, pickup arrangement, or replacement so the reviewer can connect the evidence to the disputed items. Our fulfillment and dispute evidence guide explains the operational records to preserve.

For a cancellation complaint, show the applicable terms, the customer’s acceptance where available, the cancellation request, and the billing timeline. Do not treat a general policy page as proof of what the customer saw. Subscription teams can use this renewal dispute prevention workflow to improve records before the next case.

For an unrecognized payment, include relevant transaction and customer interaction records without claiming that a delivery scan alone proves cardholder authorization. A purchase can be delivered and still involve unauthorized use. Read our guide to accidental friendly fraud for recognition problems that may be resolved through clear customer communication.

If a refund is relevant, state its actual status and reference. A refund request and a completed refund are different events. Review chargebacks received after a refund before describing the amount already returned.

Review and Submit the Complete Package

Read the letter against the attachments, not from memory. Confirm names, dates, currencies, and amounts. Remove statements such as “the customer is lying” or “all sales are final, so this dispute is invalid.” Replace them with the exact policy, action, or record that addresses the claim.

Use a standard evidence checklist while preserving the facts unique to this case. Submit through the authorized case workflow, record the confirmation, and monitor subsequent processor notices. Do not assume the issuer will telephone your team for missing evidence.

Foire aux questions

Does a Chargeback Letter Guarantee a Win?

No. A clear letter helps a reviewer understand the evidence, but the outcome depends on the claim, applicable rules, and supporting records. Strong wording cannot replace missing proof.

Should I Send the Letter Directly to the Customer’s Bank?

Use the submission channel specified by your processor or acquiring bank. Sending an unsolicited email or postal letter to the issuer does not establish that the response has entered the dispute workflow.

How Long Should a Chargeback Letter Be?

Use the shortest explanation that accurately connects the claim to the evidence. There is no universal page count. Follow the case’s field, file, and size limits, and remove repeated transaction history that does not support your position.

Explore Chargeflow’s automated chargeback recovery to organize evidence and manage supported responses.