Chargebacks Dispute: The Subscription Merchant Playbook

When the dispute lands, the first question is not what happened — it's what the cardholder is asserting

A subscription chargeback hits Shopify Admin under Orders > Disputes. The instinct is to pull the billing history, screenshot the confirmation email, and submit. That sequence loses a lot of winnable cases — not because the evidence is wrong, but because it answers the wrong question.

Subscription disputes split into three distinct assertions, and each one requires a different response stack:

• "I never authorized recurring billing" — the cardholder claims the original transaction didn't establish a recurring relationship
• "I canceled and was charged anyway" — the cardholder claims they ended the subscription before the disputed charge
• "I didn't recognize this charge" — softer version of unauthorized; often resolves with a single clarifying call to the issuer, but not always

Misreading which assertion you're facing is the most common reason subscription merchants lose disputes they should win. A billing-history screenshot is strong evidence for a cancellation dispute. It's nearly irrelevant for an authorization dispute.

Pull the reason code from Shopify Admin before you touch the evidence. Visa 13.2 (Cancelled Recurring) and Mastercard 4853 (Cardholder Dispute — Not as Described or Cancelled) both cover subscription scenarios but weight evidence differently. Visa 13.2 specifically requires proof that the cancellation policy was disclosed at signup and that the cardholder was notified before the disputed billing cycle. Mastercard 4853 is broader — confirm the exact sub-reason with your processor, because the evidence bar shifts.

Step 1: Map the reason code to the actual assertion before you open the order

Don't start with the order. Start with the reason code and the cardholder's stated reason in the dispute record.

In Shopify Admin under Orders > Disputes, the dispute detail view shows the reason code and, for most processors, a brief cardholder statement. Read that statement literally. "I don't remember signing up" is an authorization dispute. "I canceled in March" is a cancellation dispute. "This charge is too high" is a billing dispute — different reason code, different evidence entirely.

Write down the assertion in one sentence before you pull a single screenshot. That sentence becomes the first line of your response narrative.

Sample internal note: Cardholder asserts cancellation prior to 4/12 charge. Reason code Visa 13.2. Need: cancellation policy at signup, notification email sent before billing, confirmation that no cancellation request exists in our system on or before 4/11.

Step 2: Check the deadline before you check anything else

Shopify Payments surfaces the response deadline in the dispute detail view. Third-party processors vary — some push deadline data through to Admin, some don't. If you're on a third-party processor and the deadline isn't visible in Admin, check your processor dashboard directly and log it manually.

Subscription disputes frequently arrive late relative to the billing date. A cardholder who was charged in January may not file until March. That gap doesn't extend your response window — your deadline runs from when the dispute was filed, not when the charge occurred. Merchants who assume they have more time because the original charge was months ago miss deadlines at a higher rate than any other merchant type in the subscription category.

Set the deadline in your internal system the moment the dispute lands. If you're using DisputeDesk, the deadline is flagged automatically — but the review still requires a human decision on whether to fight or concede before automation can build the response package.

Step 3: Pull the authorization evidence stack — and know where it stops

For subscription disputes, the authorization stack has a specific shape:

1. Signup confirmation — timestamped email or order confirmation showing the cardholder agreed to recurring billing at a specific amount and cadence
2. Cancellation policy disclosure — the exact language shown at checkout or signup, not a link to a policy page. A screenshot of the checkout page with the recurring terms visible is stronger than a URL.
3. Pre-billing notification — if your billing cadence requires advance notice (some card network rules and state laws require this; confirm with your processor for your specific plan type), the sent notification with timestamp
4. Billing history — all charges on the account, not just the disputed one. Prior cycles that weren't disputed are behavioral evidence that the cardholder knew about the subscription.
5. Cancellation request log — a system export showing no cancellation request was received before the disputed charge, or showing the request was received after the charge date

The stack fails most often at item 2. Merchants can prove the cardholder signed up. They can't always prove the recurring terms were visible and unambiguous at the moment of signup. If your checkout flow buries the recurring disclosure below the fold or in a tooltip, that's a structural vulnerability that will cost you disputes regardless of how clean the rest of your evidence is.

The $67/month SaaS dispute that had billing history and still lost

A Shopify merchant running a SaaS product on a monthly subscription received a Visa 13.2 dispute for a $67 charge. The cardholder claimed they had canceled. The merchant had:

• Six prior billing cycles, none disputed
• A signup confirmation email
• No cancellation request in the system

What the merchant didn't have: a screenshot of the checkout page showing the recurring billing disclosure. The policy existed — it was linked in the footer of the signup page — but the merchant couldn't produce a contemporaneous capture of what the cardholder actually saw at signup. The issuer ruled for the cardholder.

The prior billing cycles were treated as circumstantial. The issuer's position: the cardholder may have been unaware the subscription was active, regardless of prior charges. Without proof that the recurring terms were affirmatively disclosed at signup, the authorization assertion held.

The merchant lost a winnable case because the evidence gap was structural, not operational. No response workflow fixes a checkout that doesn't surface recurring terms clearly.

Decision point: Fight on authorization or fight on cancellation — not both

When a subscription dispute contains elements of both an authorization claim and a cancellation claim, merchants frequently try to address both. That's a mistake. A response that hedges across two assertions reads as uncertain to the issuer and dilutes the strongest argument.

Path A — Fight on authorization: Lead with the signup confirmation and checkout disclosure. The argument is that the cardholder knowingly entered a recurring billing relationship. Billing history supports this. Use this path when you have a clear checkout capture and the cardholder's claim is "I never agreed to recurring billing."

Consequence: If the issuer finds any ambiguity in your disclosure, the case collapses entirely. No fallback.

Path B — Fight on cancellation: Lead with the cancellation log showing no request was received before the disputed charge. The argument is that the subscription was active at the time of billing. Use this path when the cardholder's claim is specifically "I canceled" and you have a clean system log.

Consequence: If the cardholder produces a cancellation confirmation you didn't capture (a chat transcript, a support ticket), the case collapses. Audit your support channels before committing to this path.

Pick one. Build the entire response around it. The other evidence can appear as supporting context, but the narrative should have a single spine.

Step 4: Write the response narrative before you attach files

The narrative is not a cover letter. It's a one-paragraph argument that tells the issuer exactly what you're proving and why it resolves the dispute. Issuers read dozens of responses. A response that opens with "We are a subscription company and the customer signed up on..." loses the reader immediately.

Write the argument first. Then attach the files that prove it.

Sample response narrative (cancellation path):

The cardholder's account shows no cancellation request prior to the April 12 charge. Our system log (attached) records all cancellation requests with timestamps. The most recent activity on this account before April 12 was a login on April 3. The charge was valid under the active subscription terms the cardholder agreed to at signup on January 8 (signup confirmation attached). We request reversal of the dispute.

That's 68 words. It names the assertion, points to the evidence, and closes with a request. Don't add more.

Step 5: Sequence the evidence in issuer-readable order

Attach files in the order the narrative references them. If the narrative leads with the cancellation log, that's the first attachment. If it leads with the signup confirmation, that goes first.

Label files explicitly: cancellation-log-export-2024-04-11.pdf, not screenshot1.png. Issuers reviewing high volumes of disputes spend seconds per attachment. Unlabeled files get skipped.

For Shopify Payments disputes, the file upload interface is in the dispute detail view under Orders > Disputes. File size limits apply — confirm current limits in Shopify Admin, as they've changed. If your cancellation log is a large CSV, convert it to a filtered PDF showing only the relevant account.

The cancellation email that merchants forget to send — and then can't prove they sent

Many subscription platforms send a cancellation confirmation email when a subscriber cancels. That email is evidence. But it only helps you if you can produce it — and many merchants can't, because their email service provider purges logs after 30–90 days.

If a cardholder claims they canceled and you have no cancellation request in your system, check whether a cancellation confirmation email was ever sent. If one was sent, it means a cancellation was processed — and the dispute timeline matters. If the cancellation was processed after the disputed billing date, the charge was valid. If it was processed before, you may owe a refund and the dispute is legitimate.

Merchants who skip this check and submit a "no cancellation request found" response — when a cancellation confirmation email exists in their own outbox — hand the cardholder a winning counter-argument.

Before you submit: pull the outbound email log for the cardholder's address. Filter for cancellation-related subject lines. If anything surfaces, read it before you commit to a response path.

When to concede without submitting a response

Concede immediately when:

• Your checkout flow doesn't have a clear, visible recurring billing disclosure
• The cardholder has a cancellation confirmation email you sent them
• The charge occurred after a cancellation request that your system logged but your billing platform didn't process correctly
• The dispute amount is under your internal fight threshold and the evidence is ambiguous

A conceded dispute still costs you the chargeback fee in most cases, but it doesn't cost you the dispute ratio hit that comes from a lost fight. Subscription merchants with high dispute volumes need to protect their ratio more than they need to win individual cases. Confirm your processor's dispute ratio thresholds — Visa and Mastercard both have program triggers, and the thresholds differ.

DisputeDesk flags concede candidates based on evidence completeness scoring, but the final call on high-ambiguity cases stays with the merchant. Automation improves consistency on clear-cut cases; it doesn't replace judgment on the ones that sit in the middle.