#atob-yash_atob-connect-api-onboarding
fickle rainBOT
👋 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/1266085068766576804
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
charred locust
Hi 👋
There isn't a great property for this via the API but I think you can check the charges_enabled and payouts_enabled properties. If they are true then the account is considered verified.
foggy pike
Hey! To add more colour to our usecase, we whitelabel the onboarding experience at our end and when Stripe is unhappy with the verification, we ask users to either update information / submit an ID document (eg: invalid_street_address code). It looks like Stripe allows one doc upload, but after the document has been uploaded once, and verified, Stripe doesn't allow a second document to be uploaded
So in order to run the logic at our end "should we ask our user to upload a new document" can be checked by charges_enabled and payouts_enabled? Should this be an AND or an OR between the two properties?
charred locust
I would use an AND operator. Also, you will want to check the requirements hash to determine exactly what required verifications are still oustanding.
foggy pike
Yes, but in the case where requirements has person_xyz.address.line1 but the charges_enabled and payouts_enabled are both true, Stripe would reject a document, correct?
charred locust
Ah sorry I was thinking about other verifications. You need to check wether the document is verified or not. Not the account.
foggy pike
How would we do that?
charred locust
Retrieve the Verification Report object
https://docs.stripe.com/api/identity/verification_reports/retrieve
And check the document.status property
https://docs.stripe.com/api/identity/verification_reports/object#identity_verification_report_object-document-status
foggy pike
How do I get the vr_ id for a document uploaded to a person / account object?
charred locust
You are creating Verification Sessions when verifying the person, correct?
foggy pike
No
charred locust
Sorry, which flow are you using here?
foggy pike
We use Stripe::File.create and then call Stripe::Account.update_person( account_id, person_id, { verification: { document: { front: file_id, back: file_id_two, }.compact, }, }, {api_key: api_key} )
charred locust
Okay, sorry there are many ways to go about this and I suspect I was thinking of a different approach
In this case I think you will want to retrieve and check the Person object. Specifically the verification property: https://docs.stripe.com/api/persons/object#person_object-verification
charred locust
Yes but there are many other details in that hash that could be useful to you so I would review the entire thing and see how you can plug that into your document collection flow.
On the Account object, it shows up in Account.individual.verification https://docs.stripe.com/api/accounts/object#account_object-individual-verification
Or company.verification depending on the business type
https://docs.stripe.com/api/accounts/object#account_object-company-verification
foggy pike
Account.individual.verification is the same as Person.verification.status?
charred locust
No, did you look at the link? Each verification is a hash similar to the Person.verification
But they aren't necessarily identical since a Person can represent something other than the Individual
This gets kinda in the weeds when we talk in the abstract.
I recommend you review both the Person and Account.individual verification hashes in your flow. You can see if the properties of each update together and which object best represents what you want for your onboarding process.
foggy pike
Okay, will do, thank yoU!