Triaging KYC Failures

🚧

Sandbox ONLY: Triggering a passed status for

Classic KYC:

Please note that in Sandbox, if you have triggered a documents_required or review status, you can upload a document to the /documents endpoint. This will change the status to documents_received and in 2 minutes, the status will change to passed.

Advanced KYC:

Use /resume_verification to clear a failure trigger and get a passed verification status.

Order of operations if an end user fails KYC

1. Regardless of KYC flow, first give your end users a chance to rectify any mistakes they made with their initial registration PII with the /update endpoint.
   1. If you are using Advanced KYC, you'll want to call /resume_verification after the update's been made.
2. Regardless of KYC flow, the next step is for the end user to upload documentation.
   1. Classic KYC: when documentation is uploaded, our Banking Operations team is notified and will manually review that documentation. They will then either change the KYC status (triggering a webhook if you're subscribed), or they will reach out in your Slack channel to communicate with you.
      1. If you are using Classic KYC, there are no further steps.
   2. Advanced KYC: once the doc has been uploaded, use /resume_verification to resume the paused verification.
3. Advanced KYC ONLY: You are given two more tries to upload that same doc - you cannot upload a different doc, so be sure the one that is uploaded is the correct one. Continue to use /resume_verification to restart the verification process.

ADVANCED KYC NOTE: Which action to take - PII update or doc upload - will be indicated in an action_needed field in the webhook. Values are either entity_data or doc_upload.

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.

Classic KYC Reason Tags

📘

Advanced KYC Tags

See a list of tags returned with the Advanced KYC flow here.

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:

📘

Denied KYC

You may receive the tag "Denied KYC" which does not map back to any particular document verification request type. If you receive this tag just know that the accompanying tags below will inform you of your next steps. You need not take action on this tag alone; it will also be accompanied by additional tags.

Eg. "Denied KYC" + "Name Not Verified" means the user will need to submit name verification documents.

The tags provided during /check_kyc are for the internal use only and must never be exposed to end users.

Indviduals (Classic KYC):

• Individual Address Verification: Address Not Matched, Address Not Verified
• Name Verification: Name Mismatch, Name Not Verified
• Date of Birth Verification: DOB Miskey, DOB Not Verified
• Social Security Number Verification: SSN Miskey, SSN Not Verified
• General Identity Verification: Fraud Warning, Denied Fraud, Fraud Risk, Fraud Review, Age Verification

Businesses (Classic KYC):

• Entity Name: Company Name Not Matched
• EIN Verification: FEIN Unmatched, FEIN Document Required
• Business Address Verification: Address Not Matched, Address Not Verified

Estimate on timing for manual doc reviews

• Documents received between 6am PST and 4pm PST, M-F will be processed same day.
• As this is a manual process please allow time for this process. If document review exceeds 2 business days please contact support.