#confusedcoder
1 messages · Page 1 of 1 (latest)
Hello! Tiers aren't required when using usage-based pricing.
Not sure I understand your last question, can you provide further details? Like have you tried this and run into something that's blocking you?
Thank you for the response! I haven't tried this yet, but I'm reading through the documentation and trying to see what to implement.
My current flow is 3 monthly subscription based products using stripe checkout.
My application allows users to make API calls and other processing that would require extra payment. I'm currently keeping track in my own logic and database of usage. I want to be able to bill them once a month for the extra usage.
I strongly recommend you give this a try. Seeing how this actually works in practice will provide a lot of clarity.
The only thing I'm questioning at the moment is this:
"Throughout each billing period, you need to report usage to Stripe so that customers are billed the correct amounts by creating usage records with a subscription item, quantity used, and a timestamp."
What would the subscription item in this case be? In the example they use pricing like $0.0010 per email. So you have an item and a quantity. I wouldn't have these.
What would you have instead?
Well the processing and API calls I'm using don't have a set structure. It's completely dependent on how complex the user makes them.
I wanted to just bill them every month with the metrics I'm using in my application
On top of the monthly subscription
It sounds like you don't want usage-based billing at all, but rather you want to add Invoice Items throughout the period for arbitrary amounts that will be swept up and charged when the Subscription generates the next Invoice: https://stripe.com/docs/api/invoiceitems
Are invoices automatically charged or are they left to the end user to submit payment? It looks like the latter?