#simeng
1 messages · Page 1 of 1 (latest)
👋 How can I help?
Hi we are tring to integrate our SaaS product with Stripe using a subsciption base billing method.
And we would like to define a pricing model with different tiers
however the tier threshold is base on two factors MAU and average DAU
What are MAU and DAU?
Monthly active users and Daily active users
Can you share an example of how you expect the pricing model to be like?
sure. Give me a moment.
Under the hood it is a Usage-based pricing model. The base unit will be MAU (monthly active users ). And there will be a unit price P. Without tiers, a foundamental monthly billing will be simply MAU * P.
However we would like to define different tiers with different unit prices basd on the usage frequency. The tier variable would be calculated based on average DAU divided by MAU. That may represent how frequently a end user use this product. The more often they use, the cheaper unit price would be.
So in a short words. Our request would be define a tier logic that is based on two dynamic factors, the standard usage unit (MAU). and another one average DAU
Some example. Two differnt billing with same MAU 30.
A: MAU 30, average DAU: 1.
B: MAU 30 average DAU: 30
A stands for there are different users visiting this product every day. Each user only be active for one day. B on the other hand, have 30 different users active daily.
You can use usage-based tier pricing: https://stripe.com/docs/products-prices/pricing-models#usage-based-pricing
How the usage is calculated and submitted will be done at your server, i.e. the average DAU divided by MAU toward the end of the cycle, and Stripe will calculate based the tiering provided
I thought we have to precisely define a pricing model ahead, including the tier definitions, and all the final bill is calculated based on the usage unit we provided.
At the stripe side
Yes. From the example you shared, shouldn't you have precise pricing model of the DAU/MAU on different tiers?
referencing this schema
yes, but both DAU and MAU is a dynamic variable based on the usage right?
The final price is still MAU * unit price
but we need a way to provide the DAU/MAU on each billing cycle
Why can't you define the pricing model based on DAU divide by MAU since the usage records are based on DAU/MAU?
DAU/MAU is gonna be a factor to be used to identify the unit price.
The final bill would still based on the MAU usage
MAU * unit price
e.g. if DAU/MAU < 0.5 unit price is $2.
DAU/MAU >= 0.5 unit price is $1
the difference is MAU * $2 or MAU * $1
I see! Stripe tiering is based on the quantity/usage submitted. It can't be tiered by the factor (DAU/MAU)
As I understand. unit_amount here will be the MAU which stands for the usage ammount.
yes
that is sth I would like to figure out
One way I can think of is to manage the factor tiering on your own. For example,
- DAU/MAU < 0.5 is price_A
- DAU/MAU >= 0.5 is price_B
When your system submits the usage records, check the price of the factor tier and then submit to the corresponding pricing tier
hmm trying to absorb this. So a customer will sign with a subscription contract with a specifiic pruduct and a price model right?
So we define multiple price under that product, or define multiple product.
when our server submit the final usage, we calculate the tier and submit to differnt products?
instead of using strips tiered pricing model. translate info different product based on the prcing tier?
So we define multiple price under that product, or define multiple product.
Multiple prices under the product
when our server submit the final usage, we calculate the tier and submit to differnt products?
Submit to different prices that corresponds to the factor tier
instead of using strips tiered pricing model. translate info different product based on the prcing tier?
One product can have multiple prices. You will translate the factor into different prices
get it. I'll take a deep look at that direction thx. Just two more quick questions:
- since the tier gonna be calculated at our side. Is there any rules stripe request us to follow or must present to the customers ahead of signing the subscriptions? I understand stripe trying to make the billing info as transparent as possible. With this approach the average DAU number going to be a black box for the stripe and customers.
- Another thing come to my mind. Is it possible to apply discount automativelly based on the DAU/MAU we just mentioned? Would that be another approach
- We recommend to show the pricing details in your website or in the subscription details shown to customer as clear as possible to avoid any dispute/chargeback in the future.
Alternatively, you can add all the tier prices to the subscription. Since they are usage-based billing, customer will only be charged on the price that the usage records submitted. However, customer will see all your self-defined pricing tiers with this approach.
- Stripe doesn't support automatic discount. Your system can add discount to the invoice when the invoice is still in
draftstatus
I see. good to known. Thx for the assist. Appreciate it.