#fatcat_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1367243811268329472
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there!
I just want to make sure that you've looked at our recurring pricing models guide, which explicitly details how you would model a per-seat Subscriptions: https://docs.stripe.com/products-prices/pricing-models#per-seat
I see, so you wouldn't add new subscriptions. You would switch them to a team product that is priced per seat
Then modify the number of seats
Yeah and the billing would be represented by a Customer object that represents your client as an entity and has a payment method associated with it
OK I have 2 questions
- If a customer is already on a regular subscription, I am assuming I will need to switch their subscription to this new per seat model instead. Should my new default product be just a 1 seat subscription so I don't have to change them in the future?
- Our webhooks currently are set up to remove access from a user on the subscription.deleted event (when the subscription ends). How would I fire this webhook when the amount of seats changes? Should I trigger it manually instead when they remove the seat?
- That is one option, but you could also delete the Subscription and create a new one. I'm not sure if I understand the second question, though - the price is your cost per seat and then you would be using quantity to adjust the number of seats
2 - using a per-seat model you would instead probably need to pay attention to customer.subscription.updated and look at the quantity (seats)
So yes, you probably would want to delete Subscriptions manually in this case