#jemen_docs
1 messages Β· Page 1 of 1 (latest)
π 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/1261226455128477719
π Have more to share? Add details, code, screenshots, videos, etc. below.
hello! It's mentioned in that doc you shared :
application: Your platform is responsible for collecting updated information when requirements are due or change
OK, so in means in "Your platform" ... That's us. We who making application which uses Stripe?
I want to be explicit.
This is legal stuff, so I'm being carefull @silver crag.
I assume you are the Platform, and you have connected accounts, so yes, you are responsible for collecting updated information
Thank you very much π
One more question @silver crag . Are we able to get (legal entity) connected account's address and tax registrations? Without being responsible?
What informations are we able to get from connected account, when we leave responsibility on shoulders of Stripe platform?
Because, I'm aware Webhook does not include those information implicitly.
@silver crag, does π» means conversation is closed? Just curious.
π» is just my version of you're welcome
Oh, got it.
generally, you won't be able to get what Stripe considers as KYC information if you leave the responsibility on Stripe to collect those details
So, there are only two options, first is being responsible - I mean a lot, and second not being responsible, but not gettting almost none information about our customers, right?
Sophie's choice
pretty much yep
Any exceptions you are aware of?
I think it's possibly not as onerous as what you currently have in mind, you can use Stripe embedded components to help collect the information required e.g. https://docs.stripe.com/connect/supported-embedded-components/account-onboarding, https://docs.stripe.com/connect/embedded-onboarding. However, I will say though, that it's definitely still way more effort than letting Stripe handle everything on your behalf
Show a localized onboarding form that validates data.
Yeah, I see. OK then, we have to consider this. Thank you very much for your effort. π»
I'm so sorry. On more question
Please
Sure
Oh, hello. π What informations can we collect from those embedded components @surreal drum ?
Connect Embedded Onboarding allows the Connected account to fulfill pretty much all requirements to be able to activate the account.
Specifics depend on the country
I see, and are we able to collect them, when using on our Plaform's website?
Embedded components are not my field of interest @surreal drum, so I'm not aware what am I able to get from them.
Well, they're sent directly to Stripe and used to activate the Connected account.
So, what are you trying to achieve exactly, on high-level?
We are trying to get as much information as possible. We also want to collect some data in our application. We just want to check, our user is not laying to us.
When user leaves our site and register on yours we can't pair those informations.
Those embedded components are just HTML elements and just before sending you data, we check they match with our data, right?
We are scared this could mean, let's say this user can do some fraund, or money laundering, or something.
Stripe conducts extensive checks on every new account that's activated. If they passed our check there's not much you should need to worry about.
Yeah, I see, but we need this match - I mean address match.
When we use those embedded elements, we can prefill it with our information?
This could also help us to make registration process more efficient and user friendly.
OH. To embedd those elements to our app, we just need those JS code, right? So we can create our registration form, which will use those JS code and send you all necessary data?
In that case we don't need to call API to check if information match with information on our side.
Correct.
Happy to help.