#dusk_connect-onboarding
slender sphinxBOT
shadow micaBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- dusk-_docs, 4 days ago, 71 messages
- dusk-_docs, 5 days ago, 52 messages
slender sphinxBOT
👋 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/1242136175473328169
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rare pebble
Hello
indigo gazelle
Hi!
rare pebble
Basically when you create the account you want to prefill as much information as you already have collected from your user
indigo gazelle
Yes
rare pebble
That is the only real way to make onboarding "shorter"
indigo gazelle
Is there a way to skip phone number verification?
rare pebble
Otherwise we collect only the information that is required
No you can't skip anything within the flow
indigo gazelle
I see, and how would phone number verification happen if we use purely the API instead of the embedded onboarding component
rare pebble
What type of Connected Accounts are you working with?
indigo gazelle
I don't quite understand the question but we're just creating a regular Stripe account (https://docs.stripe.com/api/accounts/create) followed by an account session (https://docs.stripe.com/api/account_sessions) whose client secret field we use in the embeddable component.
Our goal is to onboard our customers (non-profits) and then create Payment Links / Checkout for them so they can accept the donation. When creating their Stripe account, we input their bank account details that they have with us, and our goal is that they'll receive the donations through payouts in their bank account on our platform
I hope that answers it, if not, please let me know if I can provide more info
Our other goal is to make this as quick as possible for them since they already go through a KYB/KYC with us
rare pebble
When you create the account why type do you use: https://docs.stripe.com/api/accounts/create#create_account-type
indigo gazelle
We use custom atm but we're not sure which one would be best
rare pebble
Gotcha, with Custom the only reason phone number verification is required is if you are having our Onboarding flow collect their external account information.
But you can't pre-fill that from your end -- that is PII for the user.
So unless you want to handle external account collections and updates, you can't really get around phone number 2FA
indigo gazelle
Would using express or standard help us in any way?
rare pebble
Not really, both of those require more user interaction if anything
Since they have an actual Dashboard
indigo gazelle
If phone number verification is a requirement, then that's fine. Our main concern is to make the whole process super fast for them
slender sphinxBOT
rare pebble
Yeah I mean you are already doing everything you can in that case -- you prefill all the information you have on account creation. There is no real way to speed it up further. All other info collected will be required.
indigo gazelle
I see, and how would phone number verification happen if we use purely the API i...
And this?
rare pebble
You can't do phone number 2FA via the API
That is what I'm explaining above -- that is just between the Connected Account merchant and Stripe so that they can securely add/update their external account
indigo gazelle
I see
The current way that we're doing it, is that the only option we have for our use case of letting our customers (non-profits) accept payments via Stripe when then get sent to their bank account on our platform via a payout
whole fossil
Hi 👋
I"m stepping in as my colleague needs to go. I agree with my colleague that your current approach is doing everything you can to ensure your customers have an easy time signing up.
indigo gazelle
Okay
Just a little confusion. How would phone number verification happen if we are using API onboarding and not allowing any Stripe dashboard?
whole fossil
That is a little confusing since we don't clearly spell that out. Let me check on that
indigo gazelle
That is a little confusing since we don't clearly spell that out. Let me check ...
Thank you
whole fossil
Okay, after conferring with my colleagues I realize that, for Custom Account onboarding done entirely through the API, you as the platform handle all the information collection and we trust that you have verified who the Connect Accounts are.
So there would not be any phone number 2FA verification.
indigo gazelle
Perect, and no document submission either?
whole fossil
You may need to collect and supply documentation at some point. the required verification checks get updated after some activity on the connected accounts
indigo gazelle
Okay
What is the minimum information we have to submit for Custom Account onboarding done entirely through the API? The goal is to onboard them super fast and allow them to start receiving donations through payment links
whole fossil
It depends a lot on the type of businesses they are, where they are located, etc. I recommend you use this form to check what will be required and when: https://docs.stripe.com/connect/required-verification-information
indigo gazelle
Awesome, thank you so much
Will we be able to create payment links for them as soon as we create an account with that minimum information?
whole fossil
You will need to check the Account object to see if the transfers and card_payments capabilities are active: https://docs.stripe.com/api/accounts/object#account_object-capabilities
indigo gazelle
Yep, they are!
Account.CreateParams(
business_type="non_profit",
capabilities={
"transfers": {"requested": True},
"us_bank_account_ach_payments": {"requested": True},
},
controller={
"stripe_dashboard": {"type": "none"},
"fees": {"payer": "application"},
"losses": {"payments": "application"},
"requirement_collection": "application",
},
company=company,
country="US",
email=email,
external_account=external_account,
Okay, that's what you would need to check.
Wait.. no they are not
They have been requested but they are not active
indigo gazelle
What should I change it to
whole fossil
You cannot change it. You, the platform, request the capabilities. Stripe determines whether they are enabled or not. You need to check the Account objects that are returned
indigo gazelle
I see. Since we are going to be using just API onboarding, how would Stripe determine whether it (payments) should be enabled or not? Since you also said that "you as the platform handle all the information collection and we trust that you have verified who the Connect Accounts are"
whole fossil
We need to perform some basic verification checks for the information you provide.
Have you tested any of this in Test mode?
indigo gazelle
Was doing it before through embeddable component. Will give it a shot with just the api onboarding
How long does this thread stay open?
whole fossil
Depends on activity but usually if it's silent for longer than 1 hour
shadow micaBOT
indigo gazelle
Okay, thanks. I will try and get back to you within the hour