#ynspc

1 messages · Page 1 of 1 (latest)

floral boughBOT
rough anchor
#

Hi 👋 thank you for flagging this, I agree that looks incorrect.

gentle prism
#

So with proration:
using option as
proration_behavior: always_invoice
in the mentioned link, do we charge $150

rough anchor
#

Using that example, if you use always_invoice, then on May 15th when the update is made, a new Invoice for the prorated amount of $50 will be charged. $100 for the remaining half of the month at the higher $200 price, minus $50 from the previous payment that was only half used.

You can use Test Clocks to create test Subscriptions in sandboxes where you can advance time, so you can see exactly how the various proration behavior will play out:
https://stripe.com/docs/billing/testing/test-clocks

gentle prism
#

thanks so muck

rough anchor
#

Any time!

floral boughBOT
gentle prism
#

I have a normal scenario where JANE;
subscribes to planA -> sub_xxxxxxplanA
now if JANE wants to upgrade her plan to planB or downgrade to planC then, we need to create new subscription or update the same sub_xxxxxxxplanA?

rough anchor
#

You can update the existing Subscription object, and provide it with the ID of the new Price that you want to charge Jane.