#bp_api
wicked basinBOT
👋 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/1420581878125166713
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
unique cloud
hello there 👋 give me awhile to catch up
Thanks for waiting. If you don't want proration to happen when the subscription "upgrades" or change in price, you can set proration_behaviour: none during the price change : https://docs.stripe.com/api/subscriptions/update#update_subscription-proration_behavior
However, do note that setting proration_behaviour: none on a specific API call does not completely disable proration on a subscription's future changes. It only impacts that specific update you're making when passing proration_behaviour: none ; in your scenario, it would be the price update.
I'd recommend testing this in your Stripe account's Test Mode / Sandbox to confirm it fits your use case before you make changes to your live subscriptions
dark edge
When you set proration to none, it doesnt upgrade the subscription until the end of the billing cycle though? We need to upgrade them straight away.
We want to:
- Upgrade and bill immediately
- Not refund any amount of the subscription (no proration)
- We will then update their balance in our system. This works for everyone as their balance is fair to what they have or havent used in our system
unique cloud
I see, got it. Yes, disabling proration will only invoice the full payment in the next cycle [0]. But to confirm, you'd want the customer to be billed immediately on the full (new) price.
Do you need to billing cycle anchor to stay the same? Because you can achieve this behaviour (disable proration + bill now) if you set billing_cycle_anchor: now. This means you're resetting the subscription's billing cycle date — example: if you upgrade a monthly subscription today (25 Sep) and bill it now, the next payment will be 25 Oct, regardless of when the customer initially started their subscription.
[0] https://docs.stripe.com/billing/subscriptions/prorations#disable-prorations
dark edge
That sounds like what I need. Setting the billing anchor to the day they upgrade does make the most sense. So I just need to set proration_behaviour: none & billing_cycle_anchor: now and they will be billed, upgraded, start a new cycle from the day of upgrade and not given a refund
unique cloud
yep