A document via a link
After booking, the passenger gets a link and photographs the document with a phone. Fields are not typed by hand.
An agency sells a ticket issued to one person but paid for by another. We read the passenger’s document in a second, check that it is genuine and valid, and check a risky payer with Liveness and database checks. Ticket issuing stays in your system.
Data stored in Russia · Russian software registry no. 19972 · 152‑FZ
An agency does not carry passengers, but it issues a transport document on the carrier’s behalf, which means it is responsible for the data in it.
That is what the rules say; the blocks below show what can be checked automatically.
Air Code, Art. 102, 105; Federal Aviation Rules FAP‑82, cl. 50, 51, 55
Ministry of Transport Order No. 352, items 15, 16, 22, 79, 81
Air Code, Art. 102; Ministry of Transport Order No. 162, cl. 27
One ticket, five points of sale. The passenger’s document is the same everywhere; the channels and the payment differ.
The payer, the buyer and the passenger are often one person. When they are not, a mismatch is not a reason to refuse but a reason to look at the order more closely.
Full name, date of birth, document type and number are read from the photo and placed in the ticket fields. A letter that slips through manual entry stays as it is in the document.
A Russian passport is checked against the Ministry of Internal Affairs database: an invalid, replaced or lost document is visible before issuing. The check costs ₽5.
For a foreign passport and a foreign document, the surname and given name are taken from the machine-readable zone — exactly as in the passport. Passports of 195+ countries and territories.
The date of birth from the document sets the fare without the buyer’s word: age is seen at the time of travel, not at the time of the order.
Anti-fraud sees a photo of a document taken from a screen, a photocopy, a printout, a pasted-in photo and editing in an editor. A fake image is cut off before payment.
For orders matching your rule — an expensive ticket, a fresh account, departure tomorrow — the payer goes through Liveness and a one-off selfie-to-document match. Your system matches the name from the document against the card data.
The ticket is issued after the check, not right after payment.
There is no fraud here — only mistakes that cost money.
The surname on the ticket differs from the document. The passenger cannot check in, the ticket is reissued at the fare rate, and the customer writes to the agency’s support.
The passenger replaced the document before the flight. The rules require the new data to be entered in the ticket, and an agency that does not know about the replacement finds out at check-in.
The buyer entered the wrong date of birth. The fare did not match, and the ticket must be topped up or reissued.
The passenger bought a ticket with one document but presents another. A train accepts one of twenty types; a plane accepts the one the route requires.
Which steps the product covers and which stay with the agency and the carrier.
A fraudster buys tickets with a stolen card and resells them. The cardholder disputes the payment, the money goes back to the bank, and the ticket has already been used.
What stops it: For risky orders — Liveness the payer and the name from the document against the card data. The decision stays with the agency and the bank.
The details of a non-existent person are entered in the order.
What stops it: Document anti-fraud, validity of a Russian passport, database checks.
The buyer asks for the money to be returned to a card other than the one used to pay.
What stops it: A refund goes only to the payer; the payer’s document is in the order.
A ticket is issued on a document that is already invalid.
What stops it: Validity of a Russian passport against the Ministry of Internal Affairs database — 5 ₽.
Each scheme relies on a ticket being issued fast while nobody matches the payer and the passenger. Charter flights — on the private aviation page.
Carriage, fare, exchange and refund rules, boarding and check-in.
The agent acts on its behalf and under its rules.
Payment, card protection, a decision on a disputed transaction.
NeuroVision does not check the cardholder.
The ticket, support, a refund to the payer.
The decision whether to issue a ticket in case of doubt stays with the agency.
Ticket issuing and the transfer of passenger data.
Order storage also stays with your system.
Document: fields, authenticity, validity.
Payer — Liveness and matching with the document. Databases — wanted lists and debts.
FAP‑82
A ticket — by the document
A new session — one person, one document.
Before check-in the new data must be entered in the ticket: the passenger sends a new photo, the agency gets fresh fields.
The document is the same but the order is new: matching is needed if the period since purchase has expired or the payer has changed.
A refund goes to the payer. If the request comes from someone else, we first confirm who they are.
At 14 a teenager has their own passport, and the ticket is issued on it, not on the old document.
The “Document” package is usually enough for a ticket. Liveness and database checks are enabled under your risk rule.
Passenger document
Ticket fields without manual entry.
A Russian passport and a foreigner’s document are recognised from a photo; anti-fraud flags a screen photo, printout, pasted-in photo and edit.
from 16 ₽
Learn moreName in Latin letters, number and validity — from the machine-readable zone with a check of the check digits.
in the “Document” package
Learn moreAnti-fraud flags a document photo taken from a screen, a photocopy, a printout, a pasted-in photo and editing in an editor.
in the “Document” package
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 ₽ / check
Learn moreA risky order
Under your rule.
Passport, Liveness and a one-off match of a selfie with the passport photo — for the payer of a risky order.
from 29 ₽
Learn moreA check that the phone number belongs to the person in the order — against telecom operators’ data.
on request
Learn moreA check against the Ministry of Internal Affairs wanted-persons database using the document data.
5 ₽
Learn moreScreening against the consolidated lists of OFAC (USA), the European Union, the United Kingdom and the UN. Every match comes with a similarity score and a flag if it was triggered by an alias.
5 ₽
Learn moreYou pay for completed requests. There is no subscription fee; the trial period is 1 month.
from ₽16 per session (₽18 at 10,000 checks a year)
Document, anti-fraud, ticket fields.
from 29 ₽ per session
Document + Liveness, selfie-to-document matching.
₽5 per check
Passport, wanted lists, enforcement proceedings and others.
An additional document of the same person — ₽10. International screening — ₽36, optional for tickets on international flights.
Recognition is embedded where the agency already works with an order: in the email after booking, on the payment page and in the back office.
Payment for completed checks; the data retention period is set in the scenario; support — through a ticket system.
Four reasons to check the document and the payer before issuing a ticket, not after a complaint.
The passenger sends the document themselves, the fields arrive in the order from the document, a risky payer goes through Liveness, and the response reaches your system before issuing.
There is no need to assemble a solution from several vendors and reconcile their responses.
A short guide to terms from carriage rules and agency practice.
Document authenticity, invalid passports and MRZ — in our blog.
The law does not separately require such a check. A ticket is issued from the passenger’s document details, and checking the customer is the agency’s decision: so as not to issue tickets with a typo and not to lose money on stolen cards.
The passenger sends a photo of the document via a link. The system reads the fields, checks authenticity and, for a Russian passport, validity against the Ministry of Internal Affairs database. The response goes to your system.
No. The bank knows the cardholder. We confirm the payer’s identity by document and Liveness, and your system matches the name from the document against the card data.
No, that is the agency’s decision. Usually the passenger’s document is checked on every order, while Liveness and databases are for orders matching a risk rule: an expensive ticket, a fresh account, departure within hours.
The same way: the document is recognised and the fields go into the order. A train accepts twenty document types, and at boarding one typo in the name and one in the number are allowed.
Contact the carrier or the agent before check-in: ticket data is changed under the fare rules. To avoid mismatches, fields are taken from the document, not typed.
Yes, both the passenger and a relative can pay. But the ticket is issued to the person who travels, and the document needed is theirs, not the payer’s.
The payer: the refund goes to the card used to pay. If the request comes from someone else, their identity is confirmed separately.
No. The document is photographed anew, and Liveness and selfie-to-document matching are needed only for a risky payer.
A passport from 195+ countries and territories is recognised the same way as a Russian one: the surname and given name in Latin letters are taken from the MRZ.
A passenger — from ₽16 per session, a payer with Liveness — from ₽29, a database check — ₽5. Calculation — by the price matrix.
Through a link after booking, a Web SDK in checkout or a REST API. For an app there is an SDK for iOS and Android.
Tell us how you sell tickets and how many orders a day you have. We will set up the risk rule and give you 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 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.