#karl_connect-account-onboarding
compact sableBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1246162241733001298
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
ebon plover
HI 👋
No, it is not possible to skip or remove this form. You can pre-fill this information when you create the account but the person going through the onboarding will still be shown the form so they. have the option to review and change it if appropriate.
unique dragon
Ok thank you! Would using an embedded onboarding setup allow for this information to be entered upon account creation and prevent users from having to complete this form?
ebon plover
Are you referring to the entire onboarding process or just the page with business location and type?
unique dragon
The entire onboarding process. Im following the connect onboarding quick start guide https://docs.stripe.com/connect/onboarding/quickstart?connect-onboarding-surface=embedded&connect-dashboard-type=express&connect-economic-model=buy-rate&connect-loss-liability-owner=platform&connect-charge-type=destination#init-stripe, and am deciding whether to use "hosted", "embedded", or "API" for my application. For context, my site is marketplace where individuals can buy and sell online assets (which most users will only do once or twice). Ultimately I would want this process to be as simple as possible for users and to have users complete this process with the intent of receiving payments for their sales. Additionally, I was hoping to avoid API if possible as Im not to most experienced programmer. Thanks.
ebon plover
So if you want to skip the entire form process you will need to use the "API" approach we document. It does require you to build the information collection yourself but it gives you more flexibility in terms of what your users see
unique dragon
Alright thanks for the help
ebon plover
sorry I just say the last sentence there. Using the API approach would be a significant engineering effort. If your only issue is that we are presenting some of the same info you've already collected then I would try out the embedded onboarding just to get a sense for how disruptive it really is.
Are you just trying to reduce the number of pages your users have to complete? Or is there another goal here?
compact sableBOT