Proof of Travel
On 14 March 2026, Yuki Tanaka, travelling on a Japanese passport, checked in at Charles de Gaulle Airport (CDG) for an Emirates flight to Dubai International (DXB). The check-in agent requested proof of onward travel from the UAE. Yuki presented a PDF from an online travel agency showing a booking reference number. The agent entered the reference into Amadeus and returned no active record. The check-in was suspended for 22 minutes.
A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. The resolution came when a separate confirmed booking from DXB to Singapore Changi (SIN), with a valid 6-character PNR returning status HK in the GDS, was produced. This case is instructive because Japanese passport holders are entitled to visa-free entry to the UAE for up to 30 days, and yet the failure occurred precisely because the document did not constitute a verifiable airline reservation.
The regulatory framework: UAE entry and proof of onward travel
The UAE does not publish a single consolidated onward-ticket regulation in the manner of, for instance, the Schengen Visa Code. Entry conditions are administered by the UAE Federal Authority for Identity, Citizenship, Customs and Port Security (ICP) at ports of entry, with airline-facing requirements communicated through IATA Timatic, the industry-standard entry requirements database used by carriers to verify boarding eligibility.
The Timatic entry for Japanese passport holders in the UAE states that entry is permitted visa-free for up to 30 days and that travellers must hold a ticket and sufficient funds for the duration of stay. The phrase "hold a ticket" means a confirmed, verifiable onward or return booking, not a booking reference or travel itinerary.
Under IATA Resolution 731, airlines are required to verify that passengers meet destination-entry requirements before boarding. Carriers that board passengers subsequently refused entry at the destination bear the repatriation cost. This financial exposure is the structural reason check-in agents apply UAE entry conditions rigorously.
Document requirements: what the verification check examines
| Document element | Required standard | Consequence of failure |
|---|---|---|
| PNR code | 6-character alphanumeric, confirmed in GDS | Agent returns "no record"; boarding suspended |
| Passenger name | Match to travel passport exactly | Agent cannot confirm the reservation belongs to the traveller |
| Departure from UAE | DXB, AUH, SHJ, or another UAE airport | Document does not establish UAE departure |
| GDS booking status | HK (confirmed) | TK, HL, or XX statuses are not accepted |
| Travel date | Within permitted stay period | Document does not satisfy the entry condition for that visit |
In Yuki's case, the OTA had issued a booking reference but had not completed ticketing. The OTA's internal reference number is not an airline PNR. The OTA's system had placed a fare hold, but the airline's GDS showed no confirmed reservation under that reference at the time of check-in. The document was a purchase intention, not a confirmed booking record.
Why OTA booking references are not airline PNRs
When a booking is initiated through an online travel agency, the OTA issues its own internal reference to track the transaction. That reference does not become an airline PNR until the carrier confirms the reservation in its GDS. For many OTAs, this confirmation occurs only after full payment is processed, which can take 24 to 72 hours. The document that arrives immediately in the traveller's inbox may look like a ticket but may not yet reflect a live GDS record.
The three document types that travellers frequently conflate are:
- OTA booking reference: An OTA-internal identifier. It may or may not correspond to a live airline PNR at the time of check-in.
- Airline PNR (record locator): The 6-character alphanumeric code assigned by the airline's GDS, the reference actually queried by check-in agents and border officers.
- E-ticket number: A 13-digit numeric string confirming payment. Only issued for fully ticketed, paid bookings.
A dummy ticket (onward ticket) issued through a specialist provider maps directly to an airline PNR from the point of issuance. There's no OTA intermediary layer. The PNR is live in the GDS immediately, making it verifiable from the moment it's in the traveller's possession.
For a comparable analysis of what check-in agents look up at the counter across multiple carriers, the airline check-in onward ticket compliance case study covers the verification process in detail.
What a compliant document set looks like for UAE entry
Travellers entering the UAE on visa-free or visa-on-arrival conditions should carry the following documentation:
- Passport with at least six months' remaining validity from the date of entry
- Onward or return ticket with a confirmed airline PNR, passenger name matching the passport, a UAE airport as the departure point, and a travel date within the permitted stay period
- Proof of accommodation: a confirmed hotel booking, Airbnb reservation, or a letter of invitation from a UAE resident
- Sufficient funds evidence: a bank statement, credit card, or travel cash covering the duration of stay
Proof of Travel's verified onward ticket booking service produces a document that meets all elements of item 2 above, issued with a confirmed airline PNR in the GDS and a passenger-name record matching the traveller's submitted passport details.
The US State Department's country information page for the UAE notes that travellers may be asked to demonstrate sufficient funds and onward travel: travel.state.gov UAE travel information.
Compliance lessons from the CDG case
Three conclusions follow from Yuki's check-in hold:
First, confirm the airline PNR independently of the OTA booking reference. The airline's manage-booking page accepts the PNR and surname to return current GDS status. If the record isn't there, the OTA's reference has no value at check-in.
Second, check GDS status 24 to 48 hours before check-in. PNR records can be cancelled by the airline through the ticketing time limit (TTL) process if payment is not received within the booking window. A PNR that was valid at booking may not be valid on travel day.
Third, allow adequate GDS propagation time. For bookings made within 24 hours of check-in, the PNR may not yet have propagated across all GDS nodes, producing a false "no record" response at the check-in counter.
They're different problems, but all three resolve with the same action: obtain a document with a confirmed airline PNR well before your check-in date and verify its status before travel.
For context on typical PNR validity windows and how consulates and border officers treat different expiry scenarios, the onward ticket PNR validity compliance case study covers the timeline mechanics in detail.
Frequently asked questions
Does UAE immigration check for onward travel on arrival as well as at check-in?
Yes. Under IATA Resolution 731, the airline verifies entry requirements at check-in before boarding. UAE ICP officers can then conduct their own check on arrival. In practice, if the check-in agent has already confirmed the document, the immigration desk is brief. The check-in stage is where the majority of compliance failures are identified.
Does the UAE have a published statutory requirement for onward tickets?
The UAE doesn't publish a single consolidated onward-ticket statute accessible to the public. The operative requirements are distributed through IATA Timatic, which airlines query directly, and through UAE ICP operational directives. The practical effect is consistent across nationalities: onward or return travel documentation is required for most visitors.
Can a confirmed hotel booking substitute for an onward flight ticket?
No. A hotel booking is evidence of accommodation, not evidence of departure. The UAE entry condition requires proof of outbound travel from UAE territory, which a hotel booking doesn't establish.
What is the airline's liability if it boards a passenger who is subsequently refused UAE entry?
Under IATA Resolution 731 and applicable bilateral agreements, the carrier is responsible for return transportation at its own cost. This structural liability is why Emirates, Etihad, and other UAE-bound carriers verify entry requirements proactively at check-in, regardless of the traveller's nationality or prior travel history.