#dfenersky_api
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1228252690090426430
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hi there!
, if a user with multiple subs opens the portal, he cannot change it, only cancel.
you want users to be able to change what exactly on their Subscriptions?
Additionally, user with single subscription cannot add another one from the portal
that's expected. the portal is only to manage existing Subscriptions, not to create new ones.
hi soma,
bpcs allow me to say what other plans the user can switch to, given his current plan.
I want to be able to control these same updates, in the case when a user has multiple concurrent subscriptions (i.e subscription with multiple items)
so you want to allow users to upgrade/downgrade their existing Subscription? yes that should be possible
so while creation is indeed not planned to happen there, i would consider removing or adding "addons" to be a sort of an update
but these addons are just subscriptions themselves.
this is how the portal looks like with multiple concurrent active subscriptions. usually, a user may change one i.e upgrade or downgrade. but with multiple:
- upgrade/downgrade is not possible for the "main" subscriptions
- addition/removal of the addon ("secondary" subscription) is not possible
you can learn more about the features of the customer poral here https://docs.stripe.com/customer-management/configure-portal#configure-subscription-management. in particular:
Let your customer switch between subscription plans. This option is best when you have a good-better-best pricing model.
is this what you want?
- it should be possible. what's the issue?
- that is not supported indeeed. you would need to build your own customer portal for this
- i have a configured
bpcwhich should allow upgrades/downgrades. when i navigate user to billing porta, with thisbpcid, while the user has multiple concurrent subscription items, the portal looks like in the screenshots. see how no other plan switches are listed, but there should be
- thanks, I was wondering whether this is possible or not.
- thanks for the clarification, give me a few minutes to look into this
- for comparison, here is screenshot how the same
bcplooks like, when user has a single subscription
can you share the Customer ID (cus_xxx) that has multiple Subscription but doesn't have the "update plan" button?
sure, 1 second
Customer ID: cus_PuCyhgVk1HqLZA
BPC ID: bpc_1OX2FpChm4LZb0pQdC9mphLJ
both are test mode objects
this customer has a single active subscription. I was looking for the customer with multiple Subscriptions
sorry, i may have miscommunicated this
the single subscription was created by using 2 line items for 2 distinct products, with recurring payments
oh, so it's a single subscriptions with multiple items. got it.
in this case not sure if it's supported, looking into this
yes it's explained here: https://docs.stripe.com/customer-management#customer-portal-limitations
If subscriptions use any of the following, customers can only cancel them in the portal (they can’t update such subscriptions):
- Multiple products
thanks for the info, I must have missed this one, sorry!
so you should either use multiple Subscriptions for this to work, or not use the Portal and build something yourself.
exploring the "multiple subscriptions" option briefly:
- this means multiple invoices, 1 per subscription, right?
- subscriptions can potentially have different start/end dates
- user can combine them freely and we can't easily say "addon X only goes with subscription Y", right?
- correct
- correct
- not sure what you mean exactly. can you share a concrete example
point 3) is probably most crucial. we want to be able to define the business logic, which "addon" goes with which "sub"
so user has "Gold" subscription. he then buys "Medium addon". he should not be able to have "Gold" subscription with "Small addon". "Small addon" is only allowed with "Silver" subscription
for product A you could have 2 prices: "silver" and "silver + addon".
for product B you could have 2 prices: "gold" and "gold + addon".
so users would be able to add/remove the addon on their product