Recurring billing disputes, cancellation claim patterns, and win-rate data for subscription-based businesses.
SaaS and subscription merchants enjoy a below-average dispute rate of 0.6%, but face an outsized friendly fraud problem. Nearly half of all disputes in this vertical are friendly fraud — customers who used the product but claim they didn't authorize the charge, or insist they cancelled before billing occurred.
The good news is structural: subscription businesses typically accumulate more data about their customers than almost any other merchant type. Login logs, session records, usage histories, email engagement, feature interaction data, support ticket archives — all of these constitute evidence that the product was accessed and used, which is the central question in most subscription disputes.
The challenge is operational: most SaaS companies don't organize this data in a way that's retrievable and presentable for dispute responses. Merchants who win at the highest rates treat cancellation logging and access record retention as first-class engineering concerns, not afterthoughts.
Cancelled recurring billing codes dominate the SaaS dispute landscape, accounting for more than half of all disputes across networks. Authorization disputes and CNP fraud round out the top codes.
| Code | Network | Description | Share of Disputes |
|---|---|---|---|
| MC 4841 | Mastercard | Cancelled Recurring Transaction | 31% |
| Visa 13.6 | Visa | Credit Not Processed – Cancelled Recurring | 22% |
| MC 4837 | Mastercard | No Cardholder Authorization | 18% |
| Visa 10.4 | Visa | CNP Fraud | 14% |
| Amex C28 | Amex | Cancelled Recurring Billing | 10% |
| Other | Various | Various | 5% |
Cancellation disputes are the defining challenge for subscription businesses. Understanding why they happen at scale — and how to document against them — is the most important operational work a SaaS company can do for dispute defense.
The core ambiguity: customers frequently cancel subscriptions through informal channels. An email to support saying "please cancel my account," a reply to a billing notification, a tweet, a chat conversation — customers treat these as equivalent to an in-product cancellation. Many subscription platforms only record cancellations that flow through their official cancellation portal. If the customer used any other channel, the cancellation may not exist in your records, even though the customer is certain they cancelled.
Log every cancellation request with a timestamp, user ID, and method. This single practice can increase your win rate on 4841 and 13.6 disputes by 30 or more percentage points. It doesn't matter whether the cancellation came through email, chat, your portal, or a phone call — log it the moment it's received, and store it in a retrievable format.
The second layer of the problem: annual plan customers. A customer who signed up for an annual plan twelve months ago may have forgotten entirely that they opted for the year-long commitment. When the renewal charge hits, they dispute it as unauthorized. Your defense requires showing them what they agreed to at signup, when they agreed to it, and that they received adequate advance notice of the renewal.
The impact of cancellation logging on dispute outcomes is one of the most dramatic evidence-to-win-rate relationships in the dataset. Merchants with formal cancellation logs win cancelled recurring disputes at more than double the rate of those without.
| Dispute Type | With Cancellation Log | Without Log |
|---|---|---|
| Cancelled Recurring (4841 / 13.6) | 78% | 31% |
| No Authorization (4837) | 69% | 44% |
The no-authorization win rate also benefits from cancellation logs because they document a customer's ongoing engagement with the account — someone who "never authorized" the subscription typically has a cancellation request or usage record that directly contradicts the claim.
Three structural product decisions drive the majority of elevated dispute rates in SaaS. If your business has any of these characteristics, they should be the first place you look when addressing dispute volume.
When customers cannot cancel through the product itself, they resort to chargebacks as the path of least resistance. An in-app cancellation flow that creates a timestamped, logged record is both better for the customer experience and essential for dispute defense. The absence of one is a structural dispute driver.
Annual plan renewals are the most common trigger for high-value subscription disputes. Customers who signed up for a year-long commitment twelve months prior often don't remember the billing terms. The dispute rate on annual renewals is 3–4x the rate on monthly billing cycles. Mitigate with 30-day advance renewal notices.
Free-to-paid conversions are the highest-volume source of disputed first charges in SaaS. Customers who signed up for a free trial and forgot about it dispute the first paid charge as unauthorized. Clear pre-conversion notices, email reminders before conversion, and explicit consent at trial signup dramatically reduce this category.
These four operational practices, implemented together, address the majority of dispute risk in the SaaS vertical. Each one is also directly usable as evidence in dispute responses.