#abhishek-kumar_docs
ocean frostBOT
👋 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/1222546632177090770
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
versed stratusBOT
ashen mist
When you say "pay upfront price", do you mean a one-time fee when starting the subscription? Or like a flat fee each month?
versed stratusBOT
modern thorn
No I mean, if the user adds a new "seat" then they'd have to pay the fee for that seat at that moment itself and then later it'll be adjusted in end of cycle billing.
eg.
1 seat = $10
Org with 1 seat
Billing amount: $10
_Another seat is added to the org _
User pays $10
the subscription is of 2 seats and since 1 seat price is paid upfront then the user only needs to pay $10 again at the end of billling cycle.
1 seat is removed
For the current billing cycle, the price would remain the same.
2x seats
But for the next billing cycle, since the seat is removed it'll 1x seat
lmk if this makes sense^
and thanks for the speedy reply!
ashen mist
Ah in that case, you'd need to set proration_behavior to invoice_now when you update the seat quantity on the subscription
See: https://docs.stripe.com/billing/subscriptions/upgrade-downgrade#immediate-payment:~:text=to past_due.-,To bill a customer,-immediately for a
modern thorn
I'm running simulations for this rn
thanks for this I don't know how I missed this 😓
modern thorn
alright thanks for this!
Apparently I had tried this just found out from the logs.
The pay upfront works upto an extent of what we require 🚀
Now the last hurdle would be to avoid decreasing the amount if seat is removed.
I've tried to decrease from 4 -> 3 seats and this is how it calculated
it charged $20.32 but my expected price is $30.
It balanced with the previous billing cycle :/
I updated the subscription with: Charge proration amount on next invoice from the Update subscription slider
Please let me know how else this can be achived
glass sluice
Hey @modern thorn, apologies for missing this update originally. Looking in to this...
If you specify proration_behavior='none' that will prevent the user from getting credit from the change
modern thorn
But then it’ll reduce the amount for the current cycle itself right?
Meaning the user will be still paying for 3 seats itself but used 4 seats for a brief period of time, am I getting this right?
Instead I want like a “downgrade in next cycle” kinda change.
I’m not sure if this is possible atm or not.
But please let me know
thanks!
glass sluice
Ah gotcha, you can do this with a subscription schedule
https://docs.stripe.com/billing/subscriptions/subscription-schedules/use-cases#existing-subscription
https://docs.stripe.com/billing/subscriptions/subscription-schedules/use-cases#increasing-quantity
A subscription schedule manages a subscription and can make scheduled changes like this. Unfortunately, subscriptions cannot schedule this kind of thing by themselves. One thing to consider is that once you have this scheduled update, updating your subscription again gets a bit more complicated. Schedules work in phases, and if you update the subscription directly, that will only change the current phase, so you will want to make any changes that you want to persist on both the current phase and next phase if you want the change to persist.
modern thorn
aahh got it.
yep, any updates going through are via our webhooks and can configure it accordingly.
I'm trying this out in simulations