We appreciate you taking the time to help us.
Governments of several countries require us to collect Advance Passenger Information prior to travel. It's essential that you enter correct details for customers as we're unable to validate this.
Governments ask us to supply information that is mostly found on passports and can include:
Some countries, including USA, will also ask non-citizens to supply a destination address in the country travelled to.
Customers can update their own information in Manage My Booking on ba.com.
Alternatively you can add this into their booking using the API industry standards applicable to your GDS. Please refer to GDS information pages for specific entries.
Executive Club Members can add API details into their profile so whenever their Executive Club number is added into a booking, their details are pulled across automatically.
Sometimes customers may not know exactly where they are staying for the 1st night. In these cases, the API address can be updated with a general itinerary eg.
Street address: Touring the Grand Canyon
City: Grand Canyon
Zip code: 99999
A customer is classed as a transit passenger if they depart within 8 hours of arrival and don't leave the airport. They must have confirmed onward reservations.
Passport information and country of residence for each passenger must be provided, a destination address is not required but must be updated accordingly. eg. transferring to another flight enter the flight number and destination city: TRANSIT TO FLIGHT MX123/MEXICO CITY
If a customer is going on a daytrip to the USA, the same rules as a transit passenger applies. eg. TRANSIT TO FLIGHT BA178/LONDON HEATHROW
Where customers are joining a cruise, the address must still be updated with "transit to" followed by the vessel/cruise name and the US city of cruise embarkation. eg.
Street Address: Transit to MV Princess of the Seas
Zip code: 99999
Group bookings have a specific process and GDS entries to accommodate bookings with 10 or more passengers.
The TSA (Transportation Security Administration) has implemented a program to enhance domestic and international travel, to, from and within the USA. SFPD does not replace the requirement for API data. If customers have provided their full API data, this will also satisfy Secure Flight. The information we provide for SFPD (Secure Flight Passenger Details) includes:
You will be required to collect minimum SFPD for bookings made on applicable routes, either at the time of booking or before ticketing that sector. This must be collected before a customer can check-in.
The TSA have also mandated the Secure Flight program to cover "overflights" as well ie flights categorised as overflying the US and 12 miles off the coast. This currently affects our flights on the following 4 routes (and return sectors): LHR-YUL,
LHR-YYZ, LHR-MEX, LGW-CUN.