#teeluxiii
restive tulip
Hello, if you want to cancel the Subscription at the end of a cycle, then I don't think that a Subscription Schedule is necessary. A Subscription Schedule would make sense if you need to make multiple changes to a subscription over different time intervals, or you only want to cancel after more than a single billing cycle
Subscription Schedules are complicated, and if you can achieve the same with Subscriptions alone, then I don't think you should use a Subscription Schedule
broken widget
what if i wanted to extend the cancellation time? Ex. annual subscription that auto-cancels after the 1st year, but i want to extend another few days, or another year?
restive tulip
you can use cancel_at instead https://stripe.com/docs/api/subscriptions/update#update_subscription-cancel_at
vague bronzeBOT
broken widget
Ill look into that! I am already using the schedules as I delay a transition of the prices to the end of the billing cycle (upgrading from monthly to annual prices). I guess the main thing i'm trying to avoid is an active subscription when creating via a schedule, even when the payment may potentially fail after the 1 hour draft invoice. Is there any way to avoid that?
like an error_if_incomplete but for the schedule creation
dusky sky
Yes Schedule works different with a regular Subscription, especially on how it starts. As you observe Schedule will likely simulate continuous phases, while the regular Subscription has parameters for how the first ever cycle behaves. There is no equivalent of payment_behavior on Schedule AFAIK.
You can think of creating a Subscription first, with your desired payment_behavior, then extract a Schedule from that Subscription (from_subscription parameter), then modify the Schedule to simulate your price changes transition
broken widget
I just implemented what you mentioned and it seems to be working. Wanted to double check there wasn't an alternative before having to make 3 api calls