#lennard.
1 messages ยท Page 1 of 1 (latest)
HI ๐
You would want to review our recurring pricing models for working with Subscriptions to verify we can support the use case you are envisioning.
https://stripe.com/docs/products-prices/pricing-models#model-usage-based-pricing-on-stripe
You would likely want to use an initial flat fee to represent the first x number of requests: https://stripe.com/docs/products-prices/pricing-models#adding-flat-fees
Thanks! Basically, this is the pricing I would need:
10$ flat fee -> includes 1k requests
0.1$ per unit -> over 1k requests
99$ flat fee -> includes 10k requests
0.02$ per unit -> over 10k requests
Which of the ones you sent would be better for that?
I wasnt sure because both could replicate my usecase, if I understood that right.
I would not try to pick and choose just yet. Read the whole doc carefuly and make sure you understand how each pricing model works before you decide which one will work for you
My approach would be a flat_amount=1000 and then a unit_amount=0010 + up_to=inf. Is that right? @rustic anvil
What API are you referring to? What section of the doc I sent you?
In that case you would be charging per request for the first 1K or 10K requests. You want 2 tiers with the same flat fee
0 - 1K unit_amount=0
1k up_to=inf unit_amount = 10
So that way your customers pay just the flat fee for their first batch of requests, and extra for each request after that
Okay, thanks a lot for clarifying.
Sure thing! I would recommend building this out in Test mode to verify the behavior you want: https://stripe.com/docs/test-mode
You can even use Test clocks to simulate time passing so you can test out Subscriptions https://stripe.com/docs/billing/testing/test-clocks
Wow I did not know about the clocks. Thanks!!
Happy to help ๐
Hope you have a nice day.