denjaland_api

[worthy elbow]

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

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

[lavish valley]

this is all I get, when clicking the button, it opens a new screen and starts the "classic" onboarding there... I was under the impression we needed to be able to fully embed it in our page...

[queen wave]

Hello! You're probably running into a scenario that embedded onboarding doesn't support, so it's kicking out to the full page

[lavish valley]

that's what I thought - where can I find info on these scenario's?

fyi - I just followed the guide on https://docs.stripe.com/connect/onboarding/quickstart 🙂

[queen wave]

I was looking and we used to have a page explaining this, but it got moved... hang on...

Ah, here it is: https://docs.stripe.com/connect/get-started-connect-embedded-components?client=js#user-authentication-in-connect-embedded-components

I think that's what you're running into.

[lavish valley]

let me have a look at that page

hmm - reading that, it doesn't seem that I can ever do an onboarding "embeddedly"?

[queen wave]

You can if the user is already authenticated.

[lavish valley]

but you're right - once I authenticate, it takes me back to the embedded component

I was kinda hoping it would all stay within our page to be honest 🙂

[queen wave]

Yep, I understand, but some parts sometimes need to happen elsewhere.