A measurable share of no-shows and gate refusals are document failures that were already knowable at the moment of booking. The passenger needed a visa or a travel authorisation for the destination or for a stop along the way, nobody told them while there was still time to get one, and the outcome was either a seat that flew empty or a passenger the desk had to turn away. eVisa data closes that gap at three points in the journey: when the ticket is sold, in the weeks between booking and departure, and at check-in.
Each catches what the one before it missed, and the earlier the catch, the cheaper it is.
At booking: resolve the requirement while the passenger can still act
Booking is the only moment where the airline holds the passenger's attention, the complete itinerary and enough runway before departure for a government to actually issue something. A requirement surfaced there is a requirement the passenger can do something about. The same requirement surfaced at the airport is a refusal.
Three things separate a useful check from a notice nobody reads:
- Resolved against the passport in hand. Nationality decides the answer. A generic destination page tells the passenger what most travelers need, which is exactly the sentence that gets ignored by the one who needs something different.
- Applied to the full routing. Transit stops carry their own rules, and a connection through a third country is where requirements checks most often go quiet. The itinerary the airline just sold is the itinerary that has to be evaluated, stops included.
- Shown with the clock attached. A requirement with a realistic processing time next to it, presented while the passenger is still in the flow, converts into an application. The same information in a confirmation email footer converts into nothing.
Between booking and departure: a message that carries a status
Most pre-travel communication is generic. It reminds every passenger on the flight to check their documents, which tells the compliant passenger something they already know and the exposed passenger nothing they can use. A message carrying the passenger's actual document status distinguishes between them.
A passenger with no application on file three weeks out and a passenger whose authorisation was approved last Tuesday are not the same risk, and the airline has the data to tell them apart:
- Nothing on file, weeks remaining. The message that matters is a link to apply, with the processing time stated.
- Submitted, awaiting a decision. No action from the passenger, and a reason for the airline not to chase them. Chasing people who have already complied is how pre-travel messaging trains passengers to ignore it.
- Nothing on file, days remaining. This is a no-show forecast with a name and a PNR attached. That is worth a phone call, and worth knowing while the seat can still be sold to someone else.
- Approved. The record moves forward to check-in already resolved.
At check-in and the gate: verification against the manifest
The last intervention point is the one airlines already staff. Running document status against the manifest turns the check-in desk into a place that confirms documents rather than a place that discovers their absence. Verification done hours ahead of departure, against the passenger list the airline already produces, leaves the gate with a shorter list of exceptions and gives ops the time to work them.
Why the gate is an expensive place to find out
By the time a passenger is standing at the desk without the authorisation their nationality requires, every option left costs money. There is the fine: the United Kingdom charges £2,000 per improperly documented arrival under section 40 of the Immigration and Asylum Act 1999, and most other regimes sit in the same order of magnitude. Where entry is refused on arrival, the return sector is generally the carrier's to fly. After that come the rebooking, the agent time, the delay if the bag has to come off, and the internal review that follows a cluster of them on one route. The airline pays all of it for a failure that happened weeks earlier, at a screen where the passenger could still have fixed it.
What the data has to be
- Per passport, not per route. A requirement belongs to a document, and a single booking can carry several nationalities. Route-level generalities produce answers that are correct on average and wrong for the passenger reading them.
- Current. Governments change fees, validity windows and eligibility with little notice, and a requirements set that was accurate last quarter will refuse someone this quarter. Our post on how three people track sixty governments sets out the tracking discipline this depends on.
- Where staff already look. Document status inside the booking record and on the manifest gets used. Document status in a separate portal with its own login does not.
How this sits with the compliance engine you already run
None of this replaces the boarding-decision system the airline already operates. Those systems exist to answer a binary question at the gate under regulatory pressure, and they answer it well. What eVisa data adds is earlier, at a point where the answer can still change the outcome. When the requirement is resolved at booking and the application is filed weeks out, the compliance check at departure confirms a document that already exists instead of catching its absence. We have written on what a compliance engine and a modern visa API are each for.
What SimpleVisa offers airlines
SimpleVisa resolves requirements per passport and per full routing, transit stops included, and returns them fast enough to sit in a booking flow. Passengers who need a document can apply through a checkout attached to the booking, with the application record linked to the PNR, and SimpleVisa handles submission to the government portal and traveler support from there. Verify runs at check-in against the manifest the airline already produces and returns a verdict per passenger. The airlines page covers the commercial models, and the requirements checker shows what the underlying data returns for a given passport and route.