#Pranay

1 messages · Page 1 of 1 (latest)

solid boneBOT
dusty remnant
#

Hi
Could you please share the invoiceId ?

tribal sierra
#

Invoice id - in_1NSyg8SAdkvFpi1wMutMRc6E
Mind you the above information was just for example and I'm doing this in test mode.

dusty remnant
#

Checking...

#

The invoiceId you were sharing is for $1,632.00 is it the same scenario?

#

If so what were you expecting as amount ?

tribal sierra
#

As the billing start date is July 12, I will be using the product for remaining 18 days. So the amount should be (18/30) * 1632 = $979.2

dusty remnant
#

OK I think I'm missing something here... Could you please reexaplain the pricing model you are using and what you want to achieve ?

tribal sierra
#

Sure. I have volume-tiered pricing where if my usage is 50 users, I will be charged total of $1632 for a month. But for the first month, If I start my subscription on 12th of July, I shouldn't be charged for the first 12 days. I should be charged only for the remaining 18 days.

forest glen
#

Hi! I'm taking over this thread. Give me a few minutes to catchup.

#

This is your pricing:
The invoice you shared has an usage record of 50, so it's expected that the total is $1,632.00

tribal sierra
#

Why is the amount calculated for the whole month? Why doesn't the prorated billing charge only for 18 days?

forest glen
#

This is a metered subscription, so there's no protation. The total only depends on the number or record usage you set (here 50).

#

I think your use case is not a metered subscription, but a regular subscription where you update the price (and/or quantity), which would create prorations.

tribal sierra
#

No. My use case is a high-water mark type of subscription. That's why I have selected Maximum value during period and I want the above behavior to take place. Does stripe support it out of the box? Could you please help with some alternative ways to handle this in stripe?

forest glen
#

If you set a record usage of 50 on the subscription, it means the user actually used your service 50 times, and so will be charged $1,632 exactly as mentioned in your pricing. There are no prorations in this case since it's usage based.

#

So I still don't understand how you want prorations to work in usage based subscription.

tribal sierra
#

Thanks! I got your point. I might come back here and ask some more related doubts. Is it possible to keep this thread open?