Electronic Travel Authorisations were supposed to make airline document checks easier. In many ways they have: once passport data is in the system, an ETA query can return a clear yes or no without reading a sticker visa.
On 7 April 2026, IATA's Knowledge Hub published a sharper diagnosis: ETAs are ending the validation problem and starting a travel-readiness problem. Travelers confuse visa-free travel with ETA requirements, apply on the wrong site, pay inflated third-party fees, or bind the authorisation to the wrong passport. The failure then lands at check-in, where agents escalate share-code and portal lookups under time pressure.
For airlines and OTAs, the product response is earlier messaging, from booking through manage-my-booking, long before the traditional check-in cut-off. Training every agent harder does not move that window.
This piece is for B2B travel operators. It is not legal advice. Figures below are quoted from named IATA or government sources only.
What IATA actually said
In ETAs Are Ending the Validation Problem, but They Are Starting a New One (7 April 2026), IATA makes several claims worth product teams treating as primary:
Validation got easier. ETAs are, in principle, easier to check than sticker visas. Passport number, nationality, and date of birth are already captured for many airline processes. Connected systems can inquire automatically and get a clear response without interpreting a physical visa.
Confusion grew. IATA notes growing passenger confusion between visa-free travel and ETA requirements. Countries typically roll out ETAs for travelers who previously needed no visa. IATA cites Europeans needing a UK ETA after years of free travel, and the forthcoming European Travel Information and Authorisation System (ETIAS) as the reverse case.
Wrong channels and fraud sites. Official government pages sit alongside third-party services. Some charge fees well above the official cost. IATA states that fraudulent sites have been "well documented" for collecting payment and personal data without submitting any application, leaving passengers who believe they complied to discover the opposite at check-in.
Wrong passport, late discovery. Passengers may not get an ETA on time, apply through wrong channels, or use a passport they will not travel with. IATA describes UK ETA check-in outcomes that force manual escalation, for example assisting a passenger to generate a share code for verification through a government portal.
The check-in window is too short. IATA's operational punchline: an ETA may take only minutes to apply for, but discovering the requirement 40 minutes prior to departure is a different problem. Leading airlines, IATA writes, are shifting focus to travel readiness from booking to travel date.
IATA's INAD cost framing
IATA attributes the following to its latest study of 49 airlines, as stated in the same 7 April 2026 article. These are IATA's figures. They are not SimpleVisa measurements, and they should not be remixed into partner case studies without fresh measurement.
IATA also notes that passenger frustration from denied boarding (missed trips, lost accommodation, broken connections) can be more damaging than the direct INAD cost. For airline checklists focused on that cost stack, see the denied-boarding costs calculator and how airlines reduce denied boarding with visa data. IATA's related explainer is Understanding INADs.
UK ETA as a live carrier example
The UK's ETA regime illustrates IATA's readiness gap in production. These specifics are government-attributed context. They are not a substitute for your carrier charging guide or a legal review.
What product teams should change
Move messaging to booking and manage-my-booking. If the first time a passenger hears "you need an ETA" is at the airport, the airline has already lost the chance to fix it calmly. Surface nationality- and route-specific ETA requirements at booking confirmation, in pre-travel email and push sequences keyed to departure date, and in manage-my-booking, with a status cue (not obtained, applied, verified) where your stack supports it. IATA's framing matches what many OTAs already know commercially: the attach and assist moment is early.
Deep-link official channels, and be explicit about assisted versus DIY. When you send passengers to apply themselves, deep-link the official government app or site (for the UK: GOV.UK and the UK ETA app). When you offer an assisted application as an ancillary, state clearly what you do (form completion, status tracking, support) and that the government decides the outcome. IATA's point about third-party fee confusion and fraud sites is a customer-experience risk even when your own product is legitimate. Copy that names the official fee, for example the Home Office's £20 as of the April 2026 factsheet, reduces "I already paid someone" disputes at check-in.
Enforce passport binding in the journey. ETAs are typically bound to a specific passport. IATA flags passengers who apply with a document they will not travel on. Prompt re-verification if passport details change after booking. Warn that a renewed passport usually means a new authorisation, or an official transfer process where one exists (destination-specific). Align API passenger objects so check-in and authorisation queries use the same document identity.
Separate Timatic-class rules from authorisation status. Timatic, and equivalent rule engines, answer "is an ETA required for this itinerary?" Government interfaces and carrier APIs answer "does this passport hold a valid ETA?" Both are required. Collapsing them into one boolean creates false greens. See Timatic and modern visa APIs: what each is for.
Measure readiness on your own traffic. Define the metrics on your bookings. Do not borrow IATA's ratios as your benchmarks. Useful ones: share of ETA-required bookings with a pre-departure readiness signal before T-24h; volume of gate and check-in document exceptions per 10,000 passengers on ETA routes; median time from first requirement notice to a completed application; contact-centre contacts tagged ETA, fraud site, or wrong passport. Ancillary attach rate stays relevant for commercial teams, covered in Visa ancillary revenue: the complete guide. Readiness is the ops figure that tracks denied-boarding risk.
ETIAS on the horizon
IATA's April 2026 article notes that when ETIAS launches, airlines will run traditional Schengen visa checks alongside ETIAS inquiries during the transition, creating multiple breakpoints. The European Commission stated on 28 April 2026 that ETIAS was scheduled to start in the last quarter of 2026, with the exact date to be communicated later, and that ETIAS was not yet in operation (European Commission, DG Migration and Home Affairs; official ETIAS site).
Build readiness messaging patterns now on live ETA schemes, the UK and others. Reuse them when ETIAS starts, and do not assert an unofficial launch date.
If your airline or OTA still treats ETA compliance as a check-in problem, the IATA framing is a useful internal brief for product and operations leadership. SimpleVisa helps partners surface requirements earlier in the journey, connect assisted application flows where they make sense, and keep destination coverage current as ETA schemes proliferate. Book a demo and bring one ETA-heavy route plus your current T-24h exception rate.
This article is for operational and product planning by travel businesses. It summarises IATA Knowledge Hub content and official government publications. It is not legal advice, not an IATA endorsement of SimpleVisa, and not a substitute for carrier obligations, Timatic or operational manuals, or counsel. Quote IATA figures only with attribution to IATA's published study. Do not present them as SimpleVisa measurements.
IATA Knowledge Hub, 7 Apr 2026 verified 30 Sep 2026 · IATA, Understanding INADs verified 30 Sep 2026 · GOV.UK, 24 Feb 2026 verified 30 Sep 2026 · Home Office ETA factsheet, Apr 2026 verified 30 Sep 2026 · European Commission, 28 Apr 2026 verified 30 Sep 2026 · travel-europe.europa.eu/etias verified 30 Sep 2026