geo_best-practices

[small orbit]

👋 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/1395765070599815198

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• geo_best-practices, 21 hours ago, 28 messages

[glacial silo]

I believe you're referring to the no-code portal access that customer can acces at some URL

eg: https://docs.stripe.com/customer-management/activate-no-code-customer-portal

This is a different way of providing access vs creating portal sessions yourself

When you're creating portal sessions with the API, they are short lived for a single customer, and you can send the configuration you want

With the no code URL its set for a static configuration that is not customizable per customer

For help setting up the no-code access URL, please work with our support team: https://support.stripe.com/contact

If you need mroe help with the portal sessions creation via API, please let me know what you need help with and I can take a look

[vocal bobcat]

So essentially I have a small management portal for subscripbers, when they log in they see some info which includes a portal link to manage their subscription in stripe. I do this by calling stripe.billingPortal.sessions.create. However when they don't have the setting in the screenshot on, they get the following error
'No configuration provided and your live mode default configuration has not been created. Provide a configuration or create your default by saving your customer portal settings in live mode at https://dashboard.stripe.com/settings/billing/portal.',
I was recommended to use the Configuration api before calling stripe.billingPortal.sessions.create but from the docs I don't see anythign that correlates to the setting in the screenshot

[glacial silo]

Oh, interesting. Not sure why you wouldnt have a default.

So you can either create a configuration that you just staticly pass to portal sessions creations, or your can go to your dashboard to create a default configuration to use when you don't pass one explicitly

When you load that dashboard URL, what do you find?

Provide a configuration or create your default by saving your customer portal settings in live mode at https://dashboard.stripe.com/settings/billing/portal.',
this one

[vocal bobcat]

ahh so just the act of passing a configuration object to stripe.billingPortal.sessions.create is the same as manually turning that setting on?

The actual link is fine, I see payment methods, billing info and invoice history

I'm just more concerned with having to turn that setting on manually for every customer which will not scale at all

[glacial silo]

when you say "customers" do you mean your own direct customers, or other accounts your software will operate on?

If you're talking about your own stripe customers, then this will not vary per customer, a default configuration is a single account level setting

If you're managing portal session creation for other stripe accounts, then yes having a default configuration would be needed for each or you will need to pass one in the sessions create requests

[vocal bobcat]

Got it, the second scenario is what I'm after. So I'll call the create configuration and pass it to session create everytime I generate the link which I think it's better than having to manually flip that setting on in the dashboard

and just to confirm, just need to pass the configuration id correct?

Is there an issue with calling the configuration create everytime?

[glacial silo]

Assuming the settings are the same, you can store & reuse the configuration. ie, you only need to create it once and can use with as many portal sessions as needed

[vocal bobcat]

would that not creat many?

I see

sorry one more question, if we have customers with each having their own connect account, can I still share the same config?