#whoami_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1313660498809585726
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! You didn't really ask a question. What specific help do you need?
Hi! I understand the API integration for connect accounts. What will be the operational differences if I choose embedded integration
Those are covered in the documentation you linked to. Can you ask a more specific question?
I see that in the backend I still need to call create account api, what value do I need to set for type? full? express? custom?
If I provide some of the information in the api, does the stripe onboarding still pops up those fields for users to enter?
The type of the connected account is up to you and depends on your use case. We actually recommend controller properties instead of account types now. See here for details: https://docs.stripe.com/connect/migrate-to-controller-properties
And yes, if you provide info when creating the Account it will be prefilled during onboarding.
For embedded onboarding, do I (as a platform) still have controls over the connected account's bank accounts and payouts?
It depends on the Connected account and the type or controller properties it has.
which type and properties allow me to have the control?
There are details about that here: https://docs.stripe.com/connect/payouts-bank-accounts
It's basically accounts where you're liable for negative balances, which includes Express and Custom accounts.
thanks
If I create connect accounts with type: custom, and client side uses this accountId to generate account session, does the user get redirected to the Stripe onboarding page?
If you're using embedded components we try to keep as much as possible in the embed, but some parts do need to happen outside of it. We don't fully redirect to another onboarding experience, though, we'll always bring them back to the embeded component after.
I see, thank you
You might also find the controller parameters in the API reference to be of interest: https://docs.stripe.com/api/accounts/create#create_account-controller
If my platform account is already onboarded as API, is it easy to switch to embedded?
There's no such thing as "onboarded as API". You can use API or embedded onboarding at will for any connected account.
but when I choose embedded, the Note is saying I selected API, so I thought I can't use that
Hi! Stepping in.. As mentioned by Rubeus, you can use API or embedded onboarding at will for any connected account. I believe the note might be based on your platform's Connect questionnaire when you first enabled Connect on your Stripe account.