Miroslav

[obsidian crystal]

I've read somewhere that only the single default portal configuration can be managed through the Stripe portal
Not sure what you mean by this?

Should I try to reuse portal configurations?
Seems logical, yep! Persist them in a database or something

How do I do that? I don't see an API for deleting.
I guess they can't be deleted. You can disable them though to prevent them being used: https://stripe.com/docs/api/customer_portal/configurations/update

[lunar pelican]

What I meant is that you can manage a single portal configuration through the Stripe Dashboard UI. I guess that's the one that's marked as "default".

All additional portal configurations can only be seen and managed through the API, right?

[obsidian crystal]

Correct, yes

[obsidian crystal]

Also correct

[lunar pelican]

Ok, thanks. Do you have an advice whether I should dynamically create these portal configurations when customers try to access the portal for the first time, or I should maybe create them separately and only store the relevant IDs in my app settings or DB?

[obsidian crystal]

Up to you. I guess if you have a set of pre-configured configurations for common actions then it doesn't hurt to store them in your database (which is totally safe), likely to be more efficient in your app

[lunar pelican]

yeah, creating them on the fly also complicates things as I see, as tomorrow we may decide to change the list of products, which I currently need to pass as a parameter to the portal configuration for subscription_update

thanks

[obsidian crystal]

np!