#MadMac
quartz moat
vital heart
Can you share the request ID (req_xxx) of the error? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
worthy path
This is the req for the 2nd one. The workaround.
This is the req for the first error I mention: https://dashboard.stripe.com/acct_1L6OJoJNo64cYhJW/test/logs/req_veKVM7Qir3SjSI
Note I am in testmode
vital heart
For default portal configuration, it can only be updated in the dashboard: https://dashboard.stripe.com/test/settings/billing/portal
worthy path
Ok so is there a workaround? Could I make more than one configuration and use a the non default one?
I want to update from the API as otherwise my connected accounts have to manually do this
And they won't
vital heart
Yes, you can create a new portal configuration from API: https://stripe.com/docs/api/customer_portal/configurations/create
Then use the newly created portal configuration: https://stripe.com/docs/customer-management/integrate-customer-portal#customize
worthy path
I have already created one. So creating multiple portal configurations from the API for a connected account is all good?
The 2nd one will not be the default?
I did notice the "application" field on the configuration was null too. Not sure if this will cause a problem.
vital heart
The newly created one from API will not be default. Those configurations created from API can be used in the portal session as described here: https://stripe.com/docs/customer-management/integrate-customer-portal#customize
worthy path
Awesome I will give that a try now. Thanks for the super fast help!
vital heart
https://dashboard.stripe.com/test/logs/req_FlregNoifjvamp
The reason why No such customer: 'cus_McvffY9U4bNvj0' was thrown in req_FlregNoifjvamp is because cus_McvffY9U4bNvj0 is created on the connected account whereas the portal session is on platform. If you wish to use the customer on the connected account, both portal configuration and session should include Stripe-Account header: https://stripe.com/docs/api/connected_accounts
worthy path
I figured that. The last link you sent had a better explanation of on_behalf_of so I think I understand it now
vital heart
Awesome! Glad that it's been figured out!
worthy path
Genius. It works.
Its a bit weird having to create a default portal config first to be a placeholder but I have no problem doing that.
Thanks so much for your help I have been stuck on this for ages!
vital heart
No problem! Happy to help 😄