#bamelement_best-practices
shell sluiceBOT
đ 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/1395809685965377617
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
runic mulch
Hi! You might want to reach out to get included in this: https://docs.stripe.com/billing/subscriptions/mixed-interval
heady agate
Interesting! This solves one of our issues.
However, to get to our desired result, it seems like we would need something similar to this on the tier level (i.e. 1st tier on annual billing cycle, 2nd tier on monthly). Now that sounds unnecessarily complicated.
The alternative is having the flat free portion and the overage portion of this model as separate products and pull them both into the sub. It just would have been nice to it all self-contained in a single product.
runic mulch
Yup, fair. Stripe Products and Prices won't map to everyone's concept of a 'product' or 'price', so there will always be some adapter/wrapper-like abstraction required there.
shell sluiceBOT