Chargeback Lifecycle, Costs, and How to Respond

The dispute is already running before you see it

A cardholder calls their bank. The bank provisionally credits the account. The network routes a dispute to your acquirer. Your acquirer debits your account. Then — sometimes days later — Shopify surfaces it under Admin → Orders → Disputes. By the time you see the notification, the clock has been running for a while.

That lag is the first operational trap. Merchants treat the notification date as the start date. It isn't. The response window is measured from when the dispute was filed at the network level, not when it appeared in your dashboard. Confirm the exact deadline with your processor — do not assume the Shopify notification timestamp is your baseline.

This playbook covers the full lifecycle, the real cost structure, and the step-by-step response sequence. It's written for merchants who already know what a chargeback is and want to know what to actually do.

The lifecycle: what happens at each stage

Stage 1 — Cardholder initiates. The cardholder disputes a transaction with their issuing bank. The issuer assigns a reason code based on the cardholder's stated complaint. That reason code determines which network rules apply, what evidence is relevant, and how much time you have. The issuer provisionally credits the cardholder immediately in most cases — the money leaves your account before any evidence is reviewed.

Stage 2 — Chargeback filed. The issuer submits the dispute to the card network (Visa, Mastercard, Amex, Discover). The network routes it to your acquirer. Your acquirer debits your settlement account for the transaction amount plus a dispute fee. On Shopify Payments, this appears as a debit in your payout history. Third-party gateways handle this differently — some hold reserves, some debit immediately, some batch disputes monthly. Know your processor's mechanics.

Stage 3 — Merchant response window. You have a fixed window to submit evidence. Visa's standard is 20 calendar days from the dispute date; Mastercard varies by reason code — confirm with your processor. Miss the window and the issuer rules against you automatically, without reading a single document you submitted. This is the most common way merchants lose winnable cases.

Stage 4 — Issuer review. The issuer evaluates your evidence against the reason code's specific requirements. They are not reading your evidence to understand what happened — they are checking whether your submission satisfies the network's evidentiary standard for that code. A thorough evidence packet that answers the wrong question loses. A targeted packet that directly addresses the reason code's assertion wins more often.

Stage 5 — Decision. The issuer rules Won or Lost. If you lose, you can escalate to pre-arbitration or arbitration depending on the network and reason code — but arbitration is expensive (fees can reach $500+ per case, confirm with your processor) and rarely worth it on transactions under $300 unless you have a pattern of identical disputes from the same cardholder.

Stage 6 — Second presentment / pre-arbitration (optional). On some networks and reason codes, a second presentment is available. Visa's CE 3.0 framework changed how fraud disputes are handled — merchants with qualifying fraud tools can shift liability back to the issuer under specific conditions. This is not available on all dispute types and not automatic. Check whether your Shopify Payments setup qualifies.

What a chargeback actually costs

The transaction amount is the visible cost. It's not the full cost.

A $150 order that results in a lost chargeback typically costs:

• Transaction amount: $150 (debited at dispute filing)
• Dispute fee: $15–$25 on Shopify Payments; varies by processor — confirm yours
• COGS already shipped: product cost, fulfillment, shipping — not recoverable
• Staff time: evidence gathering, response writing, internal review — often 45–90 minutes per dispute
• Chargeback ratio impact: if your ratio exceeds network thresholds (Visa's standard program triggers at 0.9% monthly), you enter monitoring programs with additional fees and potential account termination

The ratio risk is the one merchants underweight. A single high-volume fraud event — a compromised card batch, a reshipping ring, a social media ad that attracted fraudulent buyers — can push a merchant into Visa's Dispute Monitoring Program or Mastercard's Excessive Chargeback Program within a single billing cycle. Recovery from those programs takes months and involves acquirer-imposed reserve requirements.

Friendly fraud compounds this. Cardholders who successfully dispute a transaction once are statistically more likely to do it again. There's no network-level mechanism that flags repeat friendly fraudsters to merchants — you have to build that list internally.

Reading the reason code before you do anything else

The reason code is the issuer's formal statement of what the cardholder is claiming. It maps to a specific network rule with specific evidentiary requirements. Responding to the wrong assertion — even with strong evidence — loses.

The three dispute types Shopify merchants see most often:

Fraud / Unauthorized Transaction (Visa 10.4, Mastercard 4837): The cardholder claims they didn't authorize the transaction. The issuer is asking: did the legitimate cardholder authorize this charge? Your evidence needs to address authorization signals — AVS match, CVV match, device fingerprint, IP geolocation, behavioral data — not just delivery confirmation. Delivery confirmation proves the package arrived; it doesn't prove the cardholder authorized the purchase.

Item Not Received / INR (Visa 13.1, Mastercard 4853-INR): The cardholder claims the item never arrived. Your evidence needs to show delivery — carrier confirmation with timestamp, signature if available, delivery address matching the billing address. If you shipped to a freight forwarder or reshipper address, this dispute is harder to win regardless of what the tracking shows.

Item Not as Described / SNAD (Visa 13.3, Mastercard 4853-SNAD): The cardholder claims the product differed materially from what was advertised. Your evidence needs to show your product listing, the specific claims made, and that the item shipped matched those claims. Screenshots of your Shopify product page at the time of purchase are more useful than current screenshots — if you've updated the listing since the order, that discrepancy can hurt you.

Step-by-step response playbook

Step 1: Open the dispute record first — not the order.

In Shopify Admin, go to Orders → Disputes. Open the dispute record. Read the reason code, the dispute amount, and the response deadline. Write down the deadline before you do anything else. The order is where merchants go to feel productive; the dispute record is where the case lives.

Step 2: Confirm the actual deadline.

The date shown in Shopify Payments is your working deadline. If you're on a third-party gateway, cross-reference with your processor portal — Shopify may not surface the exact network deadline. Build in a two-business-day buffer. A response submitted at 11:58 PM on the deadline date has failed before, due to timezone mismatches between processor systems.

Step 3: Triage — fight or concede.

Not every dispute is worth fighting. Run this check before you build anything:

• Is the transaction amount above your cost threshold to respond? (Factor in staff time — a $40 dispute that takes 90 minutes to fight at $50/hr labor cost is a net loss even if you win.)
• Do you have evidence that directly addresses the reason code's assertion?
• Is there any signal this is a legitimate complaint — wrong item shipped, delayed delivery, product defect?

If the answer to the second question is no, conceding is the operationally correct choice. Submitting weak evidence doesn't just lose — it wastes response time that could go to winnable cases.

Decision point: fight with full evidence or accept the loss

Path A — Fight. You have authorization signals, delivery confirmation, or product-match evidence that directly addresses the reason code. Proceed to evidence assembly. Time cost: 45–90 minutes. Win probability depends on evidence quality and reason code — fraud disputes are harder than INR disputes on average, because authorization evidence is more complex to assemble than delivery evidence.

Path B — Accept. The evidence is thin, the transaction amount is low, or the complaint appears legitimate. Accept the chargeback, issue a refund if not already processed, and log the case internally. Accepting a chargeback does not automatically trigger a refund — if you've already refunded the customer, document that in the dispute record to avoid a double debit. In Shopify Payments, you can note this in the dispute response field before closing.

The consequence of choosing Path A with weak evidence: you lose, pay the dispute fee, and spend staff time with no recovery. The consequence of choosing Path B on a winnable case: you forfeit the transaction amount unnecessarily. The triage step is where most merchants make the wrong call — either fighting everything reflexively or accepting everything to avoid the work.

Assembling the evidence stack

Pull these in order. Stop when you have enough to directly address the reason code — more evidence is not always better. An unfocused 15-document submission reads as noise to an issuer reviewer.

For fraud disputes:

1. Authorization record — AVS result, CVV result, 3DS authentication if applicable. Pull from Shopify Admin → Payments → Transaction detail.
2. Device and IP data — browser fingerprint, IP address at checkout, geolocation. If the IP is a VPN or proxy, note it but don't hide it — issuers can see this too.
3. Order history — has this cardholder ordered before without dispute? Same shipping address used in prior orders?
4. Delivery confirmation — carrier tracking with timestamp and delivery address. Signature confirmation if you have it.
5. Customer communication — any post-purchase emails, support tickets, or chat logs showing the cardholder engaged with the order.

For INR disputes:

1. Carrier tracking with delivery confirmation and timestamp.
2. Fulfillment date vs. order date — show the order shipped within your stated handling time.
3. Shipping address confirmation — matches billing address or was explicitly provided by the cardholder.
4. Any customer communication about the order status before the dispute was filed.

For SNAD disputes:

1. Product listing screenshots — title, description, images, specifications as they appeared at purchase. If your Shopify product page has been updated since the order, note the change and provide the original if available.
2. Photos of the item as shipped, if you have them.
3. Return policy — was it visible at checkout? Screenshot the policy page.
4. Any customer communication about the product before the dispute.

The messy case: a $310 electronics order with contradictory signals

A merchant sold a $310 wireless audio device. AVS matched. CVV matched. The shipping address matched the billing address. Delivery confirmation showed the package delivered to the correct address. The cardholder filed a Visa 10.4 fraud dispute three weeks after delivery.

The merchant submitted the full evidence stack — authorization record, delivery confirmation, order history showing two prior purchases from the same account with no disputes. Looked like a strong response.

The issuer ruled against the merchant. The reason: the IP address at checkout was a residential VPN exit node in a different state from the billing address. The issuer's fraud model flagged this as a potential account takeover — the legitimate cardholder's credentials used by a third party who had access to the account but not the physical card. The delivery confirmation proved the package arrived at the billing address; it didn't resolve the account takeover question.