#bill92_api
uncut baneBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1501037803092443187
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solid jewel
hey, building a saas with a base plan + add-ons as subscription items on a single stripe subscription. when a user cancels an add-on mid-cycle i want them to keep access until period end without canceling the whole subscription.
stripe doesn't seem to support per-item cancel_at_period_end so my plan is to delete the item immediately with proration_behavior: 'none' and store the expiry date in my db to gate access.
is there a cleaner way or is this just the way it is?
jaunty rock
Hi! Let me look into this. Give me a moment.
solid jewel
thanks
jaunty rock
Thanks for waiting! Currently there isn't a native per-item cancel_at_period_end method. The way you are planning to do it is one option. Another option is to use Subscription Schedules. You can convert the subscription to a schedule and define a next phase that excludes the add-on item. Stripe will automatically remove it at phase transition (period end). This way you don't need to track the due date in your DB.
solid jewel
with this approach, all future subscription changes must go through the schedule api, not the subscription api?
jaunty rock
By "future subscription changes" are you referring to the use case you mentioned where you only want to remove 1 item instead of ending the subscription?
solid jewel
the base plan is the subscription, the traditional way of how stripe works
the add ons are items that live inside that subscription
so the user can add 1 mid cycle to the base plan, he will be prorated, and once payment is done, access will be given
he can cancel or add add ons as he wishes
the main catch is that I want everything to be billable at the same time as the subscription
thats why I prorate on addon selection and want to cancel at period end (a specific add on)
jaunty rock
Sorry so what is the exact question or issue that you are facing here?
solid jewel
sorry, just wanted to give more context, but the original question was
when a user cancels a specific add-on (subscription item), is there a native way in stripe to keep that item active until the end of the current billing period without canceling the whole subscription?
you mention subscription schedules, so I will try to check them out see if they are a good fit
jaunty rock
Ah got it! Yes Subscription Schedules is the only other option. Do check it out to see if it meets your use canse and feel free to let us know if you have any questions.
solid jewel
will you say that is a first class api for my use case? or was it built for other purposes?
(sorry, first time hearing about them hehe)
jaunty rock
It was built for multiple use cases (https://docs.stripe.com/billing/subscriptions/subscription-schedules#use-cases) and yours is one of them 🙂