Chargeback First Moves: How to Read the Dispute, Check the Clock, and Not Lose Before You Start

The first 48 hours determine more outcomes than the evidence does

A chargeback appears in Shopify Admin → Orders → Disputes. The instinct is to open the order, pull the tracking number, and start assembling screenshots. That sequence is backwards — and it's how winnable disputes get lost before a single file is uploaded.

The correct sequence: read the dispute type, lock the deadline, triage the reason code, then decide whether to fight. Evidence comes after all of that. Merchants who reverse the order spend time building responses that don't address what the issuer is actually evaluating.

This playbook runs through that sequence in order. It's written for a merchant who just saw a new dispute appear and needs to know exactly what to do next.

Step 1: Identify what you're actually looking at

Not every dispute in Shopify is a chargeback. Some are inquiries — pre-dispute clarification requests that carry a shorter response window and a different consequence for non-response. An inquiry that goes unanswered auto-converts to a full chargeback. A chargeback that goes unanswered becomes an automatic loss.

In Shopify Admin → Orders → Disputes, the dispute type is labeled. Read it before anything else. If it says "inquiry," your window is likely 20–30 days — shorter than a standard chargeback response window, and the clock started when the dispute was created, not when you noticed it.

If it's a chargeback, note the network. Visa, Mastercard, Amex, and Discover each run different timelines and different arbitration rules. Shopify Payments surfaces the network in the dispute detail panel. Third-party gateways may not — confirm with your processor if the network isn't visible.

Operational note: Shopify Payments disputes are managed through the Admin dispute interface. If you're running a third-party gateway like Stripe or Braintree alongside Shopify, those disputes live in the gateway's own dashboard — not in Shopify Admin. Merchants running split payment setups miss disputes because they're checking the wrong dashboard.

Step 2: Lock the deadline — then back it up by two business days

The response deadline shown in Shopify Admin is the network deadline — the last possible moment the processor will accept a submission. That is not your working deadline.

Set your internal cutoff two business days before the displayed deadline. That buffer absorbs: file upload failures, evidence that needs to be pulled from a third-party system, internal review delays, and the occasional Shopify Admin session timeout mid-upload.

Visa's standard merchant response window is 30 days from dispute creation. Mastercard's is also 30 days in most cases, but some reason codes carry tighter windows — confirm with your processor for the specific code. Amex disputes can run shorter, sometimes 20 days. The deadline in Shopify Admin reflects your processor's interpretation of the network rule, which may already include a buffer — or may not.

Write the deadline down. Put it in your internal ticket, your Slack thread, your spreadsheet — wherever your team tracks open disputes. Do not rely on Shopify's notification system as your only reminder. Notification emails get buried. Disputes expire quietly.

Sample internal note: "Dispute [order #] opened [date]. Network deadline: [date]. Internal submission cutoff: [date minus 2 business days]. Reason code: [code]. Assigned to: [name]."

Step 3: Read the reason code before you open the order

The reason code tells you what the issuer is evaluating. It does not tell you what actually happened. Those are different problems, and conflating them is the most common first-move error.

A reason code of "item not received" means the issuer is asking whether the merchant can prove delivery — not whether the merchant shipped the item. A reason code of "unauthorized" means the issuer is asking whether the transaction was authorized by the cardholder — not whether the order looks legitimate to you.

Map the reason code to the specific question the issuer is asking before you touch the order record. Then open the order and evaluate whether your evidence actually answers that question.

Common Shopify merchant reason codes and what they're actually asking:

• Visa 13.1 / Mastercard 4855 — Item not received: Can you prove the goods were delivered to the cardholder's address? Tracking showing "delivered" is necessary but not always sufficient — especially if the shipping address is a freight forwarder or the delivery was to a building lobby.
• Visa 10.4 / Mastercard 4837 — Unauthorized transaction: Can you prove the legitimate cardholder authorized the charge? AVS and CVV match help but don't close the case alone. Behavioral signals — device fingerprint, IP consistency, account history — carry more weight than most merchants expect.
• Visa 13.3 / Mastercard 4853 — Not as described: Can you prove the item delivered matched what was advertised? Product description, photos, and any pre-sale communication are the core evidence. Return policy and any customer service exchange matter here too.
• Visa 13.6 / Mastercard 4853 — Credit not processed: Did you issue the refund? If yes, when? If no, why not? This is often the easiest dispute to resolve — and the one merchants most frequently fight unnecessarily.

Decision point: Fight or concede — before you build anything

This is the most consequential decision in the chargeback workflow, and most merchants make it too late — after they've already spent time assembling evidence.

Path A: Concede. Accept the dispute and issue the refund (if not already processed). The chargeback fee is typically non-refundable regardless — confirm with your processor, but on Shopify Payments it's $15 per dispute and not returned on concession. Conceding costs you the transaction and the fee. It does not cost you a dispute ratio hit in the same way a lost fight does, because the outcome is recorded differently by some networks. More importantly, it costs you zero time — time you can redirect to disputes you can actually win.

Concede when: the cardholder has a legitimate complaint, the evidence is weak, the transaction amount is under your cost-to-fight threshold, or the reason code doesn't match your available evidence.

Path B: Fight. Build and submit a response. This path costs time, carries no guarantee, and — if you lose — still results in the chargeback fee plus the transaction loss. Fighting a dispute you can't win also consumes response capacity that could go toward disputes you can win.

Fight when: you have direct evidence that answers the specific question the reason code is asking, the transaction amount justifies the time investment, and the dispute pattern doesn't suggest a customer relationship you want to preserve.

The threshold question most merchants skip: What's your cost to build and submit a response? If it's 45 minutes of staff time plus review, that's real cost. A $40 dispute with weak evidence is almost always a concede. A $400 dispute with strong delivery confirmation and behavioral signals is almost always a fight.

Step 4: Pull the evidence stack — in reason-code order, not chronological order

Once you've decided to fight, pull evidence in the order the issuer will evaluate it — starting with whatever directly answers the reason code question.

For an "item not received" dispute: start with the delivery confirmation, then the fulfillment record, then the order details. Don't open with the order confirmation email — the issuer already knows the order was placed.

For an "unauthorized" dispute: start with the authorization signals (AVS result, CVV match, 3DS if applicable), then behavioral evidence (IP address, device, account history), then fulfillment. The authorization stack is what the issuer is evaluating first.

In Shopify Admin, the order timeline shows fulfillment events, tracking updates, and customer communication. Screenshot the timeline — it's often the clearest single-frame view of what happened and when. For Shopify Payments, the payment details panel shows AVS and CVV results. Pull those before you close the order view.

Third-party fulfillment data — carrier tracking pages, 3PL delivery confirmations — needs to be pulled from outside Shopify. Do this before the carrier's tracking record ages out. Some carriers purge delivery event data after 90–120 days. If the dispute is on a transaction from two months ago, pull the tracking record now.

The $220 home goods dispute that was winnable and wasn't

A merchant sold a $220 ceramic planter set. Shipped via UPS with tracking. Delivered to the address on file — confirmed by UPS with a delivery scan. The cardholder filed a Visa 13.1 (item not received) dispute three weeks after delivery.

The merchant had the tracking confirmation. They also had a partial AVS match (ZIP matched, street address didn't) and a shipping address that was a residential building with a package room — not a freight forwarder, but not a direct-to-door delivery either.

The merchant submitted the UPS tracking confirmation as the primary evidence, added the order confirmation email, and submitted. Lost.

The issuer's note on the loss: delivery to a building package room without signature confirmation was insufficient for a disputed high-value item. The partial AVS match added doubt. The merchant had a UPS signature-required option available at checkout and hadn't used it.

The winnable version of this response would have included: the UPS delivery scan with timestamp, a screenshot of the building's package room policy (publicly available on the building's website), a note that the cardholder had received three previous orders at the same address without dispute, and a request for the cardholder to check with building management. None of that was in the submission.

The merchant lost not because the evidence didn't exist — it did — but because the response didn't address the issuer's actual concern: was the package accessible to the cardholder, or just delivered to a building?

Step 5: Write the narrative before you attach files

The evidence narrative — the written explanation in the response — is read before the attachments. Issuers reviewing dozens of disputes per shift will read the narrative first and use it to decide how much attention to give the attached files.

A narrative that says "please see attached tracking information" is not a narrative. It's a file index. It tells the issuer nothing about why the evidence answers their question.

Write two to four sentences that directly answer the reason code question, reference the specific evidence attached, and address any contradictory signals proactively. If there's a partial AVS match, name it and explain it. If the shipping address is a freight forwarder, address it. Issuers notice contradictions — if you don't explain them, they'll weigh them against you.

Sample evidence narrative (item not received, confirmed delivery):
"The cardholder's order was fulfilled on [date] and delivered to the address provided at checkout on [date] per the attached UPS delivery confirmation (tracking #[number]). The delivery scan shows [time] delivery to [address]. This is the cardholder's third order to this address; previous orders [order #s] were delivered without dispute. No return or non-delivery contact was received prior to this dispute filing. Full order timeline and fulfillment record are attached."

That narrative answers the question, references the evidence, and preempts the "but did the cardholder actually receive it" objection with behavioral history. It takes three minutes to write and meaningfully changes how the issuer reads the attached files.

Step 6: Submit — then log what you submitted and why

After submission, log the dispute outcome in your internal system before you close the workflow. Not just "submitted" — log what evidence you included, what the reason code was, what the narrative said, and what your confidence level was.

That log becomes your postmortem data. When you lose a dispute six weeks from now, you'll want to know whether you lost because the evidence was weak, because the narrative didn't address the right question, or because the issuer ruled against a category of evidence you're relying on repeatedly.

Merchants who don't log submissions can't improve their win rate systematically. They fight the same losing disputes the same way, repeatedly, because they have no record of what failed and why.

DisputeDesk automates the evidence assembly and submission workflow — but the internal log is still a merchant responsibility. Automation improves consistency, not certainty. The postmortem is where the consistency compounds.

Sample post-submission log entry: "Dispute [order #] submitted [date]. Reason code: Visa 13.1. Evidence: UPS delivery confirmation, order timeline screenshot, customer order history (3 prior orders same address). Narrative: addressed delivery scan and behavioral history. Confidence: medium — no signature confirmation. Outcome TBD by [expected decision date]."

The chargeback fee is a sunk cost — stop letting it drive the fight decision

On Shopify Payments, the dispute fee is $15 and non-refundable regardless of outcome. On third-party gateways, fees vary — confirm with your processor, but $15–$25 is the common range for card-not-present disputes.

Merchants frequently fight disputes they should concede because they're trying to "recover" the fee. The fee is gone either way. The only variable is whether you also spend 45 minutes building a response that loses. Fight decisions should be driven by evidence strength and transaction value — not by fee recovery logic that doesn't hold up mathematically.