Run this endpoint after /register and /kyc. For a full list of verification records for an entity, call /get_verifications.

🚧

Advanced KYC ONLY

Only use this endpoint if you are utilizing the new Advanced KYC.

📘

Timing and Webhooks

Please make use of our webhooks so that you are notified when changes have been made. On average it takes about 33 seconds for an ID verification to complete, but can take less or more time.

If a verification status stays in review or documents_required for 30 days, the evaluation will expire and the status will be failed.

Request

Authorization / Authentication

Apps using Access Token Authorization

Use a valid access token in an Authorization: Bearer request header.

See Auth Token Overview for more details.

NOTE: Though we recommend using JWT, you can use this endpoint with ECDSA.

POST /0.2/get_verifications/<verification_uuid> HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
Authorization: Bearer [GENERATED JWT TOKEN HERE]

{
  "header": {
    "created": 1234567890, //required
    "app_handle": "your_app_handle", //required
    "user_handle":"user_handle", //required
    "version": "0.2", 
    "reference": "<your unique id>"
  }
}

***

HTTP/1.1 200 OK

{
  "success": true,
  "status": "SUCCESS",
  "message": "User has passed ID verification!",
  "response_time_ms": "171",
  "reference": "<provided reference_id>",
  "sila_reference_id": "sila_assigned_id",
  "verification_id": "<provided verification uuid>",
  "entity_type": "<idividual or business>",
  "verification_status": "passed",
  "flow": "<uuid of KYC Flow>",
  "checks_performed": "[KYC options selected]",
  "requested_at": 1592339985,
  "updated_at": 1592340016,
  "parent_verification": "<verification_uuid of parent verification if member of KYB, else null>",
  "reasons": {
    "<entity_handle>": ["<List of reasons providing rationale for the outcome, this will vary but should not be empty>"]
  },
  "kyc_action": "<entity_data or doc_upload or review>",
  "certification_status": null or bool
}

Request Attributes

Verification Statuses

If your end user receives documents_required

You have 5 total opportunities to pass. The first is giving the end user a chance to update their PII, then you have four chances to upload documentation:

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 you will need to take next will be indicated in the action_needed field of this call's response or the kyc_action webhook.

• entity_data - End user PII should be reviewed
• doc_upload - Use /documents to upload verification documentation
• review - Indicates no customer action as the verification is under manual review by Sila

Reason Tags

Tags returned by Alloy explaining the verification result. Please be aware tags are specific to KYC or KYB, not both.

Responses