Configure 6 trial settings before a SaaS free trial goes live: duration, payment, abuse checks, conversion, billing dates, and product setup.
Key Takeaways
- Set distinct trial lengths for each product variant to match your specific subscription plans, as Lemon Squeezy allows a different trial length for each product or variant in your store.
- Remember that changes to free trial settings only apply to new signups, so existing customers will not see updated trial rules, according to Recurly.
- To configure a cardless trial, include the
trial_periodobject withrequires_payment_methodset to false when creating a price, as specified by Paddle. - Prevent free trial abuse by blocking known disposable email address domains or implementing a CAPTCHA using a service like reCAPTCHA or Cloudflare Turnstile, a recommendation from Paddle.
- Understand that the customer gets an invoice for a prorated amount on July 22, for the period until August 1, as illustrated by Stripe.
Free trials let potential customers experience your service before paying, according to Recurly.
Set your trial duration and start date first
Define the exact number of days for your trial period before configuring any other settings. The start date anchors the entire subscription timeline, so clarity here prevents confusion about when the paid period begins.
Stripe documentation illustrates this with a specific timeline. On July 15, you give the customer a 7 day free trial (until July 22), according to Stripe. This example shows how the start date and duration combine to set a clear end date.
When setting this in your billing platform, choose a duration that matches your onboarding flow. See Onboarding checklists: 5 tools compared by page. A shorter trial may suit products with immediate value, while a longer trial fits complex tools that require setup. The key is that the end date is calculated automatically from the start date and the chosen length.
Verify how your specific platform calculates the end date to ensure it aligns with your service delivery.
Set the trial length in your product settings. Confirm the start date logic matches your signup process.
Choose between card-required and cardless trials
You must decide whether to collect payment details at signup or allow users to start without a card. This choice defines the friction level for your free trial and the risk profile for your billing stack. Compare Five landing-page tool testing statements compared.
Lemon Squeezy describes the second option as capturing the payment details of a customer as they sign up to your product, and onto a subscription with a free trial, according to Lemon Squeezy. This approach ensures a valid payment method is on file before the trial period ends.
Paddle requires specific configuration to enable trials without payment details. When creating a price, you must include the trial_period object with requires_payment_method set to false to make it a cardless trial, according to Paddle. This setting explicitly disables the requirement for payment information during the trial phase.
Stripe provides specific data fields for tracking trial status in flexible billing modes. As of API version 2025-04-30, for subscriptions with billing_mode set to flexible, trial_start reflects the beginning of the most recent trial, according to Stripe. This field helps you track when the trial period actually began for each subscription.
Recommendation: If you prioritize conversion volume over guaranteed payment collection, configure your platform for cardless trials. If you prioritize reducing failed payments at conversion, require payment details at signup. Read How 5 billing tools start a free trial without a card.
Check your platform's specific API or dashboard settings to toggle the payment requirement. Verify that your trial pricing object matches your intended friction level.
A filled reference table of trial configuration options
The following table summarizes specific trial configuration behaviors documented by each publisher. Each row cites the exact rule from the source material, ensuring that platform-specific logic remains distinct. Use this reference to verify how your chosen billing stack handles trial parameters before you finalize your product setup.
| Publisher | Setting | Behavior | Source |
|---|---|---|---|
| Lemon Squeezy | Trial length flexibility | You can set a different trial length for each product or variant in your store, giving you a lot of flexibility in how you offer trials for your different subscription plans. | Lemon Squeezy |
| Recurly | Renewal date logic | Trial dates fall before the current billing period: Renewal dates reflect the start date plus the trial length. | Recurly |
| Chargebee | Manual conversion action | If a subscription is in trial and the card details are available, you can charge the card and change the subscription from trial to active immediately through the Chargebee user interface or using APIs. | Chargebee |
| Paddle | Billing date presence | Card-required trials have a next billing date. | Paddle |
| Chargebee | Billing cycle independence | Trials are independent of the normal billing cycle and plan price. | Chargebee |
When reviewing these options, note that Chargebee also specifies that if proration is set to day-based, the time component of the trial end date is implied as 23:59:59.999 hrs, according to Chargebee. This level of detail matters when you are calculating exact end-of-trial moments for your users.
Compare these documented behaviors against your current billing dashboard settings. If your platform does not support separate trial lengths for each variant, you may need to adjust your product structure or accept a uniform trial duration across all plans. Verify which of these specific rules applies to your stack before you proceed to the next configuration step.
Prevent free trial abuse with email checks
Free trial abuse often stems from disposable email addresses that bypass standard signup friction. To prevent free trial abuse, consider blocking known disposable email address domains or implementing a CAPTCHA using a service like reCAPTCHA or Cloudflare Turnstile, according to Paddle. This approach targets the entry point where fraudulent accounts are created, reducing the volume of invalid trials before they consume resources.
When a legitimate user completes the trial period, the platform must transition the account to a paid status. If a subscription is in trial and the card details are available, you can charge the card and change the subscription from trial to active immediately through the Chargebee user interface or using APIs, according to Chargebee.
Combine these two controls to create a robust defense. First, filter out disposable email domains at the signup form level to stop bots and serial abusers. Second, ensure your billing system can manually convert trials to active subscriptions when card details are present, providing a fallback for edge cases. Review your current signup flow to identify where disposable email filtering can be implemented, and verify that your billing dashboard supports manual conversion actions for trial accounts.
Handle the transition from trial to paid subscription
The moment a trial ends, the billing platform must decide how to move the account to a paid state without manual intervention. Recurly’s Free trial management documentation states that you define the duration, choose whether to collect billing information upfront, and Recurly handles the rest — including the automatic conversion to a paid subscription when the trial ends Recurly. This automatic process removes the need for founders to manually switch plans at the trial boundary. The timing of this conversion is tied directly to the initial setup. According to Recurly, trial dates fall before the current billing period, and renewal dates reflect the start date plus the trial length. This logic ensures the first paid invoice aligns with the end of the trial period rather than an arbitrary calendar date.
Not all platforms handle the transition with the same granularity regarding partial usage. Stripe’s documentation on using free trial periods on subscriptions provides a specific scenario for prorated invoicing. In their example, if a trial ends mid-cycle, the customer gets an invoice for a prorated amount on July 22, for the period until August 1 Stripe. Founders should verify how their platform calculates these prorated amounts to avoid confusion in the first invoice.
Plan changes during a trial can also trigger immediate billing actions. Chargebee’s Trial Management documentation notes a specific interaction between trial usage and plan length. The new plan will update the subscription to be active and attempt to charge the customer because they have already used 10 days of trial and the new plan has only 5 days in it Chargebee. This highlights the importance of aligning trial lengths with plan structures to prevent unexpected charges when a customer switches plans.
Align product setup with the billing cycle
According to Chargebee, trials are independent of the normal billing cycle and plan price. This distinction is critical when you are defining the duration for your specific plan. According to Lemon Squeezy, the first step is to create a subscription product with a free trial in Lemon Squeezy.
These settings often interact with the billing cycle.
Illustrative example of a 7 day trial
Picture one plan with a 7 day trial. You set the length at 7 days and you choose whether signup requires a payment method. You block known disposable email domains on the form. On day 7 the trial ends. A second plan uses 10 days. If a customer has already used 10 days of trial and the new plan has only 5 days, the subscription is set to active and a charge is attempted. Before you go live, write down the length, the payment choice, the abuse check, and the day the paid period starts.
Log into your billing dashboard and verify the trial length and payment method requirement for your primary subscription product.
FAQ
How do I make a trial cardless in Paddle?
To configure a cardless trial, include a trial_period object with requires_payment_method set to false when creating a price. This setting allows customers to begin the trial without providing payment information upfront, as documented in the Paddle developer docs.
When does a Stripe trial convert to a paid invoice?
The customer receives an invoice for a prorated amount on the trial end date, covering the period until the next billing date. For example, if the trial ends on July 22 and the next billing date is August 1, the invoice is issued on July 22 for that specific interval, according to Stripe.
Can I change trial settings for existing customers in Recurly?
Changes to free trial settings apply exclusively to new signups. Existing subscriptions do not receive updated trial durations or conditions when you modify these settings, according to Recurly.
How does Lemon Squeezy handle different trial lengths for each product?
You can set a different trial length for each product or variant in your store. This flexibility allows you to offer distinct trial periods for different subscription plans within the same account, according to Lemon Squeezy.
What happens if a customer adds payment details during a cardless trial?
When a customer adds their payment details, they still have free access to your app until the end of the trial period. The addition of payment information does not immediately trigger a charge or end the free access window, according to Paddle.