...

Cloud verification service

Document checks, Liveness and database checks without your own servers. You get access, build a scenario in the dashboard and send the first request the same day. Customer data is processed on servers in Russia on your instruction, and you pay for completed sessions.

Cloud identification: the NeuroVision cloud panel and a verification session
0 servers on your side: infrastructure, models and updates are on NeuroVision
16 000+ document types from 195+ countries and territories
from 16 ₽ per “Document” KYC session — no subscription fee
1 month of test access on your own documents
Servers in Russia Data processing agreement under 152‑FZ Russian software registry no. 19972

Cloud identification: what NeuroVision takes on

Your part of the work — the scenario and the decision

You choose the documents, steps and checks, accept the result on your own server and answer to the customer as the data controller. Everything else is on the cloud side.

  • 01

    Servers and scaling

    Document recognition, Liveness and face matching run on NeuroVision servers. If the flow of applications grows, we add capacity — you don’t need to buy GPUs or recalculate the configuration.

  • 02

    Models and updates

    New document types, forgery signs and fixes are rolled out to the cloud without your involvement. Every release is described in the changelog: what changed in the API, webhooks and widget, and whether anything needs changing in your integration.

  • 03

    Monitoring and on-call

    The cloud is monitored automatically: NeuroVision engineers fix an outage without waiting for your report. How the integration should behave during an outage and what to put in the SLA — on the page about load and fault tolerance.

  • 04

    Check sources

    Connections to state registers and sanctions lists for database checks are already set up. You tick the checks you need in the scenario — we handle the agreements with the sources and their availability.

  • 24 checks in the AML catalogue, switched on in scenarios
  • 2 minutes and a new widget domain is already working
  • v1 API version in the request path, changes in the log

From contract to first request: how the cloud is connected

You can send the first test request on the day access is issued. How long going live takes depends on your integration — the widget embeds faster than your own interface on the REST API. Step-by-step details — “Quick start” and integration testing.

Step 1

Contract and data processing instruction

We sign a contract in which you instruct NeuroVision to process your customers’ data: which data, which actions, for what purposes and how it is protected. What exactly the instruction must contain — in the block below.

Contract with a data processing instruction
Step 2

Invitation code and dashboard

The manager issues an invitation code and the account owner registers in the dashboard with it. Two-factor authentication is enabled straight away and is mandatory for all users.

Registration in the dashboard by invitation code
Step 3

Token and domains

In the “Access” section create a token for server requests and add your site domains for the widget. A domain starts working within two minutes; the widget opens only over HTTPS.

Access token and allowed domains
Step 4

Verification scenario

In the “KYC Editor” assemble the steps: document, selfie or Liveness, database checks. Set the data retention period and the webhook address for your server. You can start from a template.

Verification scenario with a retention period
Step 5

Test on the test scenario

A separate test scenario in your account: run success, rejection, widget closing and an expired session on fictitious data. Make sure your server takes the result from the webhook or a status request.

Test on the test scenario
Step 6

Production

Switch the integration to the live scenario and top up the balance or choose a package. Then — reports in the dashboard and closing documents for each period.

First live session in the cloud

SaaS verification: what you don’t need to buy and configure

Your own document verification system is not just a licence. Here is what the cloud takes off your IT department and budget. How the platform works — architecture and components.

  • Servers with GPUs

    Not needed. Recognition and Liveness neural networks run on NeuroVision servers. No purchase, no downtime while the hardware is in transit.

  • Headroom for peaks

    No need to keep capacity “just in case”. A sale, a promotion or a season — the flow goes to the cloud. Agree large volumes with the manager in advance so that we can prepare for them.

  • Model updates

    No need to install and test versions. Recognition and anti-fraud improvements appear in the cloud on their own; breaking API changes are described in the log in advance.

  • Verification interface

    No need to build from scratch. Web SDK is a ready-made widget in your colours and texts; it works on the site and in a mobile browser, and in an app — via WebView.

  • Staff workplace

    No need to write an admin panel. Session history, filtered reports, manual status change and roles — in the dashboard.

  • Subscription fee

    There is none. You pay for completed KYC sessions or buy a package that can be used up in a day or in a year.

Data in the cloud: where it is stored, how long it lives and how it is destroyed

  • Servers in Russia

    Document and selfie images, recognised fields and check results are processed and stored on servers in Russia. There is no cross-border transfer in the cloud KYC process. Why this matters under Part 5, Art. 18 of 152‑FZ — on the page a KYC service in Russia.

  • Retention period is set in the scenario

    You set how many days session data is kept in the scenario settings; “0” means indefinitely. Different scenarios can have different periods: for example, short for age verification and long for financial products.

  • Destruction on request

    One call destroys the personal data of one session or of all of a user’s sessions by your customer identifier. Every destruction is recorded in the log: who, when, through the dashboard, API or system, and for what reason.

  • Less data in transit

    The webhook body is encrypted with the scenario secret key, and the “do not send personal data” flag leaves only statuses in the notification — your server fetches the data itself by the session identifier.

Methods — deleting a session’s personal data and deletion log. Retention periods under your industry rules — for example, five years under 115‑FZ — are set by you.

Data processing agreement under Part 3, Art. 6 of 152‑FZ: what it must contain

In the cloud model the operator of your customers’ personal data is you, and NeuroVision processes it on your instruction. Since the 2022 amendments the law lists what the instruction must contain. Go through the list with your lawyer.

  • A list of personal data: document and face images, recognised fields, questionnaire data, responses from check sources Contract
  • A list of actions with the data and the purposes of processing — for example, remote identity verification of a customer at registration and database checks under your scenario Contract

  • To observe confidentiality, the principles and rules of processing under 152‑FZ, the requirements on databases in Russia (Part 5, Art. 18) and on measures under Art. 18.1 NeuroVision
  • At your request — throughout the term of the instruction, including before processing starts — to provide documents on the measures taken NeuroVision

  • Data protection requirements under Art. 19 and the obligation to ensure data security during processing ContractNeuroVision
  • The obligation to notify you of an incident: as the operator you have 24 hours for the first notification of Roskomnadzor and 72 hours for the investigation results (Part 3.1, Art. 21) Your company

  • The summary is simplified and is not a legal opinion; the exact text is in ConsultantPlus. Localisation, cross-border transfer and notifying Roskomnadzor are covered on the page a KYC service in Russia.

Cloud account: staff, tokens, balance and reporting

The cloud is also a dashboard where your team manages access and spending. Access rights

  • Staff and roles

    Who gets in: the account owner invites staff and builds roles from individual permissions.

    Protection: two-factor authentication for everyone, a login log with IP address and device.

    • Roles
    • 2FA
  • Integration tokens

    A separate token for each system: site, CRM, back office.

    Term: unlimited or with an expiry date; a token can be deleted without affecting the others. Access tokens.

    • Token
    • Deadline
  • Balance and packages

    Payment: per check or by package; a package does not expire at the end of the month.

    If the balance runs out: a check returns an “insufficient funds” code — watch the balance in advance.

    • Package
    • Balance
  • Reports and documents

    Report: “KYC Reports” — sessions for a period with filters and export.

    Accounting: closing documents with the number of checks at the end of each reporting period.

    • Reports
    • Acts

A package for approving the cloud: for legal, information security and procurement

The cloud service goes through three approvals. So that none of them drags on for a month, request the document package together with test access.

  • For legal

    Contract and data.

    Request the contract

    Contract

    • a contract with a processing instruction under Part 3, Art. 6
    • a list of data, actions and purposes
    • an incident notification procedure

    NeuroVision documents

    • personal data processing policy
    • retention periods and destruction procedure
    • details of NeuroVision LLC
  • For information security

    Where the data is and who has access to it.

    Request the description of measures

    Hosting

    • servers in Russia
    • retention period in the scenario
    • data destruction log

    Access

    • roles and two-factor authentication
    • separate integration tokens
    • webhook body encryption
    • platform architecture in the documentation
  • For procurement

    Software origin and payment.

    Calculate the cost

    Software

    • an entry in the Russian software register No. 19972 dated 13.11.2023
    • Rospatent certificate No. 2023661508

    Payment

    • per session or package, no subscription fee
    • closing documents for the period
    • test access for 1 month

Questions worth asking any provider — on the page a KYC service in Russia

When the cloud is more convenient than your own installation

  • You need to launch this quarter

    An own installation starts with a survey and hardware procurement. In the cloud the first request is on the day access is issued, and the pilot runs in the test month.

  • An uneven flow

    Promotions, seasonality, a launch in a new region. The cloud doesn’t make you keep capacity for a peak that happens once a year.

  • No in-house GPU team

    Servers with GPUs require administration and updates. In the cloud that is NeuroVision’s job.

  • Several products and scenarios

    Different scenarios for retail, partners and staff live in one account and are paid for per completed check.

  • You need a predictable session price

    A per-session price from the price matrix and an annual package are clearer to finance than a licence, hardware and engineer hours.

  • You need to switch without rewriting

    Start in the cloud. If your security policy requires your own perimeter, the methods, responses and webhooks stay the same — only the API address changes.

If customer data must not leave your perimeter — on-premise installation and private cloud.

How much cloud verification costs

You pay per KYC session with all the scenario steps. Connection, dashboard, roles and updates are not listed as a separate line in the price matrix; there is no subscription fee.

  • Document

    from 16 ₽ per session

    Enable: Document

    Document recognition and anti-fraud: screen, printout, photocopy, pasted photo, editing.

  • Document and face

    Document + liveness

    from 29 ₽ per session

    Connect: Document + liveness

    Everything in the “Document” package plus a selfie or Liveness and matching the face with the photo in the document in one session.

  • Extended

    on request

    Calculate: Extended

    Document, Liveness and database checks in one session: Russian databases and international sanctions and PEP screening.

A database check is 5 ₽, all 16 Russian database checks — 50 ₽, international screening — 36 ₽, an additional document — 10 ₽. Annual packages are cheaper per session — the calculator in the price matrix.

Connecting to the cloud: Web SDK, REST API or your CRM

A ready-made widget on your site

Add the script or npm package, pass the scenario identifier and the customer’s encrypted key — the widget captures the document and selfie and runs Liveness. Your server receives the result by webhook.

Web SDK documentation

Terms

  • A 1-month trial period
  • Support under contract
  • Payment for completed sessions

Cloud verification glossary

Terms of the contract, the dashboard and the conversation with the security team.

Cloud service
Checks run on the provider’s servers, while the company connects via API or a widget and pays for usage.
SaaS
Cloud identification
Remote identity verification by document, selfie and Liveness performed by a cloud service.
cloud identity verification
Personal data operator
The company that determines the purposes and scope of processing. In the cloud model — you.
data controller
Processing on behalf
An agreement under which the operator entrusts processing to another party; its content is set by Part 3, Art. 6 of 152‑FZ.
processing agreement
Processor
A party that processes data on the operator’s instruction and answers to the operator.
data processor
Localisation
Recording and storing the data of Russian citizens in databases located in Russia.
data localization
Retention period
The number of days session data is kept in the cloud; it is set in the scenario, “0” means indefinitely.
retention period
Scenario
A set of verification steps and settings: documents, Liveness, database checks, webhook, retention period.
scenario
Access token
The key your server uses to call the API; it is created unlimited or with an expiry date.
access token
Selfie-to-document matching
A one-off comparison of the face in a selfie with the photo in the document within one session.
face match

Frequently asked questions about the cloud verification service

Remote identity verification performed by a cloud service: the customer captures a document and selfie, passes Liveness, while recognition, anti-fraud and database checks run on the provider’s servers. Your system receives the result via API. At NeuroVision the cloud runs on servers in Russia.

The first test request is on the day access is issued: registration by invitation code, token, scenario and a widget or API call. Going live depends on your integration and approvals — we name the timeline after reviewing the task.

You are. You determine the purposes and scope of processing and collect consents, while NeuroVision processes the data on your instruction. You answer to the customer for the processor, and the processor answers to you (Part 5, Art. 6 of 152‑FZ).

A list of data, actions and purposes, the obligation to observe confidentiality and the requirements on databases in Russia, the obligation to provide documents on measures at your request, protection requirements under Art. 19 and incident notification. This is how Part 3, Art. 6 of 152‑FZ is structured.

As long as you set in the scenario: the period is given in days, “0” means indefinitely. At any moment the data of a session or of all of a user’s sessions can be destroyed with one call; the fact is recorded in the log.

No. Your server only calls the API and receives webhooks, and the widget script is added to the site. Models, updates and capacity are on NeuroVision’s side.

Liveness detection and a one-off match of a selfie with the photo in the document within one session. To process face images, your company obtains the customer’s written consent (Part 1, Art. 11 of 152‑FZ).

The cloud is monitored automatically, and engineers fix an outage without waiting for a report. Build the integration so that the result can be picked up with a status request if a webhook did not arrive. More — on the page about load and fault tolerance.

Yes. The cloud and on-premise capabilities are the same, and the methods and response format stay unchanged. How installation goes — on the on-premise installation page.

“Document” — from 16 ₽ per session, “Document + Liveness” — from 29 ₽, the extended package with database checks — on request. There is no subscription fee, and a package does not expire at the end of the month. The first month is test access.

We’ll connect the cloud to your scenario

Tell us which customers and with which documents you verify and how many sessions a month you expect — we’ll build the scenario, send a contract with a processing instruction and give you test access.

Can't put your request into words? Book a call and our team will contact you at a convenient time

Book a call

The NeuroVision platform is listed in the Russian software registry, entry no. 19972. Rospatent certificate no. 2023661508.

Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.