by Matt Rej
Recurring billing chargebacks have a specific set of rules underneath them that most merchants don’t know about. This has become a real problem (and a costly one) for SaaS and subscription-based businesses.
New data suggests that recurring billing disputes represent over 27% of chargebacks for subscription businesses. And the overall chargeback rate for subscriptions is up to 4x higher compared to standard ecommerce purchases.
But lots of these losses are avoidable. So whether you’re already facing this problem or trying to get ahead of what could be a bigger issue, this guide will explain how to protect yourself.
Recurring Billing Chargeback Reason Codes
The first thing you need to do is identify the chargebacks that resulted from your recurring billing model. If subscriptions are your only transaction types, then this is straightforward. But if you also sell products, one-off services, or accept payments unrelated to your recurring offer, you’ll need to rely on the chargeback reason code to determine which ones came from recurring payments.
Every major network has its own version of this chargeback, but the code is different for each one.
- Visa — Reason Code 1320
- Mastercard — Reason Code 41 (merged with MC 53 disputes)
- Discover — Reason Code 4541 AP
- American Express — Reason Code C28
- PULSE — Reason Code 4541
- STAR — Reason Code 5000
- SHAZAM — Reason Code 0205 or 4544
- Accel — Reason Code 5000
- PayPal Network — Reason Code 34
- Maestro — Reason Code 41
The core claim here is always the same: the cardholder says the merchant billed them after they canceled or after their permission to charge the account ended.
Once you have the code, you need to figure out the specific timeline to respond and how the dispute process works for that particular network.
For example, you only have 20 days to respond to Amex C28, whereas you may have up to 45 days for a Mastercard dispute coded 41 or 53. And if you get a Visa 1320, you may be able to use CE3.0 to win the case (something that isn’t available for other networks).
Why Recurring Billing Chargebacks Happen
Just because the customer disputed a recurring charge that the issuing bank used to generate one of the reason codes above, it doesn’t always mean that the merchant did something wrong. And there are actually several distinct scenarios that all produce the same chargeback code.
Understanding which scenario you’re dealing with will ultimately determine how you respond and whether you have a chance to win.
Merchant Kept Billing After Cancellation: The customer tried to cancel the subscription but their request wasn’t processed before the next billing cycle. This is a genuine operational failure on the merchant’s side.
Customer Canceled Too Late: Request to cancel came in after the billing cycle already closed, and then the cardholder disputed the charge anyway. Cardholders do this a lot more often than merchants realize as it’s often easier to initiate a dispute instead of haggling with a customer service rep.
Cardholder Forgot About Subscription: This is most common in annual billing cycles. 12 months goes by and the charge appears on their statement. If the cardholder didn’t think they’d be automatically charged after a year, they go straight to their bank.
Customer Continued Using Service After Canceling: If documented correctly, this scenario is one of the strongest defenses available to merchants fighting a recurring billing chargeback.
Friendly Fraud: The cardholder knowingly disputed a legitimate transaction because they know that issuers typically side with the customer.
What You Actually Need to Win a Recurring Billing Dispute
When you receive one of these chargebacks, you need to gather a specific set of documentation that addresses the network’s resolution criteria.
Not every item will apply to every case. But you need to know what’s available and have it ready fast, as response windows are short.
- Signed authorization showing the customer agreed to recurring billing.
- Proof the customer acknowledged the recurring terms.
- Evidence the customer did cancel in accordance with your policy.
- Timestamped cancellation requests alongside of the transaction date (if you’re arguing the request came after or too close to the charge).
- Proof the cancellation confirmation number your customer used in the dispute does not match any number in your records.
- Proof that a credit was already issued, if you refunded the customer before the chargeback arrived.
- Login records, access logs, or session data showing the customer continued using the service after their claimed cancellation date.
- Copy of your cancellation policy with a specific explanation of which part the customer failed to follow.
- Proof the cancellation and billing occurred in the same month, with documentation that partial services were rendered.
- Contract terms showing payment was still owed after termination.
Make sure you package everything together for a single submission to the bank, and follow the exact instructions for the network within the correct time frame.
Submitting two documents via email on one day and then everything else through your processor portal days later increases the chances of things getting lost and the bank siding with the cardholder.
If there’s any doubt, the cardholder will always be favored. So the way you present your case is equally important to whether or not the charge was legitimate.
How to Prevent Recurring Billing Chargebacks
Fighting chargebacks after the fact can still be costly, even if you win. Between the administrative costs, processor fees, and impact on your VAMP ratio, your costs may even exceed the amount you’re fighting for.
So it’s really in your best interest to have bulletproof operational policies in place to prevent potential cardholder disputes before a chargeback gets issued.
Here’s what you need to have in place.
Free Trials That Are Actually Free
Trial-to-paid transitions are a common dispute trigger. So if you’re going to charge customers automatically when the trial ends, you need to make that abundantly clear during the initial sign up and prior to the charge.
Email reminders that the trial is expiring and the first payment will be processed on a particular date are much more transparent compared to fine print that nobody is going to read.
If you can’t do this, then you shouldn’t be requiring credit card information upfront.
Clear Cancellation Policies That Customers Can Read and Acknowledge
Your website Terms & Conditions are not a replacement for a standalone Cancellation Policy. The cancellation policy should be much shorter, easy to read, and something that you can prove that customers acknowledged when they were signing up.
Spell out exactly how the billing works, and exactly how customers can cancel the subscription to avoid the next charge.
Easy Ways for Customers to Cancel
You’re going to have way more chargebacks if the only way to cancel is by calling a customer service number that’s buried on the website. You’ll have even more if you only accept calls during business hours five days per week and hold times are exceptionally long.
Give customers options and make it easy on them. They should be offered 24/7 options like click-to-cancel online, via chat, through email, on the phone, text (if you support it). Don’t make this process difficult for your customers.
Ability to Act on Cancellation Requests Immediately
The cancellation request is only the first part. Once received, you need to ensure that the next upcoming payment is actually cancelled, plus all future curing payments.
For online cancellations, you can use APIs and automations to do this without human intervention (just test it regularly). But for phone calls or other methods, you need a clear procedure in place. Leaving a sticky note on someone’s desk isn’t going to cut it at scale.
Billing Notifications Sent With Plenty of Notice
Use emails or push notifications to let customers know about upcoming payments. This way, there’s no surprises. And you can use data to show that a customer opened the message ahead of the billing date or dispute date.
Stop Billing That Card Moment You Get a Chargeback
Even if a customer didn’t cancel properly, you need to put a hold on their account the second a chargeback comes in. Continuing to charge a card on file during an active dispute is not something that will play out in your favor, even if you did nothing wrong initially.
A Few Other Things Worth Noting
Beyond preventing and fighting recurring chargebacks, there are a few other layers of this that you need to understand.
First, the FTC enforces subscription practices under ROSCA and Section 5 of the FTC Act. Recent settlement orders (including Amazon’s) make it clear that simple cancellation and clear pre-billing disclosures are expected universally.
It’s also worth noting that chargebacks cost much more than just the disputed amount. You’re absorbing the chargeback fee, employee time to respond, and VAMP ratio impact on top of the lost revenue. All recurring billing disputes count against your TC15 total, even if you win.
Your processor should be able to break out your dispute data by reason code. And if they’re not, it’s something worth pushing on.
If you want a second set of eyes on what you’re being charged or how your dispute reporting is set up, that’s something we can help you out with here at MCC. Just book a free consultation to get started, and we’ll take a look at your statements with no strings attached.