Airline

Airline data processing extends standard payment processing by letting you submit additional travel data with a transaction. This guide is written for application developers who want to use to integrate credit card processing with airline data into their order management system.

To make use of airline data processing, you must submit additional information, such as:

• Carrier (airline)
• Departure date
• Destination airport
• Purchase date
• Originating airport
• Ticket class
• Travel legs (segments)
• Ticket Number

Confirmation Response

When you send a request with airline data, does not save the airline data. Instead, sends your airline data to the processor. enforces only minimal field validation, which can result in a successful response that did not send the airline data to the processor.

The response field processingInformation.enhancedDataEnabled indicates whether the airline data was sent to the processor. These are the possible field values:

• true: the airline data was not included in the request to the processor.
• false: the airline data was included in the request to the processor.

Travel Legs

Some processors require travel legs in the API service request, even for direct flights. This section describes how to successfully include travel legs in an API request.

Using Travel Legs

To include travel legs in an airline transaction, include one or more travel legs in the legs[] array.

For example, these three travel legs are valid:

"travelInformation": {  "transit": {    "airline": {      "legs": [        {          "carrierCode": "XX"        },        {          "carrierCode": "XZ"        },        {          "carrierCode": "XX"        }      ]    }  }}

Travel Leg Limitations

Some processors limit the number of travel legs for each trip based on the card type.