Travel agencies and tour operators
Passenger details, exactly as the passport prints them
One photo of the data page and the name, nationality, passport number and dates come back, ready for the booking and for issue. Nothing retyped, and no guessing how the surname is spelled.
A misspelled surname is paid for at the airline
The passenger sends a photo of their passport over WhatsApp and someone at the agency types the details into the booking engine: given names, surname, nationality, document number, date of birth, expiry. Times the four members of a family, or the thirty on a school trip.
If anything differs from the document, the error is not caught at the agency. It is caught at issue, when a name change already carries a fee, or at the airline counter on the day of travel. On an international ticket one letter costs money, and the complaint call goes to the agency, not to the passenger.
Then there is the time. Loading a group turns into an entire afternoon of typing, exactly when the sale is already closed and all that is left is paperwork.
What loading passengers looks like instead
Still your booking engine and still your issuing process. What changes is where the passenger data comes from.
- 1
You receive the passport photo as you already do
Over WhatsApp, by email, or uploaded to your own form. A photo from the passenger phone is enough as long as the whole data page is visible.
- 2
The fields come back structured
Given names and surname as the document prints them, nationality, issuing country, passport number, sex, date of birth and expiry. Each in its own field, ready for the booking.
- 3
The read checks itself
ICAO 9303 check digits are recomputed on every read. A misread passport number is rejected there and then rather than travelling all the way to issue.
- 4
It lands in your system, or on your worksheet
Whoever maintains your integrations wires the response into the passenger record with one call per document. With no system of your own, the team works straight off the returned fields.
Why this matters to an agency
The ticket name is the passport name
It is issued from what the document says, not from what was understood over the phone. That is the most expensive error in the business and the one that comes back as a complaint most often.
A group stops being an afternoon of typing
Thirty passports are processed one after another without anyone keying the same data structure thirty times.
Expiry is visible from the booking
The expiry date comes back as a field, so a passport that fails the six-month rule surfaces while quoting rather than at the airport.
No scanner, no per-branch licence
You pay per read with tokens that do not expire, so an agency with a high season and a low one carries no fixed cost out of season.
Does a photo sent over WhatsApp work?
Yes, as long as the full data page is visible with no glare across the two lines of characters at the bottom. If the image is compressed too hard and the read does not agree, you ask for another and that read is not charged.
Does it connect to my booking engine?
Through the API: you post the image and receive the fields as JSON. Whoever maintains your integrations wires it into the passenger record, and the documentation has copy-paste examples.
Do you store the passenger passport?
No. The image is processed and discarded, and the extracted fields are not retained on our side. Whatever you keep about the passenger stays in your system and under your privacy notice.
Does it work with passports from any country?
Yes. The machine-readable zone has the same format in every issuing country, so there is nothing to configure per nationality and no document costs more than another.
What does loading a group cost?
One token per passport read, with no subscription and no minimum. A group of thirty consumes thirty tokens, and tokens do not expire between seasons.
What about passengers with a Mexican ID?
Their voter credential is read by our INE service, a separate account that returns CURP, elector key and address. That site is in Spanish.