#magda_api
silent furnaceBOT
đ 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/1394327271036162163
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
long shell
Hello
So a workaround here would be to have two Billing Portal Configuration objects. One that cancels immediately and the other that cancels at period end - https://docs.stripe.com/api/customer_portal/configurations/create#create_portal_configuration-features-subscription_cancel
And when you create a Portal Session for Customers (assuming you're using the APIs) - you can specify the relevant Configuration object ID in the request - https://docs.stripe.com/api/customer_portal/sessions/create#create_portal_session-configuration
agile swallow
We have a potential workaround, which is to not use the hosted portal session but manage the cancelling via api. This way we could set a subscription to cancel immediately or at the end of billing cycle depending on the subscription status (active/past due) and building our own ui. But do you think this is something you would be avle to add to customer portal?
long shell
That would allow you to switch back and forth between two configs
agile swallow
Oh, that's great! Thank you.