Glossary
редThis section contains supporting materials on the terminology and key concepts of the NV Global platform and the KYC module.
Glossary of terms
General concepts
KYC (Know Your Customer) — a procedure for remote user identity verification based on documents and photos, with anti-fraud checks and additional database checks. In the NV Global platform, this is a separate module with its own API and WebSDK.
KYC session — a single user verification according to a given scheme (for example, «passport + selfie with a document»). All image uploads, recognition results, errors, and statuses are linked to sessionId.
Scenario (scenarioId) — KYC verification scenario: a set of steps (document, selfie, Liveness, database checks, etc.) and settings (limits, anti-fraud, callback)
Client — an end-user of your service (an individual) undergoing KYC verification. Not to be confused with an integrator’s account on the NV Global side.
WebSDK and Frontend
WebSDK is a JavaScript library for embedding a KYC widget into a website or SPA (React, etc.). It is responsible for camera capture, image uploading, and communication with the KYC backend.
KYC widget — a ready-made pop-up (popup/modal) where the user goes through all KYC steps: photographs a document, takes a selfie, and passes Liveness.
KYCWidget.setupKYC(...) is the main method for initializing the widget in the browser. It accepts a config (schemaId, clientKey, theme, callbacks) and opens the widget.
clientKey (WebSDK) — a string up to 36 characters long, set on your side and passed to the widget in encrypted form. It is used to link KYC sessions to your users/applications and for subsequent filtering in the API.
clientUser — an optional string up to 36 characters long, previously used as an additional client identifier.
closeCb — a callback that is called when the widget is closed (success, error, or manual closing).
successCb(payload) — a callback that is called when the KYC scenario is successfully completed. payload contains full information about the session; detailed data is retrieved via the REST API /kyc/session/status.
Theme (theme) — widget design: light or dark. Can be used for visual consistency with your product.
REST API and backend
REST API KYC — a set of HTTP methods for creating sessions, uploading images, checking status, and retrieving a list of sessions. Key methods:
/kyc/session/create, /kyc/process, /kyc/session/status, /kyc/sessions, /kyc/sessions/filter.
/kyc/process — a method that accepts images (document, selfie, etc.), recognizes them, and saves the result in the session. It can operate in sync and async modes.
/kyc/session/status — a method for obtaining the current session status and detailed results for each step (document, selfie, face comparison, etc.).
/kyc/sessions — a list of all KYC sessions with brief information and nested results.
/kyc/sessions/filter — selection of sessions by filters: status, errors, date range, clientKey, schemaId, database checks, etc.
JWT token is a temporary access token returned by the /user/login method. It is passed in the Authorization: Bearer ... header and used in all protected API methods. :contentReference[oaicite:11]{index=11}
Permanent token / access token — a long-term token created via /token/create and listed in /tokens. Convenient for server-side integrations and service tasks.
Webhook (callback URL) is your HTTP endpoint to which the platform can send notifications about the completion of a KYC session. The request body can be encrypted; decryption is performed on your side using a pre-agreed key.
Identifiers and Entities
sessionId — a unique identifier for the KYC session. Used in all requests to the status and log API.
clientId — the client ID in the KYC system (may differ from your userId).
clientKey (in API responses) — the original value (up to 36 characters) that you set during encryption on the backend. Allows you to link a KYC session to your user or application.
Person list — a logical collection of records about individuals (persons) that can be compared with new images: /person, /persons, /person/list/*.
Person — an entry in the list of persons: includes data (fields), information about the person and, if necessary, vector representations.
Source group — a logical group of image/video stream sources. It is managed by the methods /source/groups, /source/group/create, /source/group/update, etc.
Data source — a specific source of images tied to a group (e.g., camera, integration, project). It can have settings for automatic face addition and features to be detected (feature_check).
Liveness and face processing
Liveness (liveness detection) — a set of algorithms that confirm that a living person is in front of the camera, and not a photograph, video, or synthetic image (deepfake). It uses analysis of frame sequences, micro-movements, textures, and artifacts.
Active Liveness — a mode where the user performs actions (head turns, changes in gaze direction, etc.), and the system checks the correctness of command execution.
Passive Liveness — a mode in which one or more frames are sufficient without explicit tasks, but the system determines signs of real presence.
Face Matching — an assessment of the similarity of two or more faces in different images (document ↔ selfie, selfie ↔ selfie, selfie with document ↔ document). In the KYC results, this is a separate block with a match percentage.
Face vector is a numerical representation of a face image (a set of numbers) used for quickly finding similar faces. In the API, it is called embeddings and is used, for example, in /vector/search.
Fusion vector is a combined vector representation of a face from several images of a person. It is created using the /person/fusion method to improve search stability.
OCR, documents and anti-fraud
OCR (Optical Character Recognition) — recognition of text fields of a document (full name, dates, document number, place of birth, etc.) from an image. The ocr block in KYC responses contains title, value, conf fields and status.
MRZ (Machine Readable Zone) — a machine-readable zone of a document (usually two or three lines at the bottom of a passport/ID) containing encrypted data and checksums.
Anti-fraud checks — a set of detectors that identify fake documents and images: screen photos (display), photocopies (image printed), editing (image edited), face swapping, logical inconsistencies, etc.
Blacklist — a list of undesirable persons or entries; if there is a match with the user’s person or data, a [fraud] black list error is issued.
KYC error codes are standardized text codes (e.g., [general] bad image, [document] text fields not visible, [fraud] mobile device) that explain the reason for an unsuccessful check. A complete list is provided in a separate error reference.
External databases and scoring
External database checks — additional requests to state registers, tax and court databases, sanctions lists, and other data sources (bankruptcies, sanctions, debts, etc.). These checks may affect the overall KYC session status.
Financial scoring — assessment of risks based on data from credit bureaus and additional sources (for example, default scoring for short-term loans).
KYC session status — final verification status: success, failed, idle, sometimes suspicious. Overall success is only possible if all critical checks (document, face, Liveness, antifraud, external databases) are successfully passed.
