India's bilateral visa waiver map, and what it means at hotel check-in

When a foreign guest presents a passport at the front desk, the compliance question underneath the smile is a narrow one: does this person need an Indian visa, and if so, is it on the document. For the leisure traveller with an ordinary passport, the answer is almost always yes, and the check-in agent scans an e-Visa or sticker visa alongside the biodata page. For a smaller but consequential slice of arrivals, the answer is no, because India has a bilateral visa waiver agreement with the issuing country that covers the specific class of passport the guest holds.

That register, maintained by the Ministry of External Affairs, is the source of truth for these exemptions. It currently lists 142 countries with agreements in force. It is also more nuanced than a single visa-free list.

The passport class is the deciding field

The agreements are almost never blanket. Each one specifies the passport types it covers, most commonly some combination of diplomatic, official, service, special and consular passports. Ordinary passports sit outside the register entirely and follow the regular visa regime.

A useful way to read the register is by concentric rings. The innermost ring is 37 countries where only diplomatic passport holders are exempt, which is the narrowest form of the agreement. A broader ring, 37 countries, extends the exemption to service passports as well. The remaining agreements sit somewhere in between, typically covering diplomatic and official passports, and occasionally special or consular categories.

Two countries, Nepal and Bhutan, are separate cases. Their nationals do not require visas at all under long-standing arrangements, and this applies to any passport type they carry. Indian nationals, of course, do not need a visa to enter India.

The maximum stay is not uniform

Ninety days is the modal ceiling, but the register carries a meaningful minority of shorter windows. Bangladesh caps at 45 days. Afghanistan, Croatia, Cote d'Ivoire, Ecuador, Indonesia, Iran, Kazakhstan, Laos, Morocco, Sri Lanka, Suriname, Tajikistan, Turkmenistan and Uruguay cap at 30 days. Brunei sits at 14 days, the shortest in the list. Cambodia, Kuwait, Syria and Uzbekistan sit at 60 days.

A few agreements record no maximum in the register, either because the terms are governed by mission posting rather than tourist-style stays, or because the underlying arrangement is administered outside the standard visa-waiver framework. Belarus, Denmark, Singapore, along with the Nepal and Bhutan cases mentioned earlier, fall in this bucket.

For a front desk, this matters because expected departure and stay length are captured at the point of check-in. A 30-day cap is very different from a 90-day cap when a guest is asking to extend, and the ceiling should be surfaced before the extension is confirmed rather than after.

Why this is a machine-readable problem

Reading the MEA register once and printing a laminated card behind the desk does not survive first contact with reality. Agreements are added, some are renegotiated, and passport series are occasionally re-scoped. Saint Lucia is a recent illustration, with an updated agreement lodged in February 2026. The register is a living document, and any check-in workflow that depends on it needs to treat it as such.

The check-in decision itself, once the passport is scanned, is deterministic. The machine-readable zone yields the issuing country and, in most cases, the passport type code (P for ordinary, D for diplomatic, S for service, and so on). Cross those two fields against the register, and the answer is either a green flag to skip the visa scan, or a prompt to capture the visa document.

The subtlety is in the edge cases. A number of agreements are asymmetric, apply only to personnel posted to a diplomatic mission, or exclude specific purposes of travel. These do not lend themselves to a blanket automated decision, and a good implementation should surface the underlying agreement text alongside the automated recommendation so that the front desk can override where the context calls for it.

The compliance value at the front desk

Form C reporting to the Bureau of Immigration is required for every foreign guest, regardless of whether the visa was waived. The waiver only removes the visa scan from the workflow. It does not remove the compliance obligation. In practice, this means the check-in system still needs the full passport capture, the address, the intended date of departure and the purpose of visit, but it does not need to fail or block when a waiver-eligible guest presents no visa.

Getting this distinction right matters for two reasons. It removes friction for the class of guest most likely to notice it, which includes visiting officials and mission personnel. And it prevents a common failure mode where an over-zealous workflow demands a visa document that does not exist for that traveller, and the check-in stalls until a manager intervenes.

The full country-by-country reference is available on our visa waiver page, with links to each signed agreement on the MEA site.