What a PNR actually is
Start with the object everything else depends on. A PNR — Passenger Name Record — is not the PDF in your inbox. It is a structured record inside a reservation system: passenger name fields, one or more flight segments, contact elements, and a status code per segment. The six-character alphanumeric code printed on your confirmation (say, X4F2KQ) is the record locator — a lookup key, nothing more.
This distinction is the entire subject. The PDF is a rendering of the record at one moment in time. The record is the source of truth. Verification always goes to the source.
Where the record lives: Amadeus, Sabre, Travelport
Reservations are created in a global distribution system — Amadeus, Sabre or Travelport are the big three — or directly in an airline’s own passenger service system, which is often built on the same platforms. Either way, the airline’s reservation database and the GDS synchronise: one booking, one record, many windows onto it.
That architecture is why verification is so hard to cheat. There isn’t a “copy” of your booking at the embassy to fool. Every checker — you, the consulate, the airline’s call centre — is reading the same row in the same system.
What the airline lookup actually does
When anyone opens “Manage Booking” or “My Trips” on an airline website and enters a record locator plus a surname, the site runs a retrieval query against the live reservation database. If a record exists and the surname matches the name field, the system returns the booking: passengers, segments, dates, status codes. If not, it returns an error.
Note what is not part of that transaction: your PDF. Nobody uploads it, scans it, or compares fonts. The document you submitted is bypassed entirely — the query goes straight to the system of record. Our step-by-step verification guide walks through doing exactly this yourself in about thirty seconds.
Status codes: what HK means
A retrieved segment carries a two-letter action/status code. These are GDS-standard, so they mean the same thing everywhere:
This is why “HK (Confirmed)” appears in every serious discussion of visa flight proof: it’s the machine-readable difference between “a seat is held for this passenger” and everything else.
Why an edited PDF has nothing to resolve
Now run the fake through the same machinery. An edited PDF starts as someone else’s confirmation — or a template — with names and dates changed in an editor. The pixels change; no reservation system is touched. The “record locator” on it either never existed, belongs to a stranger’s booking with different names, or points to a booking that was cancelled long ago.
So the lookup does exactly what it is designed to do: it queries the database, finds no matching record, and returns nothing. There is no counterfeiting technique that fixes this, because the flaw isn’t in the document — it’s in the absence of data. You cannot Photoshop a database row.
The checks a consulate — or airline — can run
None of these require special powers. That’s the elegant part: the same read-only queries are available to officers, airlines and applicants alike.
Which documents get this treatment, and how officers weigh them against the rest of your file, is a separate question — covered in our guide to what visa officers actually check. The mechanical point here is simpler: when a check happens, it is a database query, and database queries are binary. See the general visa requirements tool for what each country expects in the file.
What happens when a document fails the check
A failed lookup rarely triggers drama. It triggers paperwork — and the paperwork is worse.
The refusal wording matters. Schengen refusal forms include grounds like “the information submitted regarding the justification for the purpose and conditions of the intended stay was not reliable” — and where an officer concludes a document was actually false, misrepresentation grounds carry heavier consequences, including bans in systems like the UK’s. A refusal also becomes part of your history: future applications ask about it, and officers can see it.
Why a real held reservation passes every check
Run a genuine held booking through the same four checks and the outputs converge, because they all read the same record: manage-booking returns the segments with HK status; CheckMyTrip renders the same itinerary; the airline’s phone agent reads back the same names and dates. Consistency across independent queries is precisely what “verifiable” means — and it’s a property no edited document can have.
That’s the technical case. If you’re deciding what to actually buy — and how to avoid sellers whose “dummy tickets” are the fake kind — the buyer’s side of this topic is covered in our honest answer on dummy tickets.