The below tables list the enhancements within the latest release and links to any related implementation guidance within the implementation guide.
|CR 021a||Decommission of AirDocIssue||The decommissioning of the Air Doc Issue Message was decided by the Message Flows Working Group as its used to add payment to an on-hold Order, whereas the best practice approach is to use the Order Change message. See the message flow for creating an Order with deferred payment.|
|CR 007a 007c 007d||Timelimits||The Timelimits Working Group reviewed the time limit fields within the Enhanced and Simplified Distribution messages, updated the annotations and granularity of the time limits.|
|CR 038a||Baggage Associations||As Baggage Allowance structure is common for both Carry-on and Checked bags, this change request is to include the possibility to associate Baggage Allowance information at Dated Operating Leg level, and if we are in a single leg Pax Segment, we should have the possibility to associate it at Pax Segment level.|
|CR 64a||French Regulation for the Refundability of Taxes||The French authorities enforced a decree on the display of information on prices of certain public collective transportation services of passengers affecting specifically Refundable and Unforeseeable taxes, charges and fees.
In case a passenger does not fly, and the ticket is no longer valid, he/she may be entitled to a refund of certain taxes, charges and fees. The regulation requires that the total amount of the refundable taxes/charges, the tax name + the fact that they are refundable if the traveler does not fly be included on the last page before the purchase and visible next to the final price paid, including the invoice.
|CR 065a||Supporting the Additional Collection of GST Information||The Offer Group added the capability for the collection of additional tax information by the Airline to generate a Tax Invoice for a Customer as some regimes (such as India GST) require the Airline to generate a Tax Invoice.|
|Change Request||Item||Description of Change|
|CR 058||NDC Payment Card Encryption||In order to comply with PCI-DSS requirements, and in particular the Requirement 3 regarding Protection of Cardholder Data (cf. Appendix), it is required that sensitive payment card data transmitted in Order requests be encrypted by the Seller with a third party encryption key provided by the Airline in the Offer responses.
This Change Request enables the Airline to pass an encryption key to the Seller in the Offer Response messages, so the Seller can submit encrypted Payment Card Data to the Airline in the OrderCreateRQ and OrderChangeRQ messages.
|CR 123||Shopping Response Ref ID||When integrating with Airlines who do not use the ShoppingResponseID, Seller are forced to pass a value in this field, as it is mandatory in the request messages.
This Change Request is about making the ShoppingResponseRefID optional in the request messages (OrderCreateRQ, OrderChangeRQ, OfferPriceRQ, OrderReshopRQ), adding the OfferRefID in the same data structure and correcting the naming inconsistencies.
|CR 081||Phone Type Number||This Change Request is about setting the data type for the phone number field to text, so the leading "0" and the "+" sign do not get truncated. Also clarifying the usage of each field of the Phone Number data component.|
|CR 100||Order Creation Date||This Change Request introduces the ability for the airline to return the Order Creation Date.|
|CR 106||Order Modification Date||This Change Request introduces the ability for the airline to return the Order Latest Modification Date.|
|CR 118||Remove Terms and TermsList||This Change Request is to remove the Terms and TermsList data elements from the OrderSalesInformationNotifRQ message schema, as there is no need to pass this information to an accounting system.|
|CR 125||Remove Seat Profile from OSIN||This Change Request is to remove the SeatProfileRefID data element from the OrderSalesInformationNotifRQ message schema, as there is no need to pass this information to an accounting system.|