KYC Systems Comparison
An overview of Sila's two KYC systems.
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
NOT YET UPDATED FOR PRIORITY
Please use this overview here, which is up to date.
Advanced KYC is not SDK compatible
To ensure the user_handle you're wanting to assign is unique.
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.
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.
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.
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.
Classic KYC Endpoint Order
To ensure the user_handle you're wanting to assign is unique.
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.
Kicks off KYC verification for a specific user_handle.
Returns verification status of a specific user_handle.
Do not poll this endpoint. Instead, we recommend utilizing the KYC Status Update Event webhook.
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.
Number of KYC attempts allowed:
- End users get two total attempts to pass KYC or KYB.
Endpoints by System
| Classic-specific | Advanced KYC-specific | Shared |
|---|---|---|
| /request_kyc | /kyc | /register (including /add, /update, and /delete) |
| /check_kyc | /get_verification/<verification_uuid> and /get_verifications | /check_handle |
| Classic-specific failure triggers | /resume_verification | /get_entity and /get_entities |
| new Advanced KYC-specific failure triggers | /documents (including document-related endpoints, eg: /get_documents) | |
| new Advanced KYC-specific webhooks | KYB certification endpoints |
Updated 7 days ago