Back to Blog

How to prevent repeat free trials with Stripe

Stripe starts every trial you ask for. What its setup covers, what's left to you, and how to stop one person getting your trial twice.

Stripe won't prevent multiple free trials on its own. The first one you find is rowan.hale@gmail.com, 14-day trial, canceled on day 3, all 400 free generations used. Nothing strange about that, so you scroll down one row. rowanhale@gmail.com. Same company name, same 400 generations, and a trial that started nine minutes after the last one ended. Gmail ignores dots, so those two addresses reach one inbox.

You're only in the Stripe dashboard because of an invoice. Your AI provider billed you $7,300 for October, against a budget of $4,000, and revenue didn't move. You went looking for whoever used $3,300 of model time, and now you're looking at them. You set this trial up with one line, trial_period_days: 14, and you figured the company running your billing would notice someone taking it twice. Most people would. At 11:40 p.m. you search Stripe prevent multiple free trials, and you learn that nothing in that setup was ever going to.

Signs up, first emailCheckout with 14-day trialTrial startedSigns up, second emailCheckout with 14-day trialNew trial startedThree days later, canceledSame personYour appStripeSame personYour appStripe
Signs up,first emailCheckoutwith14-day trialTrialstartedSigns up,secondemailCheckoutwith14-day trialNew trialstartedThree days later,canceledSamepersonYour appStripeSamepersonYour appStripe

Treat October as a scenario, and swap in your own numbers. A fully used trial costs you $10 in model spend. Thirty people each worked through 11 trials in the month, opening a new one about every three days as the generations ran out. That's 330 trials (30 × 11) and $3,300 (330 × $10). Over a year it's $39,600. On your $49 plan, it takes 68 paying customers just to cover one month of it ($3,300 ÷ $49 = 67.3).

Say you've got $60,000 in the bank and spend $12,000 a month, which is five months of runway. Without those trials you'd spend $8,700, which is 6.9 months. Thirty people took almost two months off the date you run out of money.

Then there's the number you've been quoting. 900 trials started in October and 36 became customers, so you've been telling everyone 4%. Take out the 330 trials those 30 people opened and it's 36 of 570, or 6.3%. You spent three weeks rewriting onboarding to fix a conversion rate that was never the problem.

Your paying customers got the rest of it. Every account shares one per-minute limit at your AI provider, and on the 21st, between 4:10 and 5:35 p.m., generations failed for everyone. Three customers asked for refunds, which is $147 (3 × $49). One of them canceled and told you they can't run client work on this.

It's midnight now, and the choices are bad. You can add a card step and lose people who'd have paid you, or cut the trial that brought in nearly every customer you have. Or you leave it, and November's invoice looks the same.

Those numbers are made up. This next one happened:

From our early beta

Scammers created account after account with a stack of email aliases and the same one or two cards. Every one of those accounts shared a payment fingerprint, but nothing was checking it, and the team's payment processor restricted their payment processing.

Every renewal you collect runs through one payment account, so a restriction reaches the customers who did nothing wrong.

Why Stripe doesn't prevent multiple free trials on its own

A Stripe trial is a setting on one subscription. You pass trial_period_days or trial_end, and that subscription starts free. The trial options Stripe documents for subscriptions and Checkout don't include one trial per customer, and its billing docs describe adding a new trial to a subscription that's already had one.

A second signup is a second account in your app, so it usually becomes a second Stripe customer. Email isn't a unique key there. Two customers can share one, Stripe's support pages say Checkout settings and integrations commonly create duplicates, and Stripe doesn't merge them. The email filter on its List Customers API only returns exact, case-sensitive matches. To Stripe, rowan.hale@gmail.com and rowanhale@gmail.com are strangers.

The obvious fix is to remember who's had a trial. It's worth building, and it takes an afternoon. It stops one account getting two trials, and it does nothing about a new account, which has no history to find.

What Stripe's trial setup covers and what's left to you

Free trial with StripeStripe coversLeft to youTrial length and end dateCard collection at CheckoutTrial ending eventsWho already had a trialSame person, new emailWhat a returner sees
Free trial with StripeStripe coversLeft to youTrial length and end dateCard collection at CheckoutTrial ending eventsWho already had a trialSame person, new emailWhat a returner sees

Stripe handles the billing side of a trial well:

  • Length. trial_period_days or trial_end, for up to 730 days.
  • Cards. Checkout collects a payment method by default. payment_method_collection=if_required makes it optional.
  • Ending with no card. missing_payment_method can cancel the subscription, pause it or create an invoice. Pick cancel or pause, so an abandoned trial doesn't become an unpaid invoice.
  • Warnings. customer.subscription.trial_will_end fires 3 days before the end, by default.

Stripe's docs also warn that trials without a payment method can let spammers create lots of fake customers, and they suggest a user account and a CAPTCHA first. A person signing up by hand gets through both.

If you collect a card, look at the free trial abuse control in Radar, Stripe's fraud product. Stripe says it blocks high-risk trial starts from customers unlikely to pay when the trial ends. Find out what it costs on your account. It's built around the step where a payment method is saved, so read how far it reaches if your trial doesn't ask for one. Free credits or a free plan handed out in your own app never reach it at all.

How to stop a second trial on the same account

Keep your own record of who's had the trial. One row per user. Write it when the subscription starts, and don't clear it when the subscription is canceled.

Reuse one Stripe customer per user. Store the customer ID and pass it to Checkout, so a returning user doesn't become a new customer.

Add the trial only when there's no row.

checkout.ts
const hadTrial = await db.trialClaims.exists({ userId: user.id });

const session = await stripe.checkout.sessions.create({
  mode: "subscription",
  customer: user.stripeCustomerId,
  line_items: [{ price: PRICE_ID, quantity: 1 }],
  success_url: SUCCESS_URL,
  subscription_data: hadTrial ? undefined : { trial_period_days: 14 },
});

Decide what a no looks like. Show the paid plan with no trial and a way to reach you, because some people asking again are real customers.

What teams try for new accounts, and where it breaks

Those steps cover one account. For a new account, most teams reach for these, and each one does catch something.

Start with email. Gmail ignores dots, and mail to name+anything@gmail.com lands in the name@gmail.com inbox, so one mailbox can look like many customers. That's how email works. And none of it touches a second real mailbox.

Cards go further, because a card is harder to come by than an email. It still isn't one per person. Stripe's docs list prepaid and virtual cards among the common patterns in trial abuse, a no-card trial has no card to look at, and a card rule will flag a couple sharing a card or two teams on one company card.

A card step also costs you people. Say it turns away a third of your 570 real trial starts, a guess to show the arithmetic. That's 190 people, and at 6.3% about 12 customers you never meet. At $49, you've given up $588 of new monthly revenue, every month. Whether that trade is worth it depends on your numbers.

Basic checkWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead inboxesAny second real inboxPeople whose code lands in spamDeliverability work
Unique emailsThe exact same addressAny different addressAlmost nobodyVery little
Disposable-domain blocksKnown throwaway servicesNew domains, ordinary mailboxesPeople using forwarding servicesA list that never stays current
CAPTCHASimple scriptsPeople signing up by handScreen reader and privacy tool usersFees and lost signups
Phone numberCasual repeat signupsAnyone with another numberPeople without a stable mobile numberA charge per text
One trial per IPRepeats on one connectionAny other networkOffices, campuses, householdsExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listPrivacy-minded people, company VPNsAnother list to maintain
Rate limitsBursts from one sourceSignups spread over daysReal users in a busy hourTuning per route
Usage capsOne account overrunningEach new account's new capAnyone who hits the capPicking when your product stops
Shorter trialsSome cost per trialMore accounts make up for itEveryone who needed the timeFewer people reach paying
Manual reviewWhat a person can spotNights and slow patternsWhoever looks odd to a tired reader15 hours a month at 1 minute a trial

Stack them and an honest person now faces a code, a puzzle, a phone number and a card to try your product. The domain list goes stale, someone's office gets flagged, and your support inbox fills with people explaining that they're real. Each rule only answers the one narrow thing it was written for, so you never finish.

One answer before the trial starts

What none of those rules can tell you is whether this claim looks like a repeat. AbuseZero exists for that question, so you don't have to build your own abuse prevention system. You get multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and those signals are read together, never one at a time. You also get a proprietary algorithm, with AI that checks the claim again. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. It checks mailbox aliases, disposable domains and mail routing, and it detects repeated payment fingerprints across users, even when new accounts and emails hide the connection. Your IP rule sees an address, while AbuseZero sees beyond it with VPN, hosting, network reputation, Tor and proxy intelligence. Creating a fresh account isn't enough to erase previous activity.

You make one API call before your code adds the trial, and you get a clear allow or deny under rules you control. Your billing stays exactly where it is. Observe mode shows you what would be denied before anyone is blocked, and the quickstart gets your first benefit running.

Frequently asked questions

Does Stripe limit each customer to one free trial?

Not through any trial setting it documents. A trial starts when your code asks for one, so the limit has to live in your code.

Is a second free trial always abuse?

No. People change jobs and come back a year later. With AbuseZero, eligibility can be once per user or once per rolling number of days, so you decide what counts as a repeat.

Keep your trial for people who haven't had it

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.