FILTER BY TAG

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
[]
character
s
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,
Barclays
ignores the legs that follow the skipped number.
This table describes the maximum number of legs for each trip based on card type.
Barclays
Leg Limitations
Supported Card Types
Maximum Number of Trip 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.smartpayfuse.barclaycard
/pts/v2/payments/
{id}
/captures
Test:
POST
https://api.smartpayfuse-test.barclaycard
/pts/v2/payments/
{id}
/captures
The
{id}
is the transaction ID returned in the authorization response.