#qualle-custom-accounts
1 messages · Page 1 of 1 (latest)
hello
I'd recommend starting by going through our docs about this specifically: https://stripe.com/docs/connect/identity-verification-api
there isn't "one exact field" , the fields depend on many factors: country, business types, what other information was passed, etc.
There's a lot of work you need to do here
We also strongly recommend not building this yourself, we built Connect Onboarding so that you never have to worry about it: https://stripe.com/connect/onboarding
we have a specific requirement to handle this in-app
not an "exact field" sure, but fields necessary to verify a company
there's no exact fields, there are numerous things to provide
I'd recommend reading our docs carefully, this is all covered in details, it's just a lot of work. Possibly months of work if you wnat to handle multiple countries and business types
thats fine
and there are exact fields
"eventually_due": [
"external_account",
"individual.address.city",
"individual.address.line1",
"individual.address.postal_code",
"individual.address.state",
"individual.dob.day",
"individual.dob.month",
"individual.dob.year",
"individual.first_name",
"individual.last_name",
"individual.ssn_last_4",
"tos_acceptance.date",
"tos_acceptance.ip"
],
and I believe an ID document
that's for an individual
you said a company earlier
companies require collecting information about every owner and the representative and details about each one, and sometimes extra information based on what we can and ca't verify
https://stripe.com/docs/connect/required-verification-information documents this clearly that's why I recommend going through our docs first
I've definitely looked at it for weeks
but its not clear what apis are used
the bigger question is, we might be steering away from connect if there is such risk involved onboarding users
we need to manage payouts in a marketplace fashion, but this will cause high bounce rates
here it seems only accounts api is used
I'm not sure what risk and bounce you cause. Not using Connect is not possible, unless you don't use Stripe at all I guess. If you want to disburse funds to other businesses/accept payments on their behalf you have to use Connect.
And for the APIs, you use the Accounts API for the account/business/company details and the Persons API for representing individual humans involved in the business
I'm totally happy to clarify/chat about it.What I can't do is give you a magic list of fields, that's not how identify verification works worldwide
thank you for clarifying, my job is to manage expectations with my business, I've sold them on connect - but we really prefer to have the onboarding in-app
interesting, yes, we are only focused on US for time being
but I can communicate that to business and we can switch over to provided onboarding
I actually tested including accountLink in their welcome email upon registration, which worked like a charm
but if there are multiple apis/region considerations, we may just stick with the provided onboarding
The links expire after a few minutes and on first use. We recommend getting the person to your website and from there redirecting them to Stripe
no iframe
full page redirect only
And for US it's definitely easier, but still a ton of work. You need to do SSN validation, file upload, date of birth validation. It's not impossible, hundreds of businesses do this, but it's hard. It's our job to focus on this while you focus on your business 🙂
I was going to mention, I haven't seen any examples of companies using this
but that is my own ignorance
bigger companies have capacity to hand-roll solutions, which my team understands
there are more users of Connect Onboarding than people using the raw APIs, I can tell you that :p
Also rules change, in a year we might say "hey you need to collect a phone number now" because it's a new rule/regulation and you'll have to make changes. While with Connect Onboarding we just do that for you!
interesting, very helpful
this channel is very very good for stripe, and we are going to be doing huge business through this
millions a year
But this is me helping developers do this right
if I dont convince you, I'll spend 5 hours helping you do each field so I'm definitely biased :p
(and thanks, really appreciated)
it seems convoluted for sure
just one more question, the stripe provided onboarding includes credit card info?
and I can still listen to webhook to update our database records with their account info?
you can ask many more questions I'm happy to help. I'll just send you to the docs if you didn't read them :p
Connect Onboarding with Custom accounts only collects personal information about the business/people involved.
It does not collect the payout details like their bank account or debit card in the US
ok we are handling this in-app right now, lets just say the provided onboarding is completely finished
it's something we want to add but it's tricky since there's no authentication in that flow, we rely on you, the platform, to send the right person to the right page
on our side
there was ask from business to provide in-app, I'll explain to them why
yep totally understand
I have the discussion we just had with dozens of people
it's like people who don't want to use Checkout. They just want their payment form, but many want that because they never really tried Checkout and saw how many more things it can do than just card payments
We have a marketplace which requires a very high volume of ACH transfers from 1 customer to another
and our business takes a fee
these transfer payments could amount in thousands per day
it is 100% built, using provided onboarding, we are just worried about bounce rates with ID card, SSN
sure but that problem would happen wherever you go