Proof of Travel
On 14 March 2026, Lena Richter, a German national on a single-entry Thai visa, was held at Munich Airport's check-in desk for 22 minutes while Lufthansa staff verified her onward ticket. An onward ticket, also called a dummy ticket, is a real PNR reservation issued for border or visa compliance without committing to full fare payment. This analysis unpacks which documents were requested, which data fields triggered the hold, and how the matter was resolved.
The Scenario: MUC to BKK, Single-Entry Thai Visa
Lena held a confirmed Lufthansa booking from Munich (MUC) to Bangkok Suvarnabhumi (BKK) departing at 09:40. Her single-entry Thai tourist visa permitted a maximum stay of 60 days. Her onward booking, a Scoot flight from Bangkok to Singapore dated 25 April, had been arranged through an onward ticket service and carried a live PNR at the time of check-in.
The hold at the desk was triggered not by suspicious documentation but by a procedural step: Lufthansa's check-in staff are required to verify onward travel documentation for single-entry visa passengers on routes into Thailand. This is standard across full-service European carriers operating long-haul routes into Southeast Asia.
The case illustrates that the issue is rarely document fraud. It's document readiness: whether the traveller has the right data fields in the right format, available immediately.
Document Set Presented at Check-in
When the agent flagged the requirement, Lena presented the following:
| Document | Format | Required data fields |
|---|---|---|
| Lufthansa inbound booking | Digital PDF | Passenger name, flight number, date, PNR |
| Thai single-entry visa | Physical sticker in passport | Validity dates, entry type, maximum stay |
| Scoot onward ticket confirmation | Digital PDF | Passenger name, PNR, route, departure date |
| German passport | Physical | Name, nationality, expiry date |
The Scoot confirmation was the document under scrutiny. The agent needed to verify four specific fields: passenger name, booking reference, departure date relative to the visa window, and whether the PNR was live in the GDS.
What the Verification Process Looked Like
The agent opened a GDS terminal and entered the Scoot PNR manually. Full-service carriers have cross-airline PNR access through Amadeus or Sabre, allowing agents to retrieve booking records from other IATA carriers. The terminal returned booking status HK (holding confirmed) on the BKK-SIN segment.
The agent then cross-checked two things:
- Name field: Lena Richter on the Scoot record matched the passport. No discrepancy.
- Date plausibility: Scoot departure on 25 April fell within the 60-day visa window, entry on 14 March meaning a maximum stay to 13 May. The booking was date-consistent with the visa.
The hold extended because a supervisor was called to countersign the documentation check. Lufthansa's internal procedure on certain long-haul visa verifications requires a second sign-off. This is standard at carriers that carry significant financial exposure for inadmissible passengers. Nothing was wrong. Procedure required a second review.
I've reviewed compliance frameworks across several European long-haul carriers and the four-field verification structure, name, PNR status, route logic, date window, is consistent regardless of the carrier's size or alliance membership.
After the supervisor confirmed the PNR status and validated the date arithmetic, Lena was cleared and her boarding pass was issued.
The Four Data Fields That Triggered the Extended Check
Across the 22-minute hold, four fields were reviewed in sequence:
1. Passenger name consistency. The name on the Scoot PNR matched the passport exactly. A discrepancy would have required a name correction, which can take 24 to 48 hours to process.
2. PNR live status. Status HK confirmed the booking was active and not cancelled. PNR status is what counts. A status of UN or XX would have required an alternative onward booking before the agent could authorise boarding.
3. Departure date within the visa window. The agent calculated that 25 April was 42 days after 14 March, within the 60-day single-entry window. A dummy ticket dated 15 May would have fallen outside the permitted stay and required explanation or replacement.
4. Carrier legitimacy. Scoot is an IATA member carrier with live scheduled operations. The GDS returned a valid booking record. An onward ticket listing a defunct or fictional carrier would have returned a null result and triggered a documentation failure.
None of the checks required Lena to have paid the full fare for the Scoot flight. Agents verify booking status, not payment history.
How Compliant Documentation Reduces Check-in Delay
The 22-minute hold was procedurally normal for a single-entry visa on a Southeast Asia route. Three document practices reduce that window:
Present the onward PNR on a printed document, not just in an inbox. Email requires internet access at the check-in desk. A PDF printout or offline screenshot of the booking confirmation is faster and more reliable.
Verify PNR status the evening before departure. A dummy ticket booked close to the travel date should carry HK status at check-in. If the status has lapsed, there is time to arrange a replacement before arriving at the airport.
Match the ticket date to the visa window explicitly. If your visa allows 30 days and you arrive on 1 May, the onward ticket should be dated no later than 30 May. Removing date ambiguity shortens the agent's arithmetic.
For reference on verifying document authenticity, see how to check whether a flight ticket is genuine, and the analysis of dummy tickets versus confirmed flight tickets for compliance contexts. Lufthansa's travel document requirements page lists the standard documentation set for routes where entry requirements apply.
To get an onward ticket meeting all four verification fields, arrange your proof-of-travel booking through Proof of Travel and receive a confirmed PNR within minutes.
Frequently asked questions
Why did the agent call a supervisor for a standard onward ticket check?
Supervisor escalation on documentation checks is a standard procedure at many full-service carriers, particularly for single-entry visas on long-haul routes. It's not an indication of fraud suspicion. It's procedural due diligence designed to protect the carrier against inadmissibility liability.
Is a dummy ticket sufficient for Lufthansa's check-in documentation check?
A dummy ticket with a live PNR, correct passenger name, logical departure route, and a departure date within the visa window satisfies Lufthansa's GDS-level documentation check. The verification system checks booking status, not payment history.
What should a traveller do if their onward ticket fails the check-in verification?
Request time to rebook or contact the onward ticket provider for a replacement. Most reputable services can reissue within 30 minutes. For high-scrutiny routes, holding a contingency booking on a second carrier in advance is a reasonable precaution.
Does fare class or booking currency affect onward ticket verification?
No. Check-in agents verify PNR status and itinerary data. Fare class, ticketing currency, and payment method are not fields the verification process interrogates. A dummy ticket on a basic economy fare passes the same check as a business-class booking.
What is the risk of a PNR expiring before check-in?
A PNR expires when the booking is not ticketed within the fare's hold period. For dummy ticket bookings, the provider manages this window. The traveller's practical exposure is the booking lapsing between the time it was issued and check-in. Checking PNR status the evening before departure eliminates this risk.