Subscription Chargeback Shopify: The Evidence Stack for Recurring Billing Disputes

A renewal charge disputed three months in — do this before you open the order

A subscription chargeback lands in Shopify Admin → Orders → Disputes. The reason code says "not authorized" or "credit not processed." The instinct is to pull the billing history, screenshot six months of successful charges, and submit. That sequence loses a lot of otherwise-winnable cases.

Billing history proves the card was charged. It does not prove the cardholder consented to recurring charges at signup, understood the renewal terms, or received adequate notice before the disputed charge. Those are the three questions issuers actually ask. Answer them in that order.

Before you touch the order record, note the reason code and the response deadline. Visa 13.2 (Recurring Transaction) and Mastercard 4853 (Cardholder Dispute) are the most common codes for subscription disputes — and they have different evidentiary expectations. Visa 13.2 specifically requires proof that the cardholder authorized recurring billing. Mastercard 4853 often surfaces when a cancellation was requested but the charge still processed. Confirm the exact code in the dispute record — the response strategy branches from there.

Step 1: Pull consent documentation first

Consent is the load-bearing piece. Everything else is supporting context.

Locate the original order in Shopify Admin → Orders. Find the checkout timestamp and the subscription agreement the customer accepted at that session. What you need:

• A screenshot or export of the checkout page showing the recurring billing disclosure — the exact language, not a generic terms link
• The IP address and timestamp of the order (visible in the order's Timeline section)
• The confirmation email sent at signup, which should restate the billing cadence and amount
• If you use a subscription app (Recharge, Bold Subscriptions, Skio, etc.), pull the subscriber record showing the plan selected and the consent checkbox state at signup

The disclosure language matters more than most merchants realize. "By completing your purchase, you agree to our terms" does not establish recurring billing consent. "You authorize [Merchant] to charge $49/month to your card on file until you cancel" does. If your checkout language is vague, note that before you submit — it affects how hard to fight this dispute.

A merchant running a $29/month wellness subscription had six months of clean billing history, a confirmation email, and a delivery record for the physical welcome kit. They lost the Visa 13.2 dispute because the checkout disclosure read "subscription pricing applies" with no dollar amount, no cadence, and no cancellation terms. The issuer sided with the cardholder. The billing history was irrelevant once consent failed.

Step 2: Map the dispute reason to the actual complaint

Subscription chargebacks cluster into three real complaints, regardless of what the reason code says:

1. "I never agreed to recurring charges" — consent dispute. Your evidence is the checkout disclosure and signup confirmation.
2. "I canceled and was charged anyway" — cancellation failure dispute. Your evidence is the cancellation flow record and whether the charge processed before or after the cancellation timestamp.
3. "I didn't recognize this charge" — descriptor confusion. Your evidence is the billing descriptor match and any reminder emails sent before the charge.

Misreading the complaint type produces a response that answers the wrong question. A merchant who submits billing history and delivery confirmation against a cancellation dispute has not addressed what the issuer is evaluating. Read the cardholder's stated reason in the dispute record — it often contains plain-language context beyond the code.

Step 3: Pull the cancellation flow record

If the dispute involves a cancellation claim, this is where most merchants either win or lose operationally.

Pull from your subscription platform: the cancellation request timestamp, the confirmation sent to the customer, and the date the subscription status changed to inactive. If the disputed charge processed after the cancellation timestamp, you have a problem — and fighting the dispute is unlikely to succeed. Refund and close. If the charge processed before the cancellation request, document that sequence explicitly.

What to include in the evidence file:

• Cancellation confirmation email (with timestamp)
• Subscription platform export showing status change date
• The disputed charge date relative to the cancellation date — stated explicitly in your narrative, not left for the issuer to calculate

If your cancellation flow requires multiple steps — a survey, a retention offer, a confirmation click — document each step the customer did or did not complete. Some issuers treat multi-step cancellation flows skeptically if the customer claims they attempted to cancel and couldn't complete the process. If your flow has friction, acknowledge it in the narrative rather than presenting a clean record that contradicts the cardholder's experience.

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

When a dispute contains elements of both a consent claim and a cancellation claim, merchants often try to address both simultaneously. That produces a diluted response.

Path A — Fight on consent: The cardholder claims they never agreed to recurring billing. You have clear checkout disclosure language, a timestamped confirmation email, and no cancellation request on record. Lead with consent documentation. Billing history is secondary. This path has the strongest win probability when the consent record is clean.

Path B — Fight on cancellation timing: The cardholder claims they canceled but were charged. You have a cancellation request timestamp that postdates the disputed charge. Lead with the timeline — cancellation came after the charge, charge was valid at processing time. Include the cancellation confirmation you sent and the refund or termination you processed after. This path works when the sequence is unambiguous.

Trying to argue both simultaneously signals to the issuer that you're not sure which assertion to rebut. Pick the stronger path. If the cancellation record is messy and the consent record is clean, fight on consent. If consent language is weak but the cancellation timeline is clear, fight on timing.

Step 4: Assemble the renewal notice and reminder email record

For annual subscriptions especially, renewal notice emails are often the difference between a won and lost dispute. A cardholder who disputes a $299 annual renewal charge and claims they didn't know it was coming is making a notice claim, not just a consent claim.

Pull from your email platform (Klaviyo, Mailchimp, or whatever you use):

• The renewal reminder email — sent date, recipient address, subject line, and the renewal amount stated in the body
• Open/click data if available — not required, but useful if the cardholder claims they never received it
• The billing descriptor that appeared on their statement — confirm it matches your store name or a recognizable variant

Visa's rules for recurring transactions (confirm specifics with your processor, as network rules update) generally require that merchants notify cardholders before charging a stored credential for a renewal, particularly for annual billing cycles. If you sent a reminder 7–10 days before the charge, document it. If you didn't send one, that's a gap the issuer may weigh against you.

Sample evidence narrative line for a renewal dispute:
"The cardholder enrolled in an annual subscription on [date] at [amount]/year. A renewal notice was sent to [email address] on [date], 10 days prior to the [charge date] renewal charge of [amount]. The email confirmed the renewal amount, the charge date, and the cancellation link. No cancellation request was received prior to the charge processing."

Write this before you attach anything. The narrative tells the issuer what to look for in the files. Without it, they're reading screenshots without context.

Step 5: Build the billing history as context, not as the lead

Billing history belongs in the response — but as corroborating context, not the primary argument. A clean 8-month billing record with no prior disputes does two things: it shows the cardholder used the subscription without complaint, and it establishes that the disputed charge is consistent with prior authorized charges.

Export from Shopify Admin → Orders (filter by customer) or from your subscription platform. Include:

• Charge dates and amounts for the full subscription lifecycle
• Any refunds processed and why
• The disputed charge highlighted in the sequence

One line in the narrative: "The cardholder has been billed [amount] on the [Xth] of each month since [start date], with no prior disputes or refund requests. The disputed charge on [date] is consistent with all prior billing."

That's enough. Don't over-explain the billing history. The issuer can read a table.

The $47/month SaaS dispute that had everything and still had a problem

A merchant running a project management SaaS submitted a Visa 13.2 response with: six months of billing history, a signup confirmation email, a cancellation confirmation (the customer had canceled two weeks after the disputed charge), and a renewal reminder sent five days before the charge.

They lost. The issuer's feedback cited the checkout disclosure — the merchant's signup page had a checkbox labeled "I agree to the Terms of Service" with a hyperlink, but the recurring billing terms were buried in section 14 of a 22-section ToS document. The disclosure was not presented inline at checkout. The cardholder's claim that they didn't understand they were signing up for recurring billing was plausible given the checkout structure.

The billing history, the reminder email, the cancellation record — all of it was irrelevant once the issuer determined that the initial consent capture was insufficient. The merchant had operationally clean records of everything except the one thing that mattered first.

The fix isn't complicated: inline disclosure at checkout, restated in the confirmation email, with the billing amount and cadence explicit. But it has to be in place before the dispute, not after.

What to check in Shopify Admin before you submit

Run this before finalizing any subscription dispute response:

• Orders → [Order] → Timeline: Confirm the original order timestamp, IP, and any customer notes or contact history logged against the order
• Orders → [Order] → Subscription details (if using a native Shopify subscription app): Pull the plan name, billing interval, and next billing date as of the disputed charge
• Customers → [Customer] → Order history: Export the full billing sequence for the narrative
• Orders → Disputes → [Dispute]: Confirm the reason code, the response deadline, and whether Shopify Payments has pre-populated any evidence fields — review those fields before accepting them, they sometimes pull generic order data that doesn't address the specific dispute type

Shopify Payments surfaces some evidence automatically in the dispute response form. For subscription disputes, the auto-populated fields often include the order confirmation and billing address — useful, but not sufficient. Add the consent documentation, the renewal notice, and the cancellation record manually. The platform won't pull those from your email tool or subscription app.

Internal note before you close the workflow

After submitting, log this in the order Timeline or your dispute management tool:

"Dispute [ID] submitted [date]. Reason code: [code]. Response strategy: [consent / cancellation timing / renewal notice]. Evidence submitted: checkout disclosure screenshot, confirmation email, renewal reminder [date], billing history [X months], cancellation record [if applicable]. Decision: fought / conceded. Follow-up: [date]."

This note matters when the same customer disputes again, when a pattern emerges across multiple subscribers, or when a processor asks for dispute history context during an account review. Subscription merchants with high dispute rates get flagged — documented response records demonstrate that disputes are being managed, not ignored.

Where subscription dispute responses most commonly fail

Not evidence gaps — sequencing failures. Merchants submit billing history as the primary argument when the issuer is asking about consent. They attach a cancellation confirmation without stating the date relationship to the disputed charge. They include a renewal reminder email without noting that it was sent before the charge processed.

The evidence exists. The narrative doesn't connect it. Issuers read dozens of dispute responses. A response that makes them calculate the timeline themselves, or hunt for the consent language in a ToS screenshot, is a response that loses on friction alone.

Write the narrative first. Attach the files second. Every file should be referenced in the narrative before the issuer sees it.