#uziiuzair_subscription-meter
cerulean coyoteBOT
đ 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/1270811887394623638
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
wanton dust
@clever galleon I don't really follow your logic. "usage-based billing" charges at the end of the period, not at the beginning. You should be creating the Subscription first and then report usage that will accumulate over the current period and be charged on the next Invoice
uziiuzair_subscription-meter
clever galleon
You're right, it doesn't make sense to me either. haha
My product would be charging per seats, But I would love to be able to charge them when they create the subscription.
Maybe I could predefine a rate to charge them for the first invoice? Is that possible?
wanton dust
Sorry I still have no idea what this means. If you charge per seat then "usage based billing" is the wrong fit for you
Usage-based billing is more "charge for every email being sent" or "charge for every token used in an AI request".
Per-seat pricing is usually based on quantity.
See https://docs.stripe.com/products-prices/pricing-models#per-seat
cerulean coyoteBOT