This section shows the fields necessary to capture an airline payment.

Leg Limitations

UATP
limits the maximum number of legs for each trip based on card type.
You must include information for the first leg of the trip (leg 0), and you must use consecutive numbers for any additional legs. To do so, replace the
#
character in the field name with a sequential number starting with
0
. For example, for a trip with two legs, set the
airlineData_leg_#
field as
airlineData_leg_0
and
airlineData_leg_1
, for the first and second legs, respectively. If you skip a number,
Cybersource
ignores the legs that follow the skipped number.
This table shows the maximum number of legs for each trip based on card type.
UATP
Leg Limitations
Supported Card Types
Maxiumum Number of Trip Legs
UATP
4

Document Type

When capturing an airline payment, you must use the
airlineData_documentType
field to specify the purpose of the transaction. For all possible values, see Airline Document Type Codes.

Invoice Date

Cybersource
creates an invoice number (INVN) for
UATP
transactions.
You can set the invoice date by inputting it in the value of the optional
airlineData_invoiceDate
field. If you do not use the invoice date field in your request,
Cybersource
uses the date the batch file was generated.
This table shows the different values of the fourteen-digit invoice number.
Invoice Number
Three characters
Two characters
Three characters
Four characters
Two characters
Airline code
Year
Example: 06 for 2006
Day
Example: 000 for January 1
Acquirer: the left-most Four digits of the card number
Spaces

Endpoint

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