On This Page

Airline Processing

This section describes how to use this developer guide and where to find further information.

Audience and Purpose

This guide is written for application developers who want to use the
Cybersource
Simple Order API
 to integrate credit card processing with airline data into their order management system.
Implementing the
Cybersource
 credit card services requires software development skills. You must write code that uses the API request and reply fields to integrate the credit card services into your existing order management system.

Conventions

The following special statements are used in this document:
An
Important
 statement contains information essential to successfully completing a task or learning a concept.

Customer Support

For support information about any service, visit the Support Center:

Recent Revisions to This Document

24.01

This revision contains only editorial changes and no technical updates.

23.02

This revision contains only editorial changes and no technical updates.

23.01

This revision contains only editorial changes and no technical updates.

19.02

This revision contains only editorial changes and no technical updates.

19.01

Visa Platform Connect
: added the
invoiceHeader_merchantDescriptor
 field.

18.04

Visa Platform Connect
: added the following acquirers.
  • Banco Safra
  • BC Card Co., Ltd.
  • Vietnam Technological and Commercial Joint-stock Bank

18.03

Visa Platform Connect
: made technical corrections and improvements to the XML examples.

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

The following are specifications and conditions that apply to a Reseller/Partner enabling its merchants through
Cybersource for Visa Platform Connect (“VPC”) processing
. Failure to meet any of the specifications and conditions below is subject to the liability provisions and indemnification obligations under Reseller/Partner’s contract with Visa/Cybersource.
  1. Before boarding merchants for payment processing on a VPC acquirer’s connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer.
  2. Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer.
  3. Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer.
  4. Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer.
DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS OR OMISSIONS BY THE VISA PLATFORM CONNECT ACQUIRER IN PROCESSING TRANSACTIONS. NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND CONDITIONS IMPOSED BY THE RELEVANT VISA PLATFORM CONNECT ACQUIRER.

Introduction to Airline Processing

Airline data processing exceeds basic payment processing by enabling you to process specific travel data. To make use of this capability, you must submit additional information, such as:
  • Carrier (airline)
  • Departure date
  • Destination airport
  • Purchase date
  • Originating airport
  • Ticket class
  • Travel legs (segments)

Cybersource
 Airline Data Processing

Cybersource
 does not store airline data. Instead, it functions as a pass-through service for the data.
Cybersource
 enforces only the minimal level of field validation.
When you request an airline service,
Cybersource
 responds with certain fields and values to indicate whether the airline data was processed. The response fields for each service are:
  • Authorization:
    ccAuthReply_enhancedDataEnabled
  • Capture:
    ccCaptureReply_enhancedDataEnabled
  • Credit:
    ccCreditReply_enhancedDataEnabled
The possible values for the response fields are:
  • N
    : the airline data was not included in the request to the processor.
  • Y
    : the airline data was included in the request to the processor.
Cybersource
 temporarily disables your account's airline data processing capability and contacts you if your airline data transactions produce batching errors when the information is sent to the processor. If this happens, your request is not rejected, but you receive one of the above listed fields with the
N
 value in the response indicating that airline data in the request has been ignored and not sent to the processor.

Airline 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
airlineData_leg_#_
 fields, starting with the
airlineData_leg_0_
 fields.
Direct flights only use the
airlineData_leg_0_
 fields.
For multiple leg trips, the
airlineData_leg_#_
 fields must start at 0, and you must use consecutive numbers for the additional legs.
If you skip a number,
Cybersource
 ignores the legs that follow the skipped number.
For example, these three travel legs are valid:
<leg id="0">
    <carrierCode>XX</carrierCode>
</leg>
<leg id="1">
    <carrierCode>XZ</carrierCode>
</leg>
<leg id="2">
    <carrierCode>XX</carrier<code>
</leg>

Travel Leg Limitations

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

Visa Platform Connect
 Airline Processing

This section describes how to process airline payments using
Visa Platform Connect
.

Requirement

When you are ready to go live with airline data processing, contact
Cybersource
 Customer Support to have your account configured to process airline data. If your account is not enabled, and you try to send airline transactions, you will receive an error for invalid data.

Related Information

  • See Airline Data for information about and requirements for processing payments that include airline data.
  • See Airline Data Reference Information for a list and description of the different document type and ancillary service category codes that are used when processing payments that include airline data.

Authorizations

This section describes how to process an airline authorization.

Authorization Restrictions

Ticket purchases that include multiple passengers may be included in a single authorization request, but you must make separate capture requests for every passenger.
If any ancillary purchases are made at the same time as the ticket purchase, you may include all items in a single authorization request, but you must separate the ancillary and ticket purchases into their own capture requests.
If any ancillary purchases are made not at the same time as the ticket purchase, you must send separate authorization and capture requests for the ancillary and ticket purchases.

Endpoint

Set the
ccAuthService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for Authorizing an Airline Payment

Include these required fields for authorizing an airline payment.
When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see Relaxed Requirements for Address Data and Expiration Date in Payment Transactions.

Simple Order Example: Authorizing an Airline Payment

Use this example as a reference for authorizing an airline payment.
Request
<merchantID>npr_paymentech</merchantID>
         <merchantReferenceCode>TC42703-1</merchantReferenceCode>
         <billTo>
            <firstName>John</firstName>
            <lastName>Doe</lastName>
            <street1>1295 Charleston Road</street1>
            <city>Mountain View</city>
            <state>CA</state>
            <postalCode>94043</postalCode>
            <country>US</country>
            <email>
customer_email=null@cybersource.com
</email>
         </billTo>
         <purchaseTotals>
            <currency>USD</currency>
            <grandTotalAmount>1.02</grandTotalAmount>
         </purchaseTotals>
         <card>
            <accountNumber>4111111111111111</accountNumber>
            <expirationMonth>12</expirationMonth>
            <expirationYear>2023</expirationYear>
            <cardType>001</cardType>
         </card>
         <ccAuthService run="true">
         	<industryDatatype>airline</industryDatatype>
         </ccAuthService>
Response to a Successful Request
<c:merchantReferenceCode>TC42703-1</c:merchantReferenceCode>
            <c:requestID>6823465362086241603012</c:requestID>
            <c:decision>ACCEPT</c:decision>
            <c:reasonCode>100</c:reasonCode>
            <c:purchaseTotals>
                <c:currency>USD</c:currency>
            </c:purchaseTotals>
            <c:ccAuthReply>
                <c:reasonCode>100</c:reasonCode>
                <c:amount>1.02</c:amount>
                <c:authorizationCode>888888</c:authorizationCode>
                <c:avsCode>X</c:avsCode>
                <c:avsCodeRaw>I1</c:avsCodeRaw>
                <c:authorizedDateTime>2023-04-24T14:28:56Z</c:authorizedDateTime>
                <c:processorResponse>100</c:processorResponse>
                <c:reconciliationID>74375324VGM5S0S6</c:reconciliationID>
                <c:paymentNetworkTransactionID>
                    123456789619999
                </c:paymentNetworkTransactionID>
            </c:ccAuthReply>
            <c:card>
                <c:cardType>001</c:cardType>
            </c:card>
            <c:pos>
                <c:terminalID>111111</c:terminalID>
            </c:pos>

Captures for Ticket Purchases

This section describes how to capture an airline payment for ticket purchases.
Captures for ticket purchases must be made separately from captures for ancillary purchases. For more information about how to capture an ancillary purchase, see Captures for Ancillary Purchases.

Travel Legs

You can use travel leg fields for trips that have multiple legs. For more information on how to use travel leg fields, see Airline Data.

Leg Limitations

Visa Platform Connect
 limits the maximum number of legs for each trip based on card type. This table describes the maximum number of legs for each trip based on card type.
Visa Platform Connect
 Leg Limitations
Supported Card Types
Maximum Number of Trip Legs
American Express
4
Discover
4
Mastercard
4
Visa
4

Endpoint

Set the
ccCaptureService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for Capturing an Airline Payment

Include these required fields to capture an airline payment for ticket purchases.

Card-Specific Field to Capture an Airline Payment

This section includes card-specific information.

Mastercard

Use this card-specific field in addition to the required fields when capturing an authorization with a Mastercard.
airlineData_ticketIssuerCode

Optional Fields for Capturing an Airline Payment

You can use these optional fields to include additional information when capturing an airline payment.
airlineData_carrierName
airlineData_clearingCount
airlineData_clearingSequence
airlineData_creditReasonIndicator
For a list of possible values, see Airline Document Type Codes.
airlineData_electronicTicket
airlineData_numberOfPassengers
airlineData_purchaseType
airlineData_reservationSystem
airlineData_ticketIssuerCity
airlineData_ticketIssuerCode
airlineData_ticketNumber
airlineData_ticketRestrictionText
airlineData_totalClearingAmount

Simple Order Example: Capturing an Airline Payment

Use this example as a reference for capturing an airline payment.
Request
<requestMessage>
    <merchantID>World Wide Travel</merchantID>
    <merchantReferenceCode>R98TV09EN200W</merchantReferenceCode>
        <purchaseTotals> 
            <currency>USD</currency>
            <grandTotalAmount>204.78</grandTotalAmount>
        </purchaseTotals>
    <ccCaptureService run="true">
        <authRequestID>0839543530000172034078</authRequestID>
        <industryDatatype>airline</industryDatatype>
    </ccCaptureService>
    <airlineData>
        <agentCode>98222147</agentCode>
        <agentName>Cyber Vacations</agentName>
        <ticketNumber>02721187251</ticketNumber>
        <restrictedTicketIndicator>0</restrictedTicketIndicator>
        <passengerName>Johnny Smith</passengerName>
        <leg id="0">
            <carrierCode>AA</carrierCode>
            <originatingAirportCode>SJC</originatingAirportCode>
            <departureDate>121511</departureDate>
            <destination>SEA</destination>
            <fareBasis>HL7WNR</fareBasis>
            <couponNumber>1</couponNumber>
            <departureTime>0931</departureTime>
            <departureTimeSegment>A</departureTimeSegment>
            <arrivalTime>1131</arrivalTime>
            <arrivalTimeSegment>A</arrivalTimeSegment>
        </leg>
        <leg id="1">
            <carrierCode>AA</carrierCode>
            <originatingAirportCode>SEA</originatingAirportCode>
            <departureDate>122011</departureDate>
            <destination>SJC</destination>
            <fareBasis>HL7WNR</fareBasis>
            <couponNumber>2</couponNumber>
            <departureTime>1625</departureTime>
            <departureTimeSegment>P</departureTimeSegment>
            <arrivalTime>1837</arrivalTime>
            <arrivalTimeSegment>P</arrivalTimeSegment>
        </leg>
    </airlineData>
</requestMessage>
Response to a Successful Request
<c:replyMessage>
    <c:merchantReferenceCode>R98TV09EN200W</c:merchantReferenceCode>
    <c:requestID>0305782650000167905080</c:requestID>
    <c:decision>ACCEPT</c:decision>
    <c:reasonCode>100</c:reasonCode>
    <c:purchaseTotals>
        <c:currency>USD</c:currency>
    </c:purchaseTotals>
    <c:ccCaptureReply>
        <c:reasonCode>100</c:reasonCode>
        <c:amount>204.78</c:amount>
        <c:reconciliationID>1094820975023470</c:reconciliationID>
        <c:enhancedDataEnabled>y</c:enhancedDataEnabled>
    </c:ccCaptureReply>
</replyMessage>

Captures for Ancillary Purchases

This section describes how to capture an airline payment for ancillary purchases.
Ancillary purchases are any additional services, such as baggage, meals, and paid seats, that your customers can purchase. Captures for ancillary purchases must be made separately from captures for ticket purchases.

Endpoint

Set the
ccCaptureService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for Capturing an Authorization for Ancillary Purchases

Include these required fields to capture an airline payment for ancillary purchases.
Set to
true
.
Set to the
merchant_ref_number
 value used in corresponding authorization request.
industry_datatype

Ancillary Fields for Capturing an Authorization for an Ancillary Purchase

Simple Order Example: Capturing an Authorization for an Ancillary Purchase

Use this example as a reference for capturing an authorization for ancillary purchases.
Request
<requestMessage>
    <merchantID>World Wide Travel</merchantID>
    <merchantReferenceCode>R98TV09EN200W</merchantReferenceCode>
    <purchaseTotals>
        <currency>USD</currency>
        <grandTotalAmount>204.78</grandTotalAmount>
    </purchaseTotals>
    <ccCaptureService run="true">
        <authRequestID>0839543530000172034078</authRequestID>
        <industryDatatype>airline</industryDatatype>
    </ccCaptureService>
    <ancillaryData>
        <ticketNumber>123456789123456</ticketNumber>
        <passengerName>Jane Smith</passengerName>
        <connectedTicketNumber>98765432112345</connectedTicketNumber>
        <creditReasonIndicator>A</creditReasonIndicator>
        <service sequenceNumber="0">
            <categoryCode>MEAL</categoryCode>
            <subCategoryCode>SPM</subCategoryCode>
        </service>
        <service sequenceNumber="1">
            <categoryCode>ENTM</categoryCode>
            <subCategoryCode>DTV</subCategoryCode>
        </service>
    </ancillaryData>
</requestMessage>
Response to a Successful Request
<c:replyMessage>
    <c:requestID>4250238442125000001540</c:requestID>
    <c:decision>ACCEPT</c:decision>
    <c:reasonCode>100</c:reasonCode>
    <c:merchantReferenceCode>R98TV09EN200W</c:merchantReferenceCode>
    <c:purchaseTotals>
        <c:currency>USD</c:currency>
    </c:purchaseTotals>
    <c:ccCaptureReply>
        <c:reasonCode>100</c:reasonCode>
        <c:amount>204.78</c:amount>
        <c:reconciliationID>1094820975023470</c:reconciliationID>
        <c:enhancedDataEnabled>y</c:enhancedDataEnabled>
    </c:ccCaptureReply>
</c:replyMessage>

Follow-On Credits

This topic describes how to process an airline follow-on credit.
This service returns the funds used in the initial capture and requires the original capture ID.

Endpoint

Set the
ccCreditService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for Processing an Airline
Follow-On Credit

Optional Fields for Processing an Airline
Follow-On Credit

This section includes these types of optional fields for an airline
follow-on credit
:

General Optional Fields

You can use these optional fields to include additional information in any airline purchase.
airlineData_carrierName
airlineData_clearingCount
airlineData_clearingSequence
airlineData_creditReasonIndicator
For a list of possible values, see Airline Document Type Codes.
airlineData_electronicTicket
airlineData_numberOfPassengers
airlineData_purchaseType
airlineData_reservationSystem
airlineData_ticketIssuerCity
airlineData_ticketNumber
airlineData_ticketRestrictionText
airlineData_totalClearingAmount

Ancillary Optional Fields

You can use these optional fields to include additional information when requesting an airline
stand-alone credit
 for an ancillary purchase.

Simple Order Example: Processing an Airline Follow-On Credit

Use this example as a reference for processing an airline follow-on credit.
Request
<merchantID>merchantID</merchantID>
<merchantReferenceCode>merchantRefCode</merchantReferenceCode>
<purchaseTotals>
    <currency>USD</currency>
    <grandTotalAmount>1.01</grandTotalAmount>
</purchaseTotals>
<ccCreditService run="true">
    <captureRequestID>captureRequestID</captureRequestID>
</ccCreditService>
Response to a Successful Request
<c:ccCreditReply>
    <c:merchantReferenceCode>Postman-1666641056</c:merchantReferenceCode>
    <c:requestID>6666410568976150003010</c:requestID>
    <c:decision>ACCEPT</c:decision>
    <c:reasonCode>100</c:reasonCode>
    <c:purchaseTotals>
        <c:currency>USD</c:currency>
    </c:purchaseTotals>
<c:ccCreditReply>
    <c:reasonCode>100</c:reasonCode>
    <c:requestDateTime>2022-10-24T19:50:57Z</c:requestDateTime>
    <c:amount>1.01</c:amount>
    <c:reconciliationID>6691571329CM5P99</c:reconciliationID>
</c:ccCreditReply>

Stand-Alone Credits

This topic describes how to process an airline stand-alone credit.
This service distributes funds without requiring a capture ID.
All fields used in the original transaction must be included in your request.

Endpoint

Set the
ccCreditService_run
 field to
true
.
Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.

Required Fields for Processing an Airline
Stand-Alone Credit

Include these required fields to process an airline stand-alone credit.
When relaxed requirements for address data and the expiration date are being used, not all fields in this list are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required. For details about relaxed requirements, see Relaxed Requirements for Address Data and Expiration Date in Payment Transactions.

Optional Fields for Processing an Airline
Stand-Alone Credit

This section includes these types of optional fields for an airline
stand-alone credit
:

General Optional Fields

You can use these optional fields to include additional information in any airline purchase.
airlineData_carrierName
airlineData_clearingCount
airlineData_clearingSequence
airlineData_creditReasonIndicator
For a list of possible values, see Airline Document Type Codes.
airlineData_electronicTicket
airlineData_numberOfPassengers
airlineData_purchaseType
airlineData_reservationSystem
airlineData_ticketIssuerCity
airlineData_ticketNumber
airlineData_ticketRestrictionText
airlineData_totalClearingAmount

Ancillary Optional Fields

You can use these optional fields to include additional information when requesting an airline
stand-alone credit
 for an ancillary purchase.

Simple Order Example: Processing an Airline Stand-Alone Credit

Use this example as a reference for processing an airline stand-alone credit.
Request
<billTo>
     <firstName>John</firstName>
     <lastName>Doe</lastName>
     <street1>1295 Charleston Road</street1>
     <city>Mountain View</city>
     <state>CA</state>
     <postalCode>94043</postalCode>
     <country>US</country>
     <email>
customer_email=null@cybersource.com
</email>
 </billTo>
 <card>
     <accountNumber>4111111111111111</accountNumber>
     <expirationMonth>12</expirationMonth>
     <expirationYear>2023</expirationYear>
 </card>
 <merchantID>lrsebctest</merchantID>
 <merchantReferenceCode>Postman-1666381004</merchantReferenceCode>
 <purchaseTotals>
     <currency>USD</currency>
     <grandTotalAmount>1.01</grandTotalAmount>
 </purchaseTotals>
 <ccCreditService run="true">
     <captureRequestID>6663700818566565103010</captureRequestID>
 </ccCreditService>
Response to a Successful Request
<merchantReferenceCode>Postman-1666374834</merchantReferenceCode>
<requestID>6663748348516429203007</requestID>
<decision>ACCEPT</decision>
<reasonCode>100</reasonCode>
<purchaseTotals>
    <currency>USD</currency>
</purchaseTotals>
<ccAuthReply>
    <reasonCode>100</reasonCode>
    <amount>1.01</amount>
    <authorizationCode>888888</authorizationCode>
    <avsCode>X</avsCode><avsCodeRaw>I1</avsCodeRaw>
    <authorizedDateTime>2022-10-21T17:53:54Z</authorizedDateTime>
    <processorResponse>100</processorResponse>
    <reconciliationID>66737280B9CGUCCP</reconciliationID>
    <paymentNetworkTransactionID>123456789619999</paymentNetworkTransactionID>
</ccAuthReply>
<card>
    <cardType>001</cardType>
</card>
<pos>
    <terminalID>111111</terminalID>
</pos>

Airline Data Reference Information

This section contains reference information that is useful when using Airline Data.

Airline Document Type Codes

To indicate the purpose of a purchase, set the
airlineData_documentType
 field to a value listed in the Code column.
Airline Document Type Codes
Code
Description
01
Passenger ticket
02
Additional collection
03
Excess baggage
04
Miscellaneous charge order (MCO) or prepaid ticket authorization
05
Special service ticket
06
Supported refund
07
Unsupported refund
08
Lost ticket application
09
Tour order voucher
10
Ticket by mail
11
Undercharge adjustment
12
Group ticket
13
Exchange adjustment
14
SPD or air freight
15
In-flight adjustment
16
Agency passenger ticket
17
Agency tour order or voucher
18
Agency miscellaneous charge order (MCO)
19
Agency exchange order
20
Agency group ticket
21
Debit adjustment for duplicate refund or use
22
In-flight merchandise order
23
Catalogue merchandise order
24
In-flight phone charges
25
Frequent flyer fee or purchase
26
Kennel charge
27
Animal transportation charge
28
Firearms case
29
Upgrade charge
30
Credit for unused transportation
31
Credit for class of service adjustment
32
Credit for denied boarding
33
Credit for miscellaneous refund
34
Credit for lost ticket refund
35
Credit for exchange refund
36
Credit for overcharge adjustment
37
Credit for multiple Unused tickets
38
Exchange order
39
Self-service ticket
41
In-flight duty-free purchase
42
Senior citizen discount booklets
43
Club membership fee
44
Coupon book
45
In-flight charges
46
Tour deposit
47
Frequent flyer overnight delivery charge
48
Frequent flyer fulfillment
49
Small package delivery
50
Vendor sale
51
Miscellaneous taxes or fees
52
Travel agency fee
60
Vendor refund or credit
64
Duty free sale
65
Preferred seat upgrade
66
Cabin upgrade
67
Lounge or club access or day pass
68
Agent assisted reservation or ticketing fee
69
Ticket change or cancel fee
70
Trip insurance
71
Unaccompanied minor
72
Standby fee
73
Curbside baggage
74
In-flight medical equipment
75
Ticket or pass print fee
76
Checked sporting or special equipment
77
Dry ice fee
78
Mail or postage fee
79
Club membership fee or temporary trial
80
Frequent flyer activation or reinstatement
81
Gift certificate
82
Onboard or in-flight prepaid voucher
83
Optional services fee
84
Advance purchase for excess baggage
85
Advance purchase for preferred seat upgrade
86
Advance purchase for cabin upgrade
87
Advance purchase for optional services
88
Wi-Fi
89
Packages
90
In-flight entertainment or internet access
91
Overweight bag fee
92
Sleep sets
93
Special purchase fee

Ancillary Service Category Codes

To indicate the service provided in an ancillary purchase, set the
ancillaryData_service_#_categoryCode
 and
ancillaryData_service_#_subcategoryCode
 fields to a value listed in the Ancillary Service Category Code column.
Ancillary Service Category Codes
Ancillary Service Category Codes
Description
BF
Bundled service
BG
Baggage fee
CF
Change fee
CG
Cargo
CO
Carbon offset
FF
Frequent flyer
GF
Gift card
GT
Ground transport
IE
In-flight entertainment
LG
Lounge
MD
Medical
ML
Meal or beverage
OT
Other
PA
Passenger assist fee
PT
Pets
SA
Seat fees
SB
Standby
SF
Service fee
ST
Store
TS
Travel service
UN
Unaccompanied travel
UP
Upgrades
WI
Wi-Fi

Airline Data

Airline data processing goes beyond basic payment transactions by allowing you to process specific travel data. This requires you to submit additional information, such as:
  • Carrier
  • Departure Date
  • Destination Airport
  • Purchase Date
  • Originating Airport
  • Ticket Class
  • Trip Legs

Supported Card Types

  • American Express
  • Discover
  • Mastercard
  • Visa

Supported Acquirers

These
Visa Platform Connect
 acquirers are supported for airline data processing:
  • Agricultural Bank of China (ABC)
  • Ahli United Bank in Bahrain
  • Arab African International Bank (AAIB)
  • Asia Commercial Bank (ACB)
  • Auckland Savings Bank (ASB)
  • Axis Bank Ltd. of India
  • Bangkok Bank Ltd.
  • Bank Muscat of Oman
  • Bank of Ayudhya (BAY)
  • Bank of China (BOC)
  • Bank of Communications
  • Bank Sinarmas (Omise Ltd.)
  • Banque Pour Le Commerce Exterieur Lao (BCEL)
  • Barclays Bank Mauritius Ltd.
  • Barclays Bank Botswana
  • Barclays Bank of Ghana Ltd., Barclays Bank of Tanzania Ltd., and Barclays Bank of Uganda Ltd.
  • Barclays Bank of Kenya
  • Barclays Bank of Zambia
  • Barclays Bank Seychelles
  • BC Card Co., Ltd.
  • BLOM Bank
  • Cathay United Bank (CUB)
  • Citibank Hongkong and Macau
  • Citibank Singapore Ltd.
  • Commercial Bank of Qatar
  • CrediMax (Bahrain)
  • CTBC Bank Ltd.
  • FirstRand Bank
  • Global Payments Asia Pacific
  • Habib Bank Ltd. (HBL)
  • HDFC Bank Ltd. of India
  • I&M Bank
  • ICICI of India
  • Korea Exchange Bank (KEB)
  • Mashreq
  • National Bank of Abu Dhabi (NBAD)
  • National Bank of Kuwait (NBK)
  • National Commercial Bank
  • Network International
  • Overseas Chinese Banking Corp (OCBC)
  • Promerica in Honduras and Nicaragua
  • Qatar National Bank (QNB Group)
  • Raiffeisenbank
  • Rosbank
  • Taishin Bank Ltd.
  • United Overseas Bank (UOB) in Singapore and Vietnam
  • United Overseas Bank (UOB) in Thailand
  • Vietcombank
  • VTB24
  • Wing Lung Bank

Requirement

When you are ready to go live with airline data processing, contact
Cybersource
 Customer Support to have your account configured to process airline data. If your account is not enabled, and you try to send airline transactions, you will receive an error for invalid data.

Related Information

Airline Data Processing

This section describes how to process airline payments.

Requirement

When you are ready to go live with airline data processing, contact
Cybersource
 Customer Support to have your account configured to process airline data. If your account is not enabled, and you try to send airline transactions, you will receive an error for invalid data.

Related Information

  • See Airline Data for information about and requirements for processing payments that include airline data.
  • See Airline Data Reference Information for a list and description of the different document type and ancillary service category codes that are used when processing payments that include airline data.

Relaxed Requirements for Address Data and Expiration Date in Payment Transactions

With relaxed requirements for address data and the expiration date, not all standard payment request fields are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required.