Chargeback QA Checklist: Catch Weak Responses Before They Leave Your Queue

Most self-inflicted losses happen after the evidence is assembled

The order data was there. The tracking confirmed delivery. The IP matched. And the merchant still lost — because the narrative said "order was delivered" while the attached screenshot showed a different order number, and the carrier PDF was a 90KB blur that no analyst could read at 100% zoom.

QA failures are not evidence failures. They're submission failures. The checklist below is designed to catch them before the response leaves Shopify Admin → Orders → Disputes.

Prerequisites

• The dispute record is open and the reason code is confirmed — not assumed from the email notification.
• The response deadline is logged. Visa standard: 20 days from dispute date. Mastercard varies by reason code — confirm with your processor. Do not rely on Shopify's UI countdown alone; it can reflect acquirer-adjusted windows.
• A fight/concede decision has already been made. This checklist is for responses you've committed to submitting, not for triage.
• One person owns the final QA pass. Shared ownership means no one checks.

Phase 1: Reason Code Alignment

1. Confirm the exact reason code from the dispute record — not the category label. Visa 10.4 and 13.1 require different evidence stacks. Treating them the same is a top-five loss driver.
2. Verify your narrative directly addresses what the reason code asserts. If the code is INR (Visa 13.1), your narrative should lead with delivery proof — not authorization signals. If it's 10.4 unauthorized, lead with behavioral and device evidence — not just tracking.
3. Check that every claim in your narrative has a corresponding document attached. Underline or annotate each claim, then match it to a file. Unmatched claims are unsupported claims.

Phase 2: Document Integrity

1. Open every attached file. Confirm it renders. A PDF that opens as a blank page or a JPEG that loads as a gray box has happened in more submitted responses than any team admits.
2. Check file resolution. Screenshots of tracking pages should be legible at standard screen zoom. If you have to squint to read the delivery date, the issuer analyst will skip it.
3. Confirm each document shows the correct order. Order number, customer name, or shipping address should be visible in the document itself — not just in your narrative. An analyst matching documents to a case has no reason to assume a generic carrier screenshot belongs to this dispute.
4. Verify timestamps are visible and consistent. A delivery confirmation timestamped three days after the dispute date needs an explanation in the narrative, or it actively hurts the response.
5. Check that carrier tracking links are not the only delivery proof. Links rot. Static screenshots or carrier-issued PDFs are the submission-safe format.

Phase 3: Narrative Quality

1. Read the narrative as if you have no order context. If it references "the attached tracking" without specifying what the tracking shows, rewrite it. Analysts process volume — they do not infer.
2. Confirm the narrative is sequential. Authorization → fulfillment → delivery → customer contact (if applicable). Non-linear narratives force the analyst to reconstruct the timeline themselves. Most don't.
3. Remove hedging language. "We believe the order was delivered" is weaker than "Carrier confirmed delivery on [date] at [address], signature obtained." Belief is not evidence.
4. Check that the narrative does not introduce facts not supported by attached documents. A narrative that mentions a customer phone call with no call log attached creates a credibility gap, not a stronger case.
5. Confirm the narrative length is proportionate. A 600-word narrative for a $45 dispute with clean delivery confirmation is noise. A 90-word narrative for a $900 fraud dispute with contradictory signals is insufficient. Neither extreme helps.

Phase 4: High-Risk Signal Check

These are the conditions where otherwise solid responses fail at the issuer level. Check each one explicitly.

1. If the shipping address differs from the billing address, confirm the narrative addresses it. Silence on a known risk signal reads as evasion.
2. If the order used a freight forwarder or reshipper address, confirm you have documentation of the customer's explicit instruction to ship there. Without it, the issuer will treat the address anomaly as a fraud indicator regardless of delivery confirmation.
3. If AVS returned a partial match or no match, confirm your fraud response does not lead with AVS as a primary authorization signal. A partial AVS match used as a headline defense has lost disputes that had stronger supporting evidence buried underneath it.
4. If the customer contacted support before the dispute, confirm that communication is attached and the narrative references it. A customer who emailed "where is my order" two days before filing a chargeback is a meaningful signal — but only if it's in the file.
5. If the dispute involves a digital product or subscription, confirm the IP address, device fingerprint, and login/access logs are attached as separate documents — not embedded in a single screenshot. Issuers reviewing CE 3.0-eligible digital disputes weight these signals heavily; confirm CE 3.0 eligibility with your processor before relying on that pathway.

Phase 5: Final Submission Check

1. Confirm total file size is within your acquirer's submission limit. Shopify Payments has its own attachment constraints — check the active dispute record in Admin for any size warnings before submitting. Oversized bundles get truncated or rejected silently.
2. Verify the response is being submitted against the correct dispute ID. In high-volume queues, submitting evidence to the wrong dispute is rare but has happened — and the window to correct it may not exist.
3. Confirm the submission deadline has not passed. If it has, do not submit. A late response can reset the dispute clock against you depending on the network and acquirer. Confirm the exact consequence with your processor before attempting a late submission.
4. Log the submission timestamp internally. Shopify Admin records the submission, but an internal log with the submitting team member's name creates accountability and supports any escalation or arbitration review later.

Common Mistakes

• Submitting the narrative without reading it aloud or cold. The person who wrote it cannot catch its gaps. QA requires a second reader or a deliberate cold-read after a break.
• Attaching the right documents in the wrong order. Issuers read sequentially. Leading with a refund policy when the dispute is fraud-coded wastes the first impression.
• Assuming a previously won response template works for a new dispute. Reason codes, networks, and issuer behavior shift. A template that won six months ago may be misaligned with current network rules — confirm with your processor if you're reusing old formats.
• Skipping the document-open check under deadline pressure. Deadline pressure is exactly when corrupted files get submitted. Build the open-every-file step into the workflow as non-negotiable.
• Treating QA as optional for low-value disputes. Chargeback ratios count every loss equally. A $35 dispute lost to a blank PDF attachment counts the same as a $350 one.

Revisit When…

• Your win rate drops more than 5 percentage points over a rolling 60-day window — the checklist may have drifted from actual submission behavior.
• A new reason code type appears in your dispute queue that wasn't present when the checklist was built.
• Your processor or acquirer updates submission format requirements. These change without merchant-facing announcements.
• A post-loss review surfaces a document integrity failure — corrupted file, wrong order number, missing timestamp — that QA should have caught.
• Team composition changes. A checklist calibrated to one operator's judgment needs re-validation when a new person runs submissions.