#volco5952_docs
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/1333945691537670145
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- volco5952_docs, 16 minutes ago, 28 messages
Previous discussion about subscription prorations with tiered volume pricing. Trying to think of a way to accomplish similar behaviour using usage-based pricing to take advantage of billing thresholds, which don't seem to be available to volume pricing
๐
I think you're looking for this: https://docs.stripe.com/billing/subscriptions/usage-based/pricing-models?dashboard-or-api=api
So when you create the Subscription, the customer is immediately charged for the flat fee for Jan 1 - Feb 1. The next invoice on Feb 1 will contain usage from Jan 1 - Feb 1 plus the flat fee for Feb 1 - Mar 1
No prorations though
Great, that is really helpful. It wasn't exactly what I wanted since it only charges a flat rate upfront, rather than an initial (so if my unit count was more than what is given in the flat rate, the difference wouldn't be charged until end of billing period) but its pretty close! Is it safe to say there is never any prorations possible for usage-based models?
Right, that's safe to say. There's no "credit" for time not used on a billing model that depends on reporting usage and where usage is calculated in arrears
Got it, thanks. You've been really helpful today and I appreciated your time