Captures

American Express Direct, Barclays, Chase Paymentech Solutions, Elavon, FDC Nashville Global, Lloyds-OmniPay, OmniPay Direct, Streamline, TSYS Acquiring Solutions, UATP, Visa Platform Connect

American Express Direct supports this transaction through Simple Order only.

This table describes the maximum number of travel legs allowed for each trip, by card type:

This table describes the maximum number of travel legs allowed for each trip, by card type:

When capturing an airline payment with a Visa card, you also need the airlineData_restrictedTicketIndicator field. See Barclays Required Fields.

For a ticket purchase with multiple passengers, recommends sending a separate capture request for each passenger. The original authorization can be a single request.

Capture requests must include all the airline-related information, with the processingInformation.industryDataType field set to airline. You must send ticket purchases and ancillary purchases in separate captures.

Chase Paymentech Solutions uses the travelInformation.transit.airline.transactionType field to distinguish between a ticket purchase and an ancillary purchase. For a ticket capture, set this field to 01.

When the card type is American Express, Chase Paymentech Solutions also requires the document type field. It is ignored for other card types. See Chase Paymentech Solutions Required Fields.

Elavon allows you to 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.

This table describes the maximum number of travel legs allowed for each trip, by card type:

When capturing an airline payment with a Diners Club card, you also need the flight number field. See Elavon Required Fields.

This table describes the maximum number of travel legs allowed for each trip, by card type:

Depending on the card type, FDC Nashville Global requires additional fields for a capture. See FDC Nashville Global Required Fields.

Lloyds-OmniPay supports this transaction through Simple Order only.

This table describes the maximum number of travel legs allowed for each trip, by card type:

OmniPay Direct supports this transaction through Simple Order only. Its required fields appear in the Simple Order Captures reference.

This table describes the maximum number of travel legs allowed for each trip, by card type:

OmniPay Direct also uses reduced interchange fields that vary by card type. See OmniPay Direct Required Fields.

Streamline supports this transaction through Simple Order only.

This table describes the maximum number of travel legs allowed for each trip, by card type:

TSYS Acquiring Solutions supports this transaction through Simple Order only. Its required fields appear in the Simple Order Captures reference.

This table describes the maximum number of travel legs allowed for each trip, by card type:

TSYS Acquiring Solutions allows you to request multiple partial captures for one authorization when using the Visa card type. You must ensure that the total amount for all captures does not exceed the authorized amount. See TSYS Acquiring Solutions Required Fields for the fields required for multiple captures.

UATP supports this transaction through Simple Order only. Its required fields appear in the Simple Order Captures reference.

This table describes the maximum number of travel legs allowed for each trip, by card type:

creates an invoice number for UATP transactions. You can set the invoice date using the optional invoice date field. If you do not include the invoice date field in your request, uses the date the batch file was generated.

You must include a valid ticket document number in either the ticket number field or the reconciliation ID field. See UATP Required Fields for the value and usage requirements.

This table describes the maximum number of travel legs allowed for each trip, by card type:

When capturing an airline payment with a Mastercard, you also need the ticket issuer code field. See Visa Platform Connect Required Fields.

For a ticket purchase with multiple passengers, recommends sending a separate capture request for each passenger. The original authorization can be a single request.

Capture requests must include all the airline-related information, with the processingInformation.industryDataType field set to airline. You must send ticket purchases and ancillary purchases in separate captures.

Chase Paymentech Solutions uses the travelInformation.transit.airline.transactionType field to distinguish between a ticket purchase and an ancillary purchase. For a ticket capture, set this field to 01.

When the card type is American Express, Chase Paymentech Solutions also requires the document type field. It is ignored for other card types. See Chase Paymentech Solutions Required Fields.

This table describes the maximum number of travel legs allowed for each trip, by card type:

Depending on the card type, FDC Nashville Global requires additional fields for a capture. See FDC Nashville Global Required Fields.

Streamline supports this transaction through Simple Order only.

This table describes the maximum number of travel legs allowed for each trip, by card type:

This table describes the maximum number of travel legs allowed for each trip, by card type:

When capturing an airline payment with a Mastercard, you also need the ticket issuer code field. See Required Fields.

This table describes the maximum number of travel legs allowed for each trip, by card type:

When capturing an airline payment with a Visa card, you also need the airlineData_restrictedTicketIndicator field. See Barclays Required Fields.