Ritchie

[hollow dew]

Hi there!

Now, is there an easier or recommend way to manage achieve the above? Or is what I described a good solution?
What you described seems correct to me! One subscription per user, and adding/removing price on the subscription when needed.

Also, how would I charge the customer as soon as a new item is added?
With this https://stripe.com/docs/api/subscriptions/update#update_subscription-proration_behavior set to always_invoice

[dense ginkgo]

Perfect, thank you. What about a customer keeping their items until the next billing period when you remove an item? I think from my experimentation yesterday, the item was removed in the customer.subscription.updated event?

Is that something I have to keep track of?

[hollow dew]

When you remove an item it is removed immediately. If you don't want to create prorations, set proration_behavior: none, and keep track on your end if the user should have access to the feature or not.
Another option is to remove the item in the future, by using a subscription schedule: https://stripe.com/docs/billing/subscriptions/subscription-schedules

[dense ginkgo]

Thank you. Last thing, which webhook event is typically used to detect when a subscription has successfully renewed?

[hollow dew]

invoice.paid https://stripe.com/docs/billing/subscriptions/webhooks#active-subscriptions

[dense ginkgo]

Amazing. Thank you so much for your help!

[hollow dew]

Happy to help 🙂