#xxxxxxxxxxxx_api
vapid lightBOT
👋 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/1314227263746609254
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
stable merlin
• How can I change the billing interval only after payment succeeds, preventing access without payment?
• How do I prevent extra invoices when changing billing intervals, since proration_behavior='none' doesn’t help?
• What are the best practices for handling such subscription upgrades?
hoary raptor
hi! https://docs.stripe.com/billing/subscriptions/pending-updates would be the general answer here yes but there are some limitations of that feature unfortunately.
stable merlin
Hi 🙂
Sadly it doesn't work with product having different recurring times (monthly product to yearly)
Maybe I should have asked for "code" help and not "api", sorry 😦
hoary raptor
How can I change the billing interval only after payment succeeds, preventing access without payment?
not really a good way. You could process your own directly-created Invoice or PaymentIntent, and when that succeeds, do the update call. Use something like a 100% off one-time coupon to avoid the payment on the new invoice.
How do I prevent extra invoices when changing billing intervals, since proration_behavior='none' doesn’t help?
we always create an invoice when the cycle changes. Consider a coupon as above to avoid payment.
stable merlin
Oh okay, didn't think about a coupon. Is it a good practice to generate a coupon like this to handle unwanted invoices ?
hoary raptor
I think it's the only way really. Well the other way is adding a negative invoice item or adding to the customer's balance; overall the idea is just to cancel out the payment.
Ideally the best practise is to use the pending updates feature but it's not possible in many cases and this is about the only workaround I can suggest. Otherwise it's a case of do the update and then manually roll it back if the payment fails, which is just really messy
stable merlin
I don't really know if there is any technical limitation for Stripe to handle this case but it seems common (for big saas even more after days like Black Friday where upgrades happens a lot).
Hope one day we will have a better way to handle this, anyways, thanks a lot for your help karllekko you are my hero