#cbayford
1 messages · Page 1 of 1 (latest)
I cant seem to see a way to set this up without creating a massive number of tiers in a given price on a product.
Can you explain why you think this needs many tiers?
It sounds like it needs just two tiers, under and over the monthly base limit
Unless you have many different limits
it would be $x per 1000 units... i.e. $5 for the first 1000 and another $5 for the next 1000 ($10 for 2000)
so I would have to set up a tier for each 1000 units
0 - 2000 $0
2001 - 3000 $5
3001 - 4000 $5
etc
Ah, gotcha
i just want to set it up so that the first x units is free and then each additional 1000 units get charged $x
does that make sense?
I'm inferring this is usage based / metered, right?
correct, they will pay a base fee per month or year... but the usage will be metered monthly
So I think you'd want to use graduated pricing with flat fees
https://stripe.com/docs/products-prices/pricing-models#adding-flat-fees
The first tier, up to your monthly limit, would have zero unit cost but the monthly flat rate
the second tier would have no flat fee but the per unit cost
For amounts below 1c (unit_amount=1) you should be able to set that using unit_amount_decimal
https://stripe.com/docs/api/prices/create#create_price-tiers-unit_amount_decimal
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
but it would seem that I would still need to create multiple tiers this way? or am I missing something?
one tier per 1000 units i mean
No the cutoff is the monthly allowance
then you enter the per unit cost, eg $5/1000 = $0.005/1
So if you monthly flat rate was $50 for the first 10000, say
tier 1 would be up to 10000, with 0 unit amount, 50$ flat rate
tier 2 would be over 10000 units, 0 flat rate, 0.005$ unit cost
you can also consider unit quantity transformations if you wanted to price that way:
https://stripe.com/docs/products-prices/pricing-models#transforming-quantities
ok, so lets say the base monthly usage is 2000, once the user hits 2001 they get charged an additional $5, and then if they hit 3001 they get charged an additional $5, I cant really charge per unit in this scenario...its more of a flat rate...
I am sorry if I am missing what you are meaning
Ah gotcha, yea so transforms handle that scenario with rounding up
See the example there
ok, i will have a look.