# Platform User Guide

The **NV Global™** platform is a set of computer vision solutions for KYC/AML, face workflows, and video analytics.\
Below is a practical guide for operators and administrators: from registration and statistics to “Working with faces,” access tokens, and the full KYC workflow.

> For integration via API/Web SDK see the links inside the corresponding sections.

***

## Personal account

### Registration and login

A user registers via **e-mail**. **To register you need an** ***invite code*** — it is issued by your administrator or a representative of **NV Global**.

After logging in, the user enters the personal account.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FGDd0c2pOXBuy5nAtYYYj%2Flk-registration-login.jpg?alt=media&#x26;token=cac8d6e6-c525-424d-b45a-38981ef00c48" alt=""><figcaption></figcaption></figure>

*Registration and login to the platform*

***

## “Statistics” section (KYC dashboard)

One of the main sections of the account is **Statistics**. It contains key metrics, filters, and settings. For new accounts all counters are zero.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FlsyF4z7OVwMoLlxf6W7M%2Fstatistics-dashboard.jpg?alt=media&#x26;token=72113cfe-877c-4e30-8ad9-356bd12c44a7" alt=""><figcaption></figcaption></figure>

*Summary dashboard*

**KYC dashboard structure:**

1. **Percentage of successful/rejected sessions** — for the selected interval and scenario.
2. **Error distribution** — a “pie” showing proportions of error types (e.g., “fields not visible,” “screen/printout,” etc.).
3. **Success rate by attempts** — a “pie” showing shares of sessions completed on the 1st, 2nd, 3rd attempt, etc.
4. **Daily dynamics** — a bar chart: the number and share of successful/unsuccessful sessions by date.

The statistics are designed for self-analysis without external BI tools: filter and group the data right here.

***

## Working with faces

This block combines three areas: **Data sources**, **Person lists**, and **History of operations (Face search)**.

### Data sources

Sources are channels through which the **NV Global**™ platform receives images/video streams: surveillance cameras, photo files, archived videos.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FizapxmWR1AcHS3c3eOGx%2Fdata-sources.jpg?alt=media&#x26;token=90cb7bf7-73a5-4453-b698-4cb71ca0a826" alt=""><figcaption></figcaption></figure>

*“Data sources” section*

**Adding a new source**

1. Open **Data sources** → **Add new source**.
2. Specify:
   * **Source name**
   * **Face check parameters for additional attributes** (if needed)
3. Click **Create source**.

**Source groups**

* Create **groups** to organize sources by locations/projects.

**View and status**

* The list shows: activity, basic statistics, state.

***

### Person lists

The **Person lists** section is key: it stores the database of people recognized by the system.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FGP5UIRPdUTQx9NcfaJan%2Fpersons.jpg?alt=media&#x26;token=076dffde-aadd-4106-b76a-48214369b187" alt=""><figcaption></figcaption></figure>

*Lists, cards, and face search*

**Operations with lists and persons**

* **Add a person**: upload photo(s), fill in the data.
* **Import from multiple files** — bulk addition.
* **Edit card**: replace photo, update fields, **find similar**, **move to another list**.
* **Delete**: individually or in batch.

**Analytics and alerts**

* Configure events.
* Use aggregated analytics of visits and activity.

***

### History of operations (Face search)

**History of operations** is a log of recognition events and admin-panel actions.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FCY0oYht2JMLocXzpPryJ%2Fface-search.jpg?alt=media&#x26;token=2152c9b7-83a2-4e9d-bb88-f5b67c5eae4c" alt=""><figcaption></figcaption></figure>

*Log of recognitions and actions*

**What is available**

* View timeline with filters by **sources**, **groups**, **dates**, **person**.
* Navigate to the person/source card, browse related objects.

***

## Access Tokens

Tokens are used for authentication/authorization of API requests.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2F1njDBgKWt63Y3q1Kt9lE%2Faccess-tokens.jpg?alt=media&#x26;token=4e63e669-40a2-4240-8d53-f29f3bd5afc7" alt=""><figcaption></figcaption></figure>

*“Access Tokens” section*

**Create a token**

1. **Access Tokens** → **Create new token**.
2. Specify **name**, **expiration date** (if needed), **permissions**.
3. **Save**.

**View/edit/delete**

* Token list; click to edit/delete.

**How to pass the token**\
**Feature for endpoints:** the token can (and often is more convenient to) be passed **in the request body** as the `token` field. Example:

```
# Endpoint URL
url = "https://api.enface.ai/v1/kyc/process"

# Parameters for KYCDocument
data = {
    "token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",        # the token is transmitted in the body
    "schemaId": "ca30efc0-9202-11f0-ad12-90496423b317",
    "mode": "sync",                                    # or "async"
}
```

> For the full specification see the corresponding API sections. In most endpoints any option (header/body) is acceptable, but **in `multipart/form-data` the `token` field is often more convenient**.

**Important**

* Store tokens as secrets, do not share them with third parties and do not publish.

***

## Help Center

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FncM9pFuxI7GEKRLSxTEL%2Fhelp-center.jpg?alt=media&#x26;token=8230ec69-a212-4d57-909e-7de68e400296" alt=""><figcaption></figcaption></figure>

*Support and notifications*

* **Support** — support contacts, knowledge base (FAQ/articles/videos).
* **Notifications** — system messages about updates and maintenance.
* **Create Issue** — support tickets with file attachments and status tracking.

***

## KYC (Know Your Customer) / AML

The main section for working with incoming and processed requests.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2F2GQQDIrx1WAdGhuR2TDL%2Fkyc-overview.jpg?alt=media&#x26;token=953f74ac-ef3a-4e21-b8d3-12d380c2dc25" alt=""><figcaption></figcaption></figure>

*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.

*Manual session addition for tests/manual verification*

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2Fu5oUrcB5TnhCUwvtb82O%2Fkyc-choose-verification.jpg?alt=media&#x26;token=54581b03-86ea-40a6-a2e5-6dc38b5a3327" alt=""><figcaption></figcaption></figure>

### 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*

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2F4CHOvZ1IR3cbtuJRLECz%2Fkyc-reports.jpg?alt=media&#x26;token=8de6858a-73ea-413f-830c-3ae3c6f93226" alt=""><figcaption></figcaption></figure>

### KYC Editor (scenario editor)

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

*List of created scenarios*

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FzzwJYb1Hg9vdednkw5Bp%2Fkyc-editor-overview.jpg?alt=media&#x26;token=8b5034dc-dbe9-4955-92ce-b5cc4b14bfa2" alt=""><figcaption></figcaption></figure>

**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).

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FGj8kgcAgxsS3jweTN3vN%2Fkyc-editor-callback.jpg?alt=media&#x26;token=55ec9a39-ba52-4bff-984c-e9625c7c7424" alt=""><figcaption></figcaption></figure>

*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**.

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2FUxUqtjSmTEowcEIr8Qr3%2Fkyc-editor-step1.jpg?alt=media&#x26;token=83c1fce8-c5f8-4065-b88b-34a531274465" alt=""><figcaption></figcaption></figure>

*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.).

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2F4AeEcCnXxmDP38MdhIon%2Fkyc-editor-step2.jpg?alt=media&#x26;token=3ea1f12f-b3bd-4a59-8efd-b6f120ee4734" alt=""><figcaption></figcaption></figure>

*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.

### KYC links (one-time links)

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.).

<figure><img src="https://1453876250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRr3zB0xucM3fgCViuJqz%2Fuploads%2Fc8YSNr475ZyD02ksqjlp%2Fkyc-links.jpg?alt=media&#x26;token=c0d06188-a2fe-44a0-9d1b-320b4b0344fe" alt=""><figcaption></figcaption></figure>

*Generating one-time links*

***

## Notes on versions

Features and interfaces may differ depending on platform version and your environment settings. For clarifications, contact your administrator or support.

***

```
```