Subscription Chargeback: Why They Happen and How to Win

Why Subscription Chargebacks Are Growing

Subscription billing has become the dominant model for SaaS, digital services, and content platforms. But as subscription revenue has scaled, so have disputes. B2C SaaS chargeback volume has grown 83% in recent years; B2B SaaS is up 77%. The average SaaS chargeback rate now sits around 1.85% — the second highest of any industry, behind only digital goods. That rate is dangerously close to Visa's 1% monitoring threshold and well above the 0.5% threshold that triggers Mastercard's Excessive Chargeback Program.

Three root causes explain most of this growth. First, subscription fatigue: the average consumer now has more than five active subscriptions. When a charge appears on a statement, many customers simply don't recognise it — especially if the billing descriptor shows a legal entity name rather than the product they use. Filing a chargeback takes less time than searching email for a receipt.

Second, trial-to-paid confusion. Many SaaS businesses offer 7-day, 14-day, or 30-day free trials. When the trial converts to a paid plan, the first charge often comes as a surprise to customers who either forgot they signed up or assumed cancellation was automatic. The charge triggers a dispute rather than a support request.

Third, the path of least resistance. Cancelling a subscription often requires navigating menus, emailing support, or waiting for a response. Filing a chargeback takes two minutes and the bank handles the rest. Even customers who could have cancelled legitimately sometimes choose to dispute instead. This is sometimes called “friendly fraud,” though the intent is often careless rather than malicious.

Most Common Reason Codes for Subscription Disputes

Different reason codes require fundamentally different evidence strategies. Filing the wrong response for a given reason code is a guaranteed loss. Here are the three codes that account for the majority of subscription chargebacks.

For a full breakdown of all Visa and Mastercard codes relevant to subscription businesses, see the chargeback reason codes reference.

The Subscription Chargeback Lifecycle

Understanding the dispute lifecycle helps you know how much time you have and where intervention is most effective.

The chain typically looks like this: a customer is charged for a renewal (or a trial converts to paid). The customer does not recognise the charge or decides not to contact the merchant. They call their bank or tap the dispute button in their banking app. The bank files a chargeback with Visa or Mastercard. The card network routes it to your acquiring bank. Your acquirer notifies you, usually within a few days.

Under Visa and Mastercard rules, cardholders have up to 120 days from the statement date to dispute a charge. In practice, most subscription disputes are filed within 30 days — immediately after the renewal charge appears on a statement. However, you should be prepared to see disputes arrive months after a charge, particularly from customers who only review statements periodically.

The statistic that surprises most subscription merchants: approximately 75% of customers who file a chargeback did not contact the merchant first. This is not primarily malicious — it reflects how little friction the modern banking app puts between a customer and a dispute button. The practical implication is that pre-charge communication (reminders, clear descriptors) is more effective than reactive customer service.

Once a chargeback is filed, you typically have 30 days (Visa) or 45 days (Mastercard) from the date of notification to submit your representment response. Missing this window means an automatic loss regardless of how strong your evidence is.

Evidence That Wins Subscription Chargebacks

The right evidence depends on the reason code, but these six categories of evidence are relevant across most subscription disputes. Gather what you can before the response deadline.

For a broader framework on building dispute responses, see the chargeback representment process guide.

Preventing Subscription Chargebacks

Prevention is significantly more valuable than winning disputes. Each prevented chargeback saves not just the transaction value but also the chargeback fee (typically $15–$100) and the time cost of preparing a response. Merchants who implement proactive measures typically see 40–60% reductions in subscription dispute rates.

Billing descriptors deserve special attention. The descriptor is what appears on a customer's bank statement when they view a charge. If your legal company name is different from your product name — or if your processor assigns a generic code — customers may not recognise the charge. Work with your payment processor to set a descriptor that clearly identifies your product. Many processors allow a soft descriptor (the first ~22 characters visible on a statement) to be customised independently from the hard descriptor.

For a broader framework on bringing your chargeback rate down, see the guide to reducing chargeback rates.

Visa 13.2: Cancelled Recurring Transaction — In Detail

Visa 13.2 is the most contested and most misunderstood reason code in subscription billing. It applies specifically when a cardholder claims their recurring subscription was cancelled and that the merchant charged them anyway. Understanding exactly what Visa requires to win this dispute — and what it does not require — is essential.

To prevail under Visa 13.2, you must demonstrate at least one of the following:

• •The customer did not request cancellation before the billing date covered by the disputed charge.
• •The customer requested cancellation after the billing date — meaning the charge was legitimately incurred before cancellation took effect.
• •The charge was the final instalment of an agreed instalment plan that the customer enrolled in and has not yet completed.
• •The cancellation policy was clearly presented at the time of signup, and the customer did not follow the stated procedure.

What you cannot do under Visa 13.2 is argue that the charge was valid simply because the customer agreed to a subscription at some point in the past. If the customer did properly cancel — in writing, through your portal, or by any method your policy permits — before the billing date, and you still charged them, you will lose the dispute.

A note on timing: the 120-day dispute window means customers can dispute a subscription charge up to four months after it was billed. This matters for annual subscriptions in particular — a customer can dispute a January renewal as late as May. Preserve your cancellation request logs (or the absence thereof) for at least six months after each billing date.

Dunning vs Chargebacks: What You Should Avoid

Dunning — the process of retrying failed payments and notifying customers of declined charges — is a standard part of subscription operations. But poorly-executed dunning can directly generate chargebacks rather than prevent them.

When a renewal payment fails, the right path is a clear notification email explaining the issue and asking the customer to update their payment method, followed by a scheduled retry (typically after 3–7 days). This gives the customer the opportunity to act before access is restricted.

The path that generates chargebacks: retrying the card immediately and repeatedly without notification. Multiple rapid charges appearing on a statement — especially when the customer wasn't aware a payment had failed — look like errors or fraud. Customers dispute all of the charges rather than investigating.

A second dunning risk: retrying a card that has already been reported as lost or stolen. This triggers automatic fraud detection and virtually guarantees a chargeback. Processors with account updater services can help by automatically updating card details when a card is reissued, reducing both failed payments and the risk of dunning-triggered disputes.

If your subscription business has volume, consider working with a specialist chargeback management service to handle dispute responses professionally and track patterns that indicate billing flow problems before they become a chargeback rate problem.