It's normal for some users to fail their initial KYC or KYB evaluation. As the app owner you'll naturally want to give these user the opportunity to rectify any mistakes they've made in their initial registration data, such as a typo, but only give your users the opportunity to update their registration data one-time. Make use of our /update endpoint to allow users a one-time opportunity to update their registration data if they fail their first KYC or KYB screen.
It's also your responsibility to take the right steps in ensuring you don't on-board nefarious actors who seek to defraud your platform.
Users who fail their KYC or KYB screen may upload documents which verify their information. Each of the following categories has particular documents which can be used to verify the user's information. It's best practice to make use of our /documents endpoint to securely upload and send Sila documents which need to be reviewed.
Sila's API response body has an attribute
Tags which distinguishes the kind of documents you'll need to send us. They are as follows:
- Individual Address Verification:
Address Not Matched,
Address Not Verified
- Name Verification:
Name Not Verified
- Date of Birth Verification:
DOB Not Verified
- Social Security Number Verification:
SSN Not Verified
- General Identity Verification:
- Entity Name:
Company Name Not Matched
- EIN Verification:
FEIN Document Required
- Business Address Verification:
Address Not Matched
Once documents are received, they will be reviewed within 2 business days. No matter the outcome (documents being sufficient or insufficient), Support will update you directly and will discuss if there are any next steps.
Updating user data
A user may input old or faulty registration information causing them to fail KYC or KYB. You may give your users one opportunity to update their information using our /update endpoint. If they fail again then they need to provide documents to verify their identity.
Updated about a month ago