KYC documentation
KYC: general information
What the module does and how you connect it.
What it is
The KYC module verifies the identity of a person remotely. One session combines a document, a selfie, liveness and a face match, and the set of steps is a scenario that you build in the dashboard editor.
What it does
| Capability | What it covers |
|---|---|
| Document recognition | Detects, classifies and reads IDs: printed and handwritten text, the machine readable zone with its checksum, and signature and stamp checks. Coverage: 10,000+ document types, 195+ countries and territories. |
| Document anti-fraud | 20+ checks that catch screen photos, photocopies, printouts, glued photos, drawn-on elements, erasures, edited images and logical data errors. |
| Face match | A one-to-one comparison of the selfie with the document portrait, detection of a foreign face, and an age check against the date of birth. |
| Liveness | The liveness step is active: the person moves the face closer through two ovals. |
| Deepfake and face-swap detection | Detects generated faces and face swap inside the selfie and liveness steps. |
| Repeat-user and list search | Finds a returning person among earlier verified faces, and checks uploaded person lists and blacklists. |
| Proof of address | A utility bill, a bank statement or a lease as an extra document in the same session. |
| Database checks | AML screening and other checks against external databases. Their verdicts come separately and are not part of the body of a session. See AML screening. |
How you connect it
- REST API 2.0. Your server creates a session, sends images, reads the result and manages data. See the REST API reference.
- Web SDK. A widget for your page, in desktop and mobile browsers. It guides the user through the steps and takes the images with the camera. See the Web SDK and the mobile and WebView guide.
- Webhooks. Four events tell your backend when something completes. See webhooks.
- Dashboard. Scenarios, logs, reports, access and statistics. See the platform user guide.
The path of one verification
- You build a scenario and get its identifier.
- Your server creates a session, or the widget does it for the user.
- The user passes the steps.
- The platform checks every image and returns the result of each step.
- You get the final result by a webhook or a session status request.