On This Page
FILTER BY TAG

Capture an Airline Ticket Payment

This topic describes how to capture an airline payment.
Before you can capture payment, you must authorize the funds by sending an authorization request. The authorization response includes a request ID in the
requestID
 field. The request ID is required in the capture request. For more information about how to send an authorization request, see the Standard Payment Processing section in the
Payments Developer Guide
.

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 describes 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 describes 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

Ticket Document Number

You must include a valid ticket document number in one of these fields:
  • airlineData_ticketNumber
    : Set the value to the ticket number, which can be up to 12 digits.
    Cybersource
     will append this value with your 3-digit IATA merchant code to send a 15-digit ticket document number to
    UATP
    .
  • ccCaptureService_reconciliationID
    : Set this value to your 3-digit IATA merchant code followed by the ticket number, which can be up to 12 digits, for a total of 15 digits.
If you include both fields in the request, and you use the reconciliation ID for your own reconciliation rather than the ticket document number, you must set the value for the
airlineData_ticketNumber
 as described above and ensure that the first three digits of the reconciliation ID do not include your IATA code.

Endpoint

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

Required Fields for an Airline Capture

See the service description for the value and usage requirements.
See the service description for the value and usage requirements.
Set the value to the
merchant_ref_number
 value used in corresponding authorization request.

Optional Fields for an Airline Capture

Choose from these optional fields to include additional information when capturing an airline payment.

Simple Order Example: Airline Capture

Request
<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.23">
   <merchantID>okgo</merchantID>
   <merchantReferenceCode>R98TV09EN200W</merchantReferenceCode>
   <ccCaptureService run="true">
      <authRequestID>0839543530000172034078</authRequestID>
      <reconciliationID>98R33X7</reconciliationID>
   </ccCaptureService>
   <purchaseTotals>
      <currency>USD</currency>
      <grandTotalAmount>204.78</grandTotalAmount>
   </purchaseTotals>
   <airlineData>
      <passengerName>Johnny Smith</passengerName>
      <leg id="0">
         <carrierCode>AA</carrierCode>
         <departureDate>20061215</departureDate>
         <originatingAirportCode>SJC</originatingAirportCode>
         <destination>SEA</destination>
      </leg>
      <leg id="1">
         <carrierCode>AA</carrierCode>
         <destination>SJC</destination>
      </leg>
   </airlineData>
</requestMessage>
Response
<c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.23">
   <c:requestID>0305782650000167905080</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>
RELATED TO THIS PAGE