nukesforbreakfast_best-practices

[worthy 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/1407809648374976693

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

[dark scroll]

I should also mention we're planning on using the connect embedded components in our app to let connected accounts manage their stripe accounts.

[silk parrot]

We don't know anything about metrics and reporting in here, so I recommend asking support that question. It's possible one of the connect report types will give you what you need but not sure: https://docs.stripe.com/reports/report-types/connect . As for creating customer portal sessions on the connect account, you can do it the same way you'd create a direct charge. By passing the stripe account header: https://docs.stripe.com/connect/authentication

[dark scroll]

As for creating customer portal sessions on the connect account, you can do it the same way you'd create a direct charge. By passing the stripe account header: https://docs.stripe.com/connect/authentication
but the customer portal docs explicitly state not to do this: https://docs.stripe.com/customer-management/integrate-customer-portal#configure

[silk parrot]

I don't really understand that warning. It's not saying you can't do direct charges

That's about portal configuration

Let me double check with a colleague what that means exactly

[dark scroll]

so there's this field in the session: https://docs.stripe.com/api/customer_portal/sessions/create#create_portal_session-on_behalf_of

[silk parrot]

I don't see an issue using stripe account header with portal

[dark scroll]

and it almost reads like it's the same as using the stripe account header

but I'm not sure whether it means to only be used with destination charges/invoices/subscriptions created with on_behalf_of

[silk parrot]

yeah that's what that field is for

[dark scroll]

The docs also state

If you want to create multiple portal configurations for different sets of customers (or if you’re a Connect platform and want to manage configurations for your connected accounts), you can do so using the API:

so it sounds like I should be creating portal configurations on my platform account when combined with the warning about the configurations.

but if that's the case, how would that work if I used the stripe account header?

[silk parrot]

I'm double checking with a colleague what that warning is all about

[tiny jolt]

We are still unclear on what exactly the doc is trying to say there, but you definitely can/should use Stripe-Account to manage portal configurations for direct charge flows. We'll flag internally that that doc section needs to be fixed to clearly communicate whatever it is going for now

[dark scroll]

ok, so I should use a stripe account header to create portal configs on my connected accounts, and then use a stripe account header when creating the portal sessions?

[tiny jolt]

Correct, because the payment objects are on the connected accounts, you will want to use that header when dealing with things that can effect those payments

[dark scroll]

ok, and just to be clear this is a customer portal session, not a stripe checkout session. So it's dealing with invoices and subscriptions.

[tiny jolt]

Correct, you're using the Stripe-Account header when making the portals and subscriptions, so you will also want to use it for the portal sessions that work with those subscriptions and invoices.