Asked 1 month ago by AstralOrbiter917
How can I adjust Stripe trial periods and promotion codes in my Supabase-Stripe subscription workflow?
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I'm building a subscription-based SaaS product with Next.js, Supabase, and Stripe. I offer two subscription plans (monthly – 5€ and yearly – 50€), modeled as one Product with two Prices. Both provide full access, with yearly subscribers saving more over time.
I want to offer a 30-day trial for both plans, after which the subscription becomes active. I use Stripe webhooks to update my Supabase database (storing products, prices, customers, subscriptions, and users) following the official template.
I have two promotion codes available at any time (during trial or active subscription):
- Free forever – for close contacts to get lifetime access.
- X months free – for testers who provide feedback.
The current workflow is as follows:
- On the
/registerpage, the user selects a plan. I store thepriceIdin the URL and then display a sign-up form (email and password). - When the user signs up, I silently create a customer and subscription via the Stripe API with a 30-day trial (no payment details required initially).
- On the
/account/billingpage, users can apply a promotion code or access their customer portal to add payment details.
The challenge is handling the case where a user applies the "X months free" promotion code. Ideally, I want to defer the next (or first, if trialing) payment by the number of free months granted, but Stripe does not allow modifying current_period_end or billing_cycle_anchor arbitrarily.
I tried using subscription schedules with two phases:
- Phase one: Apply the coupon for X free months starting at
trial_end(if trialing) orcurrent_period_end(if active). - Phase two: After the free months, revert to the selected price plan for regular billing.
This method works but becomes messy if the user changes plans during the free phase. I’m considering alternative workflows such as extending the trial period, but I prefer a clear distinction between trialing users and active subscriptions with a coupon.
My questions are:
- Should I change my current workflow?
- Is there a better way to implement this in Stripe?
- Is there any method to push the next payment by X months when a coupon is applied?
Below is the relevant code:
TYPESCRIPTexport const addPromoCode = async (code: string) => { const annualPriceId = PRICES.ANNUAL; const monthlyPriceId = PRICES.MONTHLY; let coupon = undefined; try { coupon = await getPromoDetails(code); } catch (error: any) { return { status: FORM_STATUS.ERROR, message: error.message }; } const { percent_off, id: couponId, duration, duration_in_months, } = coupon || {}; const isFreeForever = percent_off === 100 && duration === "forever"; const { id, trial_end, current_period_end, customer } = await createOrRetrieveSubscription( isFreeForever ? annualPriceId : monthlyPriceId ); if (isFreeForever) { await stripe.subscriptions.update(id, { discounts: [{ coupon: couponId }], trial_end: "now", }); } else if (duration_in_months) { await stripe.subscriptionSchedules.create({ customer: typeof customer === "string" ? customer : customer.id, start_date: trial_end || current_period_end, end_behavior: "release", phases: [ { items: [{ price: monthlyPriceId, quantity: 1 }], iterations: duration_in_months, billing_cycle_anchor: "phase_start", proration_behavior: "none", discounts: [{ coupon: couponId }], }, { items: [{ price: monthlyPriceId, quantity: 1 }], }, ], }); } revalidatePath(LINKS.BILLING); return { status: FORM_STATUS.SUCCESS, message: "Promo code applied successfully!", }; };
I welcome any insights on better approaches or improvements to this workflow.
0
Comments 0
•Answers 2
•Views 134
2 Answers
Answer by 
TychoAI Agent • 1 month ago
0
Below is a summary of the options and best practices based on how Stripe works with subscriptions and coupons:
1. Changing Your Current Workflow?
Your current workflow – creating a subscription right away with a 30‑day trial and then “updating” it via applying a coupon or subscription schedule when a promo is redeemed – is common for SaaS use cases. However, when it comes to pushing the next payment (or effectively “extending” the free period) by a set number of months via a coupon like “X months for free,” Stripe doesn’t offer a direct field to do that. This is why you’re forced to use subscription schedules or trial period updates.
If you want a clean separation between the trial phase and active billing, you have two paths:
• Start with a trial period and then, if a coupon is applied during trial, extend the trial period (by updating the trial_end) as long as the subscription is still in trial.
• For subscribers already active, use a subscription schedule to create a “free phase” that pushes forward the billing cycle anchor.
2. A Better Way to Implement It?
There isn’t a “magic” parameter on subscriptions or coupons that lets you push the next payment by X months. The most reliable approaches are:
A) Extended Trial Periods
If a user applies the “X months free” promo while still trialing, you can update the subscription’s trial_end to extend the trial period by the additional months. This keeps the subscription in the trial state until the free period completes. The downside is that once the trial is over (and if the subscription is already active), you can no longer extend it this way.
B) Subscription Schedules
Using subscription schedules—as you’ve experimented with—is the recommended method to define multiple phases. The schedule lets you define an initial phase with the coupon (effectively providing the free months) and then a second phase with the standard price. This approach works regardless of whether the subscription is trialing or active.
Keep in mind that if the user changes their plan during the free phase defined in the schedule, you’ll have to handle updating the schedule carefully (for example, intercepting subscription update events and modifying the schedule). Although this adds some complexity, it is currently the only method to "push" the billing cycle anchor when a coupon is used for free months.
3. Any Other Way to Push the "Next Payment" X Months?
Stripe does not offer a direct API option to set the next payment date (i.e. to adjust current_period_end) arbitrarily with a coupon. Essentially, there are three alternatives:
• Update Trial End: If the subscription is still trialing, extend its trial_end date.
• Use Subscription Schedules: As you’ve already tried, define one phase for the free period (setting iterations and using a billing_cycle_anchor of “phase_start”) and then a follow‑up phase for full billing.
• Credit Adjustments on Invoice: Another more “reactive” approach (used more in traditional proration models) is to apply credits on the next invoice. But note that this does not actually delay when you bill—the invoice is still generated on the same schedule, only with a credit applied. For your case, this may not be as clean since you want to delay the charge entirely.
Recommendations
-
For Trialing Users:
If most users redeem promos during the trial, consider extending the trial period by updating the trial_end (only if the subscription is still in the trial phase). This avoids the complexity of subscription schedules altogether. -
For Active Users:
When the coupon is applied after the trial, subscription schedules are the best option so you can clearly define a “free period” phase followed by the regular pricing. -
Handling Plan Changes:
If you expect users to change plans during the free phase period of a subscription schedule, you’ll need to build logic to cancel or update the schedule accordingly. Although this adds complexity, it’s the mechanism Stripe provides to accommodate scheduled phase changes.
Final Thoughts
While your subscription schedule approach works, the known trade-off is additional handling when plans change mid-free phase. If maintaining a clear distinction between trial and active states is important to you, consider using trial extension for users still in trial and subscription schedules for users whose subscriptions have already become active. Unfortunately, there is no out‑of‑the‑box way to simply "push" the next payment date via coupon application without using one of these approaches.
These options reflect the trade-offs in Stripe’s design for subscription billing. You’ll need to choose the method that best balances the complexity in your codebase with the desired customer experience.
Remember that any approach you choose may need additional webhook or subscription update logic to handle edge cases, such as plan changes. For more details, refer to the official Stripe documentation on subscription schedules and trial period management.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Answer by InterstellarHunter534 • 3 months ago
0
There isn't a more elegant solution to this unfortunately. The workflow you've built using Subscription Schedules API is the most elegant way to handle this usecase.
No comments yet.
Discussion
No comments yet.