KYC Systems Overview

🚧

IMPORTANT

If you are a current customer migrating to TPB or a new customer, you are required to use Advanced KYC rather than Classic KYC.

While there is no current ETA, we do plan to eventually sunset the Classic system and only support Advanced KYC.

We recommend using Advanced KYC rather than Classic. Advanced KYC includes automated doc review and updated webhooks for next actions for a more streamlined and efficient KYC process. While there is not an ETA, we also plan to sunset the Classic system.

Advanced KYC Endpoint Order

📘

Advanced KYC is not SDK compatible

/check_handle

To ensure the user_handle you're wanting to assign is unique.

/register

Creates a new individual or business entity in the Sila ecosystem with associated PII. Does NOT begin KYC verification. Creates a Sila wallet for the user_handle.

NOTE: Prior to beginning KYC verification in the next step with /kyc, end users can update their information with /update.

/kyc

Kicks off KYC verification for a specific user_handle.

/get_verifications/<verification_uuid> or /get_verifications

Return the verification status of a single KYC application with /get_verification or a full list of all verification records for a specific user_handle with /get_verifications.

🚧

Important! When end user doesn't pass KYC

If your end user doesn't pass KYC, you have five total tries to get the user to pass:

1. The first try will always be to update end user PII. Use /update. Once updated, use /resume_verification to restart the verification process.
2. If the end user still doesn't pass, the next try will be to upload a doc. Once uploaded, use /resume_verification to restart the verification process.
3. You are given three 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.

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.

/resume_verification

If an end user fails verification, use this endpoint to restart the verification process after PII has been updated or after uploading a doc to /documents.

/documents

Upload end user documentation to this endpoint if necessary to verify their identity. Only one doc can be uploaded, so be sure to upload the correct one on the first try. The only options for documents to upload for Advanced KYC are driver's license, state ID, or passport.

🚧

KYB Doc Upload

Doc upload is not supported for business entities. Additional verification will be done manually by the Sila BankOps team.

Classic KYC Endpoint Order

/check_handle

To ensure the user_handle you're wanting to assign is unique.

/register

Creates a new individual or business entity in the Sila ecosystem with associated PII. Does NOT begin KYC verification. Creates a Sila wallet for the user_handle.

NOTE: Prior to beginning KYC verification in the next step with /request_kyc, end users can update their information with /update.

/request_kyc

Kicks off KYC verification for a specific user_handle.

/check_kyc

Returns verification status of a specific user_handle.

Do not poll this endpoint. Instead, we recommend utilizing the KYC Status Update Event webhook.

/documents

Upload end user documentation to this endpoint is necessary to verify their identity.

Use the Triaging KYC Failures doc to determine what documents are needed based on the tags returned. Do NOT reveal the tags to end users, only what document to provide.

Endpoints by System

Number of KYC attempts allowed:

• End users get two total attempts to pass KYC or KYB, regardless if Advanced KYC or Classic is used.