Why subscription businesses get chargebacks
Recurring billing creates disputes that one time sales rarely see. A customer signs up for a trial, forgets about it and sees a renewal three months later. Someone in finance does not recognize the descriptor on the company card. A user tries to cancel, cannot find the button and calls the bank instead. Each of these turns into a chargeback that costs the subscription amount, a dispute fee and time that a small team does not have.
Most SaaS companies have nobody who owns disputes. Notices sit in the Stripe dashboard until the deadline passes, and the dispute is lost by default. Meanwhile every lost dispute counts toward your chargeback ratio, and a high ratio can lead your processor to hold funds or close the account.
The reason codes SaaS merchants see most
| Reason code | What the customer claims | Evidence that wins |
|---|---|---|
| Visa 13.2 Canceled recurring | They canceled, or were never told about the renewal | Cancellation policy, renewal notice, proof the account was not canceled, usage after the charge |
| Visa 10.4 Card absent fraud | They did not authorize the charge | 3D Secure result, IP and device match, Compelling Evidence 3.0 history, login after purchase |
| Visa 13.6 Credit not processed | They were promised a refund | Refund policy, communication log, proof no refund was agreed |
| Mastercard 4841 Canceled recurring | Same as Visa 13.2 | Same as Visa 13.2 |
| Mastercard 4837 No authorization | Same as Visa 10.4 | Same as Visa 10.4, plus authentication data |
Read the full breakdown of Visa reason code 13.2 and Visa reason code 10.4.
Winning Visa 13.2 canceled recurring disputes
A 13.2 dispute is won by showing that the customer agreed to recurring billing, was told how to cancel and did not cancel before the charge. NoChargeback builds that story from your data.
-
The terms and subscription agreement the customer accepted, with version and time.
-
The renewal reminder emails you sent, with delivery status.
-
The cancellation flow: where the cancel button sits, and whether the customer opened it.
-
Logins and actions after the disputed renewal, which show the service was still in use.
-
The subscription history from Stripe: start date, plan changes, past paid invoices.
If the customer did cancel and the renewal was a mistake, the pack tells you so and recommends accepting the dispute instead of paying for a losing fight.
Winning Visa 10.4 fraud disputes with Compelling Evidence 3.0
Many "fraud" disputes in SaaS come from real customers who do not recognize the charge. Visa Compelling Evidence 3.0 lets you prove this with history: at least two earlier undisputed transactions from the same card, 120 to 365 days old, that share the IP address or device plus another identifier with the disputed one. NoChargeback checks your Stripe history for qualifying transactions and adds them to the pack, together with the 3D Secure result, AVS and CVC checks and logins after the charge. CE 3.0 data submission is part of Scale and Enterprise.
Login and usage proof from your product
Stripe knows about payments. Your app knows that the customer logged in on Tuesday, created four projects and invited a colleague. That second set of facts wins subscription disputes. NoChargeback connects to an evidence endpoint in your app that returns account creation time, email verification, logins with IP and browser, key actions after purchase and cancellation attempts. Until you add the endpoint, packs use everything Stripe holds: customer, receipts, 3D Secure, IP from the charge and the subscription history.
Prevent disputes with descriptor clarity
The cheapest chargeback is the one that never happens. NoChargeback looks at where your disputes come from and recommends fixes that reduce them.
-
Use a statement descriptor with your product name and a support address, so the charge is recognizable.
-
Send a reminder before annual renewals and before the end of a trial.
-
Keep the cancel option visible in the billing page.
-
Turn on 3D Secure for first payments on risky countries or card types.
-
Refund when an early fraud warning arrives and the refund costs less than the expected chargeback.
Read how digital goods sellers use the same rules for courses and downloads.
How it works for a Stripe subscription business
-
Connect Stripe with read access plus dispute evidence permission. No code changes are needed.
-
Every dispute, inquiry and early fraud warning appears in your feed within minutes.
-
An evidence pack is built for each dispute, with a letter written for the reason code.
-
Review and submit with one click on Starter, or let Growth and higher plans submit automatically before the due date.
-
Watch your Visa VAMP and Mastercard ECM ratio and get an email at 70 and 90 percent of each threshold.
Which plan fits a SaaS company
Starter fits a company with one Stripe account and up to 15 disputes a month, for 49 USD a month or 24 USD a month billed yearly. Growth adds automatic submission, prevention rules, Slack alerts, three seats and up to 100 disputes a month for 299 USD a month or 149 USD billed yearly. Scale adds Compelling Evidence 3.0 data, network alerts and multiple products across up to 20 accounts. Full details are on the pricing page. If you run several SaaS brands, see chargeback management for multiple merchant accounts.
Does NoChargeback work with Stripe Billing subscriptions?
Yes. It reads subscriptions, invoices, customers and disputes from Stripe and adds the subscription history to every pack. No changes to your checkout or billing code are needed.
How do I prove a customer used my SaaS after the charge?
Connect the evidence endpoint in your app, which returns logins, actions and cancellation attempts. Without it, packs still include Stripe data such as receipts, 3D Secure and IP addresses.
Can I win a dispute when the customer says they canceled?
Yes, if your records show they did not cancel before the renewal and they accepted the recurring terms. If they did cancel, the pack recommends accepting the dispute.
Will NoChargeback refund customers automatically?
No. It never refunds on its own. On Growth and higher plans you can turn on refund rules for your own account, and they stay off until you enable them.
What is Compelling Evidence 3.0?
It is a Visa rule for fraud disputes. If you show earlier undisputed transactions from the same cardholder with matching IP or device data, the issuer must consider the dispute again.