harun0221

[sturdy goblet]

Hello 👋
Is there a specific concern you have with Schedule having an end date? An end date just means the schedule would end. Doesn't mean the subscription would be cancelled. You can set the beahviour with end_behaviour
https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-end_behavior

When you set end_behavior to release, the subscription will continue as is.

The alternative would be
1/ Create a schedule when customer wants to update a sub
2/ Add a new phase for the "update"
3/ Once the schedule moves to the new phase, release the subscription from the schedule.

[real karma]

Hey,
Tanks for the quick response!
My usecase is, whenever a user upgrade his subscription to another subscription i want it to change on the end of the current period.

So lets say I have Sub A and Sub B . The user wants to change from SubA to Sub B in the middle of the subscription period. It should not immediately change. Instead it should change in the upcoming period.

If i understood what you mean, i just should create a schedule for the subscription with the end_behavior set to "release" and the user stays in the new Subscription?

[whole urchin]

Yes, setting up a subscription schedule will allow to you schedule whatever changes and then the release behavior means that the subscription stays around after the schedule is over

You'll set up something like this example use case https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#upgrading-subscriptions