#yi-heng_connect-requirements-capabilities
kindred viperBOT
👋 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/1344711853271552131
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hasty laurel
Hi 👋
Are you looking for a pending status under account capabilities? Or somewhere else?
You should be aware that we do not have 1 to 1 parity between what we display on the Dashboard and what is available via the API
hasty laurel
pending is one of the three potential values you can see here. Do you have a specific capability that you see as pending in the Dashboard but is not represented that way in the Account object?
wicked fog
Oh sorry, the capability for some accounts remain as "active" while the verification is pending. What we want to know is how to get the status Information pending verification
hasty laurel
Sorry but it's not clear to me what you mean by "the status information pending verification"? The verification process isn't something that is exposed via the API except for the status of capbilities and the information requested in the requirements property
wicked fog
Before a user submits the necessary information, there is "pending_verification" under "requirements" but once submitted, the account object does not tell us about "verification".
Is there a different way to get the information on successful completion of the verification?
hasty laurel
The requirements property is simply there to indicate what information Stripe requires in order to keep the Connected Account in compliance. You must collection this information by redirecting the Connect Account holder through the Account Link https://docs.stripe.com/api/account_links
Whether or not the verification is successful can be inferred by whether or not capaiblities for the account were de-activated.
I don't think Stripe sends more details about the verification process via the API
wicked fog
Ok I see, so we just have to assume that the verification is pending until a change of capability status during onboarding of an account
hasty laurel
If capabilities that are pending become active then yes, you can assume the verification is successful. You can also continue to review the contents of the requirements property, as that will update (and trigger and account.updated webhook event) whenever we require more information.
wicked fog
But for orgs that have capabilities active and submit information as part of the new verification requirements, we'd have to manage this "pending verification" state ourselves since the api won't return any information on it
hasty laurel
Correct. In that scenario you are in a "no news is good neews" situation.
wicked fog
Ok thank you for your help!
Wasn't aware that the webhook event shown in the dashboard could be different from the api
it just seemed that all the information contained within the request would be sent
hasty laurel
Yeah the Dashboard does a lot of extra processing to be "helpful" but it can lead to confusion about what is in the API
wicked fog
Good to know and thanks again
hasty laurel
Happy to shed what 💡 I can 🙂