Payment API Reference

POST

paymentoffer/reservationworkbench/{workbenchID}/payments

For {workbenchID} send the workbench identifier returned in ReservationResponse/Identifer/value in the workbench create response.

Base path:

Pre-production https://api.pp.travelport.com/11/air/

Production https://api.travelport.com/11/air/

Related Content: Ticketing Guide

The Payment step takes place in a ticketing workbench session and sends the payment. It references both the form of payment to be used for the payment and the offer/s to pay for.

Form of payment information must either already be present in the reservation or the workbench. At workbench commit, tickets are issued for any offer payment has been sent for.

Request

Query Parameters

None.

Request Body

If multiple forms of payment have been added, repeat the Payment step for each FOP. The Payment request can include multiple offer IDs, such as for the itinerary and for paid seats, but supports only one FOP.

Response

Example Request

To issue the ticket and an EMD for a paid seat or ancillary, send all applicable offer IDs per this example.

When exchanging a GDS ticket, you can choose to forfeit residual amounts. Send Add FOP with the FormOfPaymentForfeit payload. In the Add Payment request, per the examples below, specify what to forfeit.

Example Response

The response returns a confirmation identifier.