#mateuszinsys_93238
toxic basin
Hi, are you setting the billing cycle anchor to now when you make the update, https://stripe.com/docs/api/subscriptions/update#update_subscription-billing_cycle_anchor? You can learn more about billing cycle anchors here, https://stripe.com/docs/billing/subscriptions/billing-cycle#changing. I think it's just how our prorations works, however, without a specific example it's hard to say what you're seeing.
hybrid fossil
I am not setting billing cycle anchor
I am using 3 parameters:
items[0][id], items[0][price] and proration_behavior
toxic basin
Can you share the request that updated the subscription? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
hybrid fossil
Yes, I am seraching
rain hamletBOT
hybrid fossil
Here you have request ID: req_Acrw0YEpUdAfzz
heady otter
👋 stepping in as pgskc needs to step away
hybrid fossil
Yes
heady otter
You are using proration_behavior: "always_invoice", which will always immediately create an Invoice and reset the billing anchor
hybrid fossil
🤔
heady otter
You want the upgrade/downgrade to occur at the end of the current cycle?
hybrid fossil
but if I started 1 of January (monthly sub) and now is 15 and today i will update with alywas_invoice then I will get invoice and then 15 more days with new price (upgrade) is this correct?
heady otter
No
hybrid fossil
Because invoice will be not for 100% price, but there will be some calculations to calculate the price
heady otter
The way it works is you either force an Invoice immediately, which resets the billing cycle. Or you have proration items created upon that update (if you set proration_behavior: create_prorations which is also the default) but those proration items are add to the next billing cycle (Feb 1st in your example).
hybrid fossil
so using create_prorations nothing will reset, and after current piriod ends user will get an downgrade?
heady otter
The Price for the Subscription changes immediately, but the associated proration items won't be included in an Invoice until the next natural Invoice (unless you create on manually)
I'd recommend testing it out
And using a test clock
https://stripe.com/docs/billing/testing/test-clocks if you aren't familiar
This is the best way to understand how it works
hybrid fossil
Yes I am familiar with test clock
so just for summary: for upgrade: always_invoice, and for downgrade: create_proration?
heady otter
All depends on what you want
They both will perform the update, just they will handle the billing cycle anchor differently
hybrid fossil
ok thanks