- Introduction to Payments
- Standard Payment Processing
- Card Present Connect | Retail Processing
- Authorization with Contact EMV and Online PIN
- Authorization with Contact EMV and Offline PIN
- Card Present Connect | Mass Transit 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
- Merchant-Initiated Recurring Payments with PAN
- Token Management Service Processing
On This Page
REST 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
travel legs in the
legs[]
array. For example, these three travel legs are valid:
"travelInformation": { "transit": { "airline": { "legs": [ { "carrierCode": "XX" }, { "carrierCode": "XZ" }, { "carrierCode": "XX" } ] }
IMPORTANT
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.