#stephen.h-customerportal
1 messages · Page 1 of 1 (latest)
ok
While you can apply custom "nickname" sort of values via metadata, this is not shown to the customer in the portal. Everything is driving by the product name.
If they have multiple subscriptions, make sure you're products have distinct meaningful names that can be used
The problem is that the subscriptions are all for the same product, just for different instances of it.
For example, picture a subscription for a car sales site, like Auto Trader
The customer can do a listing now to sell their Pinto
Then later to sell a Mustang
Ok that's going to cause an issue for the second question then too, which I was going to say you can configure to limit to specific products in the configuration: https://stripe.com/docs/api/customer_portal/configurations/create#create_portal_configuration-features-subscription_update-products
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Both are using the same plan "Monthly Car Sales Plan"
Why not increase the quantity to 2 instead?
When they go to the portal, I'd like to see an option for the Mustang, and another for Pinto
They won't have the same start and end dates.
Hmm this isn't directly supported the way you're expecting to be able to, then
You'd need to consider using ad-hoc product data to show customize subscription names, all the UI there and on the invoices is from the product name
Or otherwise implement a custom flow rather than using the portal if it doesnt fit your use case currently
Thanks for sharing that use case, I've submitted some feedback internally explaining why this didn't fit well for you 🙂
Thank you. It would work really well if I could just override the plan name when I created the checkout session, and have that "stick" for that specific subscription.