#dayvvo_api

1 messages ¡ Page 1 of 1 (latest)

nimble kilnBOT
#

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

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

forest linden
#

hey there! the first step for most Stripe Connect flows is to create a connected account for your user, and then the second step is to collect info from the user to onboard the account

this doc breaks down the key pieces of a Connect integration: https://docs.stripe.com/connect/design-an-integration

#

feel free to clarify what feels possibly incorrect about the approach that you're following, and let me know what your points of confusion are

elfin sigil
#

thank you. my point of confusion is when using an embdded widget the current flow(not implemented by me but being reviewed by me) creates an account first, before creating a session id using that account id to pass to the embedded widget on the front end. so before the user has any info filled a "connected account is created first" is this the right flow?

and in the event that the user does not go through with filling the info and aborts the page. does it mean said user has a stripe account created on their behalf before they even went through with the setup process

forest linden
#

yep, creating the account first and then onboarding it with a session/account link is the right approach!

it sounds like you're confused about the user having an 'account' before they actually complete signup, which is understandable

the thing to keep in mind is, unless you pre-fill information via the API, the user's details aren't collected until the account has been successfully onboarded (i.e. the onboarding session is completed)

so, if the user doesn't fill out their info and aborts the page, there will be a Stripe account created on your platform for them, but it will be a blank account that never finished signing up/onboarding

elfin sigil
#

okay! perfect. one more thing please. It seems like right now I am unable to distinguish between a user who has not filled any info on their platform at all and one who has some info filled and is pending verification or failed to submit some valid info. is there a way to distinguish between these for an account that is not yet onboarded

forest linden
#

no problem! yes it should be quite clear to differentiate, in both the API and the dashboard

do you have any specific examples to check?

nimble kilnBOT
elfin sigil
#

This looks like a detailed doc. can I read it and come back to this thread to resume it later?