Air Booking with Loyalty Program

Air bookings are created using the results from an Air Pricing response. Air Booking requests can be made to include loyalty program memberships, also known as frequent flyer accounts.

Schema

Located in Universal.xsd:

How To

  1. Include the minimum required information for creating an air booking.

  2. Include loyalty program information in the BookingTraveler data and imported from a profile. E.g., 


    <com:BookingTraveler>
    <com:BookingTravelerName First="Maria" Last="Evans"/>
    <com:PhoneNumber Number="010 3999 4777"/>
    <com:Email EmailID="maria.evans@test.com"/>
    <LoyaltyCard Key="xyz123" SupplierCode="XX" CardNumber="AB12345678" SupplierType="Air"/>
    </com:BookingTraveler>
    • One or multiple loyalty cards for different carriers can be entered. Each card number is applied to the segment(s) whose carrier matches that of the loyalty card.
    • Galileo, and Worldspan support cross-accrual, where the passenger flies on Carrier A but specifies a loyalty card for Carrier B. Galileo does not support partial cross-accrual (e.g., where a passenger has two UA segments and specifies a BA card for one segment and an AA card for the other).
    • @PriorityCode supports one alphanumeric character. If the priority code in an imported Universal Record is an alpha character, the priority code is not mapped by Universal API.

  3. A standard Air Booking response is returned. Depending on each supplier's fare policies, loyalty information may or may not affect the fares returned.

    The mileage membership status is returned in the MembershipStatus attribute. It is associated with a loyalty number (any loyalty number) that is added.

 

Exceptions

Apollo does not support the concept of providing a separate cross accrual supplier in the request; this functionality is handled internally. This means that the supplier code provided in the OperatedBy field is not mapped to the Apollo request, and a warning is sent in the response: Multiple vendors cannot be provided for this provider. Cross Accrual will be handled internally by the provider.

Note: Apollo returns the cross accrual supplier the same as the vendor's supplier code in the response. The OperatedBy field is populated in the response to indicate that this is a cross-accrued card instead of a normal loyalty card.

For a more complete list of functionality available from various ACH carriers, see ACH Carriers Functionality. Because functionality for carriers may be subject to change, always confirm functionality directly with the ACH carrier before implementation.

  • Some ACH carriers require loyalty details to be included in the entire shopping flow (Shop/Price/Book).

  • Some ACH carriers limit the number of loyalty cards to one card per booking.

If Loyalty membership data is included in a request, KLM (KL) requires validation that includes a priority code (Interactive Frequent Flyer Validation). KL files seat prices with ATPCO based on loyalty card priority code; therefore, the priority code is used to get the correct seat price for the passenger. If the Seat Map request includes a PNR locator code, Universal API imports the Universal Record (UR) to get frequent flyer details (if available). The frequent flyer details will be mapped from the imported UR, which is not persisted.

This functionality is currently supported only for Galileo, and is not supported on Apollo.