On This Page
Airline Processing Developer Guide
This section describes how to use this guide and where to find further information.
- Audience and Purpose
- This guide is written for application developers who want to use theCybersourceREST APIto integrate credit card processing with airline data into their order management system.Implementing theCybersourcecredit 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
- This special statement is used in this document:IMPORTANTAnImportantstatement contains information essential to successfully completing a task or learning a concept.
- Related Documentation
- Visit theCybersourcedocumentation hub to find additional processor-specific versions of this guide and additional technical documentation.
- Customer Support
- For support information about any service, visit the Support Center:
Recent Revisions to This Document
26.10.01
Added ancillary fields in Airline Ancillary Fields.
26.06.01
- Chase Paymentech Solutions
26.02.01
- Elavon
- Added support forElavonancillary purchases. See Elavon Airline Transactions.
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
. 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.Visa Platform Connect
(“VPC”)
processing- 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.
- 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.
- 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.
- 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)
- Ticket Number
Before you can test or process airline payments, your merchant account must be set up for
airline processing, including adding the airline merchant category code (MCC) provided
by your processor. Contact your
Cybersource
account manager for help
with this setup. Prerequisite
To begin processing payments through
Cybersource
, you must first set
up your payment processing system to be REST compliant. If you have not set up
secure communications between your client and server using either JSON Web Token
(JWT)
or HTTP signature
messaging, see the Getting Started with REST Developer
Guide
.Confirmation Response
When you send a request with airline data,
Cybersource
does not save the
airline data. Instead, Cybersource
sends your airline data to the
processor. Cybersource
enforces only minimal field validation, which can
result in a successful response that did not send the airline data to the processor.IMPORTANT
If your airline data transactions produce batching errors when the
information is sent to the processor,
Cybersource
temporarily disables
your account's airline data processing capability and contacts you. If this occurs, your
request is not rejected, but you receive a field in the response indicating that airline
data in the request has been ignored and not sent to the processor.The response field
processingInformation.enhancedDataEnabled
indicates whether the airline data was sent to the processor. These are the possible field values:
- true: the airline data wasnotincluded in the request to the processor.
- false: the airline data was included in the request 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
travel legs in the
legs[]
array. For example, these three travel legs are valid:
"travelInformation": { "transit": { "airline": { "legs": [ { "carrierCode": "XX" }, { "carrierCode": "XZ" }, { "carrierCode": "XX" } ] }
Travel Leg Limitations
Some processors limit the number of travel legs for each trip based on the card type.
Barclays Airline Transactions
Barclays
Airline TransactionsThis section describes the airline payment services you can use when processing with
Barclays
.IMPORTANT
You cannot process a cash advance and airline data in the same transaction.
Supported Card Types
These are the card types that
Barclays
supports:- Maestro (International)
- Maestro (UK Domestic)
- Mastercard
- Visa
Travel Legs
Maximum number of travel legs: 99
Numbering for the travel legs: 0 to 98
You must include information for at least the first leg of the trip (leg 0). You must use consecutive numbers for the legs; do not skip a number. If you skip a number,
Cybersource
ignores the legs that follow the skipped number.Capture an Airline Ticket Payment
This section describes how to capture an airline payment for a ticket purchase.
Before you can capture payment, you must authorize the
funds by sending an authorization request. The authorization response includes a request
ID in the
id
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
Barclays
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
[]
characters
in the field name with a sequential number starting with
0
. For example, for a trip with two legs, set the transit[]
field
as transit0
and
transit1
, 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.
Supported Card Types | Maximum Number of Travel Legs |
|---|---|
Maestro (International) | 99 |
Maestro (UK Domestic) | 99 |
Mastercard | 99 |
Visa | 99 |
Document Type
When capturing an airline payment, you must use the
travelInformation.transit.airline.documentType
field to specify the purpose of the transaction. For all possible values, see Airline Document Type Codes. Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Airline Ticket Capture
- Set the value toairline.
Card-Specific Field for an Airline Ticket Capture
Some card types require additional fields.
Visa
Use this field to capture an airline payment when using a Visa
card.
Optional Fields for an Airline Ticket Capture
- travelInformation.transit.airline.invoiceNumber
- travelInformation.transit.airline.legs[].departTaxAmount
For ancillary fields, see Airline Ancillary Fields.
REST Example: Airline Ticket Capture
Request
{ "clientReferenceInformation": { "code": "refnum123" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "GBP" } }, "travelInformation": { "agency": { "name": "test-airline" }, "transit": { "airline": { "ticketNumber": "123456789", "passengerName": "John Smith", "legs": [ { "originatingAirportCode": "TST", "class": "A", "departureDate": "092525" } ] } } } }
Response
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6823025890736075903954/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6823025890736075903954" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "6823025890736075903954", "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "GBP" } }, "reconciliationId": "67720603YGMSE5JE", "status": "PENDING", "submitTimeUtc": "2025-04-24T02:16:29Z" }
Issue a Stand-Alone Credit
This topic describes how to process a stand-alone credit for an airline payment.
Stand-alone credits are not linked to the original payment. This service distributes
funds without requiring a capture ID.
IMPORTANT
All fields used in the original transaction must be included in your
request.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/credits/Test:
POST
https://apitest.cybersource.com
/pts/v2/credits/Required Fields for an Airline Stand-Alone Credit
- Set the value toairline.
Card-Specific Field for an Airline Stand-Alone Credit
Some card types require additional fields.
Visa
Use this field to capture an airline payment when using a Visa
card.
Optional Fields for an Airline Stand-Alone Credit
- travelInformation.transit.airline.invoiceNumber
- travelInformation.transit.airline.legs[].departTaxAmount
For ancillary fields, see Airline Ancillary Fields.
REST Example: Airline Stand-Alone Credit
Request
{ "clientReferenceInformation": { "code": "12345678" }, "processingInformation": { "industryDataType": "airline" }, "paymentInformation": { "card": { "number": "4111111111111111", "expirationMonth": "01", "expirationYear": "2031" } }, "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "GBP" }, "billTo": { "firstName": "John", "lastName": "Deo", "address1": "1 The Street", "locality": "City", "administrativeArea": "County", "postalCode": "AB12CD", "country": "GB", "email": "[email protected]" } }, "travelInformation": { "agency": { "name": "test-airline" }, "transit": { "airline": { "ticketIssuer": { "address": "123 Happy St" }, "ticketNumber": "123456789", "passengerName": "John Smith", "legs": [ { "originatingAirportCode": "AAA", "departureDate": "03092025" } ] } } } }
Response
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6823025890736075903954/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6823025890736075903954" } }, "clientReferenceInformation": { "code": "12345678" }, "id": "6823025890736075903954", "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "GBP" } }, "reconciliationId": "67720603YGMSE5JE", "status": "PENDING", "submitTimeUtc": "2025-04-24T02:16:29Z" }
Chase Paymentech Solutions Airline Transactions
Chase Paymentech Solutions
Airline TransactionsThis section describes the airline payment services you can use when processing with
Chase Paymentech Solutions
.Supported Card Types and Travel Legs
Chase Paymentech Solutions
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 processor and card type. Supported Card Type | Maximum Number of Travel Legs |
|---|---|
American Express | 4 |
Discover | 99 |
Diners | 99 |
JCB | 99 |
Mastercard | 99 |
Visa | 4 |
Airline Processing Rules
For airline authorization requests, you can combine multiple ticket and ancillary
purchase amounts in one request.
For airline capture requests, each ticket deposit or payment must be captured
separately. You cannot capture multiple deposits or ticket purchases in one
capture. Ancillary captures must be separate from ticket captures.
For airline captures and refunds, you must include the
processingInformation.industryDataType
field with
the value Set the value to airline
.For the best possible interchange rate on Visa card purchases, include the
travelInformation.transit.airline.clearingSequence
and travelInformation.transit.airline.clearingCount
fields in each capture request.The value of the
orderInformation.amountDetails.totalAmount
field should equal the value of the ticket, including all fares, fees,
and taxes. If more than one ticket is authorized with a single
authorization, then the value of the amount field of the deposit may not
always equal the amount of the original authorization.Authorize an Airline Payment
Airline data is not required for authorizations. A single authorization request can cover
multiple tickets, with the authorized amount in the
orderInformation.amountDetails.totalAmount
field equal to the
total of all fares, fees, and taxes.You can include multiple passenger tickets in a single authorization request.
However, you must submit a separate capture request with airline data for each passenger
ticket.
When the customer makes ancillary purchases at the same time as the ticket purchase, you
can include the ticket and the ancillary purchase in a single authorization request.
However, you must submit separate captures for each ticket purchase and ancillary
purchase.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/paymentsTest:
POST
https://apitest.cybersource.com
/pts/v2/paymentsProduction in Saudi Arabia:
POST
https://api.sa.cybersource.com
/pts/v2/paymentsTest in Saudi Arabia:
POST
https://apitest.sa.cybersource.com
/pts/v2/paymentsRequired Fields for an Airline Authorization
- Set the value to the total amount of the fares, fees, and taxes.
REST Example: Airline Authorization
Request
{ "clientReferenceInformation": { "code": "TICKET-123" }, "processingInformation": { "commerceIndicator": "internet" }, "orderInformation": { "billTo": { "country": "US", "administrativeArea": "MI", "locality": "Ann Arbor", "address1": "201 S. Division St.", "postalCode": "48104-2201", "firstName": "John", "lastName": "Smith", "phoneNumber": "999-999-9999", "email": "[email protected]" }, "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "paymentInformation": { "card": { "number": "411111111111XXXX", "expirationMonth": "12", "expirationYear": "2030", "type": "001" } } }
Response to a Successful Request
{ "_links" : { "authReversal" : { "method" : "POST", "href" : "/pts/v2/payments/6461731521426399003473/reversals" }, "self" : { "method" : "GET", "href" : "/pts/v2/payments/6461731521426399003473" }, "capture" : { "method" : "POST", "href" : "/pts/v2/payments/6461731521426399003473/captures" } }, "clientReferenceInformation" : { "code" : "TICKET-123" }, "id" : "6461731521426399003473", "orderInformation" : { "amountDetails" : { "authorizedAmount" : "100.00", "currency" : "usd" } }, "paymentAccountInformation" : { "card" : { "type" : "001" } }, "paymentInformation" : { "tokenizedCard" : { "type" : "001" }, "card" : { "type" : "001" } }, "paymentInsightsInformation" : { "responseInsights" : { "categoryCode" : "01" } }, "processorInformation" : { "systemTraceAuditNumber" : "862481", "approvalCode" : "831000", "merchantAdvice" : { "code" : "01", "codeRaw" : "M001" }, "responseDetails" : "ABC", "networkTransactionId" : "016153570198200", "consumerAuthenticationResponse" : { "code" : "2", "codeRaw" : "2" }, "transactionId" : "016153570198200", "responseCode" : "00", "avs" : { "code" : "Y", "codeRaw" : "Y" } }, "reconciliationId" : "6461731521426399003473", "status" : "AUTHORIZED", "submitTimeUtc" : "2026-04-14T21:37:05Z" }
Unsuccessful Response
{ "submitTimeUtc" : "2020-05-20T21:06:56Z", "status" : "INVALID_REQUEST", "reason" : "INVALID_DATA", "message" : "Declined - One or more fields in the request contains invalid data", "details" : [ { "field" : "stopover_code", "reason" : "INVALID_DATA" } ] }
Capture an Airline Payment
This section describes how to capture airline ticket and ancillary purchases when a
customer is purchasing a ticket and related services on your e-commerce site.
Capture Restrictions
For a ticket purchase with multiple passengers, you can send a single authorization, but
you must send a separate capture for each passenger.
Capture requests must include all the airline related information and the
processingInformation.industryDataType
field set to
airline
. You must send ticket purchases and ancillary purchases
in separate captures.Document Type
You must send the
travelInformation.transit.airline.documentType
field for American
Express capture requests. It will be ignored for other card types. For possible
values, see Airline Document Type Codes.Ancillary Data
Ancillary data includes various purchases and services, such as ticket upgrades,
baggage fees, merchandise purchases, food and beverage, change fees, cancellation
charges, partial airline ticket refunds, and ancillary fee cancellations.
To indicate the service provided in an ancillary purchase, set the
travelInformation.transit.airline.ancillaryInformation.service[].categoryCode
field to an ancillary service category code. For possible values, see Ancillary Service Category Codes.Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Airline Capture
- Set the value to the total amount of the fares, fees, and taxes.
- Set the value toairline.
- Value format:lastname/firstname
- travelInformation.transit.airline.transactionType
- Set the value to one of these possible values:
- 01: Payment is for an airline ticket.
- 02: Payment is for an ancillary purchase.
Card-Specific Field for an Airline Capture
This section includes card-specific information.
American Express
Use this card-specific field in addition to the required fields when capturing an
authorization with a American Express card.
- For possible values, see Airline Document Type Codes.
Optional Fields for an Airline Capture
Choose from these optional fields to include additional information when capturing an
airline payment for tickets and ancillary purchases.
- For possible values, see Ancillary Service Category Codes.
- Include this field and the clearing sequence field for the best exchange rate on Visa.
- Include this field and the clearing count field for the best exchange rate on Visa.
- For possible values, see Airline Document Type Codes.
- travelInformation.transit.airline.invoiceNumber
- Optional. Visa only.
- Available for Visa only.
- Available for Visa only.
For ancillary fields, see Airline Ancillary Fields.
REST Example: Capture a Ticket Payment
Request
This example includes optional fields.
{ "clientReferenceInformation": { "code": "TICKET-123" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "970.50", "currency": "USD" } }, "travelInformation": { "agency": { "code": "AGT001", "name": "Agency/Name" }, "transit": { "exchangeTicketAmount": "12", "airline": { "electronicTicketIndicator": "true", "restrictedTicketIndicator": "1", "carrierName": "UA", "totalInsuranceAmount": "150.00", "passengerName": "Jane Smith", "totalFeeAmount": "75.50", "ticketNumber": "2721187251", "customerCode": "TESTCUSTOMERCODE", "ticketIssueDate": "20261210", "arrivalDate": "12202026", "numberOfPassengers": "1", "creditReasonIndicator": "A", "ticketChangeIndicator": "A", "documentType": "01", "transactionType": "01", "exchangeTicketAmount": "13", "exchangeTicketFeeAmount": "13", "invoiceNumber": "INV982", "legs": [ { "carrierCode": "AAAA", "totalFareAmount": "700.00", "taxAmount": "25", "couponNumber": "1", "class": "FC", "stopoverIndicator": "X", "originatingAirportCode": "JFK", "destinationAirportCode": "LAX", "flightNumber": "12345", "departureDate": "20261219", "departureTime": "2030", "arrivalTime": "1509", "fareBasis": "Y26OPEN12345678", "feeAmount": "20.00", "endorsementsRestrictions": "ENDREST" } ] } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6811595456806928403955/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6811595456806928403955" } }, "clientReferenceInformation": { "code": "TICKET-123" }, "id": "6811595456806928403955", "orderInformation": { "amountDetails": { "totalAmount": "970.50", "currency": "USD" } }, "reconciliationId": "658927039G5GNF51", "status": "PENDING", "submitTimeUtc": "2026-04-10T20:45:45Z" }
REST Example: Capture an Ancillary Payment
Request
This example includes optional fields.
{ "clientReferenceInformation": { "code": "TICKET-123" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "225.50", "currency": "USD" } }, "travelInformation": { "agency": { "code": "AGT001", "name": "Agency/Name" }, "transit": { "airline": { "electronicTicketIndicator": "true", "carrierName": "UA", "passengerName": "Smith/Jane", "totalFeeAmount": "75.50", "ticketNumber": "2721187251", "customerCode": "TESTCUSTOMERCODE", "ticketIssueDate": "20261210", "arrivalDate": "12202026", "numberOfPassengers": "1", "ticketChangeIndicator": "N", "documentType": "45", "transactionType": "02", "invoiceNumber": "INV982", "ancillaryInformation": { "passengerName": "AncillaryPName", "connectedTicketNumber": "AncTicketNumber", "service": [ { "categoryCode": "BG" }, { "categoryCode": "FF" }, { "categoryCode": "IE" }, { "categoryCode": "ML" } ] } } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6811595456806928403955/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6811595456806928403955" } }, "clientReferenceInformation": { "code": "TICKET-123" }, "id": "6811595456806928403955", "orderInformation": { "amountDetails": { "totalAmount": "225.50", "currency": "USD" } }, "reconciliationId": "658927039G5GNF51", "status": "PENDING", "submitTimeUtc": "2026-04-10T20:45:45Z" }
Refund an Airline Payment
This section describes how to issue a refund, which is also known as a follow-on credit.
It returns the payment amount from a completed capture or sale. You must include the
original capture or sale transaction ID.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/refundsTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/refundsThe is the transaction ID
returned in the capture or sale response.
{id}
Required Fields for an Airline Refund
Optional Fields for an Airline Refund
- Set the value to one of these possible values:
- A: Passenger transport ancillary fee cancellation
- B: Airline ticket and passenger transport ancillary fee cancellation
- C: Airline ticket cancellation
- O: Other
- P: Partial refund of airline ticket
- For a list of all possible values, see Ancillary Service Category Codes.
- For a list of all possible values, see Ancillary Service Category Codes.
- For possible values, see Airline Document Type Codes.
- travelInformation.transit.airline.invoiceNumber
- Value format:lastname/firstname
- Available for Visa only.
- travelInformation.transit.airline.transactionType
- Set the value to one of these possible values:
- 01: Payment is for an airline ticket.
- 02: Payment is for an ancillary purchase.
For ancillary fields, see Airline Ancillary Fields.
REST Example: Airline Refund
Request
{ "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "102.21", "currency": "USD" } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/refunds/6805496388936342404953/voids" }, "self": { "method": "GET", "href": "/pts/v2/refunds/6805496388936342404953" } }, "clientReferenceInformation": { "code": "1680549638986" }, "id": "6805496388936342404953", "orderInformation": { "amountDetails": { "currency": "USD" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "712678686G0ONA52", "refundAmountDetails": { "currency": "USD", "refundAmount": "102.21" }, "status": "PENDING", "submitTimeUtc": "2026-04-03T19:20:39Z" }
Elavon Airline Transactions
Elavon
Airline TransactionsThis section describes the airline payment services you can use when processing with
Elavon
.Supported Card Types
This table lists the card types that
Elavon
supports.Supported Card Types |
|---|
Diners Club |
Discover |
JCB Card |
Mastercard |
Visa |
Capture an Airline Payment
This section describes how to capture an airline payment.
You can include an airline ticket purchase and any ancillary purchases in the same
capture request. Ancillary purchases are any additional services, such as baggage,
meals, and paid seats, your customers can purchase.
- Prerequisite
- Before you can capture payment, you must authorize the funds by sending an authorization request. The authorization response includes a request ID in theidfield. 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 thePayments Developer Guide.
Leg Limitations
Elavon
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
[]
characters in the field name with a sequential number starting with
0
. For example, for a trip with two legs, set the transit[]
field as transit0
and
transit1
, 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.
Supported Card Types | Maximum Number of Travel Legs |
|---|---|
Diners Club | 4 |
Discover | 4 |
JCB Card | 4 |
Mastercard | 4 |
Visa | 4 |
Document Type
When capturing an airline payment, you must use the
travelInformation.transit.airline.documentType
field to specify the purpose of the transaction. For all possible values, see Airline Document Type Codes. Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Airline Capture
- Set the value toairline.
Required Fields for an Ancillary Purchase
Include these fields, in addition to the above fields, if there is an ancillary
purchase:
- Include one of the possible values listed in the Ancillary Service Category Codes section.
- To send multiple category codes, you must include additional entries of this field in the array.
Card-Specific Field for an Airline Capture
Card-Specific Field for an Airline Capture
Certain card types require additional fields.
Diners Club
Use this field in addition to the required fields to capture an airline
authorization when using a Diners Club card.
Optional Fields for an Airline Capture
- For a list of all possible values, see Ancillary Service Category Codes.
- For a list of all possible values, see Ancillary Service Category Codes.
REST Example: Airline Ticket Capture
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "350.00", "currency": "USD" } }, "travelInformation": { "agency": { "name": "Test Airline" }, "transit": { "airline": { "ticketIssuer": { "code": "123456789" }, "ticketNumber": "123456798", "restrictedTicketIndicator": null, "passengerName": "John Smith", "legs": [ { "carrierCode": "AA", "originatingAirportCode": "DFW", "class": "First", "stopoverIndicator": "X", "departureDate": "20251231", "destinationAirportCode": "DFW" } ] } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/7659260363866784003812/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/7659260363866784003812" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "7659260363866784003812", "orderInformation": { "amountDetails": { "totalAmount": "350.00", "currency": "USD" } }, "reconciliationId": "69854049CJ7QD97N", "status": "PENDING", "submitTimeUtc": "2025-12-16T23:00:36Z" }
REST Example: Ancillary Capture
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "350.00", "currency": "USD" } }, "travelInformation": { "agency": { "name": "Test Airline" }, "transit": { "airline": { "ticketIssuer": { "code": "123456789" }, "ticketNumber": "123456798", "restrictedTicketIndicator": null, "passengerName": "John Smith", "legs": [ { "carrierCode": "AA", "originatingAirportCode": "DFW", "class": "First", "stopoverIndicator": "X", "departureDate": "20251231", "destinationAirportCode": "DFW" } ] } }, "travelInformation": { "transit": { "airline": { "ancillaryInformation": { "ticketNumber": "123456789", "passengerName": "John Smith", "connectedTicketNumber": "987654321", "service": [ { "categoryCode": "BF" } ] } } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/7659260363866784003812/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/7659260363866784003812" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "7659260363866784003812", "orderInformation": { "amountDetails": { "totalAmount": "350.00", "currency": "USD" } }, "reconciliationId": "69854049CJ7QD97N", "status": "PENDING", "submitTimeUtc": "2025-12-16T23:00:36Z" }
Refund an Airline Payment
This section describes how to issue a refund, also known as a follow-on credit. A refund
is follow-on request that returns the payment amount from a completed capture or sale.
You must have a capture or sale transaction ID.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/refundsTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/refundsThe is the transaction ID
returned in the capture or sale response.
{id}
Required Fields for an Airline Refund
Required Fields for an Ancillary Purchase
Include these fields, in addition to the above fields, if there is an ancillary
purchase:
- Include one of the possible values listed in the Ancillary Service Category Codes section.
- To send multiple category codes, you must include additional entries of this field in the array.
Card-Specific Field for an Airline Refund
Certain card types require additional fields.
Diners Club
Use this field in addition to the required fields to capture an airline
authorization when using a Diners Club card.
Optional Fields for an Airline Refund
- Set the value to one of these possible values:
- A: Passenger transport ancillary fee cancellation
- B: Airline ticket and passenger transport ancillary fee cancellation
- C: Airline ticket cancellation
- O: Other
- P: Partial refund of airline ticket
- For a list of all possible values, see Ancillary Service Category Codes.
- For a list of all possible values, see Ancillary Service Category Codes.
REST Example: Airline Refund
Request
{ "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "102.21" } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/refunds/6805496388936342404953/voids" }, "self": { "method": "GET", "href": "/pts/v2/refunds/6805496388936342404953" } }, "clientReferenceInformation": { "code": "1680549638986" }, "id": "6805496388936342404953", "orderInformation": { "amountDetails": { "currency": "USD" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "712678686G0ONA52", "refundAmountDetails": { "currency": "USD", "refundAmount": "102.21" }, "status": "PENDING", "submitTimeUtc": "2026-04-03T19:20:39Z" }
REST Example: Ancillary Refund
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "orderInformation": { "amountDetails": { "totalAmount": "102.21", "currency": "USD" } }, "travelInformation": { "transit": { "airline": { "ancillaryInformation": { "ticketNumber": "123456789123456", "passengerName": "John Smith", "connectedTicketNumber": "987654321987654", "service": [ { "categoryCode": "1" } ] } } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/refunds/6805496388936342404953/voids" }, "self": { "method": "GET", "href": "/pts/v2/refunds/6805496388936342404953" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "6805496388936342404953", "orderInformation": { "amountDetails": { "currency": "USD" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "712678686G0ONA52", "refundAmountDetails": { "currency": "USD", "refundAmount": "102.21" }, "status": "PENDING", "submitTimeUtc": "2026-04-03T19:20:39Z" }
Issue a Stand-Alone Credit
This topic describes how to process a stand-alone credit for an airline payment.
Stand-alone credits are not linked to the original payment. This service distributes
funds without requiring a capture ID.
IMPORTANT
All fields used in the original transaction must be included in your
request.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/credits/Test:
POST
https://apitest.cybersource.com
/pts/v2/credits/Required Fields for an Airline Stand-Alone Credit
Required Fields for an Ancillary Purchase
Include these fields, in addition to the above fields, if there is an ancillary
purchase:
- Include one of the possible values listed in the Ancillary Service Category Codes section.
- To send multiple category codes, you must include additional entries of this field in the array.
Card-Specific Field for an Airline Stand-Alone Credit
Certain card types require additional fields.
Diners Club
Use this field in addition to the required fields to capture an airline
authorization when using a Diners Club card.
Optional Fields for an Airline Stand-Alone Credit
- Set the value to one of these possible values:
- A: Passenger transport ancillary fee cancellation
- B: Airline ticket and passenger transport ancillary fee cancellation
- C: Airline ticket cancellation
- O: Other
- P: Partial refund of airline ticket
- For a list of all possible values, see Ancillary Service Category Codes.
- For a list of all possible values, see Ancillary Service Category Codes.
REST Example: Airline Stand-Alone Credit
Request
{ "paymentInformation": { "card": { "number": "4111111111111111", "expirationMonth": "07", "expirationYear": "2027" } }, "orderInformation": { "amountDetails": { "totalAmount": "300.00", "currency": "USD" }, "billTo": { "firstName": "John", "lastName": "Smith", "address1": "123 Happy St", "locality": "Sunnyville", "administrativeArea": "TX", "postalCode": "55555", "country": "US", "email": "[email protected]" } } }
Response
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/credits/7678035881236488904805/voids" }, "self": { "method": "GET", "href": "/pts/v2/credits/7678035881236488904805" } }, "clientReferenceInformation": { "code": "1767803588270" }, "creditAmountDetails": { "currency": "USD", "creditAmount": "300.00" }, "id": "7678035881236488904805", "orderInformation": { "amountDetails": { "currency": "USD" } }, "paymentAccountInformation": { "card": { "type": "001" } }, "paymentInformation": { "tokenizedCard": { "type": "001" }, "card": { "type": "001" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "JDWEIJB43Y09", "status": "PENDING", "submitTimeUtc": "2026-01-07T16:33:08Z" }
REST Example: Ancillary Stand-Alone Credit
Request
{ "paymentInformation": { "card": { "number": "4111111111111111", "expirationMonth": "07", "expirationYear": "2027" } }, "orderInformation": { "amountDetails": { "totalAmount": "300.00", "currency": "USD" }, "billTo": { "firstName": "John", "lastName": "Smith", "address1": "123 Happy St", "locality": "Sunnyville", "administrativeArea": "TX", "postalCode": "55555", "country": "US", "email": "[email protected]" } }, "travelInformation": { "transit": { "airline": { "ancillaryInformation": { "ticketNumber": "1234567981234567989", "passengerName": "John Smith", "connectedTicketNumber": "987654321987654", "service": [ { "categoryCode": "1" } ] } } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/credits/7678040337136100204805/voids" }, "self": { "method": "GET", "href": "/pts/v2/credits/7678040337136100204805" } }, "clientReferenceInformation": { "code": "1767804033806" }, "creditAmountDetails": { "currency": "USD", "creditAmount": "300.00" }, "id": "7678040337136100204805", "orderInformation": { "amountDetails": { "currency": "USD" } }, "paymentAccountInformation": { "card": { "type": "001" } }, "paymentInformation": { "tokenizedCard": { "type": "001" }, "card": { "type": "001" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "JQT0PJB4FMOB", "status": "PENDING", "submitTimeUtc": "2026-01-07T16:40:33Z" }
FDC Nashville Global Airline Transactions
FDC Nashville Global
Airline TransactionsThis section describes the airline payment services you can use when processing with
FDC Nashville Global
.Supported Card Types
This table lists the card types
FDC Nashville Global
supports and their
values. When including the paymentInformation.card.type
field, set the field to a
value listed in the card type value column.Supported Card Type | Card Type Value |
|---|---|
American Express | 003 |
Discover | 004 |
Mastercard | 002 |
Visa | 001 |
Authorize an Airline Payment
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, however,
Cybersource
recommends sending a
separate capture request for each passenger.If any ancillary purchases are made at the same time as the ticket purchase, you may
include all the items in a single authorization request, however,
Cybersource
recommends separating the ancillary and ticket purchases into
individual capture requests.If any ancillary purchases are not made at the same time as the ticket purchase,
Cybersource
recommends separating the authorization and capture requests
for the ancillary and ticket purchases. Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/paymentsTest:
POST
https://apitest.cybersource.com
/pts/v2/paymentsProduction in Saudi Arabia:
POST
https://api.sa.cybersource.com
/pts/v2/paymentsTest in Saudi Arabia:
POST
https://apitest.sa.cybersource.com
/pts/v2/paymentsRequired Fields for an Airline Authorization
- Set the value toairline.
Card-Specific Fields for an Airline Authorization
This section includes card-specific information required for an airline
authorization.
American Express
Include these fields in addition to the required fields when using an American
Express card. American Express requires leg fields in the authorization request. For
more information about leg fields, see Airline Travel Legs.
REST Example: Airline Authorization
Request
{ "clientReferenceInformation": { "code": "RTS-Auth" }, "orderInformation": { "billTo": { "country": "US", "lastName": "VDP", "address2": "test", "address1": "201 S. Division St.", "postalCode": "48104-2201", "locality": "Ann Arbor", "administrativeArea": "MI", "firstName": "RTS", "phoneNumber": "999999999", "district": "MI", "buildingNumber": "123", "company": "Visa", "email": "" }, "amountDetails": { "totalAmount": "100.00", "currency": "usd" }, "shipTo": { "firstName": "Michale" } }, "paymentInformation": { "card": { "expirationYear": "2031", "number": "3782822463xxxxx", "expirationMonth": "12", "securityCode": "123", "type": "003" } }, "processingInformation": { "industryDataType": "airline" }, "travelInformation": { "transit": { "airline": { "passengerName": "Michale", "legs": [ { "carrierCode": "123", "fareBasis": "B1", "departureDate": "20260202", "destinationAirportCode": "NY", "originatingAirportCode": "SFO" }, { "carrierCode": "456", "fareBasis": "B2", "departureDate": "20260202", "destinationAirportCode": "SFO", "originatingAirportCode": "SJC" } ] } } } }
Response to a Successful Request
{ "_links": { "authReversal": { "method": "POST", "href": "/pts/v2/payments/6902464806406008803234/reversals" }, "self": { "method": "GET", "href": "/pts/v2/payments/6902464806406008803234" }, "capture": { "method": "POST", "href": "/pts/v2/payments/6902464806406008803234/captures" } }, "clientReferenceInformation": { "code": "1690246480572" }, "id": "6902464806406008803234", "issuerInformation": { "responseRaw": "0110322000000E1000020000000000000100000725005441300026475537344F4B48495131314D38333130303030300001590064003631342030313631373831313031353439343520202020202036363030533036303030303100103232415050524F56414C0012534443523030355959595959" }, "orderInformation": { "amountDetails": { "authorizedAmount": "100.00", "currency": "usd" } }, "paymentAccountInformation": { "card": { "type": "003" } }, "paymentInformation": { "tokenizedCard": { "type": "003" }, "card": { "type": "003" } }, "pointOfSaleInformation": { "terminalId": "00092940" }, "processorInformation": { "electronicVerificationResults": { "phoneNumberRaw": "Y", "emailRaw": "Y", "phoneNumber": "Y", "code": "Y", "postalCodeRaw": "Y", "street": "Y", "postalCode": "Y", "codeRaw": "Y", "streetRaw": "Y", "email": "Y" }, "merchantNumber": "000000000001234", "approvalCode": "831000", "responseCode": "00", "avs": { "code": "Y", "codeRaw": "Y" } }, "reconciliationId": "GU74OKHIQ11M", "status": "AUTHORIZED", "submitTimeUtc": "2026-07-25T00:54:41Z" }
Request
{ "clientReferenceInformation": { "code": "RTS-Auth" }, "processingInformation": { "industryDataType": "airline" }, "paymentInformation": { "card": { "number": "4111111111111111", "expirationMonth": "12", "expirationYear": "2031", "type": "001" } }, "orderInformation": { "amountDetails": { "totalAmount": "102.21", "currency": "USD" }, "billTo": { "firstName": "John", "lastName": "Doe", "address1": "1 Market St", "locality": "san francisco", "administrativeArea": "CA", "postalCode": "94105", "country": "US", "email": "" } } }
Successful Response
{ "_links": { "authReversal": { "method": "POST", "href": "/pts/v2/payments/6917758602546577403955/reversals" }, "self": { "method": "GET", "href": "/pts/v2/payments/6917758602546577403955" }, "capture": { "method": "POST", "href": "/pts/v2/payments/6917758602546577403955/captures" } }, "clientReferenceInformation": { "code": "1691775860306" }, "id": "6917758602546577403955", "orderInformation": { "amountDetails": { "authorizedAmount": "102.21", "currency": "USD" } }, "paymentAccountInformation": { "card": { "type": "001" } }, "paymentInformation": { "tokenizedCard": { "type": "001" }, "card": { "type": "001" } }, "pointOfSaleInformation": { "terminalId": "111111" }, "processorInformation": { "approvalCode": "888888", "networkTransactionId": "123456789619999", "transactionId": "123456789619999", "responseCode": "100", "avs": { "code": "X", "codeRaw": "I1" } }, "reconciliationId": "68209505QL5OEHAU", "status": "AUTHORIZED", "submitTimeUtc": "2026-08-11T17:44:20Z" }
Unsuccessful Response
{ "submitTimeUtc" : "2020-05-20T21:06:56Z", "status" : "INVALID_REQUEST", "reason" : "INVALID_DATA", "message" : "Declined - One or more fields in the request contains invalid data", "details" : [ { "field" : "stopover_code", "reason" : "INVALID_DATA" } ] }
Capture an Airline Ticket Payment
This section describes how to capture an airline ticket payment, such as when a person is
purchasing a ticket on your e-commerce store.
Capture Restrictions
For a ticket purchase with multiple passengers,
Cybersource
recommends
sending separate capture requests for each passenger. The original authorization may
be a single request. When ancillary purchases are made at the same time as the ticket purchase,
Cybersource
recommends sending separate capture requests for the ticket
and ancillary purchases. Airline Travel Legs
FDC Nashville Global
requires you to include travel leg fields in your
requests, even for direct flights. For more information about how to format travel
leg fields, see Airline Travel Legs.Leg Limitations
FDC Nashville Global
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
processor and card type.Supported Card Types | Maximum Number of Travel Legs |
|---|---|
American Express | 4 |
Discover | 4 |
Mastercard | 99 |
Visa | 4 |
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Airline Ticket Capture
Include these required fields to capture an airline payment for tickets.
- Set the value toairline.
Card-Specific Fields for an Airline Ticket
Capture
This section includes card-specific information required to capture a payment for
tickets.
Discover
Include these fields in addition to the required fields when using a Discover
card.
- Set the value toAorP.
- Set the value toAorP.
Mastercard
Include these fields in addition to the required fields when using a Mastercard
card.
Visa
Include this field in addition to the required fields when using a Visa card.
- Set the value to0for refundable.
- Set the value to1for nonrefundable.
Optional Fields for an Airline Ticket Capture
Choose from these optional fields to include additional information when capturing an
airline payment for direct flight tickets.
- Set the value toO(capital letter "O") to indicate the leg of a trip is allowed to stopover. Default value.
- Set the value toXto indicate the leg of a trip is not allowed to stopover.
For ancillary fields, see Airline Ancillary Fields.
REST Example: Airline Ticket Capture
Request
{ "clientReferenceInformation": { "code": "RTS-Bill" }, "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "processingInformation": { "industryDataType": "airline" }, "travelInformation": { "agency": { "name": "Thomascook" }, "transit": { "airline": { "passengerName": "John", "ticketNumber": "asd23", "customerCode": "LDTYOU789", "totalFeeAmount": "200", "planNumber": "49252", "exchangeTicketAmount": "11", "exchangeTicketFeeAmount": "1", "legs": [ { "carrierCode": "AA", "originatingAirportCode": "SFO", "class": "1", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "NY", "exchangeTicketNumber": "ticket12", "endorsementsRestrictions": "Endorsement1234", "feeAmount": "999.99", "taxAmount": "99" }, { "carrierCode": "BB", "originatingAirportCode": "NY", "class": "2", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "SFO", "exchangeTicketNumber": "ticket13", "endorsementsRestrictions": "Endorsement1234", "feeAmount": "999.99", "taxAmount": "99" } ] } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6917768579016106103954/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6917768579016106103954" } }, "clientReferenceInformation": { "code": "RTS-Bill" }, "id": "6917768579016106103954", "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "reconciliationId": "682098706L5PQJ7Y", "status": "PENDING", "submitTimeUtc": "2026-08-11T18:00:58Z" }
Request
{ "clientReferenceInformation": { "code": "RTS-Bill" }, "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "processingInformation": { "industryDataType": "airline" }, "travelInformation": { "agency": { "name": "Thomascook", "code": "123" }, "transit": { "airline": { "passengerName": "John", "ticketNumber": "asd23", "customerCode": "LDTYOU789", "totalFeeAmount": "200", "planNumber": "49252", "exchangeTicketAmount": "11", "exchangeTicketFeeAmount": "1", "ticketIssueDate": "20190202", "arrivalDate": "20260808", "ticketIssuer": { "address": "Silicon Vally" }, "legs": [ { "carrierCode": "AA", "flightNumber": "UA789", "originatingAirportCode": "SFO", "class": "1", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "NY", "fareBasis": "B1", "totalFareAmount": "12", "exchangeTicketNumber": "ticket12", "departureTime": "1720", "endorsementsRestrictions": "Endorsement1234", "arrivalTime": "1920", "arrivalTimeMeridian": "A", "departureTime": "1230", "departureTimeMeridian": "A" }, { "carrierCode": "BB", "flightNumber": "UA788", "originatingAirportCode": "NY", "class": "2", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "SFO", "fareBasis": "B1", "totalFareAmount": "12", "exchangeTicketNumber": "ticket13", "departureTime": "1720", "endorsementsRestrictions": "Endorsement1234", "arrivalTime": "0120", "arrivalTimeMeridian": "A", "departureTime": "2030", "departureTimeMeridian": "A" } ] } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6917775047466121303955/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6917775047466121303955" } }, "clientReferenceInformation": { "code": "RTS-Bill" }, "id": "6917775047466121303955", "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "reconciliationId": "68210417JL5O06RJ", "status": "PENDING", "submitTimeUtc": "2026-08-11T18:11:44Z" }
Request
{ "clientReferenceInformation": { "code": "RTS-Bill" }, "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "processingInformation": { "industryDataType": "airline" }, "travelInformation": { "agency": { "name": "Thomascook" }, "transit": { "airline": { "passengerName": "John", "ticketNumber": "asd23", "customerCode": "LDTYOU789", "totalFeeAmount": "200", "planNumber": "49252", "exchangeTicketAmount": "11", "exchangeTicketFeeAmount": "1", "legs": [ { "carrierCode": "AA", "flightNumber": "UA789", "originatingAirportCode": "SFO", "class": "1", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "NY", "fareBasis": "B1", "exchangeTicketNumber": "ticket12", "departureTime": "1720", "endorsementsRestrictions": "Endorsement1234" }, { "carrierCode": "BB", "flightNumber": "UA788", "originatingAirportCode": "NY", "class": "2", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "SFO", "fareBasis": "B1", "exchangeTicketNumber": "ticket13", "departureTime": "1720", "endorsementsRestrictions": "Endorsement1234" } ] } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6917778689216158003955/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6917778689216158003955" } }, "clientReferenceInformation": { "code": "RTS-Bill" }, "id": "6917778689216158003955", "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "reconciliationId": "68210471JL5O06T1", "status": "PENDING", "submitTimeUtc": "2026-08-11T18:17:49Z" }
Request
{ "clientReferenceInformation": { "code": "RTS-Bill" }, "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "processingInformation": { "industryDataType": "airline" }, "travelInformation": { "agency": { "name": "Thomascook" }, "transit": { "airline": { "passengerName": "John", "ticketNumber": "asd23", "customerCode": "LDTYOU789", "totalFeeAmount": "200", "planNumber": "49252", "exchangeTicketAmount": "11", "exchangeTicketFeeAmount": "1", "restrictedTicketIndicator": "0", "legs": [ { "carrierCode": "AA", "originatingAirportCode": "SFO", "class": "1", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "NY", "exchangeTicketNumber": "ticket12", "departureTime": "1720", "endorsementsRestrictions": "Endorsement1234" }, { "carrierCode": "BB", "originatingAirportCode": "NY", "class": "2", "stopoverIndicator": "O", "departureDate": "20260202", "destinationAirportCode": "SFO", "exchangeTicketNumber": "ticket13", "departureTime": "1720", "endorsementsRestrictions": "Endorsement1234" } ] } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6917788755186225803955/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6917788755186225803955" } }, "clientReferenceInformation": { "code": "RTS-Bill" }, "id": "6917788755186225803955", "orderInformation": { "amountDetails": { "totalAmount": "100.00", "currency": "USD" } }, "reconciliationId": "68211484JL5O0702", "status": "PENDING", "submitTimeUtc": "2026-08-11T18:34:35Z" }
Capture an Ancillary Purchase
Ancillary purchases are any additional services, such as baggage, meals, and paid seats,
your customers can purchase. Captures for ancillary purchases must be separate for
captures for ticket purchases.
FDC Nashville Global
supports up to four
ancillary purchases for each capture. Capture Restrictions
When ancillary purchases are made at the same time as the ticket purchase,
Cybersource
recommends that you send separate capture requests for the
ticket and ancillary purchases. When ancillary purchases are not made at the same time as the ticket purchase,
Cybersource
recommends that you send separate authorization and
capture requests for the ancillary and ticket purchases.Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Ancillary Capture
Ancillary Airline Fields
Choose from these optional ancillary airline fields to include in your capture
request in addition to the required fields listed above.
IMPORTANT
FDC Nashville Global
supports up to four ancillary
purchases for each capture.- For a list of possible values, see Ancillary Service Category Codes.
- For a list of possible values, see Ancillary Service Category Codes.
- Set the value toCfor changing an existing ticket.
- Set the value toNfor a new ticket.
REST Example: Ancillary Capture
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "orderInformation": { "amountDetails": { "totalAmount": "102.21", "currency": "USD" } }, "travelInformation": { "transit": { "airline": { "ancillaryInformation": { "ticketNumber": "123456789", "passengerName": "John Doe", "connectedTicketNumber": "987654321", "service": [ { "categoryCode": "65", "subCategoryCode": "75" } ] } } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6811595456806928403955/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6811595456806928403955" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "6811595456806928403955", "orderInformation": { "amountDetails": { "totalAmount": "102.21", "currency": "USD" } }, "reconciliationId": "658927039G5GNF51", "status": "PENDING", "submitTimeUtc": "2026-04-10T20:45:45Z" }
Refund an Airline Payment
This section describes how to process a refund, also known as a follow-on credit. It
requires you to have the transaction ID from the original airline payment.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/refundsTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/refundsThe is the transaction ID
returned in the capture or sale response.
{id}
Required Fields for an Airline Refund
Optional Fields for an Airline Refund
Choose from these optional fields to include additional information when processing an
airline
refund
.- Set the value to one of these possible values:
- A: Passenger transport ancillary fee cancellation
- B: Airline ticket and passenger transport ancillary fee cancellation
- C: Airline ticket cancellation
- O: Other
- P: Partial refund of airline ticket
For ancillary fields, see Airline Ancillary Fields.
REST Example: Airline Refund
Request
{ "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "102.21" } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/refunds/6805496388936342404953/voids" }, "self": { "method": "GET", "href": "/pts/v2/refunds/6805496388936342404953" } }, "clientReferenceInformation": { "code": "1680549638986" }, "id": "6805496388936342404953", "orderInformation": { "amountDetails": { "currency": "USD" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "712678686G0ONA52", "refundAmountDetails": { "currency": "USD", "refundAmount": "102.21" }, "status": "PENDING", "submitTimeUtc": "2026-04-03T19:20:39Z" }
Visa Platform Connect Airline Transactions
Visa Platform Connect
Airline TransactionsThis 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 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.
Authorize an Airline Payment
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
Production:
POST
https://api.cybersource.com
/pts/v2/paymentsTest:
POST
https://apitest.cybersource.com
/pts/v2/paymentsProduction in Saudi Arabia:
POST
https://api.sa.cybersource.com
/pts/v2/paymentsTest in Saudi Arabia:
POST
https://apitest.sa.cybersource.com
/pts/v2/paymentsRequired Fields for an Airline Authorization
- Set the value toairline.
REST Example: Airline Authorization
Request
{ "processingInformation": { "industryDataType": "airline" }, "paymentInformation": { "card": { "number": "4111111111111111", "expirationMonth": "12", "expirationYear": "2031" } }, "orderInformation": { "amountDetails": { "totalAmount": "500.00", "currency": "usd" }, "billTo": { "firstName": "John", "lastName": "Doe", "address1": "123 Happy St.", "locality": "Sunny Town", "administrativeArea": "CA", "postalCode": "12345-1234", "country": "US", "email": "" } } }
Response to a Successful Request
{ "_links": { "authReversal": { "method": "POST", "href": "/pts/v2/payments/6823009451126309503954/reversals" }, "self": { "method": "GET", "href": "/pts/v2/payments/6823009451126309503954" }, "capture": { "method": "POST", "href": "/pts/v2/payments/6823009451126309503954/captures" } }, "clientReferenceInformation": { "code": "1682300945230" }, "id": "6823009451126309503954", "orderInformation": { "amountDetails": { "authorizedAmount": "500.00", "currency": "usd" } }, "paymentAccountInformation": { "card": { "type": "001" } }, "paymentInformation": { "tokenizedCard": { "type": "001" }, "card": { "type": "001" } }, "pointOfSaleInformation": { "terminalId": "111111" }, "processorInformation": { "approvalCode": "888888", "networkTransactionId": "123456789619999", "transactionId": "123456789619999", "responseCode": "100", "avs": { "code": "X", "codeRaw": "I1" } }, "reconciliationId": "67720603YGMSE5JE", "status": "AUTHORIZED", "submitTimeUtc": "2026-04-24T01:49:05Z" }
Capture an Airline Ticket Payment
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 Capture an Ancillary Purchase.
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 Travel Legs.
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.Supported Card Types | Maximum Number of Travel Legs |
|---|---|
American Express | 4 |
Discover | 4 |
Mastercard | 4 |
Visa | 4 |
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Airline Ticket Capture
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.
Optional Fields for an Airline Ticket Capture
You can use these optional fields to include additional information when capturing an
airline payment.
For ancillary fields, see Airline Ancillary Fields.
REST Example: Airline Ticket Capture
Use this example as a reference for capturing an airline payment.
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "500.00", "currency": "USD" } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6823025890736075903954/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6823025890736075903954" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "6823025890736075903954", "orderInformation": { "amountDetails": { "totalAmount": "500.00", "currency": "USD" } }, "reconciliationId": "67720603YGMSE5JE", "status": "PENDING", "submitTimeUtc": "2026-04-24T02:16:29Z" }
Capture an Ancillary Purchase
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
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/capturesTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/capturesThe is the transaction ID
returned in the authorization response.
{id}
Required Fields for an Ancillary Capture
Include these required fields to capture an airline payment for ancillary
purchases.
Related Information
Optional Fields for an Ancillary Capture
REST Example: Ancillary Capture
Use this example as a reference for capturing an ancillary purchase with the
ancillary fields.
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "500.00", "currency": "USD" } }, "travelInformation": { "transit": { "airline": { "ancillaryInformation": { "ticketNumber": "123456789123456", "passengerName": "John Doe", "connectedTicketNumber": "654321987654321" } } } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/captures/6823030661646093703954/voids" }, "self": { "method": "GET", "href": "/pts/v2/captures/6823030661646093703954" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "6823030661646093703954", "orderInformation": { "amountDetails": { "totalAmount": "500.00", "currency": "USD" } }, "reconciliationId": "67221841NGMV8WOT", "status": "PENDING", "submitTimeUtc": "2026-04-24T02:24:26Z" }
Refund an Airline Payment
This section describes how to process a refund, also known as a follow-on credit. This
service returns funds from the initial capture and requires the original capture ID.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments/{id}
/refundsTest:
POST
https://apitest.cybersource.com
/pts/v2/payments/{id}
/refundsThe is the transaction ID
returned in the capture or sale response.
{id}
Required Fields for an Airline Refund
Optional Fields for an Airline Refund
This section includes these types of optional fields for an airline refund:
General Optional Fields
You can use these optional fields to include additional information in any airline
purchase.
Airline Optional Fields for Ticket Purchases
You can use these optional fields to include additional information when requesting
an airline
credit
for a ticket purchase.Ancillary Optional Fields
You can use these optional fields to include additional information when requesting
an airline
credit
for an ancillary purchase.Related Information
REST Example: Airline Refund
Use this example as a reference for processing an airline refund.
Request
{ "clientReferenceInformation": { "code": "TC50171_3" }, "processingInformation": { "industryDataType": "airline" }, "orderInformation": { "amountDetails": { "totalAmount": "500", "currency": "USD" } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/refunds/6823038625416445403955/voids" }, "self": { "method": "GET", "href": "/pts/v2/refunds/6823038625416445403955" } }, "clientReferenceInformation": { "code": "TC50171_3" }, "id": "6823038625416445403955", "orderInformation": { "amountDetails": { "currency": "USD" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "67722608EGMV6Q7V", "refundAmountDetails": { "currency": "USD", "refundAmount": "500.00" }, "status": "PENDING", "submitTimeUtc": "2026-04-24T02:37:42Z" }
Issue a Stand-Alone Credit
This topic describes how to process a stand-alone credit for an airline payment.
Stand-alone credits are not linked to the original payment. This service distributes
funds without requiring a capture ID.
IMPORTANT
All fields used in the original transaction must be included in your
request.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/credits/Test:
POST
https://apitest.cybersource.com
/pts/v2/credits/Required Fields for an Airline Stand-Alone Credit
Optional Fields for 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.
Airline Optional Fields for Ticket Purchases
You can use these optional fields to include additional information when requesting
an airline
credit
for a ticket purchase.Ancillary Optional Fields
You can use these optional fields to include additional information when requesting
an airline
credit
for an ancillary purchase.REST Example: Airline Stand-Alone Credit
Request
{ "paymentInformation": { "card": { "number": "4111111111111111", "expirationMonth": "12", "expirationYear": "31" } }, "orderInformation": { "amountDetails": { "totalAmount": "500.00", "currency": "USD" }, "billTo": { "firstName": "John", "lastName": "Doe", "address1": "123 Happy St.", "locality": "Sunnyville", "administrativeArea": "CA", "postalCode": "12345", "country": "US", "email": "[email protected]" } } }
Response to a Successful Request
{ "_links": { "void": { "method": "POST", "href": "/pts/v2/credits/6823065885666134104951/voids" }, "self": { "method": "GET", "href": "/pts/v2/credits/6823065885666134104951" } }, "clientReferenceInformation": { "code": "1682306588644" }, "creditAmountDetails": { "currency": "USD", "creditAmount": "500.00" }, "id": "6823065885666134104951", "orderInformation": { "amountDetails": { "currency": "USD" } }, "paymentAccountInformation": { "card": { "type": "001" } }, "paymentInformation": { "tokenizedCard": { "type": "001" }, "card": { "type": "001" } }, "processorInformation": { "approvalCode": "888888", "responseCode": "100" }, "reconciliationId": "74259417PGM9TXHT", "status": "PENDING", "submitTimeUtc": "2026-04-24T03:23:08Z" }
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
travelInformation.transit.airline.documentType
field to a value listed in the Code column.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 |
Airline Ancillary Fields
Ancillary Service Category Codes
To indicate the service provided in an ancillary purchase, set the
travelInformation.transit.airline.ancillaryInformation.service[].categoryCode
and travelInformation.transit.airline.ancillaryInformation.service[].subCategoryCode
fields to a value listed in the Ancillary Service Category Code column.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 Processor
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 Processing for information that shows you how to process payments that include airline data.
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.