What it Does

Sikoia's secure identity verification solution enables you to verify a person’s identity using a live selfie and government issued documents. This acts as a robust defense against fraudulent activities.

Through a unified API, Sikoia provides access to providers such as Veriff and Au10tix ensuring you receive verified information in a standardised API response format.

How it Works

1. Create a Case & Add a Person: Create a case and add a person to the case.
2. Initiate a Request: Create an identity verification request via Sikoia's request IDV endpoint. This generates a unique URL which you share with the person undergoing verification.
3. User Input: The person clicks on the URL on their preferred device and platform and follows a series of prompts to capture images of their government-issued ID and record a simple selfie. After completion, Sikoia redirects them back to your platform.
4. Automated Liveliness Check and Face Matching: AI-powered technology conducts liveliness checks, face matching, verifies document authenticity, ensures image integrity, and delivers a swift result.
5. Review Decision: Sikoia promptly provides the result to you via the retrieve IDV result endpoint within seconds.

This white-labeled flow seamlessly integrates into any application.

See the image below for additional details.

Possible Results

The possible results of an identity verification request are as follows:

In addition to the overall identity verification result shown in the table above we also try to surface as much meta data as possible to indicate why a verification request was approved or declined. The amount of information available depends on the underlying provider but using the truncated example below our API will return the following structure:

{
  "request_id": "5b410d0b-bddc-4a14-9837-80520f4831f2",
  "status": "Complete",
  "data": {
    "verification_status": "Declined",
    "media": [],
    "meta_data": {
      "status_codes": [
        {
          "value": "0",
          "type": "Simple.Example",
          "description": "Request rejected by the server due to incorrect file size or type. Please resubmit the request with the correct file size or type (png, jpg, etc.)."
        }
      ]
    }
  }
}

🚧

Important

If the provider does not support the extraction of additional meta data then the meta_data object will be null in our response.

Provider: Au10tix

We will surface meta data for the Au10tix provider for all result codes. You can use this to confirm information and / or warning level remarks for "Approved" submissions as well as find detailed error explanations for why something was "Declined". There are five main "result" status code types that may be present here and a number of remarks.

As a general rule a "result" represents an overall status value for a portion of the IDV check (such as whether a provided document is authentic), and a "remark" represents supplementary information that further qualifies the reason for a "result". For example, a document status may be 0 (success), with a document remark 400 informing that the IDV went through the manual approval "Double Check" process.

Currently supported type values:

• DocumentAuthenticity.Result
• CompletionStatus.Result
• DocumentStatusReport2.Result
• DocumentStatusReport2.Remark
• FaceComparisonReport.Result
• RiskManagementReport.EffectiveConclusion.Result
• RiskManagementReport.EffectiveConclusion.Processing.Remark
• RiskManagementReport.EffectiveConclusion.Risk.Remark

DocumentAuthenticity.Result

This value may be represented in either a text, or numeric form. Only one will be returned and they should be considered equivalent in your consuming application.

CompletionStatus.Result

This value may be represented in either a text, or numeric form. Only one will be returned and they should be considered equivalent in your consuming application.

DocumentStatusReport2.Result

This value will only ever be numeric.

DocumentStatusReport2.Remark

This value will only ever be numeric.

FaceComparisonReport.Result

This value will only ever be numeric.

RiskManagementReport.EffectiveConclusion.Result

This value will only ever be numeric.

RiskManagementReport.EffectiveConclusion.Processing.Remark

This value will only ever be numeric.

RiskManagementReport.EffectiveConclusion.Risk.Remark

This value will only ever be numeric.

Provider: Veriff

Additional meta data not currently supported.

Supported Countries

This solution is available for all countries.

Supported Documents

The user-provided ID documents must meet the following criteria:

• Document must be a government issued driver's license, passport, residence permit, or standard ID.
• Document must be an original – photos of government issued documents are not accepted.
• Document is valid, not scratched, stained, or torn.
• Applicant’s full name, date of birth, MRZ (Machine Readable Zone), and other essential information is present and readable.

Webhook Events

If you have configured any webhooks that reference one of the Identity Verification events you will receive one of:

• IdentityVerification.Completed - sent when a user completes the identity verification successfully or unsuccessfully. It will contain the verification result from the table above
• IdentityVerification.Expired - sent only when a verification process has been requested for a user but they never completed it before the link expired

Both events will contain links for retrieving the Requests List and full IDV Result.

Recipe & Endpoints

Check out this recipe for more information on how to use Sikoia's API for identity verification.

📘

Start exploring Sikoia's identity verification endpoints here.