...

Selling air and rail tickets: who travels, who pays and what the ticket says

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.

The passenger’s document is recognised, the payer is confirmed, the ticket can be issued
from 16 ₽ passenger document and anti-fraud per session
from 29 ₽ payer document and Liveness
195+ countries and territories — passenger documents
< 1 s document recognition
Passport without entry Travel passport and MRZ Document anti-fraud Payer Liveness A link after booking

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

A ticket for the person who travels: what carriage rules require of an agency

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 ticket

    Air Code, Art. 102, 105; Federal Aviation Rules FAP‑82, cl. 50, 51, 55

    What we check

    Legal basis

    • A ticket is issued from the details of an identity document
    • A separate ticket for each passenger

    A different document

    • A passenger wants to present another document — before check-in, through the carrier or the agent
    • The agent must make the change

    The wrong person

    • A ticket cannot be used in someone else’s name
    • It is confiscated and the fare is not refunded
  • Long-distance train

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

    What we check

    Legal basis

    • A ticket is issued from the document details
    • The list covers 20 document types

    On the ticket

    • Full name, date of birth, citizenship, gender
    • Passenger document number

    At boarding

    • The ticket and the document are presented
    • One typo in the name and one in the number are allowed
  • The carrier’s agent

    Air Code, Art. 102; Ministry of Transport Order No. 162, cl. 27

    Who is responsible for what

    What the agent does

    • Books, sells and issues a ticket on the carrier’s behalf
    • The carrier is responsible to the passenger for the agent’s actions

    Passenger data

    • The details are passed to the passenger database — for air and rail carriage, within 15 minutes of the transaction
    • Your system handles the transfer

    Where the product fits

    • NeuroVision returns the document fields
    • Issuing and transfer stay with you

Online agency, aggregator, network ticket office, app: who sells someone else’s ticket

One ticket, five points of sale. The passenger’s document is the same everywhere; the channels and the payment differ.

  • Online air ticket agency

    • An order on the site and in the app
    • Payment by card and SBP
    • The passenger’s document is typed in by hand
  • Rail ticket service

    • A long-distance train ticket
    • The document is one of twenty types
    • Children and adults in one order
  • Air and rail aggregator

    • Search across many carriers
    • Payment on the aggregator’s side
    • The carrier decides on the refund, the aggregator returns the money
  • Offline agency and network ticket office

    • The customer at the counter, document in hand
    • One operator — hundreds of orders
    • A ticket for a relative who is not at the counter
  • An app or wallet that pays for tickets

    • A ticket is one of many purchases
    • The payment is tied to an account
    • Passenger data is collected on the first trip
  • A phone with an air ticket order form

Three people behind one order: what to match for the payer, the buyer and the passenger

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.

  • Surname, name and number — as in the document

    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.

  • The passport is valid

    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.

  • Latin letters from the MRZ

    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.

  • Adult or child

    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.

  • Authenticity of the image

    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.

  • A risky payer

    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.

From basket to issuing: the passenger sends a document, the system checks it, the agency issues the ticket

The ticket is issued after the check, not right after payment.

Step 1

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.

A passenger photographs a passport on a phone after booking a ticket
Step 2

Matching and checks

Fields are matched against the order, the passport against the database, the image against forgery. For a risky order the payer goes through Liveness.

Matching the passenger’s and the payer’s documents before a ticket is issued
Step 3

Order status

The response reaches your system: data for the ticket and a verdict. The agency issues the ticket or asks to repeat a step.

Order status: ticket data received

An extra letter, a new passport, a child’s age: what the agency pays for out of its own pocket

What a lack of checks costs

There is no fraud here — only mistakes that cost money.

  • 01

    A typo in the surname

    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.

  • 02

    The passport was replaced after purchase

    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.

  • 03

    A child booked as an adult

    The buyer entered the wrong date of birth. The fare did not match, and the ticket must be topped up or reissued.

  • 04

    The wrong document type

    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.

  • from 16 ₽ document and anti-fraud
  • 5 ₽ validity of a Russian passport
  • < 1 s recognition

An agent’s checklist: what to check from order to ticket refund

Which steps the product covers and which stay with the agency and the carrier.

  • Route, dates and number of passengers Your system
  • Each passenger’s document — a separate link NeuroVision
  • Document fields are placed in the order NeuroVision
  • Age from the date of birth in the document NeuroVision

  • Payment method and amount Your system
  • Cardholder and bank decision Acquiring bank
  • Liveness of the payer per your rule NeuroVision
  • The payer’s name from the document is matched against the card data Your system

  • The Russian passport is valid, the image is not a forgery NeuroVision
  • Surname and number on the ticket — as in the document Your system
  • Passenger data is sent to the carrier’s database Your system
  • The e-ticket is sent to the passenger Your system

  • A document change before check-in — a new link and matching NeuroVision
  • Exchange and refund — under the fare rules Carrier
  • Refund to the payer’s card Your system
  • A check log for disputed cases NeuroVision
  • NeuroVision — covered by NeuroVision: passenger document, anti-fraud, passport validity, payer Liveness per your rule, check log
  • Your system — your system: order, payment, issuing, passenger data transfer, refund
  • Carrier — the carrier: exchange and refund rules under the fare
  • Acquiring bank — the acquiring bank: cardholder and the payment decision

A stolen card, a fictitious passenger, a refund to someone else’s account: four schemes against an agency

  • A ticket bought with someone else’s card

    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.

  • A fictitious passenger

    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.

  • A refund to another card

    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 for an “acquaintance” on a lost passport

    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.

Exchange, refund and a passport change before the flight: when the agency looks at the document a second time

A new session — one person, one document.

  • The passenger replaced the passport

    Before check-in the new data must be entered in the ticket: the passenger sends a new photo, the agency gets fresh fields.

  • Exchange for another date

    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

    A refund goes to the payer. If the request comes from someone else, we first confirm who they are.

  • The child grew up

    At 14 a teenager has their own passport, and the ticket is issued on it, not on the old document.

Recognition and checks for an air and rail ticket agency: what to include in the scenario

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.

  • Recognition · anti-fraud

    Documents from 195+ countries and territories

    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 more
  • Machine-readable zone

    Surname and given name in Latin letters from the MRZ

    Name in Latin letters, number and validity — from the machine-readable zone with a check of the check digits.

    in the “Document” package

    Learn more
  • Document anti-fraud

    A photo of a screen, a printout, editing

    Anti-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 more
  • Police · SMEV

    Validity of a Russian passport

    The 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 more

Check price by the price matrix: passenger and payer separately

You pay for completed requests. There is no subscription fee; the trial period is 1 month.

  • Passenger

    from ₽16 per session (₽18 at 10,000 checks a year)

    Get a quote

    Document, anti-fraud, ticket fields.

  • A risky payer

    from 29 ₽ per session

    Get a quote

    Document + Liveness, selfie-to-document matching.

  • Database checks

    ₽5 per check

    Get a quote

    Passport, wanted lists, enforcement proceedings and others.

An additional document of the same person — ₽10. International screening — ₽36, optional for tickets on international flights.

A link after booking, a widget at payment, an API in the back office: where to embed the check

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.

A link after booking

The passenger gets a link by email or in your service’s messenger, photographs the document and returns to the order. No development needed; suits a pilot.

  • Link
  • Web SDK
  • iOS and Android
  • REST API
  • Docker

Test access — on request

Payment for completed checks; the data retention period is set in the scenario; support — through a ticket system.

What an agency gets by checking an order before issuing

Four reasons to check the document and the payer before issuing a ticket, not after a complaint.

Checking before issuing, 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.

Fewer reissues

The surname and number are taken from the document, not typed.

Fewer disputed payments

A risky order’s payer goes through Liveness before issuing.

Passport MRZ Liveness API

One flow for air and rail

Twenty train document types and documents of 195+ countries and territories — in one session.

Data in Russia

The NeuroVision cloud or the agency’s own environment; Russian software register No. 19972.

Issuing, reissue, chargeback, MRZ: a glossary for an air and rail ticket agency

A short guide to terms from carriage rules and agency practice.

Transport document
A ticket, a baggage receipt and other documents that certify a contract of carriage.
Carriage document
Electronic ticket
A ticket in the form of an electronic document with carriage conditions in the issuing system.
E-ticket
The carrier’s agent
An organisation that books, sells and issues tickets on behalf of a carrier.
Carrier agent
Extract
The moment a ticket is issued for a specific passenger after booking and payment.
Ticket issue
Reissue
A change of data or date in an already issued ticket under the fare rules.
Reissue
Refund
A refund of the ticket payment under the fare and carrier rules.
Refund
Chargeback
Money returned to the payer after a dispute with the bank; the agency takes the loss and penalty costs.
Chargeback
The payer
The person whose card paid for the order; not always the passenger.
Payer
MRZ
The machine-readable zone at the bottom of a foreign passport: name in Latin letters, number, validity.
Machine-readable zone
Document anti-fraud
A check that the document image is not from a screen, not printed and not edited.
Document fraud check

Agencies’ questions about checking the passenger and the payer when selling tickets

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.

We will set up passenger and payer checks for your agency

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 call

The 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.