Overview

An airline ticket capture transfers the authorized funds for a ticket purchase to the merchant account. Captures for ticket purchases must be sent separately from captures for ancillary purchases, such as baggage fees, seat upgrades, and other services purchased at the same time as the ticket. See Ancillary Purchases for information about capturing ancillary purchases.

For a ticket purchase with multiple passengers, you can send a single authorization request, but you must send a separate capture request for each passenger.

Most processors require travel leg information in a capture request, even for direct flights, and each processor limits the maximum number of legs allowed for a trip. The limit can vary by card type. See Travel Legs for information about how to format travel leg fields in a request.

Many processors also require a document type field to specify the purpose of the transaction. For a list of possible values, see Airline Document Type Codes.

Supported Processors

Endpoints

{  "clientReferenceInformation": {    "code": "TC50171_3"  },  "processingInformation": {    "industryDataType": "airline"  },  "orderInformation": {    "amountDetails": {      "totalAmount": "500.00",      "currency": "USD"    }  }}

{  "_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"}

Required Fields

These fields are required for , Barclays, Chase Paymentech Solutions, Elavon, and FDC Nashville Global unless a processor-specific section indicates otherwise. American Express Direct, Lloyds-OmniPay, OmniPay Direct, Streamline, TSYS Acquiring Solutions, and UATP support this transaction through Simple Order only, so their required fields appear in the Simple Order Captures reference.

These optional fields are commonly supported across the REST-capable processors. Each processor also supports additional processor-specific optional fields for travel leg detail, clearing amounts, and exchange ticket data that are not repeated here.