#dominikganic_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/1350048451886579797
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- dominikganic_unexpected, 1 day ago, 24 messages
- dominikganic_best-practices, 1 day ago, 31 messages
- dominikganic_unexpected, 2 days ago, 33 messages
- dominikganic_best-practices, 2 days ago, 29 messages
- dominikganic_unexpected, 3 days ago, 13 messages
Hi ๐
You should be able to see the Events generated in testmode when you test this flow. The related ones are account.created (depending on how you're handling onboarding), account.updated, capability.updated, person.created, and person.updated.
Hi, thanks for reaching out. I have another question.
I'm using Stripe Connect to onboard my customers in our platform.
Now, I've successfully completed this and their restaurant is onboarded.
Stripe displays a message like "A identitiy verification may be required soon"
Which means, my customer must upload a verification document soon.
I've seen there is "Stripe Identity" but still in preview / inivite only features. So this approach won't work now.
I use embedded components. Is there any component to handle this case, so I don't have to manually ping the users uploaded identity (picture of his identity card) to stripe?
And can I perform a identity verification even before stripe requests it - just in case, it already is there and verified then? ๐
Yeah, the onboarding component handles that.
https://docs.stripe.com/connect/supported-embedded-components/account-onboarding
You can use setCollectionOptions to indicate you want to collect eventually_due requirements too, which should cover requesting that information:
https://docs.stripe.com/connect/supported-embedded-components/account-onboarding#:~:text=false-,setCollectionOptions,-{ fields%3A 'currently_
Nice! Thank you.
So when I "setCollectionOptions" I can define that I required the user identity card.
Is there anything else really important which I should request from beginning that might "pause" his connected account?
I'm not sure what that last question means.
I mean, when Stripe requests the users identity card, it probably pauses his connected account for payouts etc.?
If you know what Capabilities you will need your Connected Accounts to have, you should add all of those to the Account up front, as it may change the required information for successful onboarding.
So, are there any other similar cases along identity cards?
Where are you seeing these requirements surfaced on the Account object? In the requirements.eventually_due hash?
array (
0 => 'individual.verification.document',
),```
That's what my webhooks have received after a successful onboarding
So nothing else could "disturb" the peace of my stripe connected account? ๐
Accounts aren't immediately paused for eventually_due requirements. Only currently_due requirements will pause an account when the current_deadline is reached.
The information we need from Connected Accounts may change at any point, for instance if our financial partners or regulatory bodies adjust what information we're required to collect, so your flow should listen for account.updated Events and pay attention to any changes in requirements or future_requirements.
That's how you'll be notified of requirements that could impact the state of your Connected Accounts.
Alright. So I could listen for "currently_due", when there is anything set, I should display the account-onboarding component to my customer and from this embedded component he may handle any triggered requirement right?
Yup, sounds right
๐ taking over for my colleague. Let me know if there's any follow-up Qs I can answer!
Nice. Thanks a lot ๐ I guess I've understood it now.
I don't think so yet, gonna handle this in my code now, thanks a lot guys. have a nice day ๐
would you mind me closing the thread then?