- Introduction to Payments
- Standard Payment Processing
- Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
- Airline Data Processing
- Japanese Payment Options Processing
- Processing Payments Using Credentials
- Using Stored Customer Credentials During a CIT
- Merchant-Initiated Delayed Transaction with PAN
- Merchant-Initiated Incremental Transaction with PAN
- Merchant-Initiated No-Show Transactions with PAN
- Merchant-Initiated Reauthorization Transactions with PAN
- Merchant-Initiated Resubmission Transaction with PAN
- Installment Payments
- Recurring Payments
On This Page
Simple Order API | Visa Platform Connect
Airline Travel Legs
Some processors require travel legs in the API service request. 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. 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>
If you skip a number,
Cybersource
ignores the legs that follow the skipped number.Travel Leg Limitations
Some processors limit the number of travel legs for each trip based on the card type.