#feminaagravat_39821
spring gust
Hello there
Proration is calculated by the second.
So based on how many seconds were used/remain from the previous period when the update occurs.
void cloak
Say for example i have product whose price is $75 per year. so when i update my subscription one month before next invoice then will i be charge like $1 or $2 ?
spring gust
You would be credited 1/12 * $75 in that case.
Really the best thing to do here is to test it out!
You can use test clocks to easily test proration: https://stripe.com/docs/billing/testing/test-clocks
void cloak
Can I have condition like minimum proration charges when i add new item to subscription. Proration amount should not be small like $5 or less
spring gust
You would have to set up that logic yourself. The way to know the proration amount ahead of time is to use our upcoming Invoice API: https://stripe.com/docs/api/invoices/upcoming
You would call that endpoint and then based on the amount of proration you would specify the proration_behavior that you would use on the Subscription update
void cloak
I am using proration_behaviour = 'always_invoice'
I am just passing the product price and stripe automatically calculate the prorated amount. Sometimes it is small charge when i add new item to subscription and update it .
spring gust
Yeah you can't prevent proration in that case really. You would have to pass proration_behavior: 'none' for proration to not occur but then an invoice may not get cut immediately
void cloak
I can have my custom proration charges for updating the subscription using API?
void cloak
If stripe proration amount is small less than $10 then I want to pass my custom prorated amount if user wants to update the subscription.
rough mountainBOT
spring gust
Patience, we help multiple people at the same time on this server
We won't always respond instantly
void cloak
ok np
spring gust
If stripe proration amount is small less than $10 then I want to pass my custom prorated amount if user wants to update the subscription.
Are your Subscription updates going to contain Prices that use the same interval? Or different intervals?
Like will they update from Yearly --> Monthly?
Or will it be Yearly --> Yearly?
void cloak
not it will yearly->yearly
spring gust
And I assume you want to always Invoice immediately, not wait until the next billing period?
void cloak
but in the mid of the year if user want to add new items in subscription then they can do it. so that's why we are using proration
void cloak
And I assume you want to always Invoice immediately, not wait until the next bil...
yes, whenever they add new item and update the subscription
spring gust
Okay so then in the scenario where you don't want to prorate you want to use proration_behavior: 'none' and billing_cycle_anchor: 'now'
In the scenario where you do want to prorate you just use proration_behavior: 'create_invoice'
void cloak
then how can i charge for difference of amount ?
spring gust
The above will charge for the difference?
Doing the above will cut a new Invoice based on the updated Prices
void cloak
Do you mena that small amount will be adjusted in next billing ?
spring gust
I don't know what that means.
If you update a Subscription with proration_behavior: 'always_invoice' then the new Invoice will contain proration from the last period.
If you update a Subscription with proration_behavior: 'none' and billing_cycle_anchor: 'now' then the Subscription will update without the Invoice containing proration from the previous period.
void cloak
Say for example,
I have one subscription whose next invoice date
is on 11/9/2023 . Now today user is adding new items of $75/year to existing subscription .
So remaining days are 64. As per proration it will charge customer $1.03 but i want atleast $15 as minimum charge for updating the subscription and from next invoice it should add 75
spring gust
Yep so you would do proration_behavior: 'none' and billing_cycle_anchor: 'now'
Have you tested doing that yet?
It will likely just be easier to test and update like that so you see what it does
void cloak
if i do that then customer has to pay full payment of invoice right ?
void cloak
Have you tested doing that yet?
not yet
spring gust
if i do that then customer has to pay full payment of invoice right ?
Yes
Which is what you said you wanted
void cloak
so it will invoice the customer
850 current subscription + 75 newly added item
void cloak
I am not sure wheather my customer will like this or not. Its like i am forcing them to pay early.
spring gust
Yeah that part is up to you
Not sure why you want to disable proration at all to be honest
void cloak
i don't want to disable proration
i like proration , but the case which i have mentioned they will pay amount which is less than $10. So i want some minimum value for busimess.
spring gust
No they would not pay less than $10 in the scenario you just spoke about
They would pay again for the whole next year
They would get a very small credit for the remainder of the current year
So they would just pay slightly less than the full amount for a year on the new Price
void cloak
in proration_bahaviour = always_invoice or billing_cylce_anchor = now ?
spring gust
proration_bahaviour = always_invoice
void cloak
So in this case
I have one subscription $850 whose next invoice date
is on 11/9/2023 . Now today user is adding new items of $75/year to existing subscription .
So remaining days are 64.
in this case what is the amount for proration_bahaviour = always_invoice
I don't know how to use test clock. Can you please create test clock for above scenario ?
spring gust
No
You are a developer and you need to create that scenario in your own test environment
I cannot do that for you.
void cloak
ok