The following hypothetical, labelled Applicant D, concerns a traveller flying one-way from Dubai to Delhi on a Tuesday evening, and it shows how three checkpoints read the same file. A dummy ticket, also called an onward ticket, is a real PNR booked for visa or border-check purposes without paying for the flight. This case study treats it as a document, not a formality.

The scenario: Applicant D

Applicant D holds a passport from a country whose citizens may need an Indian electronic visa. Applicant D has an approved authorisation, a hotel booking for the first four nights and a one-way ticket from Dubai to Delhi. There is no booking out of India. The plan is to travel overland and decide later.

Nothing in this file is unlawful, and it isn't unusual. The difficulty is evidentiary: three separate parties review it, and each wants something different.

This is a constructed example. It describes no real person, and the facts are illustrative only.

Checkpoint one: the carrier

The first review happens at the departure airport. Carriers commonly consult the IATA Timatic database to determine whether a passenger's documents match the destination's entry conditions. The carrier's interest is narrow: it does not want to transport a passenger who may be refused and returned at its expense.

For Applicant D, the carrier will look at the following exhibits:

  1. Passport, in date and in good condition
  2. The approved electronic visa or authorisation
  3. A document showing departure from India, if the carrier's procedure requires one

Exhibit three is where the file is weakest. The carrier's rule may exceed the government's published rule, and the carrier decides at the desk.

Checkpoint two: the issuing authority

The second review is the visa or authorisation stage. Our earlier analysis of the application stage versus the arrival check for India addresses what an application may request. In this case study the relevant point is simpler: the content of an application and the content of a desk check are not identical. A document that satisfies one does not automatically satisfy the other.

Applicants should read the official entry guidance for their own nationality. British passport holders can consult the UK government's India entry requirements. That page is guidance for UK nationals and does not replace the published rules of the issuing authority.

Checkpoint three: the border officer

The third review is at arrival. An officer may ask about the purpose of the visit, the duration and the intended departure. Here the booking has a different function. It is corroboration of a stated intention, not an entry requirement in itself.

Consistency matters more than volume. The officer will compare:

Item Stated by traveller Shown in document
Name As in passport Identical on booking
Duration Roughly the planned stay Departure date inside it
Exit route Where they say they will go next Same city on booking
Accommodation First nights Hotel confirmation

A mismatch in any row is a reason to ask further questions. A match in every row rarely prompts any.

The case also illustrates a point about sequence. The checkpoints are not simultaneous. Carrier review precedes the journey, authority review precedes both in time, and border review follows arrival. A defect is cheapest to correct at the earliest stage, and most expensive at the last. Applicant D therefore corrects the file before departure, not at the counter.

It is worth noting what the file does not need. It doesn't need a paid, flexible or premium fare. It needs a verifiable reservation that is internally consistent. Excess documentation can itself invite questions, so the file should contain what each checkpoint requires and no more.

Remedy and record-keeping

Applicant D resolves the weak exhibit by obtaining a temporary booking that departs India within the expected stay. That is a dummy ticket in the ordinary sense: a verifiable reservation, not a paid fare. For the general distinction, see what the record shows when a dummy ticket is compared with a real one.

Three record-keeping practices follow from this case.

First, retain the confirmation in three forms: electronic, printed and emailed. Second, record the date on which the entry guidance was last read. Third, keep the stated plan and the booking aligned, so that an oral answer never contradicts a document.

Applicant D should also be ready to revise the file if the plan changes. A traveller who extends a stay must do so through the official channel. The original booking is not a substitute for permission.

Limits of this analysis

This case study offers general information. It is not legal or immigration advice, and entry rules differ by nationality and change over time. Where a rule matters to a decision, the traveller should confirm it with the issuing authority and the carrier before departure.

Where a documented exit is required, obtain a verifiable booking for your file.