#captions_75309_62523
snow roost
steady thunder
Hello, good questions, though I am still trying to fully understand your usecase here. Is there basically one person with permission to change what plan all of the team subscriptions on? And can you explain in a bit more depth what the difference between the team products vs the non team products?
how would billing periods be affected?
Basically, if you are changing the period length (ex: monthly -> yearly), Stripe will reset the billing cycle anchor, so that will be the basis for when months/years on the subscription starts from then on. If you are updating between products but the cycle length is staying the same (ex: Premium monthly -> enterprise monthly), you have the option of keeping the cycle anchor as is or resetting it to the time of the update.
fading oasis
Yes, it would be one user (team owner) who has purchased all the subscriptions for users on the team. Essentially, we want one person to be billed. We use our own backend to track the team data. To determine if a team member has access, we query Stripe to verify the owner has purchased enough seats for their team
There should be no difference between team vs non-team products, the access level should be exactly the same. It was another approach I tried to better display to the user the subscriptions that they have purchased for the team
steady thunder
Gotcha, in that case I think it would be the most straightforward to represent this as one subscription and give the team owner access to the customer portal (or at least access to the portal with a configuration that allows for subscription updates). That would make it easiest to update everyone to the same plan at once.
Up to you what you want to do for one product vs two. Two could definitely make the invoices and customer portal clearer if you think that simply having a quantity won't be clear enough.
Oh though good callout on the customer portal not allowing updates on multi product subscriptions. So ideally you would want one of the items on the subscription to not be designated as a team seat?
fading oasis
Ty for the help. Yes, I would like it to be on one subscription and have the owner use the customer portal to modify their subscription.
So is it not possible to use the customer portal tool to update a subscription if the subscription has multiple products/line_items associated with it?
The issue with the one product is that it doesn't feel obvious to the user why they are paying for Premium x5. Yes, ideally it would be nice if it could be separated out into team seat subscriptions but it sounds like it may not be an option.
How do clients typically implement a family sharing plan / per-user pricing plans?
steady thunder
Gotcha, apologies I initially missed your response here. I am double checking now but as far as I know, the checkout portal does not support updating multi product subscriptions.
I have not run in to this scenario enough to know what is typical, but the ideas that you laid out are sensible. One other option would be to use two products and make your own page to update the subscriptions. Our API does allow updating two items on a subscription at once, though of course making your own custom page takes a lot more development time and resources than using the Customer Portal.
fading oasis
how might I use the API to update the quantity for a subscription with two products
steady thunder
When updating a subscription, you pass in a list of items, so you can pass in a list of two items instead of one. Basically you get the ID(s) of the existing subscription item(s) and them you pass in an item with that ID along with the attributes that you want to change
https://docs.stripe.com/billing/subscriptions/upgrade-downgrade#changing
So if you want to upgrade the quantity of two items your items array would look something like this:
[
{
id: 'si_1234',
quantity: 6
},
{
id: 'si_5678'
quantity: 6
},
]
that makes sense, ty!
steady thunder
Of course, also I have confirmed that the customer portal does not support multi-product subscriptions. I'll put in feedback to request support for that in future, but for now that is where its capabilities are.