KYC for integrators: NeuroVision document recognition, liveness, AML and KYB checks and anti-fraud are built into your customers’ core banking systems, remote banking, 1C, CRM and ERP — as a widget under their brand or via REST API. You run the project; the NeuroVision team helps with the platform.
You do not need to assemble OCR, liveness and database checks from different vendors and bring them together in one interface: the session, the result and the log are in one platform.
Russian passports, foreign passports, driving licences and documents of 195+ countries and territories are recognised automatically; the recognised fields go to the customer’s system.
A check that a live person is in front of the camera, not a photo, a screen, a mask or a deepfake, and signs of document forgery — in one KYC session.
Rosfinmonitoring lists, OFAC, EU, UK and UN sanctions lists, passport validity; for legal entities — a counterparty check by tax ID (INN). The catalogue is on the page AML checks.
Anti-fraud signals and the recommended action are returned to the customer’s system before a payment is debited or access is opened. More — anti-fraud.
The check is placed where customer data first appears: in an application, a record, a contract or a registration window. The connection is through REST API and webhook; how it works is on the page KYC module for CRM, ERP and 1C.
Recognition, liveness and checks are connected to the customer’s system through a widget or REST API rather than developed from scratch. The integration time is estimated for each project.
NeuroVision trains and updates the recognition, liveness and anti-fraud models; your team works on integration, not on models.
The platform is listed in the Russian software registry (entry No. 19972) — customers’ procurement takes this into account. Information for the information security team is available on request.
The same API and widget in all projects; the scenario and design are configured in the editor separately for each customer.
The order of steps, documents and checks is configured in the scenario editor — the customer does not wait for a new version of your build.
NeuroVision handles questions about recognition, checks and API errors; you remain the first line for the customer. The support mode and channels are set in the contract.
Working formats and terms are on the page partner programme. Since August 2026 NeuroVision products in Russia have also been distributed by the IT distributor TERA — news of the agreement.
The scheme is chosen by who launches the check. A project often uses two: a widget for customers and a data-based check for the back office.
A typical project with a widget and database checks. For the data-based check scheme, steps 3 and 4 are combined.
Where the customer’s client is checked, which documents and databases are needed, who makes the decision and where the result is written — in core banking, 1C, CRM or ERP. The embedding scheme can be discussed with the NeuroVision team.
Steps, documents, liveness, database checks and the retention period of results are configured in the KYC editor without programming — a separate scenario per customer.
The widget is embedded with a script or an npm package, styled to the customer’s brand; for a data-based check — REST API calls from the customer’s system.
The customer’s server receives the session result, decrypts it and writes the fields, statuses and a link to the report to the customer’s or counterparty’s record.
Test access: the customer’s employees complete sessions on real documents, and you check statuses, retries and rejections.
Switching to production access, session monitoring in the account, reports in CSV. You are the first line for the customer; platform questions go to NeuroVision through the channels set in the contract.
Logo, colours, texts
The logo, colours, screen texts, languages and a light or dark theme are set in the scenario editor — no markup work on your side. About embedding the widget.
Your team builds the screens
If the widget does not fit, your team builds the screens: the platform returns the recognised fields, statuses and check results via the API.
Changed without a release
The order of steps, the set of documents and the hints to the customer’s client are configured separately for each customer and changed without a release.
The result — in core banking, 1C or CRM
The session result and check results are written to the customer’s core banking system, 1C or CRM; employees do not have to log in to the NeuroVision account.
Models and the document catalogue
The recognition, liveness and anti-fraud models, and updates to the document and database catalogue, stay on the platform side.
White label
The brand is the customer’s, the platform is NeuroVision’s
You are responsible to the customer for the project; NeuroVision helps with the platform. The scope of help is agreed at connection.
Help choosing the embedding scheme and building a scenario for the customer’s process: documents, checks, the order of steps.
You can show NeuroVision to the customer and support a pilot on their documents in test access.
The session log and API responses help explain recognition rejections, statuses and error codes.
Consultations on embedding the widget and receiving the webhook: parameters, session statuses, handling of retries and rejections.
The Russian software registry and data storage information — for the customer’s information security team, lawyers and procurement, on request.
The support mode and channels are set in the contract; 24/7 support is connected separately.
Public prices — so that you can include the checks in the estimate straight away. Payment is for completed checks, with no subscription fee.
from 16 ₽ per session
Document recognition, anti-fraud, machine-readable zone check.
from 29 ₽ per session
Everything from the “Document” package plus liveness on the customer’s device.
on request
A document, liveness and database checks in one scenario for the customer’s system.
Database checks — 5 ₽, international screening — 36 ₽, an additional document — 10 ₽. A check without the required data is not charged. Partnership formats and terms are on the page partner programme. A calculation for the estimate — the calculator in the price matrix.
A ready-made customer check that an integrator builds into the customer’s system instead of developing its own: NeuroVision document recognition, liveness, watchlist and sanctions checks, counterparty checks and anti-fraud are connected via a widget or REST API.
The time depends on the scheme: a data-based check requires REST API calls, a widget requires embedding a script and receiving a webhook, and the scenario, rejection handling and training the customer’s employees add work. The time is stated after a review of the customer’s process and the embedding scheme; you can start in test access.
Through REST API and webhook: your team writes a call from a record or on an event and writes the result to the customer’s system. Whether a ready-made module exists for a specific system, ask the manager — leave a request in the form. More — API and SDK.
Yes. Database checks are launched by full name, passport or tax ID (INN) from core banking, 1C or CRM; the result arrives asynchronously — by the run ID. Document recognition and liveness require a photo and the customer’s participation.
The logo, colours, screen texts, languages and theme of the widget are configured for the customer; when working through REST API the interface is entirely yours, and the result is written to the customer’s system. Partnership formats and resale terms are on the partner programme page.
The operator is the customer. NeuroVision and the integrator, if it gets access to the data, process it on the customer’s instruction (part 3, art. 6 of 152‑FZ). The detailed role scheme is on the partner programme page.
The result retention period is set in the scenario — in days, zero means indefinite storage — or is determined by the contract. The session’s personal data can be destroyed through the API. The webhook can send only the result, without personal data.
This is processing of biometric personal data: the customer needs the client’s written consent (art. 11 of 152‑FZ). Organisations can identify a person by biometrics without personal presence through the UBS (cl. 1, part 1, art. 15 of 572‑FZ) — more for banks.
The agent format suits those who recommend NeuroVision to clients without implementation — on the partner programme page. You can leave a request here too — we will pass it to the partner manager.
Tell us which systems you implement and what customer verification task the customer faces. We will propose an embedding scheme and discuss test access.
Can't put your request into words? Book a call and our team will contact you at a convenient time
Book a callThe 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.
