#rodney_best-practices
high drumBOT
đ 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/1392196368788885504
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
mellow bane
hello! just to double check, is your question just if this pricing model is supported in stripe?
obtuse flint
Yes! I just want to make sure I haven't missed a restriction on multiple metered prices being active on the same product on a subscription or something along those lines
mellow bane
nope that should work just fine! as with anything like this i would recommend setting up a test to confirm it works the way you expect using test mode
i strongly recommend scripting out some examples using test clocks
https://docs.stripe.com/billing/testing/test-clocks
obtuse flint
Great thanks for confirming, yes we're building out our test suite but just wanted to make sure I wasn't building down an anti-pattern (as I have done in the past lol)
mellow bane
hehe no worries. rather than building out a whole test suite i'd maybe even start with just a one-off script that creates a customer and subscription, attaches a test clock to them, registers some meter events, and advances time to see how the subscription plays out
that way you can sanity check things quickly before building something that will be harder to quickly change