#FACELESSMAN
violet aspen
noble raft
If you allow the Customer to update the Subscription, you can specify the proration_behavior in the portal configuration:
https://stripe.com/docs/api/customer_portal/configuration#portal_configuration_object-features-subscription_update-proration_behavior
sleek crane
Like what happens if I have deployed Customer Portal and the customer downgrades mid-cycle
Does create_prorations means that the customer will be billed less at the end of the cycle only after the billing cycle has ended?
noble raft
It means that the customer will be billed a reduced amount based on the downgrade
So if you have a configuration with create_prorations, you allow the customer to change prices, and they downgrade to a cheaper price the amount billed will reflect the difference between the higher price and the lower for the fraction of the billing cycle during which they were using the lower price.
sleek crane
is it possible to make it so that the customer can downgrade, but the billing cycle starts the next month
let me make an example
Jan 1st: I purchase 6 seats at $10 each = Total $60
Jan 15th: Downgrade to 3 seats.
What am I billed on Feb 1st?
The outcome I am looking for is:
You are billed for $60
then in February the user has 3 seats and they're invoice $30 on March 1st
jagged imp
Hi there, stepping in for snufkin - let me catch up here.
you can change the features.subscription_update.proration_behavior = 'none' for this use case, https://stripe.com/docs/api/customer_portal/configuration#portal_configuration_object-features-subscription_update-proration_behavior. I'd highly recommend that you test this out in your test environment.
sleek crane
Ok thank you!