...

Digital customer onboarding

Online customer onboarding is the check of a new customer before they get access to money or a deal: a questionnaire, a document, database checks and a decision. In the NeuroVision KYC editor you build a scenario from the steps and rules you need, and the customer goes through it on their phone in one session — with no office visit and no manual data entry.

up to 6 free capture attempts per step
16 000+ document types from 195+ countries and territories
2 stages a questionnaire at sign-up, the full check later
from 16 ₽ per KYC session with all scenario steps
Document anti-fraud — in all packages The session outcome goes straight to your backend Data stays on servers in Russia

Customer onboarding: what it is and where the check fits in

One session, one payment

The price of a KYC session includes all scenario steps: the document, anti-fraud, a selfie or liveness — depending on the package. Retake attempts are not charged.

  • 01

    Onboarding is bringing a customer on board, not teaching them the product

    The word “onboarding” is used both for getting to know an interface and for taking a new customer on for service. Here it means the second: a person registers and confirms their details and documents, and the company decides whether they can be given an account or a loan, or be allowed to sell or rent.

  • 02

    Digital onboarding happens in one session

    The customer opens the widget on a website, in an app or by a link, photographs a document, takes a selfie or a liveness check if needed, and the data goes to database checks. The result reaches your system right after the last step — with no manual entry and no forwarding of scans.

  • 03

    The check is built into the customer journey

    The more steps there are and the less clear the prompts, the more often customers abandon registration. That is why an online onboarding scenario is built around the product: what to ask for at the start, what to postpone until the first operation, where an operator is needed.

  • 04

    The decision follows rules, the operator handles exceptions

    The outcome of each session is “success”, “failure”, “suspicious” or “expired”, with reasons. Your system uses these outcomes to open access, ask for a retake or pass the application to an employee. That way manual review remains only where a person cannot be avoided.

  • 1 a session per customer, all steps inside
  • up to 6 free attempts per step
  • 3 months image storage is free, then charged per the tariff

Digital onboarding instead of an office visit: what changes

  • For the customer

    Where. In an office — at a branch, during working hours. Digital onboarding — at home, in a browser or an app: remote onboarding needs no visit.

    Documents. In an office — the original at the counter and a copy on a photocopier. Digital onboarding — a photo of the document with a phone camera, on-screen prompts, up to 6 attempts per step.

    Waiting. In an office — a queue and manual processing. Digital onboarding — the session outcome right after the last step; database checks arrive as they are ready.

  • For the check

    Document authenticity. In an office — by an employee’s eye. Digital onboarding — document anti-fraud: a photo of a screen, a printout, a photocopy, traces of a graphics editor, a pasted-in photo, logical mismatches between fields.

    Data entry. In an office — by hand, with typos. Digital onboarding — field recognition with a confidence level, MRZ and checksums.

    Databases. In an office — agency websites one by one. Digital onboarding — database checks in the same session: passport validity, the list of terrorists and extremists, the wanted list, sanctions lists.

  • For control

    Decision. In an office — an employee following an instruction. Digital onboarding — the rules of the scenario and of your system; an employee looks only at exceptions.

    Trail. In an office — copies in a folder. Digital onboarding — a session with photos, results and reasons in the personal account, JSON and report export to CSV.

    Scale. In an office — as many applications as there are employees. Digital onboarding — volume is limited by the tariff, not by headcount; a cloud in Russia or installation in your perimeter.

Digital onboarding changes the channel, not the obligations: the way a customer is identified is still set by 115‑FZ — more on this in the section on the Unified Biometric System and ESIA.

An onboarding scenario in the KYC editor: what you configure

KYC scenarios with rules are built in the personal account, in the “KYC/AML” → “KYC Editor” section, with no development. Each scenario has its own identifier: it is passed to the widget, the link or the API. There can be several scenarios — for example, separate ones for new customers, for withdrawing money and for customers with a foreign passport.
KYC editor guide · Which documents are recognised

  • Steps and their order

    A document, a second document, proof of address (the registration page), a selfie or a selfie with a document, liveness — in any combination. A separate scenario is the questionnaire for the two-stage check.

  • Document types and countries

    In a step you choose the document types — a passport, an ID card, a driving licence and others — and the countries of issue. The platform recognises 16,000+ document types from 195+ countries and territories.

  • Anti-fraud checks of a step

    Step flags: the document is fully visible, the MRZ is required, no traces of editing, not a photo of a screen, not a photocopy or a printout, no logical mismatches, no glare or blur, a signature and a seal are present.

  • Session rules

    How many critical errors to allow before blocking, whether to block two different documents in one step, whether to check the issuing-authority code, what age is acceptable by date of birth, how long a session lives and how many days to keep its data.

  • Selfie and liveness

    If the scenario has a selfie or liveness step, you set the liveness check mode and the reaction to extra faces in the frame. Processing such images is regulated by 152‑FZ and 572‑FZ — agree the scenario with your lawyer.

  • Notifications and texts

    The callback address on your backend, encryption, sending statuses only without personal data, notification only about the outcome. The widget screen texts — including failure, retry and exhausted attempts — are changed in the editor.

Customer onboarding stages: from the questionnaire to the decision

This is what the full scenario looks like. Steps your product does not need are simply not enabled — the customer will not see them. What the session outcome response looks like.

Step 1

The customer opens the check

A widget on a website, in an app, or a one-time link in an email or a message. Before starting — the terms and the privacy policy in the widget’s language. In a two-stage scenario, if a session with the same customer is already complete, on reopening they will see its outcome.

The start screen of the check with consent to data processing
Step 2

Questionnaire or document choice

In a two-stage scenario the customer enters their full name and, if you enabled the field, their date of birth — and immediately sees the success screen. In the full scenario they choose a document type and a country from those you allowed.

The customer questionnaire and the choice of a document type
Step 3

Capture and document check

Prompts and a frame help to shoot the document. The platform checks the quality of the frame, recognises the fields and the MRZ, and looks for signs of forgery. If the frame is not suitable, the customer retakes it: up to 6 free attempts per step.

Capturing a document with a prompt and frame checks
Step 4

Selfie or liveness — if enabled

The customer takes a selfie or passes a liveness check, and the face is compared with the photo in the document. The step is included in the “Document + liveness” package. Whether you may use it depends on 572‑FZ — your lawyer decides.

The liveness check step in an onboarding scenario
Step 5

Database checks

The recognised data triggers checks: passport validity, the list of terrorists and extremists, the wanted list, sanctions lists and others from the catalogue. Results reach the backend as they are ready.

Database check results arrive as they are ready
Step 6

Result and decision

The session gets an outcome: “success”, “failure”, “suspicious” or “expired” — with reasons for each step. Your system, by its rules, opens access, asks for a retake or passes the application to an operator.

The session outcome and decision branches in the company’s system

Decision rules: approve, retake, reject or pass to an operator

Customer onboarding automation rests on rules: some you set in the scenario, some in your own system based on the session outcome. Below is what the platform decides and what stays with you.

  • All scenario steps are completed, the document anti-fraud checks raised no flags, the face match passed if the scenario has a selfie or liveness step — the session gets the status success Session outcome
  • Database check results arrive separately. What counts as an obstacle — a list match, the wanted list, enforcement proceedings — is up to you: for example, a list match is always a stop, a debt is a reason for manual review Your system
  • The outcome notification goes to your backend; you can receive only the outcome, without intermediate statuses, and without personal data Scenario setupYour system

  • The frame was not suitable — glare, blur, a cropped document, unreadable fields. The customer sees a prompt and shoots again; each step has up to 6 free attempts Scenario setupSession outcome
  • If the faces on different steps did not match, the response contains a list of steps to retake — only those are retaken, not the whole scenario Session outcome
  • The texts of the retry screens and prompts can be rewritten in the editor for your product Scenario setup

  • The last attempt of a step fails — the session closes immediately with the status failed Session outcome
  • The threshold of critical errors is reached — protection against brute-forcing forged images; two different documents in one step Scenario setup
  • The age by date of birth is outside the allowed range Scenario setup
  • In a two-stage scenario the document data did not match the questionnaire Session outcome
  • The faces on different steps did not match in a way a retake will not fix — the session gets the status suspicious and closes Session outcome
  • The customer did not finish the session in time — the status expired Scenario setupSession outcome

  • Which outcomes to send to an employee is decided by your system: for example, a rejection for logical mismatches for a customer with a large application, or a match with a namesake in a database Your system
  • The employee opens the session in the “KYC Logs” or “KYC Reports” section: photos, recognised fields with a confidence level, anti-fraud and database results, the reason for rejection, JSON Operator
  • The employee’s decision is a manual change of the session status in the account or through the API. After a manual change the session no longer accepts frames Operator

Two-stage onboarding: a questionnaire at sign-up, documents when needed

A full check with documents at the entrance puts off some new users. The two-stage scenario removes this barrier: at sign-up a person fills in a short questionnaire — a full name and, optionally, a date of birth, with no documents or selfie. They go through the full KYC later, when it is really needed: before the first withdrawal of money, a loan or a deal.

The stages are linked: when you create a link to the full KYC, you specify which questionnaire to match the data against. The name is compared word by word, allowing for different spellings; the date of birth — exactly. No match — the check fails, and the customer does not learn which field let them down. Questionnaires are collected in a separate tab of the account and are visible with the linked checks. How to set up the two-stage check

Onboarding stage 1: a questionnaire with a full name and date of birth
Onboarding stage 2: capturing a document for the full check The result of matching the document against the questionnaire: the data matched

Risk-based onboarding: three levels of checking

Not every customer needs the same check. In the account you can keep several scenarios and choose one by risk profile: a short one — for access without money, a full one — for standard products, an enhanced one — for large sums and higher-risk customers. Which level the law requires for your operation is determined by your compliance team.

  • Simplified

    For registration without access to money and for the first stage of the two-stage scenario.

    Set up the simplified one

    Scenario steps

    • Questionnaire: full name and date of birth
    • Or a document without a selfie

    Checks and rules

    • The list of terrorists and extremists
    • Sanctions lists
    • Passport validity, if the customer provided a document
  • Full

    Standard onboarding: an account, a loan, a wallet, rental, sales on a marketplace.

    Set up the full one

    Scenario steps

    • A document with anti-fraud
    • A selfie or liveness — as your lawyer decides
    • A second document if needed

    Checks and rules

    • The “16 in 1” passport package
    • Up to 6 attempts per step
    • The acceptable-age rule
  • Enhanced

    Large sums, foreign customers, higher risk under your rules.

    Set up the enhanced one

    Scenario steps

    • The full scenario
    • Proof of address or a residence permit, temporary residence permit, visa, patent — as an additional document

    Checks and rules

    • International screening: PEP, sanctions of 50+ countries
    • Manual review by an operator
    • Re-check on an event

115‑FZ names the levels differently: identification, simplified identification (cl. 1.11 and 1.12 of art. 7) and updating of details at least once every three years for low-risk customers and once a year for the rest (subcl. 3, cl. 1, art. 7). How simplified, full and enhanced KYC differ in international practice — in the article “The three-level KYC model”; how to choose a level by risk profile — in the article “Risk-based KYC”.

Onboarding metrics in the personal account

  • Successful and rejected sessions

    The share of successful and rejected sessions for the chosen period and for each scenario, plus a daily trend: you can see how a change to the scenario affected the result.

  • Reasons for rejection

    The distribution of errors by type — for example, “fields not visible” or “screen / printout”. The first are fixed with prompts and a frame, the second point to attempted fraud.

  • Success by attempt

    How many sessions passed on the first, second, third attempt. If many pass only on the second, the customer lacks a prompt on the first frame.

Reports on all sessions — with filters by date, status, scenario, errors and recognised values, export to CSV.
Abandoned checks are visible as expired sessions, unfinished questionnaires — with the status “waiting”. Calculate the cost of an approved customer by the method from the article “KYC economics”.
The “Statistics” section in the documentation. How to link conversion and risk after launch — in the article “KYC for business: how to build a process with high conversion…”

The Unified Biometric System, ESIA and NeuroVision: who confirms identity and who checks the customer

Digital onboarding is a way to take a customer through a check, not a new way of identification. By law, identity is confirmed by state systems and the organisation itself; NeuroVision checks the document and the data and issues an outcome on which the company makes a decision.

  • Banks and other organisations supervised by the Bank of Russia may identify a customer without personal presence using ESIA and the Unified Biometric System (cl. 5.8, art. 7, 115‑FZ) The Unified Biometric System and ESIA
  • Simplified identification is carried out by one of the methods of cl. 1.12, art. 7, 115‑FZ: personal presentation of documents, sending details about oneself with their verification, signing in through ESIA Your companyThe Unified Biometric System and ESIA

  • Document recognition and anti-fraud: forgery, a photo of a screen, a printout, editing, logical mismatches NeuroVision

  • Database checks: passport validity, the list of terrorists and extremists, the wanted list, sanctions lists, foreign agents and others — from the catalogue NeuroVision
  • Matching the document against the questionnaire in the two-stage scenario, the session outcome with reasons for each step NeuroVision

  • Internal control rules, customer risk assessment, choice of check level Your company
  • Updating customer details: at least once every three years for low risk, at least once a year for the rest (subcl. 3, cl. 1, art. 7, 115‑FZ) Your company
  • This is a guide for a conversation with a lawyer, not a legal opinion. The wording of the norms is simplified; the exact text is in ConsultantPlus. How the Unified Biometric System works and where it is used — in the article “The Unified Biometric System”.
  • Processing of face images in KYC is regulated by art. 11 of 152‑FZ and by 572‑FZ — discuss the scenario with your lawyer.

Customer onboarding in different industries

The scenario steps are the same, while the set and order depend on the product: where there is money, there is a full check.

  • Banks and brokers

    • remote onboarding at a bank and an investment platform: a document, anti-fraud and database checks before opening a product
    • a questionnaire at registration, a full KYC before the first operation
    • international screening for foreign customers Learn more
    • Also: brokers and investment platforms
  • Microfinance, pawnshops and instalments

    • a passport with a validity check and the “16 in 1” package before issuing a loan
    • the acceptable-age rule
    • rejection on exhausted attempts — protection against brute-forcing Learn more
    • Also: pawnshops, instalments
  • Payment services and wallets

    • a questionnaire when opening a wallet
    • a full KYC on withdrawal or when the limit grows
    • matching the document against the questionnaire Learn more
  • Marketplaces and classifieds

    • checking a seller before the first sale: a document and self-employed status
    • a separate scenario for buyers with a large deal Learn more
    • Also: classifieds
  • Car sharing, rental and hiring

    • a driving licence and a check for deprivation of rights
    • for foreign workers — a patent, residence permit or temporary residence permit as an additional document Learn more
  • A service employee sets up a customer onboarding scenario in the personal account

How much onboarding one customer costs

The price is per KYC session: it includes all scenario steps and document anti-fraud, and retake attempts are not charged. No subscription fee.

  • Document

    from 16 ₽ per session

    Enable

    Document recognition and anti-fraud: a screen, a printout, a photocopy, a pasted-in photo, editing, logical mismatches. For the questionnaire and onboarding without a selfie.

  • Full onboarding

    Document + liveness

    from 29 ₽ per session

    Enable

    Everything in the “Document” package plus a selfie or liveness: comparing the face with the photo in the document and a liveness check. Use is at your lawyer’s decision (572‑FZ).

  • Extended

    on request

    Calculate

    A document, liveness and database checks in one session: 16 database checks for Russia and international screening.

An additional document in the same session — 10 ₽, database checks — 5 ₽, the “16 in 1” package — 50 ₽, international screening — 36 ₽. Image storage — 3 months free, then per the tariff. The price depends on volume: the calculator in the price matrix.

Connection: a widget, a link or the API

Web SDK

The widget is embedded in the registration page or opened in an app via WebView. The scenario is chosen by identifier, and the outcome comes to your backend.

How to embed the widget

Terms

  • Test access — 1 month
  • A cloud in Russia or installation in your perimeter
  • Tickets-based technical support

Onboarding glossary

Terms you meet in the account, the documentation and conversations with compliance.

Customer onboarding
The process of bringing a new customer on board: collecting data, checking documents and deciding whether to accept them for service.
customer onboarding
Digital onboarding
Onboarding without an office visit: the customer goes through all steps from a phone or a computer, and the checks run automatically.
digital onboarding
KYC session
One pass through a scenario by one customer. It includes all scenario steps and is paid as one check.
KYC session
Scenario
A set of steps, document types, countries, anti-fraud checks and rules that you build in the KYC editor.
scenario
Step
A part of a scenario: a document, a selfie, liveness, proof of address or a questionnaire. Each step gets up to 6 attempts.
step
Retake
Shooting a step again after a failed frame or a face mismatch. The response lists the steps that need to be retaken.
retake
Two-stage check
A questionnaire at registration and a full KYC later, with the document data matched against the questionnaire.
two-stage KYC
Callback
A notification the platform sends to your backend about the progress and outcome of a session.
callback, webhook
Manual review
An employee’s review of a session when the rules do not allow an automatic decision. The outcome is a manual status change.
manual review
Completion rate
How many customers who started a check reached an outcome. Abandoned sessions are visible as expired.
completion rate
Approval rate
How many completed sessions got a successful outcome.
approval rate
Simplified identification
A 115‑FZ procedure with a limited set of details for operations under cl. 1.11, art. 7 — for example, transfers up to 100,000 ₽. It is carried out by the methods of cl. 1.12.

Frequently asked questions about digital onboarding

It is bringing a new customer on board without an office visit: the customer fills in their details, photographs a document, takes a selfie or a liveness check if needed, and database checks run automatically. The company gets an outcome with reasons and decides by its own rules whether to accept the customer. Do not confuse it with adaptation onboarding, where a customer is taught to use a product.

Onboarding is the customer’s whole path before being accepted for service. KYC is the check inside it: the document, the data, the risks. Identification is the 115‑FZ procedure carried out by the organisation itself or by the Unified Biometric System with ESIA in cases set by law. NeuroVision provides the customer check and the outcome, and the identification method is chosen by your company.

Yes, the customer goes through the document and data check from a phone in the widget or by a link. Whether that is enough for your operation depends on the law: for example, banks identify a customer without personal presence through ESIA and the Unified Biometric System, and simplified identification allows its own methods. Agree the remote onboarding scenario with compliance.

Each step has up to 6 free capture attempts. If the last attempt fails, the session closes at once with a rejection. The number of allowed failed attempts and the threshold of critical errors before blocking are set in the scenario.

At registration the customer enters their full name and, if you enabled the field, their date of birth — with no documents or selfie. Later, for example before withdrawing money, you create a link to the full KYC and attach the questionnaire to it. The platform matches the document against the questionnaire: the name word by word allowing for spelling, the date exactly. The questionnaire accepts an age from 14 to 100 years.

For the most part — yes: the session outcome arrives automatically, and your system by its rules opens access or refuses. Manual review remains for the exceptions you define yourself — for example, a large application or a disputed database result. An employee views the session in the account and changes the status manually.

Remove from the first stage everything that can be postponed, use a two-stage scenario, rewrite the prompt and rejection screen texts for your product, and let the customer retake a frame. Then watch the rejection reasons and success by attempt in the dashboard — they show which step to fix first.

The platform recognises 16,000+ document types from 195+ countries and territories. The package includes one type — a passport, an ID card or a driving licence; each additional document in a session costs 10 ₽: a registration page, a residence permit, a temporary residence permit, a visa, a patent and others. The full list is in the documentation.

No, they are scenario steps and can be left out: the “Document” package works without a face. If the step is needed, it is included in the “Document + liveness” package from 29 ₽. Processing of face images is regulated by 152‑FZ and 572‑FZ — whether this step may be included in your process is decided by your lawyer.

The share of successful and rejected sessions for a period and by scenario, the distribution of errors by type, success by attempt and a daily trend. All sessions are available in reports with filters and export to CSV.

The price is per KYC session with all steps: “Document” — from 16 ₽, “Document + liveness” — from 29 ₽, the extended package with database checks — on request. For a quick pilot there is test access for 1 month and a demo; how to embed the widget — on the page verification on a website and in an app.

In the NeuroVision cloud on servers in Russia, or on your servers when installed in your perimeter. Original images in the cloud are stored for 3 months free, then per the tariff; the retention period of session data is set in the scenario. More on the page the KYC service in Russia.

Let’s discuss your onboarding scenario

Tell us whom you check and at which step you lose customers — we will suggest a scenario, check levels and a price per session estimate.

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.