#aditya-shukla_api
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1422474132926234674
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
https://dashboard.stripe.com/acct_1Ihw53CScnf89tZo/test/subscriptions/sub_1SCbC0CScnf89tZouwwRPctc
accountId : acct_1Ihw53CScnf89tZo
https://dashboard.stripe.com/acct_1Ihw53CScnf89tZo/test/events/evt_1SCbDGCScnf89tZoedZaL34O
https://dashboard.stripe.com/acct_1Ihw53CScnf89tZo/test/events/evt_1SCbItCScnf89tZoO5xmjsoh
Hi there, The proration_behavior is per-request basis, so you always need to include it in the update request if you want to set a particular proration_behavior
This behavior is explained in https://docs.stripe.com/billing/subscriptions/prorations#disable-prorations
Thanks @fervent trench
No problem!
Hey @fervent trench, I’m a bit confused. In the attached screenshot, when I set proration_behavior: none in the phase item (instead of at the root level), updating an active scheduled subscription initially applied proration, but it was removed after some time. This was happening only for a few subscriptions, not all. Could you clarify why this happened?
Note: Once we set proration_behavior: none at the root level, this issue no longer occurs.