#nintendoengineer
south pollen
Hi there 👋 when you're working with Custom accounts, you'll want to use fields like requirements to know whether there are still outstanding onboarding requirements that must be completed.
https://stripe.com/docs/api/accounts/object#account_object-requirements
If an account is disabled due to a missing requirement, that will be flagged in requirements.disabled_reason.
south dune
Hi, thanks for taking this up for me. So I am not having issues with the requirements, necessarily. It's more so that there is supposed to be a status property, but when I drill into the object in TypeScript, this property does not exist. I need to read this property to know if I can flag my user as verified
south pollen
The field you mentioned, company.verification.document.status, isn't referenced in our API spec either:
https://stripe.com/docs/api/accounts/object#account_object-company-verification-document
Can you point me to where you're seeing a reference to that field?
south dune
True, I don't see it in your API spec either. The confusing bit is here, in your docs: https://stripe.com/docs/connect/handling-api-verification#company-information
And then specifically this part in the image
It links to the Account object in your API reference, but then the status is indeed not there, as you mentioned as well
south pollen
Weird, those fields are inside of verification for the individual hash in our reference.
south dune
Yeah we also noticed. Supposedly it's on company as well. Do you think it's a documentation issue or an implementation issue?
south pollen
My suspicion is a documentation miss that may have cascaded into other places, but I'm going to ask a teammate to take another look.
Taking another look at the structure of individual, do you see company.verification.status (instead .document.status) in the typescript definitions?
south dune
Unfortunately also not present:
south pollen
What are the type definitions for the Company.Verification object type?
south dune
Sorry yeah I see I printed the wrong screen. here are Verification and Verificcation.Document, since document is the only property on Verification
south pollen
Did you by chance notice this while going through this flow with an Account? If so, could you share that ID?
south dune
I have not, sorry to say. I was first implementing the entire flow, part of which includes listening to your account.updated event. In my handler I wanted to read this status value. Since I couldn't, I didn't want to test an incomplete KYC flow as of yet
south pollen
Makes sense, was just wondering if there were any relevant objects my teammate and I could look at.
south dune
There should be some test accounts I've created, would those suffice? They have not yet been updated. Or wait, there might be one with updated data. Is a test account also fine?
south pollen
Yeah, test accounts are fine.
south dune
I will fetch the id from DDB, one sec
So it's not one that has had an account update yet, so there are requirements due. The account id is acct_1OHDTBGhJeaig9xD
If you need an account that has actually fulfilled all requirements, let me know, then I will have to provide the data through our platform
Haha nice profile pic, btw 🤣 is that how it feels working tech support?
south pollen
Hahaha, some days, but I mostly did it because I enjoy when people get a kick out of it
south dune
Hahaha it definitely sets the right mood
fervent beaconBOT
south pollen
We think this is an issue that our teams need to address, and that may take some time. I think it would be better if we move our discussion to a support case for this.
Could you please fill out the form here, and when you are selecting the topic choose "API Integration":
https://support.stripe.com/contact/email
Please also check the "I am a developer" checkbox that appears, and mention Toby in your description. If you let me know once you have I'll go find the case and take it.
south dune
I have a baby here that needs to sleep. I'll do this right after and notify you. Just don't know how long that will take. This one here is unpredictable.
In the meantime, do you know if there is another way of checking company status verification? If this is something we will also take up in the case, then let's leave it for that 😄
south pollen
I don't think there is a way to directly check it, but you can infer it from requirements hash. If the verification failed, then it should be mentioned in requirements.errors. If they are still in progress, then you'll see related entries in requirements.pending_verification.
south dune
Perfect, that helps me out in the meantime. Thanks for your help so far, Toby. I will notify you once I've made the case 👍