#seikun_best-practices
candid leafBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252399978777940118
đ Have more to share? Add details, code, screenshots, videos, etc. below.
dry tendon
We document a lot of common billing models here: https://docs.stripe.com/products-prices/pricing-models
Might be worth digging into that doc a bit
mystic solar
we have a seat-based subscription model that is working, but our main concern is with potential abuse of prorated payments. e.g.:
- user creates an annual subscription with a single seat (e.g. we've immediately charged them for 1 seat x annual price)
- user increases seat count by 99 more seats (we haven't charged them for the additional 99 seats yet, that prorated cost will be charged in the next billing cycle invoice)
- a day before the next billing cycle, the user attempts to delete their account
We were thinking that we allow the user to delete their account if we are able to successfully invoice them the prorated amount for the 99 added seats, and prevent them from deleting their account if payment fails. Just not sure if this is the right approach