#surgical_api
finite houndBOT
đ 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/1369666314821439516
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
idle quiver
this is the UI. i do se a warning about payment but not sure if that's relevant
fiery gyro
You need click one of the institutions (the first one for successful tests, typically) to set up the bank account connection
If that's not working, the conditions of running this are likely not met, such as blocking popups or framing etc
How have you included this in your app?
idle quiver
yes, I've clicked on the banking info, but nothing happens https://www.loom.com/share/8e75ee1823784f6da9e1ff9b766eff44
i think the embed code was standard (this was previously working before)
return organization.allow_stripe_connect && (
<Box my={4}>
<ConnectComponentsProvider connectInstance={stripeConnectInstance}>
<ConnectAccountOnboarding
clientSecret={clientSecret}
onExit={() => {
console.log("The account has exited onboarding");
}}
/>
</ConnectComponentsProvider>
</Box>
)
fiery gyro
Hmm
Do you have a CSP defined? If so, did you add the directives indicated here: https://docs.stripe.com/connect/get-started-connect-embedded-components?platform=web#csp-and-http-header-requirements
idle quiver
sorry for delay, working through it to see if i get same issue on localhost
fiery gyro
I am also trying a basic onboarding flow here
idle quiver
i don't think i have a CSP defined and I have the same issue on localhost
its strange that the "select industry" has no values either, I know a couple weeks ago this worked
fiery gyro
But the rest of the onboarding works up until the financial connections piece?
idle quiver
yes correct
I've created the account this way: const connectedAccount = await stripe.accounts.create({ controller: { stripe_dashboard: { type: 'express', }, fees: { payer: 'application', }, losses: { payments: 'application', }, }, });
fiery gyro
Does your implementation use any kind of iframe or similar around where the components are used?
or possibly a webview?
idle quiver
No I just have a reat app. The only iframe is stripe's onboarding screen. I do see this warning when I try to select an industry
Blocked a frame with origin "https://connect-js.stripe.com" from accessing a frame with origin "https://dashboard-test.onthestage.tickets". Protocols, domains, and ports must match.
fiery gyro
That does sound like a CSP issue, you may need to add the directives here:
https://docs.stripe.com/security/guide?csp=csp-connect#content-security-policy
WHen i get to the bank account stage the financial connections modal appears as expected, so i can't trivially reproduce what you describe
idle quiver
and you can select one of those financial connections?
idle quiver
okay. thank you for checking - it must be on my end. I would have expected if it was a CSP issue, then at least localhost would work? would you expect the same? In any case I'll keep debugging since it gives me comfort knowing that you can get to this screen
finite houndBOT