#soma-connect-verification

1 messages · Page 1 of 1 (latest)

halcyon narwhal
#

Hi there, yes overall that should capture whether they are verified or not.

#

The disabled_reason should always be present if the account is disabled for some reason or another.

frigid quartz
#

ok, then the requirement.error is not needed to make sure an account is verified?

halcyon narwhal
#

What is requirement.error?

#

Ah sorry

#

I see what you are seeing

#

So that code will inform you if more information is needed to verify the account

#

Like it will tell you the specific information that would need to be (re)collected

frigid quartz
#

so it is safe to think that asking for those two conditions is good enough?

#

I mean to verify the identity of the account

halcyon narwhal
#

Yes the requirements hash is what you should be using to determine whether an account is verified and if it isn't verified then the disabled_reason property should not be null. If you want to be extra sure, you can add a check for charges_enabled and payouts_enabled but that should align with whether there are past_due requirements.

frigid quartz
#

please, can you expand more on charges_enabled and payouts_enabled???

#

are they related to the identity?

halcyon narwhal
#

They will tell you whether the account can make charges/payouts

#

Identity verification may affect these depending on the deadline for identity verification

frigid quartz
#

ok, so, are unrelated

frigid quartz
#

certainly will do it right now

#

thanks

halcyon narwhal
#

Sure! That walks through handling ID verification at a high level

#

Let me know if you have any specific questions after reading that