The TicketIssue transaction serves the purpose to issue tickets.

All tickets are issued based on an existing PNR. Either the tickets are issued for a fare stored in the PNR or in reference to a previously performed ticket exchange. When issuing tickets for a stored fare, it is possible to issue tickets for all travelers the stored fare refers to or only for a single traveler. However, it is not possible to issue tickets for more than one stored fare at a time or for only a part of the flights a stored fare refers to.  

Although the transaction allows to issue tickets for multiple travelers at once, the recommended procedure is to only ticket one traveler at a time and send separate TicketIssue requests for each combination of stored fare and traveler. The reason is, if several tickets are issued by a single TicketIssue request and the issuance of one of the tickets fails, all tickets issued up to that point still continue to exist – they are not automatically voided. Sending separate request for each ticket to issue allows the client application to precisely control what is to happen, when one of the tickets fails, for instance to assure the previously created tickets are voided.

Instead of specifying a stored fare to ticket directly by its number, it is also possible to specify the flight segments the stored fare refer to. However, it is not possible to only ticket a subset of the flight segments of a stored fare – if one flight segment of a stored fare is specified, all flight segments of the stored fare must be specified (and will be ticketed as set).  

The QualifierGroup allows to override data in the PNR, for instance to specify a different FormOfPayment to be used for ticketing than the one defined in the PNR.

The TicketIssueRS response message provides the complete data of the electronic ticket record created (same as can be retrieved later using TicketImageRQ).