KYC (Know Your Customer) / AML

The main section for working with incoming and processed requests.

Working sections of KYC/AML

Working sections of KYC/AML

KYC Logs (online log)

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 side of 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 it is a real selfie, document in hand (if required), correct link with the document from step 1.
  • Face Matching: comparison of faces between the selfie and documents (including “selfie with document”); similarity values.
  • Database checks (if enabled): Department of Homeland Security, Federal Bureau of Investigation, etc.
  • In case of failure — reason and issue analysis.

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

Working sections of KYC/AML

Manual session addition for tests/manual verification

KYC Reports (reports)

The history of all sessions without realtime updates — for viewing, filtering, and export (CSV).

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

Filtering and export to CSV

KYC Editor (scenario editor)

The editor allows configuring KYC scenarios — any combinations of documents, selfies, and (optionally) liveness.

List of created scenarios

General scenario properties

  • Scenario ID (schemaId) — identifier of the schema, use it in API/SDK.
  • Secret key — for encrypting notifications/callbacks.
  • Mobile redirect URL upon success — where to redirect after a successful session.
  • Client face list — a list from the “Persons” section where recognized clients are added for subsequent search.
  • Blacklist of faces — a list whose match blocks the session.
  • Critical errors before blocking — e.g., 3. This protects against brute-forcing fraudulent images (probabilistic models).
  • Session data retention period (in days) — 0 = unlimited.
  • Session lifetime before freezing (min.) — after expiration, new images cannot be added.
  • Flags:
  • Block if two different documents appear in one step.
  • Block if one person submitted the same document type with different data (fraud history detection).
  • Match the issuing authority with the department code database (increases confidence).
  • Allowed age — range (based on the date of birth in the document).

Notification settings (callback)

Callback (notifications to your backend)

  • Backend Callback URL — the address to which notifications about the session progress/result are sent.
  • Flags:
  • Encrypt POST body with the secret key;
  • Do not send personal data (statuses only);
  • Notify only upon finalization (no intermediate statuses);
  • Send database check results as they become available.

Verification steps (Steps)

*Step #1 — document(s)*

  • Select document type(s) (passport/ID/driver license/…) and countries.
  • Enable required quality/anti-fraud checks, for example:
  • the document is fully visible;
  • MRZ processing (do not allow skipping MRZ);
  • editing traces (isEdited);
  • screen photo (isDisplay), mobile device;
  • photocopy/printout;
  • logical inconsistencies between fields;
  • glare/blurriness/wear;
  • signature/stamp/mandatory elements, etc.
  • Document frame for WebSDK on weak devices — vertical or horizontal.

Example of document step settings

Step #2 — selfie (or selfie with document)

  • Checks:
  • Image not modified, not a “screen photo”;
  • Document visible in the selfie (if required);
  • Age/gender by face (and comparison with the document);
  • Deepfake/synthetic detection — protection against face spoofing;
  • 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; details are not duplicated in the user guide.

Section for generating one-time links for passing KYC:

  • Select the scenario, lifetime interval for the link, number of links (1…1000).
  • Below you will see a list of created links with a status indicator (success/failure/opened, etc.).

Generating one-time links