#mochihealth
silver fossil
timber geyser
What part are you confused about?
cerulean cedar
so i want to have a way to upgrade and downgrade subscriptions but I wan the behavior to only take place in the next billing cycle
so if i have a monthly subscription and the a person wants to upgrade to a 3 month sub I want the monthly to finish out and then automatcially switch them to the 3 month the next time the billing cycle comes along
same thing with downgrades
I dont want any prorations
just have it take effect in next billing cycle
timber geyser
Gotcha. So yeah you'd want to create a subscription schedule from the existing subscription first. What that would do is set the current phase to be the current subscription. Then, you'd want to update the subscription schedule, adding a new phase for the upgrade you mentioned
timber geyser
timber geyser
You just specify 1 iteration if that's all you want
cerulean cedar
but that means that means the subscription still sticks around after that right
its just the schedule abstraction is gone after that
timber geyser
You configure the end behavior yourself: https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-end_behavior
You can cancel or keep
cerulean cedar
also if the behavior is release and the next phase is to switch from month to 3 month and the iterations is 1 would it release right away after it made that change or wait 3 months and then release
is there anyway I can do the change and then release it right away
timber geyser
No end_behavior is for when the last phase ends (not between phases)
cerulean cedar
so can i make the start and end time of the second phase the same so it releases right away?
also does a subscription being in a schedule affect any changes that you would want to make to the subscription or impact being able to make refunds or anything
timber geyser
By 3 month subscription do you mean a monthly price that only runs for 3 months?
cerulean cedar
By 3 month subscription do you mean a monthly price that only runs for 3 months?
no it renews every 3 months
is there any extra overhead that I need to worry about when using schedules
like do I need to check if a subscription has a schedule attached to it and handle any scenarios differently if one is attached as opposed to if there isn't one
timber geyser
Gotcha. You would want the end date to be slightly after the start date. You shouldn't need to handle any scenarios differently. Under the hood it's just a subscription. The subscription schedule is just an abstraction built on top so you can schedule changes
cerulean cedar
can i cancel a subscription that has a schedule on it or do i need to release it manually first
timber geyser
Good question. I think you can just cancel, but let me confirm first
cerulean cedar
is there any advantage/disadvantage of letting it realease right away vs wait one iteration
also what would be the best way to test sub schedules?
timber geyser
No advantage
Recommend just doing 1 iteration tbh
It's simpler
I recommend test clocks
And I just confirmed you cancel the sub directly and all will be fine
cerulean cedar
thanks