#dalton-connect-events
willow canyonBOT
Hello! We'll be with you shortly. 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.
distant lichen
Hello! How are you listening for events? are you just using the stripe listen command?
cold trout
It's a webhook configured in test mode on the dashboard
distant lichen
Can you share the event ID? What behavior were you expecting instead?
cold trout
evt_1OkAWFQi5aGsNpevjD7KYcq1
I assume stripe trigger account.updated would simulate an update for the platform account since the --stripe-account ID flag was not passed
However stripe trigger account.updated --stripe-account accountID errors
distant lichen
Gotcha - as far as I can tell, this is how the account.updated trigger is meant to work with the CLI. Under the hood it actually creates a new connected accuont and updates the account it just created to trigger the event
distant lichen
You're just asking how to test this event for a specific connected account?
cold trout
Right
I asked this [here](#1207770059930341436 message) and couldn't respond in time. I am trying to handle requirements by myself without stripe onboarding. These are custom connect accounts.
willow canyonBOT
dalton-connect-events
cold trout
I mean I am pretty confident my webhook will do what I want, but it would be naive of me not to test it. And to test so far all I can do is literally wait for the event to pop up by itself in test mode. Which can take awhile. For example, it is supposed to pick up any requirements and sync it with my database on the user's account. As well as notify the user to resolve them.
distant lichen
You could just update the account yourself through the API (https://docs.stripe.com/api/accounts/update)
That should triggere the account.updated event for the specific connected accuont you choose
cold trout
Right, I am assuming updating using the CLI will trigger as well?
distant lichen
correct, it should
cold trout
I can just update some arbitrary data like the metadata field?
distant lichen
yup!
cold trout
I also asked about a list of possible requirements that might come up. It seems like you guys really just want us to use your onboarding for stuff like this
Only saying that because the docs for this are very slim. I feel like handling all of this manually should be pretty common? Redirecting a user to an in-app browser to complete a verification step seems like an anti-pattern.
That in mind, do you know of any resource I am missing to help with this, or should I just keep handling the requirements as they show up?
distant lichen
Have you looked at https://docs.stripe.com/connect/required-verification-information yet?
cold trout
Yes, we collect all of that when the user "activates" their connect account. And we present them with Stripe's ToS
willow canyonBOT
cold trout
The only thing I do not collect is the identity document as I think I remember it stating it is not always required.
Worth noting these are just individuals and not businesses
distant lichen
If you've already looked at https://docs.stripe.com/connect/required-verification-information , what specifically were you hoping for with the full list of possible requirements?
rocky imp
👋 hey again, i'm catching up here to take over when karbi has to step away shortly
cold trout
Honestly, I guess I am not sure. Is what I am looking at pretty complete in what is needed or will be needed? Looking again, it says individual.verification.document and verification.additional_document might be required eventually after I can guarantee I collected all other required information.
So this "list" of eventual requirements only consists of those two items? That's basically what I am curious about. If there are no other requirements that might need to be handled then problem solved
rocky imp
Well also note the threshold details indicated lower down: https://docs.stripe.com/connect/required-verification-information#US--entity_individual--threshold-information
Broadly speaking that should cover things, but you should also monitor account.updated events and potential new requirements to future proof yourself (ie, surface anything you might not alreayd have explicit handling for).
cold trout
Right, I can plan on that as well for generic stuff that may just require customer support at that point. But stuff like identity document submission needs to be handled autonomously by the user in our app.
Also, does that threshold stuff apply for GB accounts? I apply the filter and it is no longer listed
rocky imp
Apologies for the delay, I initially missed the GB question at the end. I don't see that for GB accounts either, so it appears all the required information is required up front.