Passenger transport: from a passport to a named ticket and a boarding list without manual entry

Q: How does passenger passport recognition work?

A clerk, passenger or driver photographs the document; the service returns the full name, date of birth, document type and number, gender and citizenship with a confidence level for each field. Your ticketing system fills them into the ticket.

Q: Why recognise a passport if a clerk can type it?

A named ticket, the passenger database and the trip list are built on one line. A typo in a surname or number surfaces at boarding: under the carriage rules a passenger with mismatching data on a bus is treated as travelling without a ticket.

Q: Does NeuroVision submit data to the ACBPDP?

No. The carrier, or whoever issues tickets on its behalf, does this with its own system. NeuroVision provides the document fields for it: full name, date of birth, document type and number, gender and citizenship.

Q: Which passenger documents are recognised?

A Russian passport, an international passport, a driving licence, ID cards, passports of 195+ countries and territories, a residence permit and a temporary residence permit — over 16 000 types in all. A foreigner’s name is taken from the machine-readable zone.

Q: Can a document be recognised on a self-service kiosk?

Yes. The Web SDK works in the kiosk browser with its camera: it prompts the passenger how to photograph the document and returns the fields to your system.

Q: How can a driver check a document at an intermediate stop?

The driver photographs the document with a phone in the carrier’s app with the NeuroVision SDK. Your system matches the full name and number against the trip list; the driver compares the face with the document photo personally.

Q: Can passengers board by face?

At Sheremetyevo and Pulkovo airports an experiment with boarding by biometrics from the Unified Biometric System is under way; in chartered bus carriage the charter agreement may provide such a procedure. NeuroVision does not do boarding by face and does not keep a database of passenger faces. For face passage through security or the UBS, see the turnstiles page.

Q: Does the service flag a forged document at an online purchase?

Yes. Antifraud flags a photo of a document from a screen, a printout, a pasted-in photo, erasures and traces of a graphics editor. The validity of a Russian passport can be checked against the Ministry of Internal Affairs database — 5 ₽.

Q: Is recognition suitable for chartered and shift-worker trips?

Yes. The passenger list is built from document photos — one by one or in a batch through the API — and at boarding it is matched against each passenger’s document.

Q: How much does passenger document recognition cost?

From 16 ₽ per session; at 10 000 documents a year — 18 ₽. A second document in a session — 10 ₽, database checks — 5 ₽. There is no subscription fee.

Ticket clerks, online agents and drivers at intermediate stops no longer retype passports. A document photo becomes a full name, date of birth, document type and number — for the ticket and for your system to pass into the passenger database.

Try it for free What the rules require

Passenger passport recognised: named ticket fields and the trip list

30 minutes to submit bus passenger data to the ACBPDP

20 types of documents accepted for long-distance train tickets

195+ countries and territories: passports of foreign passengers

< 1 s document recognition

The document with no manual entry Fields for the ticket and the ACBPDP Document anti-fraud Passport validity Liveness and selfie match

Data stored in Russia · Russian software registry no. 19972 · 152‑FZ

A named travel document: what carriage rules and the transport security law require

On long-distance routes the ticket is issued to a specific person: it carries the full name, date of birth and the number of the document it was bought with. The carrier and its agent pass the same details to passenger databases.
The less manual entry between the document and the ticket, the fewer passengers argue with the inspector at boarding.

Long-distance bus

Government Resolution No. 1586, items 64, 65, 74, Annex 1

Passport recognition
A named ticket
- Passenger full name and date of birth
- Type and number of the document the ticket was bought with
Boarding
- With an electronic named ticket, an identity document is enough
- If the surname or document number does not match the ticket, the passenger is treated as travelling without a ticket
Chartered trip
- Passenger identification procedure — set in the charter agreement
- By documents or through the Unified Biometric System
- If the law requires a passenger list, boarding follows the list
Long-distance train

Ministry of Transport Order No. 352, items 15, 16, 22, 79, 81

Foreign documents
Ticket issue
- Based on the identity document details
- From a list of 20 types: Russian passport, international passport, foreign passport, residence permit and others
What the ticket shows
- Full name, date of birth, citizenship, gender
- Passenger document number
Boarding
- The ticket and the document it was issued against
- One typo in the name and one in the document number do not stop the journey
Passenger databases

Federal Law 16‑FZ, Art. 11; Ministry of Transport Order No. 162

OCR API
Which transport
- Air
- Long-distance rail
- Bus and water — international and interregional
What is transmitted
- Full name, date of birth, document type and number
- Departure and destination points, travel date
- Gender and citizenship
Who and when
- Carriers and those who issue tickets on their behalf
- Plane and train — 15 minutes after the transaction
- Bus and vessel — 30 minutes

Passenger data from the ticket office to boarding: twenty control points across sales channels

It is cheaper to catch an error at the point of sale than on the platform five minutes before departure. The tag shows who closes each line.

Passport spread or ID card recognised from the ticket office scanner or camera — no typing NeuroVision
Full name, date of birth, document type and number are filled into the ticket Your system
Foreign passport — name in Latin letters from the machine-readable zone with check-digit validation NeuroVision
Doubtful fields are highlighted with a confidence level — the clerk reviews only those NeuroVision
The document goes straight back to the passenger; the image is stored for the period set in the scenario Your system

The passenger photographs the document with a phone instead of typing 10 digits NeuroVision
Capture hints: glare, blur, cropped edge NeuroVision
Photo of a screen, printout, pasted-in photo and edits are flagged NeuroVision
A document from the list allowed for this type of transport Your system
Regular passenger account — Liveness and a one-time selfie match with the document photo NeuroVision

Gender and citizenship are taken from the document, not from the buyer’s words NeuroVision
Russian passport is valid per the MVD database NeuroVision
Passenger details submitted to the passenger database on time Your system
A repeat sale for the same document and trip — visible in your system Your system
Consent and the passenger personal data processing policy Your system

The driver photographs the document with a phone at an intermediate stop NeuroVision
Full name and document number checked against the trip passenger list Your system
The passenger’s face is compared with the document photo — by the inspector’s eyes Inspector or driver
A chartered trip passenger — on the list under the charter agreement Your system
The boarding decision — with the carrier Inspector or driver

NeuroVision — the line is closed by NeuroVision: document recognition, antifraud, passport check against the Ministry of Internal Affairs database, Liveness and selfie match
Your system — your ticketing system logic: filling in the ticket, passing data to the passenger database, the trip list, consent
Inspector or driver — a human decision: the inspector or driver compares the face with the document photo, the carrier decides on boarding

Intercity buses, bus stations, chartered trips and river vessels: who recognises what

The passenger document is the same, but the place where it is entered differs for each.

Interregional bus carrier
- A named ticket for an interregional trip
- The driver checks the document at intermediate stops
- Data goes to the passenger database within 30 minutes
Bus station and bus stop
- Ticket offices and self-service kiosks for dozens of carriers
- Queue before departure — without typing the passport
- Foreign passports — 195+ countries and territories
Chartered transport
- Shift-workers’, corporate and tour buses
- A passenger list built from document photos, not from a spreadsheet
- Identification procedure — under the charter agreement
River and sea carriers
- Trips between ports in different regions
- A cruise cabin and ticket — tied to the passenger’s document
- Group boarding — by list, without manual entry
Drivers and crew
- Driving licence and licence deprivation — against the traffic police database
- Wanted lists and the register of controlled foreign persons
- More on driver checks — on the transport hub

From a passport photo to boarding: how passenger data moves through the ticket and the trip list

The document is entered once — at the sale. After that the same fields travel to the ticket, the passenger database and the trip list.

Step 1

Document photo

The clerk puts the passport under the ticket office camera; an online passenger photographs it with a phone. A hint asks for a retake if the document has glare or is cropped.

A clerk photographs a passenger’s passport with the ticket office camera

Step 2

Fields into the ticket

Within a second you receive the full name, date of birth, document type and number, gender and citizenship with a confidence level. Your system issues the ticket and passes the data to the passenger database.

Full name, date of birth and document number filled into the ticket

Step 3

Check at boarding

The driver or inspector photographs the document with a phone. Your system matches the full name and number against the trip list; the inspector compares the face with the document photo personally.

A driver checks a passenger’s document against the trip list

A typo in a surname or passport number: where manual entry lets the carrier down at boarding

Three deadlines a carrier knows

The ticket, the passenger database and the trip list are built on a single line the clerk typed by hand. The error shows up only at boarding — when it is too late to fix.

01
A passenger “without a ticket”

On a long-distance bus a passenger whose ticket has a surname or document number that does not match the passport is treated under the carriage rules as travelling without a ticket. The dispute with the driver happens at the bus door.
02
Wrong data in the database

Passenger details go to the database 15–30 minutes after the sale. A typo then has to be corrected after transmission — as a separate operation.
03
Queue at the ticket office

Before departure passengers for several trips stand at the ticket office. Typing a passport and rechecking the digits is the longest part of a sale.
04
Foreign passenger

A name in Latin letters is copied by ear, similar letters get mixed up. The machine-readable zone gives the name and document number without the clerk transliterating.

15 minutes to submit plane and train passenger data to the database
30 minutes for buses and vessels
7 years is how long the passenger database keeps the data

Ticket office, kiosk, website or a driver’s phone: where to recognise the passenger document

One platform across all sales channels: the clerk, the passenger and the driver get the same fields, and your system gets one response format.

Bus station ticket office

Workstation scanner or camera: a passport spread — into the ticket fields.

The clerk checks only the highlighted fields and hands the document back.
- REST API · Web SDK
Self-service kiosk

The kiosk camera photographs the document, prompts guide the passenger.

No clerk: the ticket is issued once all fields are recognised with confidence.
- Web SDK
Website and app

A phone photo of the document instead of typing the number by hand.

Anti-fraud flags a photo of a screen and edits before payment.
- iOS and Android SDK · Web SDK
Driver’s phone

A document photo at the stop — the full name and number in the driver’s app.

Match against the trip list — in your system, the decision — with the driver.
- iOS and Android SDK

Boarding by face — only through the UBS: what a carrier does without a biometric database

Airports: the UBS experiment

How it works. From 1 June 2026 to 1 April 2027 at Sheremetyevo and Pulkovo you can check in for a domestic flight and board using biometrics from the Unified Biometric System — voluntarily.

What remains. The passenger shows the passport at security screening.
Chartered bus

How it works. The procedure for identifying passengers on a chartered trip is set by the charter agreement: by documents or through the Unified Biometric System.

What NeuroVision does. Builds the passenger list from document photos.
Inspector at the door

How it works. The inspector or driver looks at the passenger and at the photo in their document and decides personally.

What NeuroVision does. Provides the full name and number from the document — to check against the trip list.
Account in the app

How it works. A regular passenger creates an account with a document — Liveness and a one-time selfie match with the document photo in the same session.

What next. A change of document or a disputed login — the document and Liveness again.

We do not offer recognising a passenger by stored face photos at boarding, on the platform or in the cabin: under the biometrics law such recognition goes through the Unified Biometric System or with staff confirmation. A carrier needs only the document and the trip list.

A ticket for someone else’s passport, resold trips and other ways to cheat the passenger list

A passport photo from the internet

Buying with someone else’s data

In an online purchase, a photo of someone else’s passport or a generated image is uploaded. Antifraud flags a photo of a screen, a printout and edits before payment.

Buying up seats for a holiday trip

Tickets for made-up data

Seats on a popular trip are bought up with non-existent documents to be reissued later. Passport validity against the Ministry of Internal Affairs database and a recognised document instead of a typed number close the loophole.

A stranger on the bus

There is a ticket, but the passenger is different

A passenger boards with a ticket issued to someone else. The driver photographs the document, your system matches the full name and number against the list.

A chartered trip beyond the list

More people on the bus than in the agreement

People who are not on the list board a shift-worker or tour trip. A list built from document photos is checked at boarding in minutes.

An altered concession document

Someone else’s travel concession

The date of birth or photo has been altered to get a child or concession fare. Antifraud flags erasures, pasted-in photos and traces of a graphics editor.

1 ticket

One document — one passenger

A new passport, a changed surname, a child turned 14: when the passenger document is recognised again

A ticket was bought against one document, but the passenger took another on the trip. The carriage rules allow many such cases — but the data in the ticket and the list has to be reissued.

Passport replaced

The passenger received a new passport after buying the ticket. They are let on the train with the passport that notes the old one — the new document is recognised and the ticket data is reissued without typing.
Changed surname

The passenger presents a document with the new surname and a name change certificate. The new fields come from a photo of the new document.
A child turned 14

The ticket was issued against a birth certificate, but the child is already getting a passport. For long-distance trains a 90-day transition period applies — after that the data changes to the passport data.
Account in the app

A regular passenger changes the phone or the document in the profile. The document and Liveness again — in a new session, with a one-time selfie and photo match.

Checks and recognition for passenger transport: catalogue and prices

Each function is enabled separately — you pay only for completed requests. Start with document recognition at the ticket office and on the website, and add database checks as needed.

Fields for the ticket and the passenger database

From a single photo.

OCR · anti-fraud

Russian passport recognition with anti-fraud

A Russian passport spread is recognised from a photo: full name, date of birth, number, department code. Anti-fraud looks for editing, a photocopy and screen capture.

from 16 ₽
Learn more
OCR · MRZ

Foreign passports, residence permits, temporary residence permits

A passport of any country is recognised from a photo, the name — in Latin letters from the passport MRZ. A residence permit and a temporary residence permit — as an additional document.

10 ₽ for an extra document
Learn more
OCR

Driving licence and ID card

Both sides of a driving licence and an ID card are recognised from a photo as an additional document.

10 ₽ for an extra document
Learn more
Anti-fraud

Document authenticity check

Document antifraud looks for traces of a graphics editor, generation and a photo of a screen.

in the package
Learn more

Recognition price for a carrier’s ticket office and website

No subscription fee and no per-ticket-office fee: you pay for recognised documents and completed checks.

Most popular choice

Document

from 16 ₽ per session

Calculate

Passport recognition, fields for the ticket and the passenger database, antifraud: a photo of a screen, printout, pasted-in photo, edits.
Document + Liveness

from 29 ₽ per session

Enable

For accounts in the app: a live person in front of the camera and a one-time selfie match with the document photo.
Database checks

5 ₽ per check

Build a set

Passport validity, licence, licence deprivation and a driver’s wanted status.

One session — one passenger. At 10 000 documents a year, a “Document” session costs 18 ₽ by the calculator. A second document in a session — 10 ₽. On-premise installation is priced per project.

An SDK for the app, an API for the ticket office, an on-premise deployment for the bus station: how to connect recognition

Recognition is embedded in your ticketing system as a component: the sale, the passenger database and the trip lists stay in it.

Ticket office and server

An image from the ticket office scanner or camera is sent to the REST API; fields and the confidence level come back in JSON. Batch mode — for chartered trip lists. API documentation

REST API
iOS and Android
Web SDK
Docker

Test access — on request

Payment for completed requests, the retention period is set in the scenario, support — through a ticket system.

Why bus carriers and bus stations recognise documents with NeuroVision

A carrier needs one thing: the data in the ticket must match the document in the passenger’s hand.

The passenger document — once and in all channels

The ticket office, kiosk, website and driver get the same fields from one API. Foreign passengers are recognised from the machine-readable zone, and boarding by face stays where the law puts it — in the Unified Biometric System.

Passport MRZ Anti-fraud API

16 000+ document types

195+ countries and territories.

Under a second

to recognise a document.

Data in Russia

Cloud or on-premises installation, 152‑FZ.

A Russian developer

Russian software register No. 19972.

Carrier glossary: ACBPDP, named ticket, charter agreement

A short guide to the terms of carriage rules, transport security and document recognition.

ACBPDP: Automated centralised databases of personal data on passengers and vehicle crew — carriers submit details of tickets sold to them.; Passenger data database
A named ticket: A ticket that shows the passenger’s full name, date of birth and document number; at boarding it is matched against the document.; Named ticket
Electronic ticket: A ticket whose details are stored in the carrier’s automated system; for boarding with a named electronic ticket a document is enough.; E-ticket
Intercity service: Carriage between settlements; if they are in different regions, passenger details are submitted to the database.; Intercity service
Charter agreement: A chartered carriage agreement: it defines who travels and how passengers are identified at boarding.; Charter agreement
Fare evader: A person without a ticket or with a ticket whose surname and document number do not match the document presented.; Fare evader
MRZ: The machine-readable zone of a passport: the name in Latin letters, the number and dates with check digits.; Machine-readable zone
UBS: The Unified Biometric System — the state system through which boarding by face is possible in the airport experiment.; Unified Biometric System
Document anti-fraud: A check that the document is not a photo of a screen, not printed and not altered in an editor.; Document fraud check
Confidence level: An estimate of how reliably a field was recognised; a low one is a reason to show the field to the clerk.; Confidence score

What carriers ask about recognising passenger passports