#gpatra_docs
remote cypressBOT
đ 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/1283704717268226070
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- gpatra_code, 15 hours ago, 6 messages
daring nest
hi! no it's not possible sorry, it's a common feature request to only allow updates in one direction, but not something we've built into the portal yet.
fallen inlet
Okey. so i think we need to build custom billing ui for this.
Would it be okay if I discuss the use case with you? It will only take about 2 minutes of your time.
daring nest
of course
fallen inlet
The use case is as follows:
Suppose a customer has purchased 3 seats in a subscription, allowing them to add 2 more team members for collaboration. However, the next month, the admin decides to reduce the number of seats to 2 without removing the 3rd user. In this scenario, the user should be able to remove the additional user directly from our platform, after which we can allow them to decrease the seat quantity.
daring nest
hmm. So you mean the quantity on the Stripe SubscriptionItem (controlling what is billed) will be out of sync with the number of "seats" in your database?
fallen inlet
Syncing is working, but I want to prevent users from decreasing the quantity in billing without first reducing the actual seats used on our platform.
daring nest
well , assuming you do not use the CustomerPortal, then it's straightforward. The quantity can only be changed if you call the API, and you build your own portal/customer dashboard in such a way that you only allow upgrades not downgrades, and only call the API after you've updated your database.
if you do use the Portal it's going to work differently since instead the customer can proactively makes changes, and you respond to webhooks to update your local state
fallen inlet
got it.