Back

KYC (Know Your Customer) / AML

The main section for handling incoming and received requests.

KYC/AML Working Sections

KYC Logs

In real time, incoming sessions are displayed in KYC Logs. Each “tile” is a session assembled according to the configured scenario (a combination of steps: document(s), selfie, liveness).

What is visible on the right in the logs:

  • Result for the document: recognized type, OCR‑fields with confidence levels, authenticity status.
  • Anti‑fraud checks: MRZ and checksums, signs of screen/printout/editing, stamps/signatures, etc.
  • Result for the selfie: that this is a real selfie, a document in hand (if needed), proper match with the document from step 1.
  • Face Matching: comparison of faces between a selfie and documents (including a “selfie with a document”); similarity scores.
  • Database checks (if connected): MVD, FSSP, etc.
  • In case of failure — the reason and analysis of the problem.

The result is available in JSON (the structure matches the API response). The number of allowed failed capture attempts is configurable. Blacklist-based blocking (by face) is available.

Adding a session manually for tests/manual verification

KYC Reports

History of all sessions without real-time updates — for viewing, filtering, and exporting (CSV).

Filters: by date, status, OCR values (full name/number/city, etc.), by errors, by scenario.

Filtering and export to CSV

KYC Editor

In the editor, KYC verification flows are configured — any combinations of documents, selfies and (optionally) liveness.

List of created scenarios

General script properties

  • Scenario ID (schemaId) — schema identifier, use in the API/SDK.
  • Secret key — for encrypting notifications/callbacks.
  • Mobile redirect URL on success — where to redirect after a successful session.
  • Customer face list — a list from the “Persons” section, where recognized customers are added for subsequent search.
  • Blacklist of individuals — a list where a match blocks the session.
  • Critical errors before blocking — e.g., 3. This is protection against «brute-forcing» fraudulent images (probabilistic models).
  • Session data storage time (in days) — 0 = unlimited.
  • Session lifetime before freeze (min.) — after it expires, you cannot add new images.
  • Flags:
  • Block, if in a single step two different documents appear.
  • Block if the same person submitted the same document type with different data (fraud detection based on history).
  • Match the issuing authority against the division code database (increased confidence).
  • Allowed age — range (based on the date of birth from the document).

Notification settings (callback)

Callback (notifications to your backend)

  • Backend Callback URL — the address to which notifications about the progress/result of the session should be sent.
  • Flags:
  • Encrypt the POST body with a secret key;
  • Do not send personal data (statuses only);
  • Notify only upon finalization (without intermediate statuses);
  • Send database checks as they are ready.

Verification steps (Steps)

Step #1 — document(s)

  • Select the document type(s) (passport/ID/DL/… ) and countries.
  • Enable the necessary quality/anti-fraud checks, for example:
  • the document is fully visible;
  • MRZ processing (do not allow without MRZ);
  • signs of editing (isEdited);
  • photo of the screen (isDisplay), mobile device;
  • photocopy/printout;
  • logical inconsistencies of fields;
  • glare/blur/deterioration;
  • signature/stamp/mandatory elements etc.
  • Document frame for the WebSDK on low-end devices — vertical or horizontal.

Example of step settings for documents

Step #2 — selfie (or selfie with a document)

  • Checks:
  • The image is not modified, not a “photo of the screen”;
  • The document is visible in the selfie (if required);
  • Age/gender from the face (and matching with the document);
  • Deepfake/synthetics — protection against face substitution;
  • General quality requirements (sharpness, lighting, etc.).

Example of selfie step settings

WebSDK configuration (widget parameters, clientKey, callbacks) is described in detail in the Web SDK section; the details are not duplicated in the user manual.

KYC links

Section for generating one-time links for completing KYC:

  • Select a scenario, the time interval of the link’s lifetime, and the number of links (1…1000).
  • A list of created links will be displayed at the bottom with a status indicator (success/failure/opened, etc.).

Generation of one-time links