#sharda_02153
half badge
Hi 👋 it looks like it's including a proration from a previous update that was made to the related Subscription. If you don't want to create prorations when making updates to Subscriptions, you will want to look into leveraging the proration_behavior parameter when making those updates:
https://stripe.com/docs/api/subscriptions/update#update_subscription-proration_behavior
finite gate
We have set the proration_behavior none but it still counting the difference
What we can do to avoid adding this additional amount
half badge
Can you share the ID of the Subscription where you're seeing this?
finite gate
sub_1NmzaDSBBtImW7ZL9LqcuRC8
half badge
Thank you for that, it looks like proration_behavior wasn't included in the request you made to adjust the quantity, so the default behavior was used and prorations were created:
https://dashboard.stripe.com/test/logs/req_s2U0PcVqPZRn2M
You will need to include proration_behavior in each of your update requests, and set it to none, where you don't want to create prorations. That is not a "sticky" setting that applies to all future changes made for the Subscription, it must be included with each update request to use non-default behavior.
finite gate
Okay
Actually, I set it to none but to check the issue I have set it to defult
Let me update it again and I will message you in while
If that will work for you
half badge
The request I provided a link to did not include the proration_behavior parameter at all. If you have adjusted your code to include that parameter you will want to debug why it isn't being included in the request.
short currentBOT
half badge
Glad to hear, always happy to help!