The client photographs the document
The Web SDK shows a frame and prompts: remove the glare, move closer, turn the card over. Photos from a phone, scans and webcam frames in JPEG or PNG are suitable.
Foreign document recognition without manual entry: NeuroVision detects the country and type of the document on its own, extracts fields from a passport, ID card, residence permit or driving licence, reads the MRZ and returns the name in Latin letters. 16 000+ document types from 195+ countries and territories — in one API.
The model detects the country, type and side of the document on its own, so the client does not have to pick them from a list. 16 000+ document types from 195+ countries and territories are supported — including old and new specimens of the forms, service and diplomatic variants.
Ordinary and biometric passports, service and diplomatic, children's and temporary — the page with the photo and the MRZ and, for some countries, additional pages.
ID card recognition from both sides: the front — photo and data, the back — address, personal number and the MRZ, if there is one. Cards of the old and the new specimen.
Recognition of residence permits and temporary residence permits issued by other states, as well as documents of foreigners in Russia: a residence permit, a temporary residence permit (RVP), a refugee passport and a stateless person's document.
Licences of other countries, including national licences of individual states and provinces, and international driving permits. Both sides of the card.
Cyrillic, Latin, Arabic script and ideographs. Fields are returned as printed, and the name in Latin letters — from the machine-readable zone.
The list is updated regularly. If the document of your country is missing, the team will assess whether the model can be trained on it and an update released.
Data is extracted from an identity document field by field: for each field the service returns the value and the model's confidence level. The set of fields depends on the country and the type of the document — for example, many documents have no patronymic or address.
a passport or travel passport of another country; the page with the photo and the MRZ
a national identity card; front and back sides
a residence permit or a temporary residence permit — of a foreign state or issued in Russia
OCR of foreign documents works the same way as for a Russian passport: the client takes a photo, and in one request the system returns the fields, the MRZ and the statuses of the checks. A person gets involved only if the model is unsure about some field. How to connect: REST API and Web SDK.
JPEG or PNG. The document must take up enough of the frame: a document that is too small is rejected by the service with an error and the user is asked to retake the photo. HEIC, WEBP and PDF are not accepted.
The whole document, including the MRZ, is in the frame. Plastic ID cards and residence permits give glare under a lamp: shoot without flash, at an angle to the light. If the MRZ lines are not fully visible or the check digits do not match, an error is returned bad mrz checksum with a prompt to retake the photo.
For an ID card, a residence permit and a licence, part of the data and the MRZ are on the back. A second step is set in the verification flow: first the front, then the back.
By default the service is designed for a photo of the original: a scan, photocopy or printout may get an anti-fraud flag. If documents arrive as scans in your process, these checks are switched off in the flow.
Why users retake photos of documents · Recognition errors and prompts.
The machine-readable zone is built the same way in all countries that follow ICAO Doc 9303, so MRZ recognition works even where the visual zone is printed in an unfamiliar alphabet. The format depends on the size of the document: a passport has two lines of 44 characters, an ID card — three lines of 30, some residence permits and other documents — two lines of 36. The name in the MRZ is written in Latin letters only, without diacritics, and the surname is separated from the given name by two characters “<<”. The service reads the MRZ and recalculates the check digits; documents without an MRZ are recognised from the visual zone. How to recalculate the check digits — in the article on MRZ verification.
For matching and screening against lists, use the Latin letters from the MRZ, and for a contract — the spelling from the translation
The visual zone shows the name in the language of the country: in Cyrillic, in Latin letters with diacritics, in Arabic script or in ideographs. The service returns the field as it is printed.
In the machine-readable zone the name is written in Latin letters only, under the ICAO rules: letters with diacritics and national alphabets are rendered with Latin letters. This spelling is convenient for searching international lists and for matching against other documents.
The Russian spelling of a foreigner's full name is taken from the notarised translation of the passport or from documents issued in Russia. The service does not invent it: automatic transliteration from Latin letters may differ from the official translation.
Many countries have no patronymics, and in some documents the surname and the given name are written in one line. Federal Law 115-FZ requires the patronymic to be recorded “unless otherwise follows from the law or national custom” — the field will stay empty, and that is normal.
What you get. Data that an employee retyped.
An unfamiliar alphabet. The employee will not be able to read it.
Russian spelling of the full name. At the employee's discretion.
Data verification. By eye.
Where it is accepted. In the company's internal systems.
What you get. Document fields in JSON, the name in Latin letters from the MRZ, statuses of the checks.
An unfamiliar alphabet. Reads the fields and the MRZ.
Russian spelling of the full name. Does not produce it: returns it as printed and in Latin letters.
Data verification. MRZ check digits, validity period, traces of editing.
Where it is accepted. In the company's internal systems: questionnaire, CRM, banking system.
What you get. The text of the document in Russian with the notary's certification.
An unfamiliar alphabet. The translator translates everything.
Russian spelling of the full name. Yes, the official one.
Data verification. Does not verify the authenticity of the document.
Where it is accepted. In government bodies and wherever the law requires a translation.
Notarised translation is not our area. If your process requires a translation of a foreigner's passport, recognition will help at the step before it: it will fill in the questionnaire, check the document and show whom to check more carefully. The Russian spelling of the full name from the translation is then added to the client's record.
Anywhere clients or employees come with documents of other countries and the data is currently retyped by hand — with mistakes in Latin letters and dates. Brokers and investment platforms — checking non-resident clients.
The NeuroVision cloud operates in Russia
The NeuroVision cloud runs in data centres on the territory of the Russian Federation. Document images and recognised data are not sent to servers abroad.
Images do not leave your infrastructure
The service is deployed on your servers by NeuroVision specialists: document images stay within your perimeter.
Recognition in Russia does not create it
If you transfer clients' data abroad — for example, to a parent company — you must notify Roskomnadzor in advance under Art. 12 of Federal Law 152-FZ. Recognition in Russia does not create such a transfer.
Localisation requirements and general rules
The requirement to keep data in databases on the territory of Russia in Part 5 of Art. 18 of Federal Law 152-FZ is worded for Russian citizens. For foreigners, the general rules of processing and cross-border transfer apply.
The period is set in the flow
The retention period of session data is set in the flow settings, and the data can be destroyed at any moment with the method kyc/session/erase.
152‑FZ
a Russian developer, software in the registry, No. 19972
The same method as for a Russian passport: POST /v1/kyc/process. The response contains the document type with the country code, fields with the model's confidence and the statuses of the checks, including the MRZ. Description of the method in the API documentation.
The document image goes in the images field (up to 10 images, JPEG or PNG), the token — in the token header. There is no need to specify the type and country of the document.
Field docName contains the country code and the specimen of the form — for example, “UTO — Passport (2020)”, which is convenient for routing a request by flow. For the back of a card a separate result arrives with its own docName.
Inocr.fields— the name of the field (title, for example Surname or Document number), the value and the model's confidence level conf. Field names depend on the country and the type of the document; the list contains only those that are on the form.
In checks → fraud — the statuses of the image checks: isMRZValid (MRZ check digits), isEdited, isDisplay, isPrinted. If the image is unsuitable, an error arrives with a prompt to retake it.
Payment only for recognised documents, no subscription fee. Database checks are paid separately according to the catalogue. Test access — 1 month on your clients' documents.
Calculate the costForeigners' documents are recognised by the same integration as Russian ones: no separate method or separate contract is needed.
1 month of test access, a manager, ticket support, payment per document.
Short definitions of the terms from the API response and from the requirements for working with foreigners' documents.
Foreigners' document recognition is part of the client verification platform: the same models, infrastructure and security requirements.
NeuroVision — an expert in computer vision and AI
AI-OCR works as part of customer verification (KYC), trusted by the largest companies in fintech, e-commerce and transport services.
We develop identification algorithms that automate checks, detect fraud and help meet regulatory requirements.
Tell us which countries your clients and employees come from — we will check whether their documents are on the list and give you test access to the API and Web SDK for 1 month.
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.
How document recognition, MRZ and checking of international clients work — in our blog
Answers about document types, MRZ, checks, data storage and connection
Passports and travel passports, national ID cards, residence permits, temporary residence permits and driving licences — 16 000+ document types from 195+ countries and territories. The full list by country is published in the documentation.
From both sides: the front — photo and data, the back — address, personal number and the MRZ, if there is one. A second capture step is set in the Web SDK, and the service combines the data of both sides in one response.
Yes. The service recognises residence permits and temporary residence permits of other states, as well as foreigners' documents issued in Russia — according to the list in the documentation. The set of fields depends on the specimen of the document.
No. The service extracts the data as it is printed and returns the name in Latin letters from the MRZ. Notarised translation and the official Russian spelling of the full name are a separate service of a translator and a notary.
From the notarised translation of the passport or from documents issued in Russia. Automatic transliteration from Latin letters may differ from the official translation, so for matching and screening against lists use the Latin letters from the MRZ, and for a contract — the spelling from the translation.
No. The model detects the country, type and side of the document on its own. A type needs to be specified in the flow only if several documents of different types look almost the same.
Write to support. The team will assess whether the model can be trained on this document and will release an update; adding a new type takes time to collect data and retrain.
Yes. If there is no machine-readable zone — on old forms or in some documents — the fields are read from the visual zone. There are no MRZ check digits in this case.
Most often because of the photo: glare on the plastic of the card, a cropped MRZ, a document that is too small in the frame. The service returns an error with a prompt — for example, to retake the photo without glare — and the Web SDK helps to capture the document correctly the first time.
After recognition — the register of controlled persons of the Ministry of Internal Affairs (5 ₽) and compliance screening against PEP, sanctions lists and adverse media (36 ₽). By full name and date of birth, Russian lists are also available: the Rosfinmonitoring list, the Ministry of Internal Affairs wanted list, the Federal Penitentiary Service and the Federal Bailiff Service.
In Russia: in the NeuroVision cloud or on your servers with installation in your perimeter. Recognition does not transfer data abroad; if you transfer it abroad yourself, Roskomnadzor must be notified under Art. 12 of Federal Law 152-FZ.
Payment is for recognised documents, no subscription fee; database checks — according to the catalogue. The first month is a free trial. We will calculate the exact cost for your volume.