#luanvdw-upgrade-subscription

1 messages · Page 1 of 1 (latest)

tight torrent
#

Hi 👋 I'm not certain off the top of my head if that can be avoided as that is one of the scenarios that we explicitly say will create an immediate payment.
https://stripe.com/docs/billing/subscriptions/upgrade-downgrade#immediate-payment

I'm not sure if it will do what you want, but you can try passing proration_behavior=none when upgrading the subscription.
https://stripe.com/docs/api/subscriptions/update#update_subscription-proration_behavior

If it doesn't, you can look into Subscription Schedules which would allow you to schedule the change to happne in the future (like at the start of the next period).
https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases

Subscription schedules use cases

Learn how to use subscription schedules.

Stripe API reference – Update a subscription – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

Upgrade and downgrade subscriptions

Learn how to upgrade and downgrade subscriptions by changing the price.

frosty hound
#

Thank you for your response,

I just tried the following

When updating the subscription with, billing_cycle_anchor: unchanged it respects the billing anchor which is great and it also creates prorations accordingly which is also great

But now it is merging the following months invoice into this months invoice?

Here is a screenshot

#

The original billing_anchor was 30 April and we can see that when updating the subscription it is doing proration from 7 Appril to 30 April, that is correct

But then it adds 30 April - 31 May into this invoice as well? 🤔 when that should appear on 31 May's invoice (i.e. the next invoice)