Billing Portal Configuration - Feature Request

[Claudio Friederich]

The Billing Portal Configuration object should be made a "first class citizen" in the Stripe dashboard like the other objects.  There should be a page that lists billing portal configurations, and that allow creating configurations, the way you can products or prices or anything else in the dashboard, not just editing the one default configuration.  

While there is complete API support for creating billing portal configurations, often creating these configurations is a one-time setup job, and editing them often needs to be done by non-developer personnel (much like adding or editing products).  For example, suppose you sell different types of subscriptions (with different levels/products/prices).  You would not want to allow customers to switch a movie subscription type to a magazine subscription type via the portal, for example.  So, you would create different portal configurations, one allowing choosing between the movie subscriptions and the other between the magazine subscription plans.  But you would want to set this up in the dashboard, and just put the IDs of the configurations in your code, not write logic to enumerate all the configurations, check whether the configuration already exists, create it if it doesn't, write update logic every time the marketing manager wants the wording of the byline of the billing portal to change, etc.

Managing your billing portal configurations in code is hard also because, unlike other objects, the portal configuration is one of the few objects without a metadata dictionary, with which one could code a program to find and recognize the right portal configuration.

The API for managing and using the portal configurations is great - we just need the ability to do this in the dashboard as well

[Remi J.]

Hello Claudio,

Thanks a lot for the thoughtful feedback about potential improvements on the product!

Managing portal configurations is definitely a more advanced flow today that we decided to support only in the API at first. In many cases, that API is used for Connect platforms to control configurations per connected accounts, or to do one-off overrides for specific customers for example.

I do see the use-case you have in mind right now, where you would have multiple "high level configurations" that you would want to manage the same way that you do for the default one by using the Dashboard. If we did this though, how would you identify or find which configuration to update? Today they don't have a "name" or "description" that you could use. Do you think we would need to add something like this to fit your use-case?

I'm going to flag this internally as a feature request too. I know we won't be able to get to this one soon but it'll help us plan it in the future.

Best,

Remi

--
To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.

[Remi J.]

Hello Claudio,

Quick follow-up to indicate that our engineering team just shipped support for metadata on the Portal Configuration [1] based on your feature request! This should help you build your own UI to identify each configuration and their purpose.

Hope this improves your integration experience a little bit!

Best,

Remi

[1] https://stripe.com/docs/api/customer_portal/configurations/create#create_portal_configuration-metadata