A citizen’s passport, application and handwritten form become ready-made fields in your system — the operator checks only doubtful values. NeuroVision runs inside the agency’s secure perimeter without internet access, or in a cloud in Russia, and the platform is included in the Russian software registry.
Data stays in Russia or within your perimeter · Russian software registry no. 19972 · Rospatent certificate no. 2023661508
ID documents are recognised straight away — the models are already trained. Applications, forms and certificates of your agency are recognised using a form template, which the NeuroVision team configures on your samples.
Documents that the agency obtains through an interdepartmental request do not have to be brought by the citizen — recognition is needed for what the citizen brings in person.
The list of ID documents is in the documentation: recognised documents by country.
Recognised straight away, no configuration.
Recognised using the template of your form.
We check them on your samples before the contract.
For example, the Ministry of Internal Affairs regulation on issuing a passport: where technically possible, the application at the multifunctional centre (MFC) is filled in by software that recognises machine-readable information
The operator types the passport data and registration address field by field, and a handwritten application in full. While they type, the queue stands still. With recognition, the fields arrive ready, and the operator checks them against the document.
An error in a passport number or date of birth goes into the agency’s system and into the interdepartmental request. The response “information not found” sends the citizen back for another visit. Per-field confidence shows where the operator should check.
Applicant details are needed in the intake system, in the electronic case file and in reporting. Every retyping is another chance to make a mistake. Recognised fields are passed through the API to all systems in a single JSON.
Applications from previous years sit in folders and cannot be searched. Batch processing of scans turns the archive into data — within the agency’s perimeter, with no transfer outside.
Entry in the Russian software registry no. 19972 of 13.11.2023 and Rospatent certificate no. 2023661508. A licence agreement — rights to a component of your system. Installation in your perimeter, operation without internet after installation. Updates — by agreement, in your window and through your channel. A description of the architecture and components for the threat model.
The threat model, security class and GIS certification under FSTEC Order No. 117. The operating system, information protection tools and server cryptographic protection. ESIA, SMEV and interdepartmental requests. The decision on the service and verification of the representative’s authority. Connecting recognised fields to your system via the API.
An FSTEC certificate for the platform — to be confirmed. Compatibility with specific Russian operating systems — to be confirmed. Integration with ESIA, SMEV, the Unified Portal of Public Services (EPGU) and the Unified Biometric System (EBS). Citizen identification and biometrics. Ready-made modules for MFC automated systems and electronic document management systems.
Recognition is a component of your system, not a separate GIS. The agency is responsible for protecting and certifying the system as a whole; NeuroVision is responsible for making sure a citizen’s document arrives in it as ready-made fields. How exchange via SMEV 4 works at banks — PODD agent for the Anti-fraud GIS: NeuroVision does not install the agent.
The set of features is the same — what changes are the input documents and where the fields go. For public-sector integrators, recognition is embedded in their solution as a component.
The document is scanned or photographed at the intake counter — the system receives the fields, a confidence level for each, and the authenticity check result. The decision on the application is made by an agency specialist.
The photo spread and the registration pages are recognised in a single session: full name, date of birth, series and number, issuing authority and date of issue, address. Handwritten notes on the registration pages are recognised too.
Most often enabled:
An application on the agency’s form, filled in in block letters, is recognised using the form template: full name, dates, addresses, amounts, checkbox marks, presence of a signature. The template is configured by the NeuroVision team on your samples.
Most often enabled:
Forms, questionnaires and certificates on official forms — on the same principle: one form, one template. The free text of an appeal is recognised as text, without interpreting its meaning.
Most often enabled:
Passports of 195+ countries and territories, residence permits and temporary residence permits. The name in Latin letters comes from the machine-readable zone with check-digit verification.
Most often enabled:
Anti-fraud flags a photo of a screen, a photocopy, a pasted-in photograph, erasures and traces of a graphics editor. For scans from the archive, photocopy checks are switched off in the scenario.
Most often enabled:
A confidence level is returned for every value. The agency itself defines which fields to accept automatically and which to send to a specialist for checking in its own system.
Most often enabled:
The specialist does not type the applicant’s data — they check the ready-made fields against the document. The citizen still presents the document in person if the service regulations require it.
The specialist places the passport and application on the scanner or photographs them with the workstation camera. Scans are sent via the API, camera images via the Web SDK, which warns if an image is blurred or the document is covered by a hand.
The fields of the passport and application are recognised, the MRZ of a foreign passport is verified, and anti-fraud flags a photocopy or a photo of a screen. Doubtful fields are marked with a confidence level.
The agency system receives JSON via the API and fills in the applicant’s record. The specialist checks the highlighted fields; next come interdepartmental requests and the decision on the service, handled by the agency’s own means.
A procedure that settles the main information security and procurement questions before the contract. The timescales depend on the number of forms and the perimeter requirements — we will name them after analysing the task.
Collect several anonymised samples of each form: passports, applications, certificates. Mark which fields are needed in the system and how the form is filled in — by hand or on a computer.
ID documents are checked straight away; a template is configured for applications. The result is a report on every field: what is recognised confidently and what goes to a specialist.
The information security service decides where recognition will run: in the agency’s perimeter or in a cloud in Russia. NeuroVision provides a description of components, ports and data flows for the threat model.
A licence for on-premises installation or a cloud service — under 44-FZ or 223-FZ. The bid includes the entry number in the Russian software registry.
NeuroVision engineers install the platform on your servers under your access regulations. The integrator connects the API to the intake system.
Specialists check only the highlighted fields. New model versions are installed in the agreed window after verification on your test environment.
Government Decree No. 1875, from 1 January 2025
For software procured under 44-FZ, foreign software is barred from admission unless it is in the registry of Russian or Eurasian software. The participant confirms origin with the registry entry number in the bid. NeuroVision — entry no. 19972 of 13.11.2023.
Determined by the customer
For programs and licences, group 58.29 “Software” is usually applied — the prohibition covers it. If access to a cloud is procured as a service, the code and procedure are clarified by the customer. The exact name is taken from the Catalogue of Goods, Works and Services (KTRU).
Own procurement regulation
State companies and state corporations procure under their procurement regulation. The registry entry number is useful here too: requirements for the origin of software are set by the customer.
What exactly you are buying
On-premises installation — a platform licence under a licence agreement, priced per project. Cloud in Russia — payment for completed checks, no subscription fee. Both models are the same domestic document recognition platform.
What we will provide
A commercial proposal to justify the initial price, the registry entry number and the Rospatent certificate, a description of functions for the technical specification. Closing documents — at the end of the reporting period.
19972
Entry in the Russian software registry
Recognition of a citizen’s document — in the package, per session. For state companies — counterparty checks and sanctions lists at 5 ₽ per request. Descriptions and response fields — in the API documentation.
Documents at intake
Recognition and anti-fraud in one session.
A passport and an international passport are recognised from a photo or scan: the fields arrive as a JSON response in your system.
from 16 ₽ per session
Learn moreRegistration pages, a residence permit, a temporary residence permit and a driving licence — in the same session.
10 ₽
Learn moreApplications in block letters are recognised using your form template, with a confidence level for each field.
on request
Learn moreA photo of a screen, a photocopy, a pasted-in photograph and traces of editing are flagged in the same session.
in the package
Learn moreFor state companies and state corporations
Checking suppliers and partners, not citizens at intake.
The director, founders and sole proprietors are checked by taxpayer ID (INN): bankruptcy, arbitration cases, tax debts, related companies.
5 ₽ per register
Learn moreScreening against the consolidated lists of OFAC (USA), the European Union, the United Kingdom and the UN. Every match carries a similarity score and a flag if it was triggered by an alias.
5 ₽ / check
Learn moreInternational screening against politically exposed persons and their associates, sanctions lists from more than 50 countries, regulatory actions and adverse media coverage. For Russian citizens it runs from the international passport or from the full name and date of birth.
36 ₽ / check
Learn moreHow the fields get into the system
Without a recognition module of your own.
The system sends an image and receives JSON: fields, confidence level, anti-fraud result.
in the package
Learn moreA capture interface in the workstation browser: it warns if an image is blurred or the document is covered by a hand.
in the package
Learn moreThe platform on the agency’s servers: citizens’ documents and results stay within your perimeter.
licence, on request
Learn moreIn the cloud — payment for recognised documents, no subscription fee. On-premises — a licence for your volume and number of forms. We will prepare a commercial proposal to justify the initial price for your procurement.
A Russian passport, international passport or foreign national’s document, MRZ and document anti-fraud. At 10,000 applicants a year — 18 ₽. Registration, residence permit, temporary residence permit — +10 ₽ per document.
on request
Template configuration for the agency’s forms, handwritten fields in block letters, confidence for every field.
licence, per project
The platform on your servers, operation without internet, updates by agreement.
The retention period for images in the cloud is set in the scenario and the contract; on-premises, you determine the periods. ID document prices are on the pricing page.
For GIS and systems with citizens’ personal data — installation on your servers. For a pilot and for institutions without their own infrastructure — a cloud on servers in Russia. A detailed comparison and server requirements are on the page about KYC services in Russia.
In the cloud — 1 month, for on-premises — by agreement. Support via a ticketing system, with the service level set out in the contract.
KYC for the public sector is not about identifying citizens, but about an applicant’s document that is recognised once and then lives in the system without retyping.
A passport, application and certificate are recognised at intake or from the archive. Fields, confidence level and authenticity check go to the agency system via the API.
There is no need to assemble a solution from several vendors and reconcile their responses.
Terms you meet when choosing document recognition for an agency, an MFC or a state company.
Document recognition, handwriting and data protection — in our blog.
Yes, as a component of your intake system. Passports, registration pages, foreign nationals’ documents and applications on your forms are recognised into ready-made fields, and the specialist checks only doubtful values. Applicant identification, interdepartmental requests and the decision on the service are carried out by the agency by its own means.
Yes, if the fields are filled in in block letters — in boxes or on the lines of the form. A template is configured for each form on your samples, and a confidence level is returned for each field. We check cursive handwriting on your samples before the contract.
Yes. The platform is installed on your servers, and after installation recognition works locally. Access to an external network is needed only for updates, which can be installed in an agreed window.
Yes. The computer vision platform “Neurovision” is included in the Russian software registry, entry no. 19972 of 13.11.2023, and is registered with Rospatent, certificate no. 2023661508. The entry number is stated in the procurement bid.
From 1 January 2025, the national regime applies to software procurement under Government Decree No. 1875: the bid states the registry entry number. The OKPD2 code and the description of the procurement object are determined by the customer; to justify the initial price we will prepare a commercial proposal. Under 223-FZ, state companies procure under their own procurement regulation.
No. NeuroVision recognises documents that a citizen brings or sends and passes the fields to your system via the API. The agency connects to ESIA, SMEV and the Unified Portal of Public Services (EPGU) by its own means or through an integrator.
No. Biometric identification of citizens in Russia goes through the Unified Biometric System, and NeuroVision does not replace it. On this page we work only with documents.
On-premises — only on your servers. In the cloud — on servers in Russia: the retention period for images is set in the scenario and the contract, and the data can be destroyed at any time. In both options there is no cross-border transfer.
Yes. The director, founders and sole proprietors can be checked by taxpayer ID (INN) — 5 ₽ per registry, OFAC, EU, UK and UN sanctions lists — 5 ₽, international compliance screening — 36 ₽. This is a separate scenario, unrelated to citizen intake.
ID documents in the cloud — from 16 ₽ per session, at 10,000 applicants a year — 18 ₽. Applications by template and on-premises installation are priced per project. A test on your samples — 1 month in the cloud; for on-premises — by agreement.
Tell us which documents you receive, how many applicants a day, and where the system should run — in your perimeter or in the cloud. Send anonymised samples of forms — we will show how they are recognised. Do not attach documents with citizens’ real personal data — blank forms or anonymised samples are enough.
Can't put your request into words? Book a call and our team will contact you at a convenient time
Book a callThe company is included in the register of IT companies and the register of personal data operators of the Russian Ministry of Digital Development.
Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.
