Airline itinerary data (Level 2 / Level 3)
Achieve several cost and efficiency benefits when supplying detailed airline itinerary data. You can submit these additional details in the authorization or settlement requests, depending on when your booking system generates the ticket number.
Benefits
Benefit | Description |
|---|---|
| Reduced interchange fees | If you are an airline merchant you can qualify lower interchange fees on transactions by providing airline-specific data, such as flight details, ticket numbers, and passenger information. Card networks often offer lower rates for transactions with enhanced data, reducing processing costs. |
| Enhanced fraud detection | Detailed transaction data allows card networks to better authenticate purchases, reducing fraud and chargeback rates. This is especially important for high-ticket airline transactions, where fraud prevention is critical. |
| Improved dispute management | With comprehensive transaction details, card networks can better handle and resolve disputes. This reduces the time and effort you spend managing chargebacks and can lead to faster resolutions. |
| Increased customer trust and satisfaction | Providing enhanced data improves transaction transparency, giving customers more confidence in their purchases. It also leads to more accurate transaction records on your customer's statements, minimizing confusion or disputes. |
| Compliance with industry standards | Card networks increasingly require detailed data in specific industries, like airlines, to maintain compliance with industry standards and processing requirements. |
Parameters
The name of the airline (displayed as it would be on a bill).
An object containing ticket details.
The ticket number.
An object containing the ticket issuer's address.
An array with objects containing flight details. Each object represents one leg of a flight and you can submit up to four flight legs within this array.
Typically, restricted airfares require approval and e-ticket processing within 24 hours of making the reservation, are not transferable if cancelled, and can have specific requirements on when or whether a cancelled ticket can be rebooked. You must define if the ticket is restricted, but this does not affect the payment flows.
An object containing the ticket's issue date.
The name of the travel agent.
The IATA travel agency code.
Billing Settlement Plan invoice reference.
The two character IATA airline code.
An object containing passenger details.
Request example
{
"industryData": {
"type": "airline",
"agentCode": "0",
"agentName": "Agent Name",
"airlineCode": "MY",
"airlineName": "MyAirline",
"invoiceReference": "INV133328465768",
"passenger":{
"code": "12345678",
"firstName": "John",
"lastName": "Passenger"
},
"ticket":{
"number": "123",
"restricted": true,
"issueDate": {
"day": 1,
"month": 1,
"year": 2000
},
"issuerAddress": {
"address1": "Airport venue 1",
"city": "London",
"countryCode": "GB",
"postalCode": "AB1 CD5"
},
"flightDetails": [
{
"carrierCode": "M1",
"flightCode": "501",
"stopOver": false,
"departureAirport": "LON",
"arrivalAirport": "AMS",
"departureDate": {
"day": 1,
"month": 1,
"year": 2000
},
"fareClassCode": "F",
"fareBasisCode": "TMYA",
"taxAmount": 3500
},
{
"carrierCode": "M1",
"flightCode": "501",
"stopOver": false,
"departureAirport": "AMS",
"arrivalAirport": "LON",
"departureDate": {
"day": 1,
"month": 1,
"year": 2000
},
"fareClassCode": "F",
"fareBasisCode": "TMYA",
"taxAmount": 3500
}
],
}
}
}