Business Requirements Document NDC Payment and Ticketing

Business Requirements Document NDC Payment and Ticketing 11 June 2014 Document Status: Version 1.5 FINAL Workgroup members or interested parties should send their comments and requests to DDXWG Payment and Ticketing Taskforce (DDX-TF-PT@iata.org) and DDXWG Steering Group (DDX-SG@iata.org)

Revision History Version Date Name Description of Change 0.01 07/01/14 Payment and Ticketing Taskforce 0.1 14/01/14 Payment and Ticketing Taskforce review and updates Pre-draft version Scope, Definitions, Functional Requirements review and updates 0.12 21/01/14 Payment and Ticketing reviews and updates 0.2 19/02/14 John Huang Closed out and addressed comments from other taskforces/sg. Modified scope definitions and diagram. Added new terms and definitions. Modified Principles. Added new functional requirements, message recommendations. Consolidated and added new use cases. 0.3 20/02/14 John Huang Continued to update BRD with additional use cases, error condition chart 0.4 25/02/14 John Huang Removed all references to IATA Reso 722, 725, Changed ticketing/emd to document where appropriate; Updated authentication principle and Payment Time Limit definition to align with OM BRD; Completed Error condition chart as it applies to all functions; Imported message model; Added additional clarification and details to Scope section regarding Ticketless carriers 1.0 7/03/14 Andrei Grintchenko Version 1 PADIS Review Draft PDF 1.1 08/04/14 John Huang Updates following PADIS review and comments 1.1a 14/04/14 Andrei Grintchenko Additional updates following PADIS review and comments 1.2 15/04/14 PT Taskforce Review and finalization of the updates following PADIS review and comments 1.3 12-14/05/14 Andrei Grintchenko Updates following PADIS review calls as agreed and implemented on site 1.4 16/05/14 Andrei Grintchenko Suggested minor edits/ wording alignments following review by IATA payment card expert (track-changes left). 1.5 6/11/14 Andrei Grintchenko Edits and formatting, updated terms and definition section (aligned across all NDC BRDs). Final Extraordinary PADIS review version preparation, PDF version. Business Requirements Document - NDC Payment and Ticketing Page 2 of 49

Table of Contents 1 Introduction... 4 2 Scope... 4 2.1 Field of Application... 4 2.2 Principles... 5 3 References... 6 4 Assumptions... 6 5 Terms and Definitions... 6 6 Functional Requirements... 13 6.1 Functional Requirement Description... 13 6.2 Recommended Messages... 18 6.3 Message Sequence Flows... 19 7 Data Description... 26 8 Non-Functional Requirements... 26 9 Code Lists... 30 Appendix A: List of Use Cases... 31 Use Case 1: Ticket Issuance Single Airline, Single Passenger, Single Form of Payment Credit Card (No Prior Authorization)... 32 Use Case 2: Ticket Issuance Codeshare (Airline Marketed/OA Operated), Multi Pax, Infant-no seat, FOP Gift Card/Miles, Bundled Fare with Ancillary... 34 Use Case 3: EMD-S Issuance Single Airline, Ancillary only, Companion, Multiple Form of payment (Cash Card+ Debit Card)... 37 Use Case 4: Refund Request... 40 Use Case 5: Reissue Request... 42 Use Case 6: ET/EMD Void Request... 44 Use Case 7: ET/EMD System Cancel Request... 46 Error handling chart:... 48 Appendix C: List of Attachments... 49 Business Requirements Document - NDC Payment and Ticketing Page 3 of 49

NDC Standard NDC Standard 1 Introduction IATA PSC Resolution 787, passed in October 2012, recognised that the industry will benefit from the introduction of a standard process for airlines to distribute product offers created within their own systems and to manage the resulting orders. This standard Application Programming Interface (API) is called the New Distribution Capability (NDC) API. In September 2013 the BRD and schema for the shopping part of the NDC process (NDC Airline Shopping BRD), ie up to the point when the customer is ready to accept a product offer, was produced and reviewed by the IATA PADIS Committees. To ensure that end-to-end NDC process is covered, business requirements for subsequent components of NDC Order lifecycle must be produced. This document identifies NDC messaging requirements for Payment and Ticketing process, ie after customer product offer acceptance (NDC order management is addressed in NDC Order Management BRD), and readiness to purchase travel products, and up to airline issuance of accountable documents and payment processing. The document is intended to be submitted to PADIS for review and validation under the PADIS process, to enable NDC XML schemas to be produced and published as IATA PADIS release under the governance of PSC Resolution 783. 2 Scope 2.1 Field of Application The full NDC context is shown in the following diagram with the scope of this BRD indicated. This BRD covers the payment and ticketing processes in the NDC lifecycle when an order has been accepted by the customer and confirmed with the airline and is ready to ticket. Offer Responsible Airline system Participating Offer Airline System Airline Order Airline Product Offer NDC Standard Airline Order Airline Product Offer NDC Standard Aggregator(s) system NDC Standard Proprietary Agency/OTA/ TMC etc Seller system Airline Payment Processing Engine Airline Back office system NDC Standard Scope of BRD Payment and Ticketing Airline Profile Airline Revenue Accounting System Airline Distribution Profile NDC Standard Agency/OTA/TMC etc Seller system Business Requirements Document - NDC Payment and Ticketing Page 4 of 49

The scope covered by this BRD for NDC Shopping is: In Scope: Out of Scope: Issuance of an Accountable Document by an airline (ie electronic ticket, EMD, etc.) Acceptance of payment data. Ticket/document display Ticket/document history display Ticket/document exchange/reissue Ticket/document refund Ticket/document void Ticket/document cancel Payment types in scope: cash, various payment cards, airline currency (* Refer to terms and definition on cash and cash for payment types supported) The remaining proposed standards resulting from the NDC project are out of scope of this document, ie: Airline Profile distribution and usage. Airline Order lifecycle management prior to acceptance of the product offer. Agency back office reporting and settlement process. Revenue accounting process for airline and all involved parties. Ticketing driven by third party providers (ie Aggregators) 1 Ticketless carrier support (* While message naming conventions were developed to be flexible and accommodate carriers that use alternatives to ET and EMD (ie: Ticketless reservations), at the time of authoring this version of the BRD, there is no participating ticketless carrier that can validate and confirm the contents of this BRD can fully support ticketless carrier requirements) Payment types: Cash collected directly by airline, Paypal and Bill Me Later as integrated forms of payment into the purchase path, or when the customer must log into Paypal separately to complete the transaction, Electronic Funds Transfer (all bank transfers, SEPA (direct debit)), AirPlus DBI (Descriptive Billing Information) card, American Express BTA (Business Travel Account). * These forms of payment are out of scope for this version of the BRD and will be included in a future revision. Requirements to integrate with existing processes/ standards 2.2 Principles Seller requests to issue accountable documents (ie ticket/ EMD) Airlines will authenticate the entity sending the NDC message and trust that the identity of upstream entities included in the request message has been authenticated by each entity in turn up the chain to the originator. Parties using the API shall ensure their own compliance with all applicable laws and regulations. Parties using the API shall be responsible for maintaining data confidentiality and be compliant with all applicable privacy laws and regulations. Parties using the API shall be responsible for PCI compliance. It is not in the scope of this document to suggest any particular PCI compliance strategy, methodology or tools, and it is assumed that any party using the API will establish its own compliance strategy using methodology and tools it finds most appropriate. Comment [AG1]: Post PADIS edit. IATA Card Payment SME (agreed with PT TF): It was confirmed that these particular cards are just the types of UATP and Amex cards, and from the payment perspective they do not differ from any other cards. Hence suggest to remove from Out of Scope section. 1 It is recognized that third party (ie Aggregator driven) ticketing on behalf of airlines may be in place in transitional (hybrid) scenarios, and NDC messages maybe used to support it, if applicable and suitable and on bilateral agreements. However, requirements for third party ticketing are outside the scope of NDC. Business Requirements Document - NDC Payment and Ticketing Page 5 of 49

3 References IATA PSC Resolutions: o 787 o 728 A NDC Airline Shopping BRD NDC Order Management BRD PADIS XML 14.1 or other releases current at the time PADIS Codeset 14.1 or other releases current at the time 4 Assumptions Related to the scope of ticketing and payment there are no differences to the process steps whether it is a single, multiple passenger or group booking. 5 Terms and Definitions Term and Definitions identified in this document and in other NDC Business Requirements Documents (ie. Airline Shopping, etc.) are maintained in a separate document NDC Terms and Definitions, owned by DDXWG Steering Group. Terms and definitions are included in this document as an excerpt from NDC Terms and Definitions v.1.2 for easier reading and referencing. Term Definition BRD Reference Accountable Document Acknowledgement Affinity Shopping Aggregator Airline Airline currency Validated official document (such as any type of an airline ticket, or a Standard Traffic Document (STD) or payment voucher) that has a value and must be accounted for. Acknowledges the receipt of a message but does not imply acceptance of the message content A wide search defining a range of criteria including specific interest, destination attributes and defined budget plus date and destination ranges. The business function of distributing a Seller s shopping request to multiple Airlines and aggregating the subsequent responses. Supplies product offers in response to receiving a request from a Seller. Airline refers to itself and any subcontracted entity providing a service to the airline Miles, vouchers, residual value EMD, airline issued gift/cash card Order Management Order Management Airline Shopping Airline Shopping; Payment and Ticketing Airline Shopping; Payment and Ticketing Payment and Ticketing Business Requirements Document - NDC Payment and Ticketing Page 6 of 49

Ancillary Services or Optional Services Anonymous Shopping Ancillary Services are defined in PSC Resolution 787 as anything outside of product attributes (optional or discounted). Ancillary Services may be bundled in the product offer, or offered as additional, a la cart services. For the purposes of this document the term Ancillary Services is sometimes used interchangeably with the term Optional Services. No traveller personal data in the shopping request Airline Shopping; Interline Ancillary Shopping; Payment and Ticketing Airline Shopping API Application Programming Interface Airline Shopping; Payment and Ticketing Attribute Shopping Authentication Bilateral Interface Agreement Bilateral Time Limit Booking Time Limit A search specifying one or more attributes to get more focused results (eg equipment types, Seat types and characteristics, baggage allowance, meals, etc. The process by which a system identifies an individual or a business entity to make sure that the user or the business entity is who they claim to be, based on attributes that are sent in a message. A documented agreement made between the sender and receiver as the basis of the data exchange between systems This agreement defines a number of features which are mandatory or optional within the specification (time outs, message order processing, reject processing) A generic structure for time limits, that is subject to bilateral agreements between parties. Booking time limit is the amount of time within which the booking transaction must be completed (does not include ticketing). NOTE: This definition in Airline Shopping is superseded with the revised definition of Offer Time Limit (revised) as provided in Order Management BRD Airline Shopping Airline Shopping; Payment and Ticketing Interline Ancillary Shopping Airline Shopping (requires a change) and Order Management Airline Shopping (requires change) Cabin A compartment where passenger seats are installed Interline Ancillary Shopping Campaign Identifier Campaign ID is a tracking code used by the airline s advertising analytics system to monitor and optimize the paid advertising by the airline across interactive marketing channels. By including the Campaign ID with shopping requests the online media publisher (MSE, OTA, affiliate partner, booking widget, etc.) can help guide the airline so that the airlines personalization of Order Management Business Requirements Document - NDC Payment and Ticketing Page 7 of 49

Card payment* Cash payment offers can align with any paid advertising that may be present on the publisher s display. Various forms of payment that include: credit card (includes UATP), debit card (PIN based or signature based), pre-paid debit/bank/gift card, cash card where the Airline is the merchant. Refer to IATA Resolution 728 Attachment A for full details on card types and codes. Any payment that is collected by the agent and settled between the Airline and the agent. Refer to IATA Resolution 728 Attachment A for full details on card types and codes. Payment and Ticketing Payment and Ticketing CBT Corporate Booking Tool Airline Shopping Check/Cheque* Commercial Agreement ID Corporate ID Personal or bank issued order for transfer of money. Refer to IATA Resolution 728 Attachment A. Code or ID referenced by ORA or POA in message exchange which refers to a previously created bilateral agreement. A SPA is an example. An ID provided by an airline to uniquely identify a corporate location for which a commercial arrangement exists. Payment and Ticketing Interline Ancillary Shopping Order Management, plus change to Airline Shopping Deposit Time Limit Time by which a deposit must be paid for an Order. Airline Shopping (requires change) and Order Management Distribution Channel Provider An entity that has the capability to interface with an airline s dynamic shopping API enabling distribution of airline product offers across one or multiple channels. For the purposes of this document it is assumed that such provider shall use industry standard NDC XML messages to communicate with airlines dynamic shopping API, and may act as a content aggregator. Airline Shopping FQTV Frequent Traveler Airline Shopping Group Booking Inventory Guarantee Time Limit An Order made under a group name without individual passenger names at the point of creation The time that inventory for a specified product offer is guaranteed as available. The inventory held must be converted into a completed order before the time limit expires otherwise the guarantee is lost. Held Inventory is referenced by an Inventory Guarantee identifier (equivalent in business terms to the legacy ITAREQ Conversation ID ). In the context of Interline Ancillary Shopping, this term is defined as the time window (or Order Management Order Management; Interline Ancillary Shopping Business Requirements Document - NDC Payment and Ticketing Page 8 of 49

Inventory Guarantee Identifier Leg Marketing Carrier Meta Search deep link Meta Search shallow link MSE ( Meta search Engines) final date) identified by the ORA or POA where inventory will be held prior to booking. An unique identifier issued by an Airline to reference that inventory for a specified offer will be guaranteed as available for a period The operation between a departure station and the next arrival station The carrier that sells with its own code as part of a code share agreement on a flight that is actually operated by another carrier. A link to an airline's or OTA's itinerary purchase page enabling the user to purchase a specific itinerary offer. A link to an airline's or OTA's shopping results page listing multiple flight options for a pre-specified city pair and dates, as well as upsell / cross-sell products MSE redirect their users to an airline or Online Travel Agent for the creation of an Airline Order. A MSE is not involved in servicing the resulting order - this is done by the OTA or Airline. Order Management Interline Ancillary Shopping Interline Ancillary Shopping Airline Shopping Airline Shopping Order Management Multi Leg Flight A flight comprised of more than one leg Interline Ancillary Shopping Naming Time Limit Time by which an Order, must be completed with individual passenger names. Order Management OAL Other AirLine Airline Shopping Offer ID Offer item Offer ID facilitates the tracking and verification of individually priced offer(s) selected from the shopping response. Only the Offer IDs of the ORA (Offer Responsible Airline) are returned in shopping responses. Offer ID is unique to each individually priced offer in the shopping response even if the offer price is zero. OfferID may be specific to individual passengers in the offer, and may be associated with a segment or a journey. The set of Offer IDs returned in a response are referenced by a Shopping Response ID. One or more products that has one price, eg a product bundle Airline Shopping; Payment and Ticketing Order Management Business Requirements Document - NDC Payment and Ticketing Page 9 of 49

Offer Responsible Airline (ORA) Offer Time Limit Offer Time Limit (revised) Operating Carrier Order Offer Responsible Airline: The airline responsible for returning a combined offer, including participating airline offers, to the requesting entity Offer Time Limit is the amount of time within which offers in a shopping response maybe reserved. Upon expiring, a new shopping request must be sent. NOTE: This definition in Airline Shopping is superseded with the revised definition of Offer Time Limit (revised) as provided in Order Management BRD The time within which offers must be converted into completed Orders. On expiry a new shopping transaction is required. This definition supersedes both Offer and Booking Time Limit definitions in the Shopping BRD. Offer Time Limit is mandatory. The carrier that holds the Air Operator s Certificate for the aircraft used for that flight An Order is a uniquely identified record of the agreement of one party with another to receive products and services under specified terms and conditions. Order supports the sale of a flexible range of airline products and services that are not necessarily journey based (eg subscription services). A PNR, super PNR and ticket are all today s versions of airline implementations of aspects of an Order. An Order will contain 1 or more Order Items each with an identifier that is unique within an Airline s Order Management system. An Order may support nonhomogeneity, ie each passenger in an Order may hold different sets of order items at different prices. Airline Shopping; Interline Ancillary Shopping; Payment and Ticketing Airline Shopping (requires change) Order Management; Interline Ancillary Shopping; Payment and Ticketing Interline Ancillary Shopping Order Management; Payment and Ticketing Order item A selected Offer item. Order Management Order Management Order Management is the process of taking, amending, tracking and fulfilling requests for an airline s products and services. Order Management OSI Other Service Information Airline Shopping OTA Online Travel Agency Airline Shopping Participating Offer Airline (POA) Participating Offer Airline: An airline other than the Offer Responsible Airline involved in a product offer Airline Shopping; Interline Ancillary Shopping; Payment and Ticketing Payment Time The deadline by which a commitment to pay must be Order Management; Business Requirements Document - NDC Payment and Ticketing Page 10 of 49

Limit Personalised Shopping made for the items in the order. This includes ticketless transactions and other accountable documents (ie EMD. Payment Time Limit and Ticket Time Limit may be the same in most cases; however, Payment Time Limit expands to include ticketless transactions and other accountable documents. Payment Time Limit is mandatory. Traveller consents to include personal data in the shopping request Interline Ancillary Shopping; Payment and Ticketing Airline Shopping PNR Passenger Name Record Airline Shopping; Payment and Ticketing Price Guarantee Time Limit Product Bundle Referrer Identity Seller Service Item Period for which an Offer price is guaranteed. On expiry an Offer may be re-priced up to the point an accountable document is issued. A Price Guarantee cannot extend beyond the Offer Time Limit unless the Order has been created. Where several products are offered for sale as one product. NOTE: This definition has evolved in Order Management BRD, and has the same meaning as Offer Item Identifies to the aggregator or the airline, the specific commercial contract under which a particular message should be tracked; for example, is the message related to (A) the x cents per click for traffic from Indonesia or (B) the y % per ticket for each booking that originates from Japan. Creates shopping requests to Airlines on behalf of a customer and displays the subsequent product responses for review An airline service item is a product or a service that can be separately delivered and uniquely described by an airline. It is referenced by an ID that is unique within an airline. A service may be sold separately in a single offer/ order item or sold bundled with other service items in a single offer/order item (eg a return price consisting of inbound and outbound services). Airline Shopping (requires change) and Order Management Airline Shopping Order Management Airline Shopping; Payment and Ticketing Order Management Service Time Limit Settlement Time limit for EMD creation. May be different from Payment Time Limit Third parties that provide settlement services between agent and airlines. Could include ARC, BSP, TCH, Interline Ancillary Shopping Payment and Ticketing Business Requirements Document - NDC Payment and Ticketing Page 11 of 49

providers MoneyDirect, eenet, etc. Shopping Shopping Basket Shopping Response ID A process whereby a Seller is able to request offers from the airlines (ie flight and ancillaries) based on its desired search criteria and receive offers corresponding to its request. There are various types of shopping, including, for example, Personalized/ Anonymous and Attribute/ Affinity shopping types as defined in this document. A Shopping Basket is e-commerce software that allows visitors to an internet site to select items for eventual purchase Shopping Response ID facilitates the tracking of what was offered and is an identifier unique to the source airline for a set of product offers returned in response to a shopping request. Shopping Response ID may be comprised of an Offer ID corresponding to an individual flight and/or ancillary service product offer that make up the offer. See Appendix D for scenarios illustrating use of this identifier. Airline Shopping Airline Shopping Airline Shopping SSR Special Service Request Airline Shopping Ticket Time Limit Ticketing Ticket Time Limit is the amount of time which the booking maybe held until it must be ticketed or other accountable documents issued (eg EMD). The process of issuing any type of an accountable document to fulfil an airline order. Airline Shopping Payment and Ticketing TMC Travel Management Company Airline Shopping XML Extensible Markup Language Airline Shopping Business Requirements Document - NDC Payment and Ticketing Page 12 of 49

6 Functional Requirements 6.1 Functional Requirement Description 6.1.1 Ticketing Request Ref # Category Ticketing Requirements Description 1.1 Airline Document IssueRequest 1.2 Airline Document Issue Response Request to include: Order Id, Order Item ID, PNR reference, Agency id, aggregator id, commission info (rate, type, amount), Promotional code, contact email address(s), Passenger name and type, FOP information (unmasked, encryption required to comply with PCI requirements) (* Refer to data dictionary for optional vs. mandatory fields) Response to include: FOP information (Card payment data needs to be masked to comply with PCI requirements), fare amounts (base, total, equivalent), number of additional services, airline indexing field, booking agent id, carrier fee data, commission info (rate, type, amount), consumed at issuance indicator, coupon info (number, itinerary sequence nbr, status, value, segment id), ticket/doc nbr, ticketing mode indicator, total flt value coupons, tour code, true origin/destination city codes, validating airline designator and waiver code, customer file ref, customer id, date of issue, excess baggage info, fare basis/tkt designator, unstructured fare calc info, structured fare component info, fee owner airline designator, frequent flier info, invoice nbr, net reporting indicator, in connection doc/cpn and qualifier, issuing agent id, issuing agency/airline, ticket/doc indicators (non-commissionable, non endorsable, non interlineable, non-refundable, non reissuable/exchangeable, penalty restriction), nonrefundable/no value/penalty info,, total number of ticket or documents issued, original issue info, FOIDs, passenger name, type code, specific data, present to/at info, present credit/debit card ind, AirDocIssueRQServi ce operation to request an Airline to issue documents such as: flight (ET) and/or ancillary (EMD) AirDocDisplayRS Service operation Airline Ticket Response Business Requirements Document - NDC Payment and Ticketing Page 13 of 49

Ref # Category Ticketing Requirements Description pricing info, product characteristic info, promotional code, rate of exchange, RFIC/RFISC, refund calc indicator, ticketing iso country code, reissued flown flt coupon data, response comments, servicing airline/system provider, sold airline info, statistical code, stopover code, tax/fee/charge info, tax on commission on indicator, tax on EMD qualifier, tax/fee/charge data at coupon level, order id, offer id, PNR reference(s), endorsements/restrictions, document type, errors (Transaction and Order/PAX Order Item ID/FOP levels), transaction status (Pending, Completed) 1.3 Airline document display request 1.4 Airline document display response Request to include: Order Id, Order Item, Requestor id, aggregator id, requestor iso country code, ticket document number, PNR reference, FF number, Credit card number, FOID, Passenger name, Airline carrier code Flight date, Origin and Destination, and flight number There should be a flag in the message that allows the ability to filter the results to return: (ET only, EMD only, or all) Response to include: FOP information, fare amounts (base, total, equivalent), booking agent id, carrier fee data, commission info, consumed at issuance indicator, coupon info (number, itinerary sequence nbr, status, value, segment id), customer file ref, customer id, date of issue, excess baggage info, fare basis/tkt designator, unstructured fare calc info, structured fare component info, fee owner airline designator, frequent flier info, invoice nbr, net reporting indicator, in connection doc/cpn and qualifier, issuing agent id, issuing agency/airline, ticket/doc indicators (non-commissionable, non endorsable, non interlineable, non-refundable, non reissuable/exchangeable, penalty restriction), nonrefundable/no value/penalty info, number of booklets issued, nbr of tkt/doc nbrs, original issue info, FOIDs, passenger name, type code, specific data, PNR reference(s), present to/at info, present credit/debit card ind, pricing info, product AirDocDisplayRQ AirDocDisplayRS Business Requirements Document - NDC Payment and Ticketing Page 14 of 49

Ref # Category Ticketing Requirements Description characteristic info, promotional code, rate of exchange, RFIC/RFISC, refund calc indicator, ticketing iso country code, reissued flown flt coupon data, response comments, servicing airline/system provider, sold airline info, statistical code, stopover code, tax/fee/charge info, tax on commission on indicator, tax on EMD qualifier, tax/fee/charge data at coupon level, ticket/doc nbr, ticketing mode indicator, total flt value coupons, tour code, true origin/destination city codes, validating airline designator and waiver code, order id, order item, offer id, endorsements/restrictions, document type, errors (Transaction level). Returns: Similar name list response A similar name list might be returned if the requestor uses FF number or CC number to request the display. If a person has more than one ticket/doc with that FF number, then a list of tkt/docs are returned with minimal info to help the requestor determine which one they really want to look at. The similar name list response would use a subset of the display response but no new data items than what is listed for the display response. 1.5 Airline document exchange/reissu e request 1.6 Airline document exchange/reissu e response Request requirements: Request to include: New order Id, Requestor id, aggregator id, requestor iso country code, agency commission, PNR reference, Passenger name and type, FOP information (FOP type), doc nbrs and coupons to be exchanged, Response to include: number of additional services, airline indexing field, FOP information, fare amounts (base, total, equivalent), booking agent id, carrier fee data, commission info, consumed at issuance indicator, coupon info (number, itinerary sequence nbr, status, value, segment id), customer file ref, customer id, date of issue, excess baggage info, associated fare basis/tkt designator, unstructured fare calc info, structured fare component info, fee owner airline designator, frequent flier info, invoice nbr, issued in exchange for info (doc nbr, coupon nbr, coupon media), net reporting indicator, in connection doc/cpn and qualifier, issuing agent id, issuing agency/airline, ticket/doc indicators (noncommissionable, non endorsable, non interlineable, non-refundable, non reissuable/exchangeable, penalty restriction), non-refundable/no AirDocExchangeRQ AirDocDisplayRS Business Requirements Document - NDC Payment and Ticketing Page 15 of 49

Ref # Category Ticketing Requirements Description value/penalty info, number of booklets issued, nbr of tkt/doc nbrs, original issue info, FOIDs, passenger name, type code, specific data, PNR reference(s), present to/at info, present credit/debit card ind, pricing info, product characteristic info, promotional code, rate of exchange, RFIC/RFISC, refund calc indicator, ticketing iso country code, reissued flown flt coupon data, response comments, servicing airline/system provider, sold airline info, statistical code, stopover code, tax/fee/charge info, tax on commission on indicator, tax on EMD qualifier, tax/fee/charge data at coupon level, ticket/doc nbr, ticketing mode indicator, total flt value coupons, tour code, true origin/destination city codes, validating airline designator and waiver code, order id, offer id, endorsements/restrictions, document type, errors (Transaction and Order/PAX levels). 1.7 Airline document refund request Request includes: Requestor id, aggregator id, Order id, doc nbr, coupon nbrs, number of ticket/doc nbrs, waiver code AirDocRefundRQ 1.8 Airline document refund response Response includes: Response to include: number of additional services, FOP information, fare amounts (base, total, equivalent), booking agent id, commission info, coupon info (number, status, value, segment id), customer id, date of issue, excess baggage info, associated fare basis/tkt designator, unstructured fare calc info, fee owner airline designator, invoice nbr, issued in exchange for info (doc nbr, coupon nbr, coupon media), net reporting indicator, in connection doc/cpn and qualifier, issuing agent id, issuing agency/airline, non-refundable/no value/penalty info, number of booklets issued, original issue info, FOIDs, passenger name, PNR reference(s), present to/at info, pricing info, product characteristic info, promotional code, RFIC/RFISC, refund calc indicator, refund tax/fee charge info, refund tkt/doc total amount, ticketing iso country code, response comments, servicing airline/system provider, settlement authorization code, sold airline info, statistical code, stopover code, tax/fee/charge info, tax on commission on indicator, tax on EMD qualifier, ticket/doc nbr, ticketing mode indicator, ticket issuance originator code, total flt value coupons, tour code, true origin/destination city codes, validating airline designator and waiver code, order id, offer id, endorsements/restrictions, AirDocRefundRS Business Requirements Document - NDC Payment and Ticketing Page 16 of 49

Ref # Category Ticketing Requirements Description document type, errors (Transaction and Order/PAX levels). Airline document history Request Requestor id, aggregator id, doc nbr AirDocHistoryRQ Airline document history response 1.9 Airline document void request 1.10 Airline document void response 1.11 Airline document system cancel request 1.12 Airline document system cancel response 1.13 Airline request for customer data Additional services info, number of services, validating airline, checked in airline info, coupon number, coupon status, previous coupon status, date of service, flown airine info, issued in exchange info, passenger name, reason for issuance code, reason for issuance subcode, settlement authorization code, sold airline info, ticket document nbr, transaction agent id, transacton pseudo city code, transaction date and time, waiver code Request includes: Requestor id, aggregator id, Order id, doc nbr, number of ticket/doc nbrs Response includes: Order id, doc nbr, settlement authorization code Request includes: Requestor id, aggregator id, Order id, order item id, document number, if know Response includes: Order id, order item id, doc nbr Request by an airline for additional data from the customer, including: - One or a combination of customer credentials allowing the airline to authenticate the customer, eg Loyalty scheme membership id and partial password for payment by airline currency, url link to 3D Secure provider, security questions (eg mother s maiden name). Note it is assumed that the customer will not be passing their complete password via the Seller but that AirDocHistoryRS VoidAirlineDocRQ VoidAirlineDocRS AirDocCancelRQ AirDocCancelRS CustomerInputRQ Business Requirements Document - NDC Payment and Ticketing Page 17 of 49

Ref # Category Ticketing Requirements Description the airline request will be for a randomly generated subset (eg 2 nd, 4 th & penultimate characters) - Additional customer product delivery data eg limo pickup point If the customer provided data in a preceding Request/Response transaction was invalid then the airline may repeat the request for data, requiring that an error condition can be included in the request (eg password invalid, please try again, you have exceeded the number of allowed tries, please contact our call centre ) 1.14 Customer data response Customer data, eg - Password characters - Verification cryptogram generated by 3D Secure process response texts with their associated requests CustomerInputRS 6.2 Recommended Messages AirDocIssueRQ Request an Airline to issue flight (ET) and/or ancillary (EMD) document(s). Response is AirDocDisplayRS AirDocDisplayRQ Request an Airline to return flight (ET) and/or ancillary (EMD) document details AirDocDisplayRS Response from Airline with flight (ET) and/or ancillary (EMD) document details Request an Airline to exchange/reissue flight (ET) and/or ancillary (EMD) document(s). Response is AirDocDisplayRS AirDocExchangeRQ AirDocRefundRQ AirDocRefundRS AirDocVoidRQ AirDocVoidRS AirDocCancelRQ AirDocCancelRS Request an Airline to refund, part refund (or void if not reported) flight (ET) and/or ancillary (EMD) document(s) Response from Airline with refunded or part refunded (or voided) flight (ET) and/or ancillary (EMD) document details Request an Airline to void flight (ET) and/or ancillary (EMD) document(s) Response from Airline with voided flight (ET) and/or ancillary (EMD) document details Request an Airline to cancel flight (ET) and/or ancillary (EMD) document(s) Response from Airline with cancelled flight (ET) and/or ancillary (EMD) document details Business Requirements Document - NDC Payment and Ticketing Page 18 of 49

AirDocHistoryRQ AirDocHistoryRS CustomerInputRQ/RS Request an Airline to return history of flight (ET) and/or ancillary (EMD) document details. Response from Airline with history of flight (ET) and/or ancillary (EMD) document details. Requested in the Order Management BRD, and required to support Payment and Ticketing requirements. Allows an intermediate message pair to be inserted allowing additional information to be collected from the customer, eg authentication of scheme membership, 3D-Secure, customer product fulfillment data such as limo pickup point. 6.3 Message Sequence Flows NOTE: Message Sequence Flow diagrams are provided for illustration purposes only. These diagrams are not intended to recommend any particular business process workflow and do not cover all possible scenarios and workflows as there can be an infinite number of possible constructions. Workflows will depend on the business process users will implement, and may be different from one implementation to another. Message pairs are atomic. Business Requirements Document - NDC Payment and Ticketing Page 19 of 49

6.3.1 Order and Ticket a Flight Product with 3D Secure 2 Separately Order and Ticket a Flight Product, with 3D Secure Seller/Agregator Airline 1. AirShoppingRS Offer IDs from preceding shopping process 1.1 Request Order creation of selected offers, include minimum order completion details 2. OrderChangeRQ Selected Offer IDs, passenger details 3. OrderViewRS Order ID and details 2.1. Airline checks offer still valid & availability, creates a flight order. Returns view of Order 3.1. Order confirmation sent to customer. Copy of the Order may be stored locally. 3.2. Agency commits to pay and requests ticket issue with form of payment before Payment Time Limit expires. 4. AirDocIssueRQ Order ID, form of payment, commission 5. CustomInputRQ 3D-Secure request 4.1. Airline checks Order within Payment Time Limit, re-prices Order and if within tolerance, it authenticates the form of payment: - if on Agent merchant then check accreditation status - If on Airline merchant and if Airline requires additional 3D Secure authorisation for online agents, then Airline accesses its card authentication service for a 3D Secure url which it passes back to seller 5.1 online agency displays 3D Secure request to customer to complete. Returns 3D Secure verification cryptogram (or error) 6. CustomInputRQ 3D Secure cryptogram 6.1. Airline passes 3D Secure cryptogram to authentication service and requests payment authorisation. If authorised the Airline issues accountable documents and updates Order. Returns accountable document data & ref 7. AirDocDisplayRS accountable document details & refs 7.1. Ticket receipt sent to customer. Copy of the ticket data may be stored locally. 7.2. Airline closes sales report and processes settlement 2 3D Secure is used as an illustration for one potential methodology of securing Credit Card transactions. It must be noted, that an Airline, or any other 3 rd party implementer, may have its own strategy on credit card data processing. While 3D Secure is identified as one potential methodology, an airline may choose to use any other methodology, as would be aligned with its strategy and i t would see fit. Business Requirements Document - NDC Payment and Ticketing Page 20 of 49

6.3.2 Ticket a Flight Product with cash and miles form of payment Issue Ticket on a Flight Order using cash and miles forms of payment Seller/Agregator Airline 1. OrderViewRS Order ID and details 1.1. Order confirmation sent to customer. Copy of the Order may be stored locally. 1.2. Order is wholly or partly payable in airline loyalty points. Customer provides their airline membership scheme details to the Seller who requests ticket issue with cash and miles forms of payment. 2. AirDocIssueRQ Order ID, customer loyalty scheme identity, form of payment, commission 2.1. Airline checks Order within Payment Time Limit, re-prices Order and if within tolerance, it authenticates the form of payment (if Agent merchant then check ticket authority, if Airline merchant then authenticate payment card). 2.2 Airline requires authentication of the customer s scheme membership and generates a request for a random part of the customer s password 3. CustomInputRQ Password request 3.1 Seller passes the partial password request to the customer and enters his response. 4. CustomInputRQ Partial password 7. AirDocDisplayRS accountable document details & refs 5.1. Airline validates password response, checks the customer s account holds sufficient miles and then issues accountable documents, updates Order and deducts the miles from the customer account. Returns accountable document data & ref. If password not correct may repeat password request for a limited number of times 7.1. Ticket receipt sent to customer. Copy of the ticket data may be stored locally. 7.2. Airline closes sales report and processes settlement Business Requirements Document - NDC Payment and Ticketing Page 21 of 49

6.3.3 Separately Cancel an Order and Request a Refund Separately Cancel an Order and Request a Refund Seller/Agregator Airline 0.1. Customer asks Seller to cancel and refund an order item. Seller checks what refund rules are applicable 1. OrderRulesRQ Order ID, order item 1.1. Airline checks what refund rules apply to the order item and returns what change fees apply and the refundable amount, if any 2. OrderRulesRS Order ID and details 2.1. Seller requests cancellation of the order item 3. OrderChangeRQ (if part order) or OrderCancelRQ (if whole order) Order ID, order item 3.1 Airline cancels order item and returns an updated view of order or if whole order cancelled then return cancel confirmation. Return applicable change fees and value of the refundable amount, if any 4. OrderViewRS (part order) or OrderCancelRS (whole order) Updated order details 4.1. Seller requests refund for the cancelled order item 5. AirDocRefundRQ Order ID, order item, accountable document number 5.1 Airline checks Agency s accreditation status, that the Order item is cancelled and that the document is valid & unused and then applies refund rules. The document status is changed to Refunded against the original form of payment net of change fees. Settlement Auth Code is obtained. 6. AirDocRefundRS Updated document details, SAC 6.1 Seller sends confirmation of the change to the Order and refund due to the customer 6.2 Airline closes sales report and refunds through settlement process if agency merchant or directly to card holder account if airline merchant Business Requirements Document - NDC Payment and Ticketing Page 22 of 49

6.3.4 Combined Order Cancellation and Refund Combined Cancelation of an Order and Refund Seller/Agregator Airline 0.1. Customer asks Seller to cancel and refund an order item. Seller checks what refund rules are applicable 1. OrderRulesRQ Order ID, order item 1.1. Airline checks what refund rules apply to the order item and returns what change fees apply and the refundable amount, if any 2. OrderRulesRS Order ID and details 2.1. Seller requests cancellation of an order item and refund 3. OrderChangeRQ (if part order) or OrderCancelRQ (if whole order) Order ID, order item, accountable document number 3.1 Airline checks Agency s accreditation status and that the document is valid & unused and then applies refund rules. The document status is changed to Refunded against the original form of payment net of change fees. Settlement Auth Code is obtained. Airline cancels order item and returns an updated view of order or if whole order cancelled then return cancel confirmation, together with updated document details. 4. OrderViewRS (part order) or OrderCancelRS (whole order) Updated order details, updated document details, SAC 4.1 Seller sends confirmation of the change to the Order and refund due to the customer 4.2 Airline closes sales report and refunds through settlement process if agency merchant or directly to card holder account if airline merchant Business Requirements Document - NDC Payment and Ticketing Page 23 of 49

6.3.5 Separately Change an Order and Request Ticket Reissue Separately Change Itinerary on an Order and request Ticket Reissue Seller/Agregator Airline 0.1 Request new product options for specified order items 1. ItinReshopRQ Order ID, order item 1.1. Return new Offers, including for ancillaries impacted by the change & additional price to pay (new total price plus change fees less original value) 2. ItinReshopRS Order & new Offer IDs, 2.1. Customer reviews offers and requests order to be amended for selected offers 3. OrderChangeRQ Order and selected Offer IDs 3.1. Airline checks offer and price and checks fare rules for change fees. Airline makes changes to order and returns updated view, including outstanding amount to pay 4. OrderViewRS Updated Order 4.1 Seller submits payment and requests reissue of accountable docs 5. AirDocExchangeRQ Order ID, form of payment 5.1 Airline checks offer price still valid and within payment time limit. Airline checks Agency s accreditation status and authorises payment for the additional collection, changes status on the old documents to Exchanged and issues new documents against the new form of payment. 6. AirDocDisplayRS Order ID, new accountable docs 6.1. Updated Order confirmation and new document references sent to customer. Copy of the Order may be stored locally. Business Requirements Document - NDC Payment and Ticketing Page 24 of 49

6.3.6 Combined Order Change and Ticket Re-issue Combined Change to an Order and Ticket Reissue Seller/Agregator Airline 0.1 Request new product options for specified order items 1. ItinReshopRQ Order ID, order item 1.1. Return new Offers, including for ancillaries impacted by the change & additional price to pay (new total price plus change fees less original value) 2. ItinReshopRS Order & new Offer IDs, 2.1. Customer reviews offers and requests order to be amended for selected offers with new accountable documents issued and submits payment 3. OrderChangeRQ Order and selected Offer IDs, form of payment 3.1 Airline checks offer price still valid and within payment time limit. Airline checks Agency s accreditation status and authorises payment for the additional collection, changes status on the old documents to Exchanged and issues new documents against the new form of payment. Airline makes changes to order and returns updated view 4. OrderViewRS Updated Order, new accountable docs 4.1. Updated Order confirmation and new document references sent to customer. Copy of the Order may be stored locally. Business Requirements Document - NDC Payment and Ticketing Page 25 of 49

7 Data Description Please refer to Appendix - 20140307 NDC Payment and Ticketing - Data Dictionary Appendix v1.0 - DRAFT for PADIS REVIEW, maintained as a separate document, due to size. 8 Non-Functional Requirements Feature Definition Requirement Shopping Standard based and interoperable messaging protocol Send Only Receive only Request/Response exchange Diagnostics/Routing Reliability Messaging protocol must be based on industry standards to enable interoperability Also called Push MEP is simple one-way messaging where a message is sent with no expectation of a response. Also called Pull MEP is a message pattern where a non-addressable sender supports the ability to explicitly obtain messages from another application. This can be used for exchanges that are of pull type only Message pattern consists of one or more request/response pairs. The correlation between a request and a response is well defined. In this MEP the response maybe deferred and the requesting application may or may not block application processing until a response is received Authentication, diagnostic, logging & routing information should be included in the message header and not the payload Protocol capability to support assured and single delivery to the receiving application with no message loss Applicable n/a n/a Applicable Applicable Applicable Business Requirements Document - NDC Payment and Ticketing Page 26 of 49

Feature Definition Requirement Shopping Message acknowledgement/ delivery report Fault management Priority handling Data confidentiality Message exchange protocol acknowledgement provides guaranteed delivery in a sense that if there is any communication failure or any remote system unavailability, the message is transparently repeated until the application has received it. This is referred to as reliability feature necessary for business critical messages. Message loss may happen using application acknowledgement only in cases like application or system problems. It may however be complementary to reliability mechanism. Additionally there is also a notion of end to end delivery report that can be used to request a delivery notification form the end user generated by its messaging agent. This may be used for cases that a proof of delivery is required by the sender. Capability to report permanent or transient problems or errors in message exchange and return this information to the sending application Capability to assign priority to messages and process accordingly separate between processing and delivery related priority handling. Assurance that data remain secret except for those entities that have been authorized to access this data. (i.e. encryption/decryption). Identify any data elements that are subject to specific confidentiality requirements. For example payment card data or personal data may be subject to PCI compliance requirements. n/a Applicable Applicable Applicable to passenger personal data Business Requirements Document - NDC Payment and Ticketing Page 27 of 49

Feature Definition Requirement Shopping Requester Authentication Message integrity Capability to confirm the identity claimed by a sender or entity Capability to ensure that data are preserved in its original form and not altered Supported in all Request messages. To include the identity of the source of the request (the identity of the selling entity, the staff member making the request and the Point of Sale channel ) and any intermediaries that the request has passed through. Applicable to the message body Capability to target multiple recipients Multi part Messages Support for attachment (for rich documents (image, large files etc.) Ability to send a message to more than one recipient or applications Communications do not support the transmission of messages in multiple parts. Ability to have digital attachments (to allow simpler management of attachments and optimized transport) Applicable, eg to multiple directly connected airlines plus one or more aggregators Applicable Attachments must not appear in the message only links to them Message Compression Capability to compress (to save bandwidth) Applicable Support for specific protocols Please indicate what messaging protocols you expect the industry will use to exchange the messages. May need to support either or both SOAP and REST Business Requirements Document - NDC Payment and Ticketing Page 28 of 49

Feature Definition Requirement Shopping Response Time Communications must support a timeout function Applicable Versioning Localisation Unique Message Identification State Message Expiration Schema Language Locale Messages must comply with PADIS versioning specifications Any localisation data elements must support the ability to provide a language identifier Messages should provide the ability to support a unique message identifier Messages should have the ability to support both stateful and stateless modes of communication Communications should provide the ability to stipulate an expiration timestamp Message schema must be written in en_us Applicable Applicable Applicable Shopping messages will be stateless Applicable Applicable Business Requirements Document - NDC Payment and Ticketing Page 29 of 49

9 Code Lists PADIS Codesets must be used where existing and where possible. DDXWG is responsible for requesting PADIS to update and/ or add codesets as NDC business needs may evolve. Codesets are managed according to PADIS methodology and governance process. Please refer to NDC Airline Shopping Schema Release Notes for codesets identification. Business Requirements Document - NDC Payment and Ticketing Page 30 of 49

Appendix A: List of Use Cases The range of use cases included is not exhaustive. Use cases described are illustrations. Personalized shopping scenarios are included to demonstrate the capabilities described in the business requirements. Personalization is optional, and the level of personalization depends on the traveller choice. ID Description Passenger Type Offer Type Payment Type(s) Card Preauthorized Itinerary Type 1 Single Airline, Single Passenger, Single Form of Payment Single Passenger Fares only (no ancillaries) CC No Online (Same airline marketing/validating/operating) 2 Codeshare: Airline Marketed, OA Operated Multi Pax, Infantno seat, FOP Gift Card/Miles, Bundled Fare with Ancillary Travellers (2-9); Infants without seats Bundled Fares (Fare Families) Gift Card; ORA Mileage No Codeshare: Airline Marketed, OA Operated 3 EMD-S Issuance Single Airline, Ancillary only, Companions, Multiple Form of payment Companions Ancillary Only (No Flight) Cash card; ETF N/A Online (Same airline marketing/validating/operating) 4 Refund request Any Any Any N/A Any 5 Change request Any Any Any N/A Any 6 Void ET/EMD request Any Any Any N/A Any 7 System Cancel request Any Any Any N/A Any Business Requirements Document - NDC Payment and Ticketing Page 31 of 49

Use Case 1: Ticket Issuance Single Airline, Single Passenger, Single Form of Payment Credit Card (No Prior Authorization) Description: Request from accredited seller for airline to issue ticket Principal actors (with roles): Accredited Seller Aggregator Airlines (ORA) Preconditions/Assumptions: Offer has been accepted, itinerary has been booked and Passenger is ready to purchase Single passenger in offer Single airline in itinerary, prime flights only, air itinerary only (no ancillaries) Airline performs own ticketing Single Credit Card FOP, no pre authorization for Credit Card no card authorization provided Valid passenger email is in the ticketing message Seller will generate eticket Receipt and send to passenger Inputs: OrderID Order Item ID RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Agency commission PNR reference Passenger name Eticket Receipt Contact Info (Passenger s/ticket Purchaser s Email) Eticket Receipt Contact Info (Passenger address) Requestor ISO Country Code FOP Type (encryption required to comply with PCI requirements) o Form of Payment amount o Cardholder Name o Credit Card Vendor Code o Credit Card Corporate ID o Credit Card Account Number (Unmasked) o Credit Card Security Code o Expiration Date o Credit Card Billing Address Comment [AG2]: Post-PADIS review draft edit IATA Payment Card SME (reviewed and agreed to by PT TF): The expression Pre authorization is a card industry specific term referring to a specific process through which an hotel will block a room or an automated gas dispenser will allow you to pump gas, without knowing in advance how much the final bill will be. It is not proper to use the preauthorization term as this will lead the reader into confusion Steps to follow in the process: 1. Requestor sends the ticketing request to Airline 2. Airline authenticates and confirms accreditation status for seller and intermediary Business Requirements Document - NDC Payment and Ticketing Page 32 of 49

3. Airline validates Order ID to ensure ticket eligibility (eg. Request received within Payment time limit and Order Items are valid for Order ID) 4. Airline validates/authorizes the Credit Card 5. Airline issues eticket on Airline s stock 6. Airline sends ticketing data (XML Ticketing response) to aggregator/seller 7. Seller generates eticket Receipt and sends to passenger Post conditions: Success - no issues with payment or ticket Aggregator/Seller has a copy of the ticket Error occurred refer to error chart Use Case 1 Process Flow: 10 Flow Ends 0 Error response returned to the seller 9 Seller generates eticket Receipt and sends to passenger 1 Requestor / Seller sends ticketing request to Airline (IssueAirlineDoc.RQ) 2 Airline authenticates and confirms accreditation status for seller and intermediary 8 Airline sends ticketing data (XML Ticketing response) to aggregator/ seller (AirDocIssueRQ) 7 Airline issues eticket on Airline s stock 3 Airline validates Order ID to ensure ticket eligibility (eg. Request received within Payment time limit and Order Items are valid for Order ID) No Yes 6 Credit Card valid No 4 Payment Time Limit Valid? Yes 5 Airline validates / authorizes the credit card Business Requirements Document - NDC Payment and Ticketing Page 33 of 49

Use Case 2: Ticket Issuance Codeshare (Airline Marketed/OA Operated), Multi Pax, Infant-no seat, FOP Gift Card/Miles, Bundled Fare with Ancillary Description: Request from seller for airline to issue ET/EMD Principal actors (with roles): Offer Responsible Airline Codeshare/Alliance Partner Seller Preconditions/Assumptions: Two adult passengers with a lap child No fees or taxes apply to infant ticket without a seat Offer has been accepted, itinerary has been booked and Passengers are ready to purchase Multi passenger in offer Infant w/o seat was declared during order request Airline requires ET for lap child Assumes one loyalty account Marketing carrier is not the operating carrier, but is the validating carrier issuing ET/EMD Ticketing performed by Airline Seller will generate eticket Receipt and send to passenger Mixed responses are allowed (eg. One passenger fails to ticket due to payment failure will not prevent other passenger from ticketing) Inputs: OrderID Order Item ID RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Agency commission PNR reference Passenger name Eticket Receipt Contact Info (Passenger s/ticket Purchaser s Email) Eticket Receipt Contact Info (Passenger address) Requestor ISO Country Code FOP Type 1 (applied to Passenger 1) o Gift Card Number with redemption code FOP Type 2 (applied to Passenger 2) o Loyalty Account Number Business Requirements Document - NDC Payment and Ticketing Page 34 of 49

Steps to follow in the process: 1. Requestor sends the ticketing request to Airline 2. Airline authenticates and confirms accreditation status for seller and intermediary 3. Airline validates Order ID to ensure ticket eligibility (eg. Request received within Payment time limit and Order Items are valid for Order ID) 4. Airline validates Gift Card and Redemption Mileage 5. Airline issues eticket and EMD on Airline s stock for Order ID including Ancillary per passenger 6. Airline sends ticketing data (XML Ticketing response) to seller 7. Seller generates eticket Receipt and sends to passenger Post conditions: Success - no issues with payment or ticket Seller has a copy of the ticket Error occurred process continues via error handling use case Seller generates eticket EMD Receipt and sends to passenger No residual balance on Gift card Paid with Miles and Gift Card no balance due Error Conditions: If Gift Card number is invalid, airline returns an Error message If Loyalty Bank is deficient in redeemable miles, airline returns an Error Message to Seller Business Requirements Document - NDC Payment and Ticketing Page 35 of 49

Use Case 2 Process Flow: 10 Flow Ends 0 Error response returned to the seller 9 Seller generates eticket And EMD Receipts and sends to passenger 1 Requestor / Seller sends ticketing request to Airline (IssueAirlineDoc.RQ) 2 Airline authenticates and confirms accreditation status for seller and intermediary 8 Airline sends ticketing data (XML Ticketing response) to Seller (AirDocDisplayRS) 7 Airline issues eticket and EMD on Airline s stock 3 Airline validates Order ID to ensure ticket eligibility (eg. Request received within Payment time limit and Order Items are valid for Order ID) No Yes 6.1 Gift Card for P1 valid? No Yes 6.2 Loyalty Account for P2 valid? No 4 Payment Time Limit Valid? Yes 5 Airline validates Gift card and Loyalty Account Number for Mileage Redemption Business Requirements Document - NDC Payment and Ticketing Page 36 of 49

Use Case 3: EMD-S Issuance Single Airline, Ancillary only, Companion, Multiple Form of payment (Cash Card+ Debit Card) Description: Request to issue EMD S for an order/offer from single airline for ancillary only (no flight). Companion, multiple FOPs (Cash Card +Debit Card). EMD is issued by airline and delivered by paper receipt from Seller/Aggregator. Principal actors (with roles): Requester/Seller Aggregator Airline ORA Preconditions/Assumptions: Offer has been accepted, Ancillary services has been booked and passenger is ready to purchase EMD for companion Ancillary Service (no flight) for Companion from single airline for a lounge pass to be used at a future date Multiple FOPs: Cash Card and Debit Card EMD will be issued airline Aggregator/Seller will deliver paper receipt to passenger Inputs: OrderID Order Item ID RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Requestor ISO Country Code Agency commission PNR reference For companion o Name Sponsor name person paying for order FOP 1 (Cash Card) o FOP Type o FOP amount o Cardholder Name o Cash Card Vendor Code o Cash Card Corporate ID o Cash Card Account Number o Cash Card Security Code o Expiration Date o Cash Card Billing Address FOP 2(Debit card) o FOP Type o FOP amount o Cardholder Name Business Requirements Document - NDC Payment and Ticketing Page 37 of 49

o o o o o Vendor Code Account Number Credit Card Security Code Expiration Date Card holder billing address Steps to follow in the process: 1. Requestor sends the ticketing request to Airline 2. Airline authenticates and confirms accreditation status for seller and intermediary 3. Airline validates Order ID to ensure EMD eligibility (eg. Request received within Payment time limit and Order Items are valid for Order ID) 4. Airline validates cash card 5. Airline validates/authorizes the Debit Card 6. Airline issues EMD on Airline s stock for Order 7. Airline sends ticketing data (XML Ticketing response) to aggregator (Reso 725: Airline document issue response new function) Post conditions: Aggregator/Seller has a copy of the document ( EMD-S) Aggregator/Seller generates paper receipt and delivers to passenger Error occurred refer to error chart Use Case 3 Process Flow Business Requirements Document - NDC Payment and Ticketing Page 38 of 49

11 Flow Ends 0 Error response returned to the aggregator/seller 1 Requestor / Seller sends document issuance request to Airline (AirDocIssueRQ) 2 Airline authenticates and confirms accreditation status for seller and intermediary 10 Aggregator/Seller generates Paper EMDS receipt and Hands it over to passenger 9 Airline sends EMDS data (XML Ticketing response) to aggregator (AirDocDisplayRS) 8 Airline issues EMDS on Airline s stock 3 Airline validates Order ID to ensure document eligibility (eg. Order Items are valid for Order ID) Yes No 7 Debit Card Valid? 4 Airline validates cash card No 5 Cash Card Valid? Yes 6 Airline validates/ authorizes Debit Card Business Requirements Document - NDC Payment and Ticketing Page 39 of 49

Use Case 4: Refund Request Description: Request for airline to refund all or some ET(s) and/or EMD(s) issued on an Order Principal actors (with roles): Seller/Aggregator Airlines (Provider) Preconditions/Assumptions: ETs and EMDs have been issued by Airline One or more forms of payment may collected Aggregator/Seller will generate refund receipt and send to passenger Fares rules are stated in Offer and Order pertaining to partial refunds and seller has communicated any and all penalties to customer and customer agrees to fees if applicable Inputs: Order ID Order Item ID Service Item ID ET and EMD document number(s) to be refunded (Note: if partial refund, the coupon numbers should be sent) RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Requestor ISO Country Code Steps to follow in the process: 1. Requestor sends the refund request to Airline 2. Airline authenticates and confirms accreditation status for seller and intermediary 3. Airline validates that ETs and EMDs are still valid and unused 4. Airline checks fare and ancillary product rules to see if change fees are required and ticket is refundable. (eg. For bundled fares that do not break down the fares on a service item level, the fare rules should be clearly stated in the original Offer and Order and if the agent requests a partial refund on that Order, it would be rejected by the airline) 5. If there are change/penalty fees, the Airline will calculate these fees and deduct them from the amount to be refunded 6. Airline refunds any remaining amount to original FOPs. 7. Airline changes coupon status of the ETs and EMDs to refunded. 8. Airline sends refund response to aggregator/seller Post conditions: Aggregator/Seller has a copy of the refund response information Aggregator/Seller generates ET and EMD refund receipt and sends to passenger Business Requirements Document - NDC Payment and Ticketing Page 40 of 49

ET and EMDs have been refunded and Order item(s) have been cancelled Agency commission could be included in the refund response Error occurred refer to error chart Use Case 4 Process Flow 9 Airline changes coupon status of the ETs and EMDs to refunded 8 Airline refunds any remaining amounts to original FOPs 11 Flow Ends 10 Airline Sends refund response to Aggregator/Seller (AirDocRefundRS) 0 Error response returned to the aggregator/seller 1 Requestor / Seller sends refund request to Airline (AirDocRefundRQ) 7 Airline calculates change/penalty fee and deducts amount from refund amount 2 Airline authenticates and confirms accreditation status for seller and intermediary 3 Airline validates ETs and EMDs are still valid and unused No Yes 6 Change/Penalty Fee Applicable? No 4 Documents valid and unused? Yes 5 Airline checks fare and ancillary product rules to see if change/penalty fees are required and ticket is refundable. Business Requirements Document - NDC Payment and Ticketing Page 41 of 49

Use Case 5: Reissue Request Description: Request for airline to change the ordered itinerary requiring a new ticket to be issued and additional payment to be made to cover an increase in offer price and change fees. Principal actors (with roles): Seller/Aggregator Airlines (Provider) Preconditions/Assumptions: ETs and EMDs have already been issued by the Airline on the Order Airline internal business rules will determine the requirements for the documents to be exchanged and the need for the issuance of a residual document or a refund (such a process is outside the scope of this document) The change to the itinerary has already been made by the airline and the additional collection required communicated to the Seller Fares rules are stated in Offer and Order pertaining to change Inputs: OrderID Order Item ID RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Agency commission PNR reference Accountable document number(s) to be exchanged Sponsor name person paying for order Form of Payment Steps to follow in the process: 1. Requestor sends the form of payment for the additional collection and a request to reissue accountable document for the changed itinerary to the Airline 2. Airline checks fare and ancillary product rules to see if change fees are required and checks changed itinerary offer price is still valid and within payment time limit 3. Airline authenticates the form of payment 4. Airline validates that accountable documents (ETs and EMDs) are still valid and unused 5. Airline changes coupon status of the old accountable documents (ETs and EMDs) to Exchanged and issues new document coupons for the changed itinerary recording the new form of payment for the additional collection 6. Airline sends new document details to aggregator/seller 7. Seller confirms itinerary change and communicated new document references to their Customer Business Requirements Document - NDC Payment and Ticketing Page 42 of 49

11 Flow Ends 0 Error response returned to the Requestor / Seller 1 Requestor / Seller sends FOP details to the airline for additional collection and request to reissue accountable documents (AirdocexchangeRQ) 2 Airline authenticates FOP and confirms accreditation status for Requestor / Seller 10 Requestor/ Seller confirms itinerary change and communicates new document references to the customer 9 Airline send new document details to the Requestor / Seller 8 Airline changes coupon status of ETs and EMDs to Exchanged 3 Airline validates ETs and EMDs are still valid and unused No Yes 7 Changed Offer Price valid and within payment time limit? No 4 Documents valid and unused? Yes 6 Airline Validates whether the changed itinerary offer price is still valid and within payment time limit 5 Airline checks fare and ancillary product rules to see if change fees are required Business Requirements Document - NDC Payment and Ticketing Page 43 of 49

Use Case 6: ET/EMD Void Request Description: Request for airline to do a void for ET(s) and EMD(s) issued on single airline Principal actors (with roles): Seller/Aggregator Airlines (Provider) Preconditions/Assumptions: ETs and EMDs have been issued by Airline Form of payment does not impact void process For conjunctive tickets a void request will void all documents in a conjunctive set. Void time limit is known to requestor (i.e. published in Airline profile) Inputs: Order ID ET and EMD document number(s) (Note: if partial refund, the coupon numbers should be sent) RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Requestor ISO Country Code Steps to follow in the process: 1. Requestor sends the void request to Airline within void time limit (Airline void request possible new function) 2. Airline authenticates and confirms accreditation status for seller and intermediary 3. Airline validates that all ETs and EMDs to be voided in the request are still valid and unused 4. Airline determines if any FOP was already collected and whether to allow void to proceed or to reject and the void must now be processed as a refund request 5. Airline changes coupon status of the ETs and EMDs to void 6. Airline sends void response to aggregator/seller Post conditions: Aggregator/Seller has a copy of the void response information Aggregator/Seller could send ET and EMD void confirmation to passenger ET and EMDs have been voided and if Airline allows voids for FOP that was processed and funds collected, those are returned to the FOP Error occurred refer to error chart Business Requirements Document - NDC Payment and Ticketing Page 44 of 49

Use Case 6 Process Flow 0 Error response returned to the aggregator/seller. Void not allowed, only refund possible 9 Flow Ends 1 Requestor / Seller sends void request to Airline within the void timelimit (AirDocVoidRQ) 2 Airline authenticates and confirms accreditation status for seller and intermediary 8 Airline send void response to aggregator/seller (AirDocVoidRS) 7 Airline changes coupon status of the ETs and EMDs to Void 3 Airline validates ETs and EMDs are still valid and unused No Yes 6 Allow Void? No 4 Documents valid and unused? Yes 5 Airline determines if any FOP was already collected and whether to allow void to proceed or to reject and the void must now be processed as a refund request Business Requirements Document - NDC Payment and Ticketing Page 45 of 49

Use Case 7: ET/EMD System Cancel Request Description: Request for airline to cancel ET(s) and EMD(s) Principal actors (with roles): Aggregator Airlines (Provider) Preconditions/Assumptions: ETs and EMDs have been requested to be issued or have been issued by Airline. No response was received from an Airline for an issue, refund, exchange/ reissue or void request. For conjunctive tickets a system cancel request will cancel all documents in a conjunctive set. Inputs: Order ID Order Item ID Document number, if known Action to be cancelled RequestorID (may include multiple fields such as ARC/IATA, PCC, AgentID, RequestorType, etc ) Aggregator ID Requestor ISO Country Code Steps to follow in the process: 1. Requestor sends the cancel request to Airline 2. For a system cancel of an issues, if the document was created the Airline cancels the document and sets coupon status to void; for a system cancel of a refund, exchange/ reissue, or void the Airline sets the coupon status to open. 3. Airline sends system cancel response to aggregator Post conditions: Aggregator receives confirmation in response that the appropriate action has been taken Error occurred refer to error chart Business Requirements Document - NDC Payment and Ticketing Page 46 of 49

Use Case 7 Process Flow 1 Requestor / Seller sends a document issue request to Airline (AirDocIssueRQ) 2 Requestor / Seller does not receive any response from the Airline within the agreed response timelimit 3 Requestor/ Seller sends a cancel request to the airline if the document has been issued (AirDocCancelRQ) 4 Airline changes coupon status of the issued ETs and EMDs to Void 5 Airline sends system cancel response to aggregator/seller (AirDocCancelRS) 6 Flow Ends Business Requirements Document - NDC Payment and Ticketing Page 47 of 49

Error handling chart: Error Condition Description Action Card authorization failed Agency restricted from ticketing Agency/Aggregator not verified/authorized Issue Doc Request message data field mismatch FOP Amount does not match Order total Transaction identified as Fraudulentsuspicious FOP type not permitted (e.g. by airline, market, etc ) Payment time limit expired Void time limit expired Unable to process (refund, exchange, reissue, change or void) request due to service was provided Wrong card number, expiration date, name mismatch, wrong CID/CVVS, insufficient amount, Agent is either not accredited or restricted by Airline to request ticketing When the Requestor ID and/or Aggregator ID fails to validate in the Airiline system for any type of request When the request to issue documents contains one or more fields that do not match the original Order When there are multiple FOP s involved and the designated amounts to be charged on each FOP does not equal the total amount of the order Airline Revenue management or security determines a transaction request is suspicious, and decides not to complete the salefraudulent Airline cannot accept a certain FOP in a certain market or with a requesting agency The time limit originally specified in the Order response to send confirmation to issue documents and provide FOP details has been exceeded The void limit originally specified in the Order response to request a void is exceeded. Another case is when a void request occurs in a different time zone and the airline system thinks the ticket void time limit has exceeded, even though the request is within the time limit. To simplify implementation, in either case, the document is no longer considered voidable. When a request is received that attempts to alter any part of an order and the Airline identifies that the service was already fulfilled, there will be an error message Respond with PADIS error code message that (card authorization failed) and to reenter card payment details or different FOP Respond with error message that agent is not authorized to request ticketing and no documents are issued for the Order Respond with error message that agent/aggregator is not authorized to make the associated request Return Order Mismatch error code Return FOP Total Amount error and re-enter FOP amounts to be collected Return error code that transaction flagged as suspicious, and decides not to complete the salefraudulent Respond with error code message: (FOP not accepted) and to enter new FOP Respond with error code that payment time limit expired and requestor will need to create new order Respond with error code that void time limit expired and no longer voidable. Requestor will need to process request as a refund rather than a void. Respond with error code that change is no allowed due to services already provided and includes details of the service(s) fulfilled. Comment [AG3]: Post-PADIS edit (IATA Payment Card SME, reviewed and agreed to by PT TF): No private business can call an act fraudulent. Hence suggested to refer to a transaction as suspicious Business Requirements Document - NDC Payment and Ticketing Page 48 of 49

Appendix C: List of Attachments List of attachments referenced and included with this Business Requirements Document: 1. NDC Payment and Ticketing - Data Dictionary Appendix v1.0 2. NDC Terms and Definitions v1.1 Business Requirements Document - NDC Payment and Ticketing Page 49 of 49