A check-in agent in Istanbul, an immigration officer in Hanoi, and a consulate that already approved a visa file rarely want the same proof of onward travel, though travelers routinely assume one document satisfies every checkpoint. Under the UK's carriers' liability regime, for example, an airline can be fined for boarding a passenger who lacks the correct documents, which is one reason check-in staff verify onward proof themselves rather than trusting a visa approval alone. A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight, built to answer exactly this kind of check.

The Istanbul to Hanoi case

Consider an illustrative case: Lena Marchetti, a hypothetical consultant, books a one-way Turkish Airlines flight from Istanbul to Hanoi. Her Vietnam e-visa is already approved, but the check-in agent still asks for proof she doesn't intend to stay indefinitely. Lena produces an onward ticket PNR, a real reservation held in the airline's booking system rather than a purchased flight. The agent looks up the record locator directly, confirms it matches her name and itinerary, and clears her for boarding. When she lands, Vietnamese immigration doesn't ask for the document again; the visa file already covered that ground.

The scenario is ordinary, and that's the point. Three separate institutions touched the same traveler, and only one of them actually inspected a ticket.

What "proof of onward travel" actually requires

The phrase gets used loosely, but it collapses three distinct questions that are easy to conflate:

  • Does the traveler hold a document showing they plan to leave the country or region within the permitted stay?
  • Is that document something the checking party can actually verify, rather than a static file that could be forged?
  • Does the document satisfy the specific rule of the specific authority asking, since a consulate's checklist and an airline's boarding rule aren't the same instrument?

A dummy ticket answers the first two questions cleanly: it names a real flight and it lives in a real booking system a check-in desk or officer can query. It doesn't automatically answer the third, because different checkpoints define acceptable proof differently.

Three checkpoints, three different tests

The confusion in Lena's case, and in most disputes over onward proof, comes from treating these three checkpoints as one. Airlines commonly consult IATA's Timatic database to check a destination's entry conditions before a passenger boards, which is part of why a check-in agent's questions can feel more procedural than an immigration officer's.

Checkpoint Who is asking Basis for asking What typically satisfies it
Airline check-in Ground staff employed by the carrier Carrier liability rules that can fine the airline for boarding undocumented passengers An onward ticket PNR the agent can look up directly
Destination immigration A border or immigration officer The country's own entry law and visa conditions Onward proof, though it's sometimes waived if a visa already required it
Consulate or visa office A visa officer reviewing an application The consulate's internal document checklist Any proof on their list, which sometimes includes a hotel booking alongside a flight

The practical consequence is that a document built for one checkpoint doesn't always travel well to the next. A hotel reservation might satisfy a consulate's checklist without ever answering an airline's check-in question, and a ticket verified at check-in isn't automatically the document an immigration officer wants to see, if they ask at all.

When the checkpoints disagree

The framework matters most when the three tests point in different directions. Take a second illustrative case: a remote worker booked one-way into Bali on a digital nomad income, holding a return ticket six months out that she genuinely intends to use. Her consulate accepted the return ticket without hesitation, since it matched their checklist. Her airline's check-in agent, working from a different rulebook, flagged the same ticket because Indonesian entry stamps are typically issued for a shorter period than the return date shown, and a ticket dated well past the permitted stay can read as unconvincing rather than reassuring. The document was genuine. It simply answered the wrong question for that particular checkpoint.

This is where a dummy ticket often does more work than a real return fare. A PNR dated to match the actual permitted stay, rather than a distant real booking, can look more consistent to a check-in agent even though it costs less. Consistency, not price, is what a compliance-minded reading of these checkpoints rewards.

What doesn't count as proof

A few formats keep failing across all three checkpoints, not because the underlying trip is fake, but because the document itself can't be checked:

  • A screenshot or PDF that isn't tied to a live, queryable booking record.
  • A reservation that already lapsed before the travel date, since a hold that expired can't be verified as current.
  • A confirmation number for an itinerary the checking airline's own system can't find, which happens when a booking was made through an unrelated third party and never synced properly.

None of these are inherently dishonest attempts. They're documents that satisfied a form field but not the actual test the checkpoint applies.

There's a fourth, quieter failure mode worth naming: proof that's technically valid but was never designed to be checked. A booking made through a third-party aggregator, rather than directly with the operating carrier, sometimes doesn't sync into the airline's own reservation system at all. A check-in agent searching by name or record locator finds nothing, not because the traveler lied, but because the intermediary never passed the record through. The fix isn't a better story at the counter; it's booking through a channel that actually populates the airline's system in the first place.

Applying the framework before departure

The practical habit worth building is checking which of the three tests applies before assuming a single document covers all of them. Before a flight involving a visa-restricted destination, it's worth confirming the onward ticket PNR can be verified through the airline's own systems, not just held as a printed confirmation. Where a visa was already approved with onward proof attached, it's also worth checking that the same PNR is still active close to departure, since a hold made months earlier during the application can lapse before the flight itself.

Lena's Istanbul check-in worked because her onward ticket was still live and verifiable at the moment someone actually looked. That's a low bar, but it's the one that matters.

Travelers who need an onward ticket that survives a check-in desk, an immigration counter, and a visa checklist can arrange a verifiable one through Proof of Travel.