Chargeback Response Letter Template: What to Check Before You Submit

The letter fails before the issuer reads it

Most lost disputes aren't evidence losses — they're structural losses. The merchant submitted real evidence, but it didn't map to the reason code. Issuers dismiss evidence that doesn't directly address the dispute type, and a well-organized package built around the wrong argument is still a losing package. Before you write a single sentence of your response letter, open Shopify Admin → Orders → select the order → View Chargeback Details and confirm the exact reason code. Everything in your letter — the narrative, the evidence sequence, the framing — has to answer that specific code, not the general situation.

The reason code also determines your deadline. Confirm the response window with your processor; Shopify Payments surfaces the deadline inside the dispute view, but third-party gateways may not. Missing the window by even one day closes the case regardless of how strong the evidence is. Check Shopify Protect status on the order as well — if the order shows PROTECTED, Shopify may cover the dispute liability directly, and submitting a manual response may be unnecessary. If it shows ACTIVE or NONE, you're responding on your own.

What the evidence actually proves — and where issuers push back

Three evidence types appear in nearly every response package, and all three carry the same structural problem: they prove something adjacent to what the issuer is actually asking.

AVS Y confirms that the billing address on file matched the cardholder's bank records at authorization. That's useful for establishing that the transaction wasn't a raw card-not-present guess. But issuers arguing an "Item Not Received" dispute will counter that AVS Y proves authorization, not possession — the cardholder may have placed the order and still not received the goods. Frame AVS Y as one layer of authorization evidence, not as proof of delivery, and pair it with something that gets closer to receipt.

Tracking marked "delivered" is the most commonly over-relied piece of evidence in fulfillment disputes. Delivery to the address on record meets the fulfillment requirement on paper, but issuers routinely argue that delivery to an address doesn't confirm receipt by the cardholder — particularly for high-value orders or when the cardholder claims the package never arrived. Carrier confirmation alone rarely saves a $500+ dispute. Pair tracking data with a signature confirmation, a customer-facing delivery photo if the carrier captured one, or a post-delivery communication from the customer acknowledging receipt.

Customer acknowledgment emails — order confirmations, shipping notifications, any reply from the cardholder — establish that the customer was aware of and accepted the order terms. They don't prove receipt or satisfaction. Issuers will accept them as supporting context but won't treat them as dispositive. Use them to establish the order timeline and customer engagement, then layer in the delivery and usage evidence on top. Visa and Mastercard may weigh these evidence types differently depending on dispute category and processor routing; confirm the specific requirements with your processor before finalizing the package.

A $750 electronics order, tracking delivered, case still weak

An electronics merchant receives a chargeback on March 10th for a $750 order, reason code "Item Not Received." The order was placed March 1st with AVS Y confirmed. It shipped March 2nd and tracking shows delivery to the cardholder's address on March 5th. The merchant has an order confirmation email, the invoice with full item description, AVS Y, and the tracking record. On paper, this looks like a winnable case.

The vulnerability is structural. Tracking proves delivery to the address — it does not prove the cardholder received the item. AVS Y supports that the billing address matched at authorization, but the issuer's question is whether the cardholder got the product, not whether the address was correct. The customer acknowledgment email confirms the order was placed and terms were accepted; it doesn't confirm receipt five days later. The invoice is clean and itemized, which helps establish what was sold, but it doesn't move the needle on the core dispute question.

The better response isn't more of the same evidence — it's different evidence. A signature on delivery, a carrier photo showing the package at the door, or a post-delivery email from the customer referencing the order would each get closer to proving cardholder receipt. If none of those exist, the merchant's letter needs to acknowledge the gap explicitly and lean on the cumulative weight of the authorization and delivery chain rather than overstating what the tracking record proves. Overstating the evidence is a fast way to lose credibility with the issuer reviewer.

The letter itself should open with a one-sentence statement of the dispute and the merchant's position, then walk the timeline in order — authorization, fulfillment, delivery — with each evidence item cited inline. Don't attach evidence and hope the reviewer connects the dots. The narrative has to do that work. Issuers favor organized, narrative-driven submissions that clearly address the chargeback reason; a stack of attachments without a connecting argument reads as disorganized, not thorough.

Decision lesson: This case was fightable with a signature confirmation or post-delivery customer communication. Without either, the tracking record proves fulfillment but not receipt — and "Item Not Received" disputes are decided on receipt, not shipment. The rule: if your strongest delivery evidence stops at the carrier scan, assess the order value against your win probability before spending the response window on a weak package.

What to check before you submit

Work through this in order. Skipping steps early creates gaps that show up in the letter.

First, confirm the dispute status and deadline inside Shopify Admin → Orders → the specific order → chargeback details. Note the exact reason code — not the category, the code. Then check Shopify Protect status on the order. PROTECTED means Shopify may handle liability; ACTIVE or NONE means you're building the response. Pull the tracking record from Admin → Orders → Add Tracking Information and verify the carrier scan shows delivery to the address on the order, not a redirect or hold. If the order was rerouted or held at a facility, note that — it changes the delivery argument. Download the invoice from Admin → Orders → Download Invoice and confirm it includes itemized descriptions, not just a line total. Vague invoices create openings for issuers to question what was actually sold.

Pull all customer communications from Admin → Orders → View Customer Communication. Look for any post-delivery message from the customer — even a complaint is useful because it confirms they received something. Then match your evidence package to the reason code specifically. "Item Not Received" requires proof of delivery to the cardholder. "Not as Described" requires proof the item matched what was advertised. "Unauthorized" requires authorization evidence. A package built for the wrong code loses regardless of quality. Finally, decide whether to fight or accept. If the order is under your dispute fee threshold and the evidence is thin, accepting may cost less than the response window. If Shopify Payments is the processor, confirm whether the dispute fee applies on acceptance. DisputeDesk handles evidence collation and pack assembly automatically; merchants still own the narrative — the letter's argument has to come from someone who knows what actually happened with the order.