#nobody_api
solemn nimbusBOT
👋 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/1296328472964104283
📝 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.
- nobody_api, 5 days ago, 4 messages
- nobody_api, 6 days ago, 4 messages
devout totem
To summarize, i want my application to be liable. But disabling the stripe_dashboard causes an error.
edgy mulch
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
devout totem
req_a8MYme34Ie42WG
edgy mulch
For you wish to application to be liable, controller.requirement_collection should be set to application for no dashboard as well: https://docs.stripe.com/api/accounts/create#create_account-controller-requirement_collection
If it's not set, stripe is set to default that led to this error
devout totem
But why would that be the case, i still want to use the stripe embedded components for onboarding
edgy mulch
requirement_collection is the party who will ask the connected account to complete onboarding, not where the onboarding is completed.
If requirement_collection is set to stripe, Stripe will send reminder to ask the connected account holder to complete onboarding if there is any outstanding and updated requirements.
If requirement_collection is set to application, the platform will prompt the connected account holder to complete the onboarding either through hosted onboarding or embedded connect component
devout totem
Hm i see
Are embedded components allowed with the express dashboard?
Or is it a one-or-the-other situation
edgy mulch
Which specific embedded component are you referring to? Embedded component has nothing to do with the Express Dashboard. Express Dashboard is for the connected account to view their payment information
devout totem
Embedded components under the account session object
My understanding is it's an alternative to the express dashboard
edgy mulch
Embedded components can be used regardless the dashboard type. If you use Express dashboard as an example, you can choose to display the information via Express Dashboard or embedded components.
devout totem
Okay so if i set requirement_collection to application and use embedded onboarding and embedded account management, I'm covered?
I don't have the bandwith to implement requirement collection outside of the embedded components inherently knowing what users need to do. So this is important
I was hesitant to switch requirement_collection to the application
edgy mulch
Yup! This looks good to me. If the connected account has any outstanding or new requirements to be completed, I'd recommend checking the guide on how to do it via embedded components: https://docs.stripe.com/connect/embedded-onboarding#handle-new-requirements-becoming-due
devout totem
Ok thanks. Sometimes it's hard to know how much burden you're taking on from these settings