How to Win Subscription Chargebacks on Shopify: A Merchant's Guide

Why subscription chargebacks are different

When a customer disputes a standard order — a one-off product purchase — the dispute is usually about whether they received what they paid for. Tracking information, delivery confirmation, and product photos are often enough.

Subscription disputes work differently. The customer is not claiming they did not receive anything. They are claiming one of the following:

• They cancelled the subscription before the charge date.
• They did not know the subscription would renew automatically.
• The subscription was supposed to end after a trial or fixed term, but continued charging.
• They never agreed to the recurring billing in the first place.

These claims are evaluated by card issuers against a different set of criteria. Delivery proof addresses none of them. To win a subscription dispute, you need to address the specific claim being made — and that requires documentation most merchants do not have ready.

Common reason codes you will see

When a subscription chargeback is filed, Shopify (or your acquirer) will display a reason code. The most common ones for recurring billing disputes are:

Each reason code points to a different type of evidence. A "subscription cancelled" dispute requires you to prove the subscription was still active at the charge date. A "not recognised" dispute requires you to show the customer was informed about recurring billing before they signed up.

Reading the reason code carefully before building your response saves time and improves your win rate.

What card issuers actually want to see

Card network rules (Visa, Mastercard) give card issuers guidelines for evaluating subscription disputes. In practice, a strong dispute response needs to address three questions:

1. Was the subscription active at the time of billing?

You need to show that the disputed subscription had not been cancelled before the charge date. A clear subscription timeline — with signup date, renewal dates, and the current status at billing — is the most direct way to answer this. Screenshots from your subscription app (Shopify Subscriptions, Recharge, Appstle) showing the subscription status on the billing date are useful here.

2. Was the customer informed about recurring billing?

The customer is claiming they did not agree to continue paying, or did not know they would be charged again. To rebut this, you need to show:

• The billing terms were clearly presented at checkout (recurring billing schedule, price, cancellation method).
• What your subscription and refund policy pages said at the time of their original purchase.
• Any renewal reminder emails sent before the disputed billing date.

This last point is increasingly important. A reminder email sent before billing is direct evidence that the customer had an opportunity to cancel before the charge.

3. Could the customer easily cancel?

If your cancellation process requires customers to contact support, navigate a complex account menu, or take many steps, this weakens your position. Card issuers look unfavourably on difficult cancellation flows. Evidence that your cancellation process is accessible — a direct link in the reminder email, a visible cancel button in the customer portal — helps your case.

Building your dispute packet

A dispute packet is the collection of evidence you submit to your card acquirer in response to a chargeback. For subscription disputes, a strong packet typically contains:

1. A short narrative (1 page maximum)
   A plain-English summary of the facts: when the customer subscribed, what they agreed to, which subscription was and was not cancelled, and why the charge was valid. Write this for a reviewer who knows nothing about your business. One clear page is better than ten pages of attachments without context.
2. Subscription timeline
   A chronological log: signup date, each renewal date, billing date, cancellation date (if any), and which subscriptions were active at the disputed billing date. If the customer had multiple subscriptions and only cancelled one, show this explicitly.
3. Checkout confirmation or order history
   The original order confirmation showing the customer agreed to recurring billing. If your checkout displayed the billing terms clearly, include a screenshot.
4. Renewal reminder email evidence
   Proof that a renewal reminder was sent before the disputed billing date — ideally showing the send date, the recipient, and the email content. If your subscription app logs delivery receipts, include these.
5. Policy page snapshot at the billing date
   A dated export or screenshot of your Terms of Service, Subscription Policy, and Refund Policy as they existed at the time of the disputed charge. This is a critical piece that many merchants cannot provide quickly — see the next section.
6. Delivery confirmation
   Tracking and delivery proof for the disputed order. This alone will not win a subscription dispute, but it addresses the "not received" element and removes one potential counterargument.
7. Prior order history
   If the customer has successfully renewed and received previous orders, this demonstrates a pattern of accepted billing. A table showing previous orders, dates, and amounts is simple and effective.

Submit these as a single PDF or organised attachment, not a collection of unrelated screenshots. A reviewer spending two minutes on your packet should be able to answer all three questions above without searching.

The policy documentation problem

One of the most common gaps in subscription dispute responses is the inability to show what your policy pages said at the time of the charge, not what they say today.

Consider this scenario: a customer was billed in February, files a dispute in April, and by the time you respond in May your subscription policy has been updated twice. The card issuer's reviewer does not know what your policies said in February. If you submit your current policy, the customer can claim those terms were not in place when they signed up.

Merchants who handle this well typically do one of two things:

• Keep dated backups of policy pages. Every time you update a policy, save a copy with the date. Store these in a folder that is accessible when a dispute arrives. The Wayback Machine (web.archive.org) can also provide archived snapshots, though these are not always current.
• Use a policy audit tool that creates timestamped exports. Some tools (including our own) scan your live policy pages and generate a dated HTML or PDF report you can store. This creates a portable, dateable record of what your policies said on a given day — without manual effort every time a policy is updated.

Starting this documentation habit now means that disputes filed six or twelve months from now will be much easier to respond to.

Reducing chargebacks before they happen

The best dispute response is one you do not need to file. Most subscription chargebacks fall into predictable categories, and each has a corresponding prevention measure.

Clear billing descriptor

If your billing descriptor on bank statements is unclear — a parent company name, a generic brand, something that does not match what the customer ordered from — this triggers "transaction not recognised" disputes. Make your descriptor as recognisable as possible: include your brand name and, if space allows, the word "subscription".

Pre-renewal reminder emails

Sending a reminder email before each renewal billing cycle is the single most effective way to reduce "didn't know it would renew" disputes. The email should include the renewal date, the amount that will be charged, a clear cancellation link, and confirmation of what the customer is receiving. Even a short email three to seven days before billing significantly reduces surprise disputes.

Under DMCCA 2024 (enforcement expected Spring 2027), pre-renewal reminders will become mandatory for UK subscription merchants. Starting now means you are both reducing chargebacks and preparing for compliance at the same time.

Easy cancellation

If customers cannot find how to cancel, they cancel via their bank instead. A visible cancellation link in every renewal reminder email, a direct link from the customer account page, and a clear policy explaining the cancellation deadline all reduce dispute volume. This does not mean making cancellation frictionless — it means making it findable.

Checkout transparency

At the point of purchase, show the recurring billing terms clearly: the initial price, the renewal price and frequency, and how the customer can cancel. Do not bury this information in a terms link. The more clearly the customer understood what they were agreeing to, the weaker any future claim that the billing was unauthorised.

Dispute-readiness checklist

Use this checklist to assess whether you are ready to respond to a subscription chargeback today. Each item represents evidence or documentation you will need.

If you have gaps in the policy documentation section in particular, starting a documentation habit now means future chargebacks will be much easier to respond to.

Frequently asked questions