Free Trial Chargebacks: Why Auto-Renewal Disputes Happen
Free trial chargebacks happen when a trial auto-converts and the cardholder doesn't recognize, expect, or want the first real charge. Most get filed under a cancelled-recurring or unrecognized-transaction code.
I've watched the same pattern across the merchants on our platform. Disputes pile up on one moment, the first charge after a trial ends, the one charge the cardholder never actively said yes to. It's the same moment that drives most subscription chargebacks in SaaS. Fix that moment, and the dispute rate drops with it.
Key takeaways
Why do free trials cause chargebacks?
Free trial chargebacks cluster on the first real charge after conversion, because that charge is the first one the cardholder has to recognize on a statement. A trial starts free and turns into a paid plan. Weeks later, the cardholder has to remember a signup they made once and haven't thought about since.
A trial signup that takes card details but never checks the card leaves a gap. Nothing tests whether the card still works, or whether the person still remembers the deal. The card just sits there, saved, while the trial runs.
The longer the trial runs, the wider that gap gets. A 30-day trial gives the cardholder a month to forget the signup entirely. A 7-day trial barely gives them time to use the product once.
Short trials, under about seven days, break the other way. The cardholder still remembers signing up that soon after, so the dispute shifts from forgetting to price shock. Memory holds up fine. The amount is what surprises them.
Which reason codes free-trial disputes get filed under
Trial conversion disputes arrive under cancelled-recurring and unrecognized-transaction codes rather than fraud codes, which changes what evidence wins them. The issuer sorts a dispute by what the cardholder says happened. What happened on your end matters less than the story the issuer heard first.
"I cancelled and got charged anyway" and "I don't know this charge" lead to different codes, part of the same chargeback reason codes every card network assigns. A cancelled-recurring claim needs your cancellation records and the date the cardholder says they cancelled.
An unrecognized-transaction claim needs proof the cardholder agreed to the charge in the first place. That's exactly the step a no-cost trial signup usually skips.
In our own dataset, Visa's cancelled-recurring code (13.2) makes up 8.5% of alerts with a recorded reason code, second only to card-absent fraud. That share spans every merchant's alerts, not just trial-based ones. A trial-heavy business should expect its own share of 13.2 to run higher.
The table below maps the three codes a trial dispute can land under to what wins each one:
The cancelled recurring transaction code has its own dispute mechanics beyond what a trial-conversion dispute needs. Our reason code lookup covers the full picture for any code on a dispute notice.
What the card networks actually require for trials
Visa's trial rules require an easy way to cancel online, a descriptor that names the trial, and a notice before the first real charge. They've been in force since April 18, 2020, built around one problem, cardholders forget a free trial turns into a paid plan. That mix-up drove call-center volume, write-offs, and card closures on Visa's network.
The rules target the forgetting head-on. The notice, descriptor, and cancel path all reach a cardholder who simply forgot a charge was coming.
Four requirements make up the rule set:
- Notification: Send an electronic reminder, by email or text, with a cancellation link at least 7 days before the recurring charge processes.
- Cancellation path: Provide an easy way to cancel online, no harder than unsubscribing from an email list, regardless of how the cardholder originally signed up.
- Statement descriptor: Include a trial-identifying descriptor, such as "trial" or "free trial," in the merchant name field for the first charge after the trial ends.
- Transaction receipt: Disclose the trial length and the future charge amount and date at signup, even when no amount is due yet.
Meeting the network rules doesn't stop a dispute from being filed. A cardholder can still file the moment the charge lands. What changes is your response. Fighting a cancelled-recurring claim later needs proof you met these rules, filed before the charge went through.
Where US auto-renewal law actually stands
The FTC's click-to-cancel rule is not in force right now. A federal court struck it down in July 2025. The FTC has since started work on a new one, and state auto-renewal laws still apply either way. Read this section as true only on the publish date, since the rule is still in motion.
The court's ruling wiped out the federal rule, but it left state law untouched. What a merchant owes now depends on where the cardholder lives.
The FTC issued a new proposal on March 11, 2026, restarting the process and opening it for public comment. Until a new rule takes hold, the FTC still enforces existing law against deceptive auto-renewal practices.
Maryland requires notice before a free trial turns into a paid plan, a state rule with no federal match right now. A merchant that sells nationwide has to check each state's own law rather than count on one federal rule.
The Trial Boundary Checklist
Four controls at the trial boundary cover the dispute causes, and only one of them is a Visa rule. Check the card at signup, send a notice before the charge, make the descriptor easy to place, and keep the cancel path open.
Notice, descriptor, and cancel path build directly on the network rules above. Checking the card goes further than Visa asks, closing the one gap the rules don't reach.
Authorize the card when the trial starts
A card checked at signup gives you proof of consent that a no-charge trial never creates. A free trial takes card details but never actually charges the card. Nothing confirms the number is real, that the cardholder still holds it, or that they still remember the deal by the time the trial converts.
Say your trial converts on day 14. A small hold placed on day 0, commonly $1, tests all three at once and shows the card is live. It releases once the check clears, well before the day-14 charge arrives.
That hold record becomes proof in its own right if a dispute later claims the cardholder never agreed to anything.
The mechanics carry one catch worth planning around. Stripe holds expire after seven days. A trial that runs longer than a week needs the card saved and quietly re-checked before the hold lapses.
Trial.io builds exactly this into a merchant's own Stripe account. It places a $1 hold at signup and checks the card, then re-checks it automatically ahead of the seven-day cutoff. The proof never goes stale before the trial converts.
Send the pre-charge notification
A notice sent before the charge gives the cardholder a chance to remember, and cancel, before a dispute becomes the only exit they know. Visa's rule sets the floor at seven days before the charge, by email or text, with a working cancel link attached.
The notice does two jobs at once. It reminds a cardholder who forgot, so the dispute never starts, and it becomes proof if they dispute anyway. A logged notice, cancel link included, shows they had both the warning and the way out before the charge hit.
Make the descriptor say what the charge is
A statement descriptor that names the trial gives the cardholder a chance to place the charge without opening a support ticket or a dispute first. Visa's rule requires a trial-naming descriptor, such as "trial" or "free trial," on the first charge after conversion. It has to show up on the cardholder's statement, banking app, and card alerts.
A generic company name on that line is a common mistake merchants make here. The cardholder sees a charge from a name they don't tie to a signup from weeks earlier. Disputing it is faster than digging through their inbox for a receipt.
The full mechanics of what a statement descriptor covers, and how to fix one that's already unclear, live on their own page. The fix here is narrower. Put the trial name in the descriptor for that one charge.
Keep the cancel path shorter than the dispute path
A cancel path that takes fewer clicks than filing a dispute keeps the cardholder in your product instead of in their banking app. A cardholder choosing between digging through account settings and tapping "dispute this charge" in their bank's app picks whichever one is faster. A bank's dispute flow often beats a merchant's buried cancel page.
Visa's own guidance sets the bar at one click, the same as unsubscribing from an email list. A cancel path buried three menus deep, or gated behind a support request, sends cardholders to the bank instead.
A billing platform's own customer portal, such as Stripe's, can usually expose a direct self-serve cancel link in a couple of settings. That setting alone is often the fastest way to hit Visa's bar.
When tightening the trial costs more than the chargebacks
A card hold at signup blocks some trial starts, so the control is wrong for a business that needs trial volume more than a low dispute rate. A hold is a real charge on the card, even a small one. It fails on the same cards a no-charge signup would take with no trouble, including cards near their limit and many prepaid cards that reject holds outright.
That failure hits the exact users some funnels depend on. A product built around easy, high-volume signups from price-sensitive shoppers loses some of them the moment a card has to clear even a small hold.
The tradeoff is a real cost.
The math flips once a merchant nears a card network's dispute-rate line. Below it, a higher dispute rate is a cost you can absorb. Above it, the card network can flag the account for extra fees, reserve holds, or a full block on taking cards. No amount of trial volume is worth that.
How we sourced our data
The reason-code figures in this article come from anonymized, combined alert data across merchants on the Chargeback.io platform. We counted total alerts within each reason code and report them as shares of alerts with a recorded code. These numbers reflect alerts our platform handled, not the payments industry as a whole.
FAQ
Can a customer dispute an uncancelled trial?
Yes. A cardholder can file regardless of why they missed the cancellation window, and whether the dispute succeeds comes down to the evidence you have on file.
Does a $1 hold show up on the customer's statement?
Most banks show it as a pending or temporary charge that clears within a few days. The exact wording and timing depend on the cardholder's bank.
Should we require a card for the free trial at all?
That depends on whether your signup flow cares more about volume or quality. A card-optional trial removes the problem this article covers, but it trades that for different signup and fraud tradeoffs, outside what this article covers.
What happens if the trial runs longer than a week?
The fix is a saved card, reauthorized before the hold expires. Stripe's seven-day limit holds regardless of trial length, so a merchant who skips reauthorization ends up with an unverified card again once day seven passes.
