On 14 March 2026, Marta Varga, a Hungarian national holding a Schengen-area passport, presented at a Wizz Air check-in desk at Budapest Ferenc Liszt International Airport (BUD) for a flight to Lisbon (LIS). Her stated plan was to enter Portugal, travel through Spain, and depart for Buenos Aires approximately six weeks later. As onward proof, she presented a printed itinerary from a flight price-comparison website showing a LIS-EZE routing on LATAM. The check-in agent queried the reference. No PNR existed. She was denied boarding.

The Varga case illustrates a document-compliance failure that recurs across European gateway airports: the substitution of a price-comparison export for a verified booking. This case study unpacks the precise fields that distinguish a compliant onward ticket from a non-compliant one, and the regulatory basis for carriers' verification obligation.

The Regulatory Framework

Airlines operating intra-Schengen and outbound international routes carry explicit liability under IATA Resolution 830d for transporting passengers subsequently refused entry. The resolution requires carriers to verify, at check-in, that a passenger holds documents satisfying the destination country's entry conditions. For Portugal, as with all Schengen member states, those conditions include proof of onward or return travel for non-resident visitors.

A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without the fare being fully settled at the time of check. It satisfies the documentary requirement because the PNR exists in the airline's Global Distribution System and returns a confirmed (HK) status on terminal query. A paid ticket satisfies the same requirement through the same mechanism. The distinction between them, from the carrier's verification perspective, is nil.

What does not satisfy the requirement is any document without a GDS-queryable PNR. This includes price-comparison PDFs, Google Flights exports, OTA itineraries generated without a booking reference, and hand-typed letters of intent.

Document Gap Analysis: Varga's Non-Compliant Set

Marta Varga's submitted document set at BUD check-in contained the following:

Field Submitted document Compliant standard Gap
Document type Price-comparison export (PDF) PNR with HK status No PNR present
Carrier LATAM (listed) Real scheduled carrier with GDS record Carrier name present; booking absent
Route LIS-EZE Departure from destination country Route listed; no booking exists
Dates Approximate (6-8 weeks out) Specific departure date within permitted stay No confirmed date
Booking reference None Six-character PNR No reference
Name match Name visible Exact match to passport Match present but irrelevant without PNR
GDS-queryable No Yes Verification failed at first query

The agent's terminal returned no record. Under Wizz Air's check-in procedures, consistent with the IATA carrier liability framework, boarding was correctly denied. The carrier's exposure: if Varga had been boarded and then refused entry at LIS, Wizz Air would have been responsible for return carriage costs.

The Compliant Replacement: What Varga Should Have Presented

A compliant document for the same check would be either a paid LATAM ticket on the LIS-EZE route with a confirmed PNR, or a dummy ticket issued by a reputable provider for the same or any real onward departure from Portugal.

The compliant document set would contain:

Field Compliant document
Document type Booking confirmation with PNR
Status HK (confirmed) in GDS
Carrier Real scheduled airline (e.g. LATAM, TAP, Iberia, or any carrier operating from LIS)
Route Departure from Portugal or any Schengen country within 90 days
Dates Specific date within the permitted stay window
Booking reference Six-character PNR verifiable by terminal query
Name match Exact match to passport

Neither the carrier nor the border officer verifies payment at the check-in terminal. The IATA Timatic system, which carriers use to check destination entry requirements, does not include a payment-verification module. What it checks is the existence and status of the booking.

Carrier-Level Verification Practices

Wizz Air, operating primarily on short- and medium-haul routes across Europe and the Middle East, applies standard Timatic-driven checks at check-in. The carrier's obligation to verify onward travel applies specifically to routes where the destination country requires proof of departure as a condition of entry.

For intra-Schengen routes, the onward-ticket check is sometimes waived for Schengen-passport holders travelling within their own residency area. Varga held a Hungarian passport but was not a Portuguese resident. The check was correctly applied.

Carriers vary in the rigour of their onward-document checks. Budget carriers operating high-volume routes sometimes rely on passenger self-declaration, particularly for nationalities whose entry conditions don't require onward proof. Where Timatic returns an onward-ticket requirement, agents at most carriers are expected to verify the PNR rather than accept a document on face value.

Our analysis of onward ticket PNR validity compliance covers the timing dimension: the PNR must be live at the time of verification, not only at the time of purchase.

Post-Resolution: Varga's Compliant Booking

Following the boarding denial, Varga contacted Proof of Travel and received a compliant dummy ticket for a LIS-GRU routing on TAP Air Portugal, with a confirmed PNR valid for seven days. The second check-in attempt, on a later Wizz Air flight the same afternoon, was approved in under ninety seconds.

The resolution cost: one dummy ticket fee and a same-day rebooking charge on the original Wizz Air booking. The avoidable cost if the dummy ticket had been obtained in advance: nothing beyond the original ticket price.

The airline check-in onward ticket document compliance analysis provides a broader framework for understanding which document types satisfy which verification checks across carrier types.

Document Compliance Principles

The Varga case reduces to three compliance principles applicable to any onward-document check:

Principle 1: A PNR is not optional. Any document presented as proof of onward travel must contain a booking reference that returns a confirmed status in the GDS. Documents without PNRs fail at the first query.

Principle 2: Payment status is not queried at check-in. The terminal check is status and route, not fare settlement. A dummy ticket and a paid ticket satisfy the same check by the same mechanism.

Principle 3: The document must be current at the time of check. An expired PNR is as non-compliant as a document with no PNR. Order or refresh your dummy ticket to cover the verification date, not just the submission date.

For travellers requiring compliant onward documentation before a Schengen entry or any border check, Proof of Travel provides verified dummy tickets with confirmed PNRs deliverable within minutes of ordering.

Frequently Asked Questions

Why did the check-in agent reject the price-comparison PDF?

The PDF contained no booking reference. The agent's terminal queries a PNR against the GDS. Without a PNR, there's nothing to query, and the verification fails immediately. The document's visual appearance (carrier name, route, dates) is irrelevant if there's no underlying record.

Can a dummy ticket be used for a Schengen entry from a non-Schengen country?

Yes. A dummy ticket with a confirmed PNR for a departure from within the Schengen zone satisfies the onward-travel requirement at most Schengen entry points. The key requirement is a confirmed booking from within the permitted stay window.

What's the difference between a dummy ticket and an onward ticket?

None of substance. Both terms refer to a real PNR reservation issued for border-check or visa purposes, without the intent to fly the booked route. "Onward ticket" describes the function (proof of departure); "dummy ticket" describes the nature of the booking (not intended for actual travel).

Does a visa officer check payment when reviewing a flight itinerary?

Standard visa procedure does not include a payment verification step. Entry Clearance Officers reviewing itineraries check that the carrier is real, the route is coherent with the stated travel plan, and the PNR is retrievable via the airline's public reference tool if they choose to verify. Payment confirmation is only required when a consulate's specific checklist explicitly requests it.

How long does a dummy ticket's PNR remain valid?

Validity windows vary by provider, typically five to fourteen calendar days. For border checks, a five-day window is usually sufficient. For visa applications with uncertain processing timescales, a longer window or a provider that offers PNR refreshes is advisable.