#camsmi1993
1 messages · Page 1 of 1 (latest)
Hi there! With schedules, release means that the subscription managed by that schedule will continue indefinitely with the latest phase's details
cancel means the subscription itself will be canceled at the end of the last phase
ah okay. Thank you. A follow up question. My use case is changing a three month subscription into a month to month subscription( It's the same subscription just a different pricing model.) Would canceling the subscription or releasing the subscription before updating the subscription to the new model be the route to go? Or am I in the wrong wheelhouse entirely? Thank you for your time!
Got it. Schedules would be a good use case for this. It sounds like you'll want to start the schedule with the three month phase (one iteration of this), followed by a phase with one iteration of the monthly subscription, and the end_behavior should be release, so the monthly subscription can continue
Yep, that's exactly what I want to achieve! A seamless transition without a user being charged for both iterations at the beginning of month four. So I was wondering the best practice for that type of change
Got it. using release is the way to go here. If you haven't already, I recommend simulating subscriptions and schedules with test clocks - https://stripe.com/docs/billing/testing/test-clocks