The applicant's passport goes into the certificate application without manual entry, a forged document is caught before issue, SNILS and INN are matched in advance. For simple and unqualified signatures — a selfie, Liveness and an evidential record of who signed.
Cloud in Russia or your own perimeter · Register of Russian software No. 19972 · Rospatent certificate No. 2023661508
For a qualified signature, the law lists the identification methods and the applicant's documents. For simple and unqualified signatures, the rules are set by the agreement of the parties and by the certification authority itself. This is a guide for a lawyer, not an opinion.
An accredited certification authority issues a certificate only after identifying the applicant.
Equal to a handwritten one if the parties or the law so decide.
Identification is set by the rules of the certification authority, the face — under 572‑FZ and 152‑FZ.
Passport authenticity, SNILS and INN matching and a record of every check — in one session
With a certificate in the victim's name, a fraudster signs applications to government bodies, powers of attorney, loan agreements and documents on changing a company's head. The victim learns of it when the debt or the transaction has already taken place.
The passport holder disputes the certificate and demands compensation for losses. The certification authority proves that it identified the applicant under the rules — copies of documents, check results and the issue log become the main evidence.
An operator transfers the passport, SNILS and INN into the application field by field. A typo fails the SMEV match, and the applicant is asked to come in again. Recognised fields and a preliminary SNILS and INN match remove the repeat visit.
Authorised agents and partner offices check a passport in different ways. A single verification scenario at all points means one level of protection and one entry in the log.
The set of checks is common; what changes is the type of signature and the moment when the person is checked: when the certificate is issued or at every signing.
One session — one person: document, database checks and, if needed, the face. The decision to issue a certificate or to admit to signing is yours.
A Russian passport spread, the registration page, a foreign passport, a residence permit and documents of foreigners from 195+ countries and territories are recognised in one session. Full name, date of birth, series and number, issuing authority and date — as ready fields.
Most often enabled:
Anti-fraud flags a photo of a screen, a photocopy, a printout, a pasted-in photograph, erasures, traces of a graphics editor and signs of AI generation.
Most often enabled:
INN by passport series and number, matching of full name and SNILS, passport validity. A discrepancy is visible at once, while the applicant is present, not after the interagency match refuses.
Most often enabled:
The list of terrorists and extremists, sanctions lists, Ministry of Internal Affairs and FSSP wanted lists — at the decision of your security service before issue.
Most often enabled:
For unqualified and simple signatures and for in-person issue at authorised agents: a live person in front of the camera and a face that matches the passport photo.
Most often enabled:
Images, recognised fields, check results and the time of each step are saved in the session. Export — into your applicant file for a dispute and for audit.
Most often enabled:
The applicant uploads documents in advance — at home or with an authorised agent. At the visit, what remains is establishing identity and signing the certificate.
The applicant photographs the passport in the Web SDK on the certification authority's website or in a mobile app (the widget is embedded through WebView). Prompts help to capture the spread without glare; SNILS and INN are entered or attached.
The passport fields are recognised, anti-fraud checks the document, INN by passport and the “full name — SNILS” pair are matched against databases. Discrepancies are highlighted before the visit.
The certification authority's system receives the fields and check results through the API. An employee compares the passport with the applicant, and the certificate is issued after the information is confirmed as required by law.
A signature in someone else's name begins with a forged or someone else's passport. Some schemes are visible from the document image itself; the rest are covered by database checks and your security service's decision.
The applicant brings or sends another person's passport — lost, bought or obtained by deception. A passport validity check and, for remote scenarios, comparing the face with the passport photo weed it out before issue.
Instead of a document — a screenshot, a printout or a photocopy with a substituted field. Anti-fraud flags such images, and the employee gets a reason, not just a “refusal”.
A person is talked into obtaining a signature “for money” — later documents are signed in their name. Lists, wanted persons and repeated passports in your applications are a signal for the security service.
In a remote face check, a fraudster substitutes a video, a mask or a virtual camera. Liveness checks live presence, and deepfake signs are a separate layer. In detail — deepfake protection.
For contracts, offers, consents and acts with individuals where a qualified signature is not needed but the signatory must be known. A simple signature is equal to a handwritten one if the agreement of the parties or the law so provides — Arts. 6 and 9 of 63‑FZ.
The signatory opens the contract, photographs the passport, takes a selfie and goes through Liveness. The details in the contract are matched with the passport, the face — with the photo in the document.
Sanctions lists, the list of terrorists and extremists, wanted persons, debts and bankruptcy — automatically in the signing process, by the set you have chosen.
A session log with timestamps, check results and cryptographic document hashes: a verifiable history of who signed, when and how.
Signing — from 20 ₽ per document, integration — 250,000 ₽ one-off. Embedded in a website, personal account and mobile app through the REST API and Web SDK. More about NeuroSign.
Recognition of passports and foreigners' documents. Document anti-fraud. INN by passport, full name and SNILS, passport validity, lists and wanted persons. Selfie, Liveness and face comparison for unqualified and simple signatures. Session log. Signing with NeuroSign. Cloud in Russia or installation in your perimeter.
Identifying the applicant under Art. 18 and the decision to issue. Confirming information through SMEV and ESIA. Connection to the Unified Biometric System and issuing a cryptographic tool for remote biometrics. Creating keys and the certificate, familiarising the applicant. Storing documents under the accreditation rules.
Issuing certificates and the functions of a certification authority. Identification for a qualified signature by selfie. Connection to the Unified Biometric System and ESIA, replacing them. Reading the foreign passport chip. Cryptographic protection tools.
NeuroVision checks strengthen identification but do not replace it: the law names the methods, and responsibility for issue remains with the certification authority. We cover remote identification under 115‑FZ on a separate page.
Document and anti-fraud — in a per-session package, the face — in the “Document + Liveness” package, database checks — 5 ₽ each.
Document at the entrance
The spread and the registration page are recognised in one session: fields arrive as a JSON response in your system.
from 16 ₽ per session
Learn morePassports of 195+ countries and territories, residence permits and temporary residence permits — with a check of the machine-readable zone check digits.
in the package / +10 ₽
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 moreA live person in front of the camera and a face matching the passport photo — for unqualified and simple signatures.
from 29 ₽ per session
Learn moreBefore sending to SMEV
Determining the tax number from the passport data. It unlocks the checks that need precise identification of the person — with no namesakes.
5 ₽
Learn moreChecking the social insurance number against the full name and date of birth: does the number really belong to this person. The answer is a match or no match.
5 ₽
Learn moreThe authenticity and validity of a Russian passport through the interagency interaction system. It catches expired, replaced, lost and invalid documents and verifies that the passport was issued to this particular person.
5 ₽
Learn moreScreening against the list of persons involved in extremist activity or terrorism. A mandatory check under 115‑FZ.
5 ₽
Learn moreHow the check is built into issue and signing
Signing with a simple signature: passport, selfie, Liveness, database checks and an audit trail.
from 20 ₽ per document
Learn moreAn interface for capturing the passport, selfie and Liveness in the browser; embedded in a mobile app through WebView.
in the package
Learn moreThe certification authority's system sends images and receives JSON: document fields, the anti-fraud result, database checks.
in the package
Learn moreThe platform on the certification authority's servers: documents and results stay within your perimeter.
on request
Learn morePayment for completed checks, no subscription fee. Database checks are added to any plan at 5 ₽ each.
from 16 ₽ per session
Passport recognition and document anti-fraud. At 10,000 applicants a year — 18 ₽.
Everything in “Document” plus a selfie or Liveness and comparison of the face with the passport photo — for UES and remote scenarios.
from 20 ₽ per document
Signing with identity confirmation and an audit trail; integration — 250,000 ₽ one-off.
INN by passport, full name and SNILS, passport validity, lists — 5 ₽ each. The image retention period is set in the scenario. All prices — on the pricing page.
The check is built into the certification authority's website, personal account, mobile app and authorised agent's workstation.
A test scenario on your account. Support — under the contract; round-the-clock mode is connected separately.
One platform for all issue paths and for signing without a visit.
The passport is recognised, the document is checked, SNILS and INN are matched, and for remote scenarios — a live person in front of the camera. All of this is recorded in the session.
There is no need to assemble a solution from several vendors and reconcile their responses.
Passport checks, Liveness and the Unified Biometric System — in our blog.
No. For a QES the law names four identification methods: in person, by a valid qualified signature, by a foreign passport with an electronic data carrier, or through ESIA and the Unified Biometric System. NeuroVision strengthens each of them: it recognises the passport, checks its authenticity and matches SNILS and INN.
The passport, SNILS and INN go into the application without manual entry, anti-fraud flags a forged or altered passport, and matching INN and SNILS against databases removes refusals at the SMEV check. At all issue points — one scenario and one log.
Yes, if your certification authority's rules or the agreement with the client provide for it. A passport, a selfie, Liveness and comparison of the face with the passport photo confirm that the certificate is received by the document holder. Agree consent to processing the face image and the restrictions of 572‑FZ with a lawyer before launch.
A service for signing documents with a simple electronic signature with identity confirmation: passport, selfie, Liveness, database checks and an audit trail with document hashes. NeuroSign: signing — from 20 ₽ per document.
Yes, if the parties have concluded an agreement recognising a simple signature — usually an offer or a user agreement in the signing process. The audit trail records who signed, when and how. For documents where the law requires a qualified signature, an SES is not suitable.
No, NeuroVision does not connect to the Unified Biometric System: the connection and the cryptographic tool for the applicant are provided by the certification authority. Before the transition to the system, NeuroVision recognises the passport, checks the document and matches SNILS and INN.
Yes. INN by passport series and number and the match of full name and SNILS are checked at 5 ₽ each. Official confirmation of the information through SMEV remains with the certification authority.
Yes, passports of 195+ countries and territories, residence permits and temporary residence permits, with a check of the machine-readable zone check digits.
No. 115‑FZ regulates identification of customers of banks and other organisations, while the issue of a signature is governed by Law 63‑FZ. We cover remote identification under 115‑FZ on a separate page.
In the NeuroVision cloud on servers in Russia; the image retention period is set in the scenario. With installation in the perimeter of the certification authority — only on your servers.
The Web SDK is embedded in a website and in a mobile app through WebView, the REST API — in the certification authority's system. A test — in the test scenario on your account.
Remote notarial actions go through the notary system, and NeuroVision does not replace it. For checking a notary's customers under 115‑FZ — a separate page.
Tell us which signatures you issue or use, how many applicants a month and where the check takes place — in the office, with authorised agents or online. We will show a scenario on your flow.
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.
