#stealth_api
lusty nacelleBOT
đ 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/1492133866406805664
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
winged fox
I believe it would charge again. When Step 3 reverts the quantity with prorate=false, Stripe only suppresses new proration items for that call. It doesn't remove the pending proration items already created in Step 2, so Step 4's prorate=true adds a second set of proration charges on top of them.
Ideally, before executing Step 4, you should manually delete the stale proration invoice items from Step 2 so the upcoming invoice starts clean before the new proration is applied.
tame lintel
I see. Is there another way to avoid charging for the same quantity multiple times? What I want to achieve is that once customer increases quantity they have to stick with it for the entire period (that is, they will be charged for that amount of quantity even if they reduce the quantity later on). But I also don't want to charge multiple times if the customer has already been charged for it for the current period.
I would like to avoid schedules. They quadruple the complexity.
winged fox
The cleanest approach might be to avoid reducing the Stripe subscription quantity mid-period. Instead, when a customer decreases their seat count, record that in your own database but leave the Stripe subscription at the current (higher) quantity unchanged. Then, only sync the actual desired quantity to Stripe at the start of the next billing period. This way, mid-period upgrades always prorate correctly, downgrades are honored at renewal without any credit issued, and you'll never end up with duplicate proration items from bouncing the quantity up and down