Table of ContentsTable of Contents
Enhanced and Simplified DistributionEnhanced and Simplified Distribution
Introduction
Terms of Use
Enhanced and Simplified Distribution > Data ProtectionEnhanced and Simplified Distribution > Data Protection
New Distribution Capability
ONE Order
Enhanced and Simplified Distribution > DefinitionsEnhanced and Simplified Distribution > Definitions
Introduction
Definitions
Enhanced and Simplified Distribution > View the ModelsEnhanced and Simplified Distribution > View the Models
Overview
Scope
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
AirlineProfileAirlineProfile
Overview
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
AirlineProfileNotifAirlineProfileNotif
Overview
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
AirShoppingAirShopping
Overview
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
INVReleaseNotifINVReleaseNotif
Overview
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
OfferPriceOfferPrice
Overview
Structure of the Invol Servicing
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
SeatAvailabilitySeatAvailability
Overview
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
ServiceListServiceList
Overview
9
10
11
12
13
14
18
19
21
22
23
25
26
28
29
30
Page: 1 of 377
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
OrderRulesOrderRules
Order Rules Capabilities
Enhanced and Simplified Distribution > Messages > Offer Management >Enhanced and Simplified Distribution > Messages > Offer Management >
OrderReshopOrderReshop
Overview
Structure of the Invol Servicing
Voluntary Servicing for full, partial cancellation and order modification
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderCreateOrderCreate
Overview
Ability to Handle Multiple Types of Contacts
Net clearance amount
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderChangeOrderChange
Overview
Ability to Handle Multiple Types of Contacts
Net Clearance Amount
Structure of the Invol servicing
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderChangeNotifOrderChangeNotif
Overview
Net Clearance Amount
Structure of the order change notification
Structure of the Invol servicing
Message Capabilities
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderCancelOrderCancel
Message Capabilities
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderRetrieveOrderRetrieve
Order Retrieve Capabilities
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderHistoryOrderHistory
Overview
Ability to Handle Multiple Types of Contacts
Structure of the Invol Servicing
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderListOrderList
Overview
32
35
36
37
40
41
45
46
47
52
53
54
55
56
70
71
72
77
83
84
88
89
Page: 2 of 377
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
OrderViewOrderView
Overview
Ability to Handle Multiple Types of Contacts
Net Clearance Amount
OrderView Response Elements
Structure of the Invol servicing
Voluntary Servicing for full, partial cancellation and order modification
Enhanced and Simplified Distribution > Messages > Order Management > OrderEnhanced and Simplified Distribution > Messages > Order Management > Order
SalesSales
Net Clearance Amount
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
AirDocNotifAirDocNotif
Air Doc Notif Capabilities
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
AcknowledgementAcknowledgement
Acknowledgement Capabilities
Enhanced and Simplified Distribution > Messages > Order Management >Enhanced and Simplified Distribution > Messages > Order Management >
Example ScenariosExample Scenarios
Service Delivery Deviation
Order Modification
Enhanced and Simplified Distribution > Messages > DeliveryEnhanced and Simplified Distribution > Messages > Delivery
Introduction
Enhanced and Simplified Distribution > Messages > Delivery > ServiceDeliveryEnhanced and Simplified Distribution > Messages > Delivery > ServiceDelivery
Purpose
Enhanced and Simplified Distribution > Messages > Delivery >Enhanced and Simplified Distribution > Messages > Delivery >
ServiceDeliveryNotifServiceDeliveryNotif
Overview
Enhanced and Simplified Distribution > Messages > Delivery >Enhanced and Simplified Distribution > Messages > Delivery >
UpdateServiceNotifUpdateServiceNotif
Overview
Enhanced and Simplified Distribution > Messages > Delivery >Enhanced and Simplified Distribution > Messages > Delivery >
ServiceStatusChangeNotifServiceStatusChangeNotif
Overview
Enhanced and Simplified Distribution > Messages > AccountingEnhanced and Simplified Distribution > Messages > Accounting
Introduction
Voluntary Servicing Impact to Accounting
90
91
95
96
98
99
101
102
105
106
107
108
109
110
111
112
113
114
Page: 3 of 377
Enhanced and Simplified Distribution > Messages > Accounting >Enhanced and Simplified Distribution > Messages > Accounting >
ServiceStatusChangeNotifServiceStatusChangeNotif
Overview
Enhanced and Simplified Distribution > Messages > Accounting >Enhanced and Simplified Distribution > Messages > Accounting >
OrderClosingNotifOrderClosingNotif
Overview
Enhanced and Simplified Distribution > Messages > ManagementEnhanced and Simplified Distribution > Messages > Management
Transaction Management
Enhanced and Simplified Distribution > Business Functions > SettlementEnhanced and Simplified Distribution > Business Functions > Settlement
Net Clearance Amount
Enhanced and Simplified Distribution > Business Functions > DistributionEnhanced and Simplified Distribution > Business Functions > Distribution
Voluntary Servicing Impact Accounting
Shopping
Shopping and Ordering with Deferred Payment
Shopping and Ordering with Instant Payment
Change of Itinerary
Full Order Cancellation
Structure of the Order Change Notification
Ability to Handle Multiple Types of Contacts
Structure of the Invol Servicing
Voluntary Servicing for full,partial cancellation and order modification
Schedule Change
Servicing Multi-passenger Order
Enhanced and Simplified Distribution > Business Functions > DeliveryEnhanced and Simplified Distribution > Business Functions > Delivery
Introduction
Delivery Preparation
Service Delivery
Update of Services During Delivery
Enhanced and Simplified Distribution > Business Functions > AccountingEnhanced and Simplified Distribution > Business Functions > Accounting
Introduction
New Order Creation
Service Consumption
Order Closing
Enhanced and Simplified Distribution > Business Functions > Library >Enhanced and Simplified Distribution > Business Functions > Library >
SettlementSettlement
Inform Seller of Net Clearance Data
Inform Airline of Payment Information Including Net Clearance Amount
Enhanced and Simplified Distribution > Business Functions > Library > OfferEnhanced and Simplified Distribution > Business Functions > Library > Offer
ManagementManagement
Build Upsell Offers based on Origin, Destination and defined dates
Build Upsell Offer(s) based on the content of other Offer(s)
116
117
118
122
124
126
128
131
134
137
139
142
143
145
149
150
154
155
157
159
160
161
162
163
164
165
166
167
Page: 4 of 377
Accept Repriced Offer(s)
Request a la carte Offer(s) for ancillary services based on an existing Offer or Order
Request a new Offer based on the content of an existing Offer and on additional qualifiers and context
Request a new Reshop Offer based on the content of an existing Reshop Offer and on additional qualifiers and context
Request a Seat Map and an a la carte Offer for seats based on an existing Offer or Order
Request a set of Offers based on Origin, Destination and defined dates
Request a set of Reshop Offers based on Origin, Destination and/or defined dates as replacement of specific Order
Item(s)
Request detailed information about an Offer
Request detailed information about a Reshop Offer
Select Offer(s) to add to a shopping basket
Select Reshop Offer(s) to add to a shopping basket
Enhanced and Simplified Distribution > Business Functions > Library > OrderEnhanced and Simplified Distribution > Business Functions > Library > Order
ManagementManagement
Acceptance of a planned schedule change
Add payment information into an existing Order
Add Payment Information as part of a New Order
Create Order
Cancel Order
Cancel Order Item(s) from an existing Order
Cancellation following a Planned Schedule Change
Commit to the Terms of the Order
Commit to the Terms of the Offer during ‘Create Order’
Commit to selected accepted reshop/delete Offer(s), confirm contact details and preferences
Confirm the price of the Order Item(s)
Inform Seller of Passenger name and/or contact details changes
Inform Seller of Payment status changes
Inform seller of flight segment time changes (Schedule Change)
Inform Seller of flight number changes (Schedule Change)
Inform seller of flight arrival and/or departure changes (Schedule Changes)
Inform Seller of flight equipment changes (Schedule Change)
Inform Seller of flight cancellation (Schedule Change)
Inform seller of flight changes (Schedule Change)
Inform seller of planned schedule change and any required follow up actions
Inform Seller that request is extended to dependent Order Item(s)
Inform Seller about differential type
Inform Seller about what will happen to an existing Service should the Seller accept a reshopped Offer Item
Inform Seller if a penalty is netted or to be paid
Provide address at destination
Provide emergency contact details
Provide contact details for unaccompanied minor
Retrieve Order
Reshop following a Planned Schedule Change
Request refundable amount for existing Order Item(s)
Request Offer Item(s) to be added to an existing Order
Respond to reshop request with the details of the order modification or cancellation (partial or full)
Request full or partial Order cancellation; Airline (ORA) retains Order for future Reshop request
Report penalty to Airline Accounting
Report refundable amounts to Airline Accounting
Report non-refundable amounts to Airline Accounting
Transmit fare waiver at reshop
View emergency contact details
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
Page: 5 of 377
View contact details for unaccompanied minor
View address at destination
View the result of the order modification or cancellation (partial or full)
Enhanced and Simplified Distribution > Capabilities > PartiesEnhanced and Simplified Distribution > Capabilities > Parties
Identifying Different Organizations
Enhanced and Simplified Distribution > Capabilities > BilateralEnhanced and Simplified Distribution > Capabilities > Bilateral
Augmentation Points
Enhanced and Simplified Distribution > Capabilities > Airline TaxonomyEnhanced and Simplified Distribution > Capabilities > Airline Taxonomy
Airline Taxonomy
Airline Taxonomy Codeset
Airline Taxonomy Capabilities
Enhanced and Simplified Distribution > Capabilities > RestrictionsEnhanced and Simplified Distribution > Capabilities > Restrictions
Offer and Order Conditions and Restrictions
Stages of a Restriction
Change Restrictions
Cancel Restrictions
Stop Over Information
Unstructured Information
Enhanced and Simplified Distribution > Capabilities > PricingEnhanced and Simplified Distribution > Capabilities > Pricing
Masked Price
Ticket Designator
Enhanced and Simplified Distribution > Capabilities > Taxes, Fees and ChargesEnhanced and Simplified Distribution > Capabilities > Taxes, Fees and Charges
Display of Refundable Taxes at Time of Shopping
Collection of Contact Information relating to Goods and Services Tax
Enhanced and Simplified Distribution > Capabilities > Commissions andEnhanced and Simplified Distribution > Capabilities > Commissions and
MarginsMargins
Commissions
Margins
Enhanced and Simplified Distribution > Capabilities > Time LimitsEnhanced and Simplified Distribution > Capabilities > Time Limits
Time Limits
Granular Price Time Limits
Enhanced and Simplified Distribution > Capabilities > PaymentEnhanced and Simplified Distribution > Capabilities > Payment
Secure Customer Authentication
Secure Customer Authentication Backport
Vouchers
Enhanced and Simplified Distribution > Integration > SSRs in NDCEnhanced and Simplified Distribution > Integration > SSRs in NDC
Overview
SSR Categorisation
219
220
221
222
227
228
229
239
242
243
244
246
247
249
250
251
252
253
255
257
258
262
263
272
274
280
281
Page: 6 of 377
Enhanced and Simplified Distribution > Integration > SSRs in NDC > ServiceEnhanced and Simplified Distribution > Integration > SSRs in NDC > Service
SSRsSSRs
List of Service SSRs
Service Category Mapping
BIKE
AOXY
Enhanced and Simplified Distribution > Integration > SSRs in NDC >Enhanced and Simplified Distribution > Integration > SSRs in NDC >
Information SSRsInformation SSRs
List of Information SSRs
ACKI
CHLD
CLID
CRUZ
CTCE
CTCM
CTCR
DCRW
DEPA
DEPU
DOCA
DOCO
DOCS
EPAY
FOID
FQTR
FQTS
FQTV
GRPS/GPST
GSTA
GSTE
GSTN
GSTP
INAD
INFT
LANG
NRSB
PCTC
RFTV
SEAT
SEMN
SLPR
TKTL
TLAC
TWOV
UMNR/PDUM
Enhanced and Simplified Distribution > Integration > SSRs in NDC > ObsoleteEnhanced and Simplified Distribution > Integration > SSRs in NDC > Obsolete
SSRsSSRs
List of Obsolete SSRs (from the perspective of Enhanced and Simplified Distribution)
283
286
287
288
289
291
293
294
295
296
297
298
299
300
301
302
304
306
308
310
313
315
317
318
319
321
322
323
324
325
327
328
329
330
332
334
335
336
337
338
339
340
Page: 7 of 377
Enhanced and Simplified Distribution > Integration > SSRs in NDC > ServiceEnhanced and Simplified Distribution > Integration > SSRs in NDC > Service
Definition (AIDM)Definition (AIDM)
Overview
Enhanced and Simplified Distribution > Reference DataEnhanced and Simplified Distribution > Reference Data
Codesets
Enhanced and Simplified Distribution > Reference Data > OtherEnhanced and Simplified Distribution > Reference Data > Other
TTBS Ticket Tax Box Service
Resolution 728
Enhanced and Simplified Distribution > Reference Data > ATSBEnhanced and Simplified Distribution > Reference Data > ATSB
1001 Document/message name, coded
1153 Reference qualifier
1245 Status indicator, coded
4183 Special condition, coded
6353 Number of units qualifier
9800 Reservation booking designator
9873 Cabin class of service, coded
9888 Form of payment identification
9932 Facility type, coded
9970 Product details qualifier
FHT Flight haul type
FST Flight segment type
IPT Instant purchase type
SFB Service fee basis
TDT Touchpoint device type
TTT Touchpoint transaction
Planning/Scheduling > MCT ImplementationPlanning/Scheduling > MCT Implementation
MCT Implementation
MCT Guides
Planning/Scheduling > Slots SchemasPlanning/Scheduling > Slots Schemas
Slot Implementation Guide and Schemas
Planning/Scheduling > Schedules SchemasPlanning/Scheduling > Schedules Schemas
Implementation Guide and Schemas
AIDM > IntroductionAIDM > Introduction
AIDM Getting Access to the Modeling Repository
AIDM > Additional ResourcesAIDM > Additional Resources
AIDM Modeling Guidelines
AIDM Project and CR Templates
AIDM Training Details
341
343
344
345
346
347
348
349
350
357
358
359
360
362
363
364
365
366
367
368
369
370
371
372
373
375
376
377
Page: 8 of 377
Welcome to the Enhanced and Simplified Distribution GuideWelcome to the Enhanced and Simplified Distribution Guide
This website holds information and best practices to aid with implementations of Enhanced and
Simplified Distribution. This site is managed by the Offer and Order Standard Setting Groups.
DISCLAIMER: The information contained in this publication is subject to constant review in the light of
changing government requirements and regulations. No reader should act on the basis of any such
information without referring to applicable laws and regulations and/or without taking appropriate
professional advice. Although every effort has been made to ensure accuracy, the International Air
Transport Association shall not be held responsible for any loss or damage caused by errors,
omissions, misprints or misinterpretation of the contents hereof. Furthermore, the International Air
Transport Association expressly disclaims any liability to any person or entity in respect of anything
done or omitted, by any such person or entity in reliance on the contents of this publication.
No Part of this publication may be reproduced, recast, reformatted or transmitted in any form by any
means, electronic or mechanical, including photocopying, recording or any information storage and
retrieval system, without the prior written permission from:
Senior Vice President, Marketing and Commercial Services
International Air Transport Association
800 Place Victoria, P.O. Box 113
Montreal, Quebec, Canada H4Z 1M1
IntroductionIntroduction
Page: 9 of 377
DISCLAIMER: The information contained in this publication is subject to constant review in the light of
changing government requirements and regulations. No reader should act on the basis of any such
information without referring to applicable laws and regulations and/or without taking appropriate
professional advice. Although every effort has been made to ensure accuracy, the International Air
Transport Association shall not be held responsible for any loss or damage caused by errors,
omissions, misprints or misinterpretation of the contents hereof. Furthermore, the International Air
Transport Association expressly disclaims any liability to any person or entity in respect of anything
done or omitted, by any such person or entity in reliance on the contents of this publication.
No Part of this publication may be reproduced, recast, reformatted or transmitted in any form by any
means, electronic or mechanical, including photocopying, recording or any information storage and
retrieval system, without the prior written permission from:
Senior Vice President, Marketing and Commercial Services
International Air Transport Association
800 Place Victoria, P.O. Box 113
Montreal, Quebec, Canada H4Z 1M1
Terms of UseTerms of Use
Page: 10 of 377
New Distribution Capability (“NDC”) is a standard for the transmission of data between different actors
in the air travel value chain. It is not an industry portal nor a commercial service but a data exchange
standard providing basic definitions, structures and formats for the transmission of data, allowing a
range of possibilities for the enhancement of the air travel shopping experience.
Nothing in the standard itself (based on IATA Passenger Services Conference Resolution 787) is
specific to the uses to which the standard is put in practice. Accordingly, the NDC standard itself
cannot be measured against data protection legislation. Rather the actual collection and use of data
by relevant actors (for example, airlines, travel agents, TMCs, metasearch companies, GDSs and
other technology companies) is the matter which must be evaluated, regardless of whether the NDC
standard or another data exchange format is used. In other words, it is the responsibility of each NDC
user to ensure that compliance with data protection legislation, including the GDPR, is achieved.
IATA has however developed privacy guidance, which forms a part of its NDC implementation guide.
Because NDC is a standard, and flexible in its application, it is possible for airlines and other NDC
users to achieve compliance with local data protection legislation in a number of ways. IATA does not
prescribe one approach over another. Such a matter is for individual NDC users to make independent
decisions on, after taking appropriate legal advice.
New Distribution CapabilityNew Distribution Capability
Page: 11 of 377
ONE Order is an IATA standard under Passenger Services Conference Resolution 797. ONE Order
aims to modernise the order management process in the airline industry. It achieves this by
overcoming the inefficiencies and unnecessary cost associated by having three separate records (the
Passenger Name Record or PNR; e-ticket and EMD, a standard for electronically documenting
ancillary revenue). ONE Order will replace these three existing records by providing the technical
standards upon which a single customer order record can be created and utilised. As with NDC, ONE
Order is not an industry portal nor a commercial service. This means that individual airlines and others
can implement the standard in a number of ways so as to ensure compliance with data protection
legislation.
Because ONE Order is a standard, and flexible in its application, it is possible for airlines and other
ONE Order users to achieve compliance with local data protection legislation in a number of ways.
IATA does not intend to prescribe one approach over another. Such a matter will be for individual ONE
Order users to make independent decisions on, after taking appropriate legal advice.
ONE OrderONE Order
Page: 12 of 377
This guide will refer to various terms such as ‘Seller’ or ‘ORA’ which have a common understanding
within the Industry. This section will define what these terms mean.
IntroductionIntroduction
Page: 13 of 377
DistributionDistribution
TermTerm DefinitionDefinition SourceSource
Enhanced
Distribution
Refers to the messages and standard relating to Resolution 787.
Commonly referred to as ‘NDC’
Resolution
787
Simplified
Distribution
Refers to the messages and standard relating to Resolution 797.
Commonly referred to as ‘ONE Order’
Resolution
797
PartiesParties
TermTerm DefinitionDefinition SourceSource
AirlineAirline
An enterprise operating aircrafts for commercial purposes which (i)
performs scheduled or non-scheduled air transport Services, or both,
which are available to the public for carriage of passengers, mail
and/or cargo and (ii) is certified for such purposes by the civil aviation
authority of the state in which it is established
AIDM
Glossary
TravelTravel
AgencyAgency
A private retailer or public Service individual that provides travel and
tourism related Services to the public on behalf of suppliers such as
activities, Airlines, car rentals, cruise lines, hotels, railways, travel
insurance, and package tours
AIDM
Glossary
AggregatorAggregator
An entity who distributes a Seller’s shopping request to multiple Airlines
and aggregates subsequent responses
AIDM
Glossary
AirlineAirline
Within the context of Enhanced and Simplified Distribution (ESD); the
Airline's role will be to respond to requests for Offers and to manage
Orders. This Order Management role extends to include processing
payments, issuing accountable documents or Orders, and where it
comes to Order servicing, they will also be responsible for handling this
from re-shopping for an Offer, through to applying any changes to the
Order, processing further payments or refunds, and modifying
accountable documents. To make the necessary distinction between
the different roles Airlines can play in interline transactions the Airline
role can be further subdivided
The OfferThe Offer
ResponsibleResponsible
AirlineAirline
(ORA)(ORA)
The Offer Responsible Airline (ORA) is a role played by an Airline in an
interline scenario whereby the Airline requests products from other
Airlines (POA) to supplement its Offer back to the Seller
TheThe
ParticipatingParticipating
Offer AirlineOffer Airline
(POA)(POA)
The Participating Offer Airline (POA) is an Airline that receives a
request from an ORA to supply products to the Seller within the ORA’s
Offer
AggregatorAggregator
An Aggregator proxies requests for Offers from Sellers to Airlines (or
ORAs) and consolidates the Airline responses and transmits them back
to the Seller. The Aggregator cannot alter the Offers it receives from
the Airlines but may, as a secondary role, pass Order Management
messages between Seller and Airline
SellerSeller
An organisation that interacts within supply chain to deliver Offers and
Orders to the Customer, such as a Travel Agent
CustomerCustomer
A person or organisation that is purchasing products or Services from
the downstream parties
DeliveryDelivery
ProviderProvider
(DP)(DP)
The entity responsible for delivery of a good or Service
DefinitionsDefinitions
Page: 14 of 377
LCCLCC Low-cost carrier
OfferOffer
A proposal to sell a specific set of products or Services under specific conditions, for a certain price.
ServiceService
The individual instance of a specific flight or Service Definition as it has been offered to (and
eventually Ordered and consumed by) a specific Customer in the context of a specific Offer and/or
Order.
A Service has the following possible delivery status:
BusinessBusiness
StateState
DescriptionDescription
READY TO
PROCEED
OM is in a position to allow a DP to prepare the Service. Customer is entitled to
receive the Service. This is typically a trigger for ORA to begin accounting process
READY TO
DELIVER
Provider is in a position to start delivery of the Service
IN
PROGRESS
The DP is in the process of delivering the Service. There is a universal concept
that the “In progress” status may block any further financial transactions; e.g.
refund
DELIVERED Service has been successfully delivered
FAILED TO
DELIVER
Service could not be delivered due to Airline´s or provider limitations
SUSPENDED
Delivery of the Service is suspended as a result of an Airline decision. Can only
revert back to the previous status. Exception is that Suspended may go to
Removed. This status may be used in case of fraud detection
REMOVED Service was deleted
NOT
CLAIMED
The Service has not been claimed by the Passenger for reasons as a result of
Passenger action or inaction. e.g. Passenger no-show, etc
EXPIRED
Service is no longer available for delivery. Service purchased with an associated
time limit for consumption and Service was never claimed. Service having been at
least Confirmed is no longer available as the Customer did not claim the Service
within a specific time period, as dictated by the Airline
UNABLE TO
DELIVER
It is not possible for the DP to deliver a Service. This could be for reasons of
availability, legal or regulatory constraint
The following state transitions are possible during the lifecycle of a Service:
Page: 15 of 377
OrderOrder
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 (e.g. 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 one or more Order Items each with an identifier that is unique within an
Airline’s Order Management system.
An Order may support non-homogeneity, i.e. each passenger in an Order may hold different sets of
order items at different prices.
OtherOther
Please refer to the AIDM Glossary for a more detailed list of Terms and Recommended Practice 1008.
Data DefinitionsData Definitions
TermTerm DefinitionDefinition
Page: 16 of 377
Airline URI Airline's Uniform Resource Identifier
SellerFollowUpIndicator
These are the actions required by the Seller upon receiving the
SellerFollowUpIndicator. This element is enumerated with the following:
Accept
Reshop
Cancel
Call Airline
Presence of this indicator tells the Seller that the Order has been
changed involuntarily by the Airline (ORA).
ActionTimeLimit
Presence of this element tells the Seller that the Order will be auto-
accepted or cancelled at the defined time.
ConsequenceOfInaction
Presence of this element tells the Seller that the Order will be auto-
accepted or cancelled once the ActionTimeLimit's defined time is
expired.
REA Reason for change indicator
The values for the ReasonCode field used in this document are for
illustration purposes.
The final list of new REA codeset values will be proposed once the
analysis on the involuntary and voluntary changes use-cases is
completed.
ChangeTypeCode Type of change indicator.
The values for the ChangeTypeCode field used in this document are for
illustration purposes.
The final list of new codeset values will be proposed once the analysis
on the involuntary and voluntary changes use-cases is completed.
Fare Waiver
Defined element that can be used to in reshop scenarios after a
schedule change has occurred.
Page: 17 of 377
This guide details how to use the technical messages under Enhanced Distribution and Simplified
Distribution.
Enhanced Distribution (NDC) messages cover the shopping, ordering and managing of Offers and
Orders (with or without tickets).
Simplified Distribution (ONE Order) messages cover Orders without tickets, servicing, accounting and
delivery.
OverviewOverview
Page: 18 of 377
NDC:
Reservation of Airline products and Services and the ability to advise Airline Accounting
Systems of these reservations
Order retrieval, change and cancellation (interaction Seller & Airline)
Payment and refund.
ONE Order:
Interaction between Airline Order Management Systems (OMS) and Accounting Systems to
keep these up to date at all times, particularly with regard to payments and refunds
Reporting to accounting for sales accounting and revenue recognition purpose for both online
and interline
Delivery workflow management and data exchange between Airlines and Delivery Providers
(DCS or others) and between Airlines (interline)
The ability to prepare Delivery Providers by providing them with all necessary passenger and
flight-related information to support Service delivery processes
Tracking of Service delivery and consumption of Airline products and Services
Order closure notification for accounting to support final accounting processes.
Overview of NDC and ONE OrderOverview of NDC and ONE Order:
It is important to note that it is not mandatory to implement all of the features or messages defined for
NDC and ONE Order to begin using Enhanced and Simplified Distribution. The full scope above
defines the end-state, however the transition path may take a number of forms, covering various
aspects of Offer and Order Management, Delivery and Accounting interactions. It is possible to
implement NDC without implementing ONE Order.
ScopeScope
Page: 19 of 377
Depending on the chosen implementation and the transition path to achieve this, the messages to be
implemented may vary. For example, interactions with the accounting system to advise Order
information may be implemented without the integration with delivery providers being in place, or vice
versa. However, the fundamental basis for ONE Order is that an airline is working with Orders and
Order Management.
Page: 20 of 377
PurposePurpose
The Airline Profile schemas provide the ability for an Airline to communicate information to the Seller
on a periodic basis with general information about the products and Services, or about that Airline.
With shopping requests, the Airline Profile provides information about what it is willing to receive and
has the capability to respond to. These schemas are a way for an Airline to manage the volume of
requests they receive and reduce queries it cannot fulfil.
Note the Airline Profile is not the equivalent of today’s schedule – whilst it includes information about
the routes an Airline will accept a shopping request for, the purpose of doing so is to avoid receiving
unnecessarily large volumes of irrelevant requests.
An Airline’s Profile is also available for consumption by other Airlines (ORAs), alongside Sellers and
Aggregators, for interline requests. This is to help them decide which Airlines (POAs) to send a further
shopping request to, where the ORA cannot fulfil the Seller/Aggregator’s entire request with its own
Services.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Request one of more Airline Profiles ✔ -
Filtering Request for all Airline Profiles ✔ -
Request simply a location of the Airline Profile ✔ -
Filter by Airline Owner Code ✔ -
Response List of Airline Supported Messages ✔ -
List of Warnings ✔ -
Airline Profile(s) including Points of sale, Address,
Rich Media and external resources (URLs)
✔ -
Message General Rich Content ✔ -
OverviewOverview
Page: 21 of 377
PurposePurpose
Like AirlineProfile, this notification will be used to send Airline Profile changes from the Airline to the
Seller (or ORA) as the change happens.
Implementation of this notification prevents excessive polling by partners and allows for event driven
updates to be sent directly from the Airline to its partners.
Features
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Push of an Airline Profile (or elements of) ✔ -
Response See Acknowledgement ✔ -
Message General Rich Content ✔ -
OverviewOverview
Page: 22 of 377
PurposePurpose
The AirShopping transaction set supports both specific and flexible shopping experiences for
anonymous or personalized shopping. Both functionally-rich attribute shopping and affinity shopping
support date range or specific month (calendar) shopping, amongst other features.
The response returns Offers which may include branded or itinerary-priced Offers with or without
ancillary Services. It also returns applicable rules for the integrated prices as well as for each Service.
The message also returns multi-media content at message level as well as media references at the
individual Offer level.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Search by Origin and Destination ✔ -
Search by Affinity Shopping ✔ -
Search either side of your query ✔ -
Search for specific Flight(s) ✔ -
Search in context of an existing Order ✔ -
Search in context of a Passenger ✔ -
Filtering Cabin Type ✔ -
Budget Amount ✔ -
Maximum Journey Distance ✔ -
Keyword Preferences ✔ -
Stay Period ✔ -
Boarding Gate ✔ -
Station Name ✔ -
Terminal Name ✔ -
Departure Time ✔ -
Time before or after ✔ -
Alliance Criteria ✔ -
Baggage Pricing Criteria ✔ -
Carrier Preference ✔ -
Fare Criteria ✔ -
Aircraft Type ✔ -
Flight Characteristics (red eye etc) ✔ -
Payment Information ✔ -
Frequent Flyer Information ✔ -
Promotions ✔ -
Seat Characteristics ✔ -
Special Needs ✔ -
Trip Purpose ✔ -
Response Carrier Offers Summary of Offers (highest, lowest) ✔ -
Lowest Offer Price ✔ -
A la Carte Offer ✔ -
Carrier Offers ✔ -
OverviewOverview
Page: 23 of 377
Price Calendar ✔ -
Other Marketing Messages ✔ -
Commission applicable to the Agent ✔ -
Promotion used ✔ -
Policy Information used (PCI, PII) ✔ -
Payment Information ✔ -
Message General Multilingual Support ✔ -
Inventory Guarantee ✔ -
Multi-Currency ✔ -
Rich Media Support ✔ -
Page: 24 of 377
PurposePurpose
InvReleaseNotif transaction sends an unsolicited notification of released guaranteed inventory. The
Acknowledgement message may be returned to acknowledge receipt of the notification.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Notification
Advises of the Inventory Guarantee
Reference which will be released
✔ -
Advises of Time Limit ✔ -
Advises the related Offer ✔ -
Advised the related order ✔ -
Response
See
Acknowledgement
OverviewOverview
Note:Note:
This message is under review for PADIS 19.2 and above.
Page: 25 of 377
PurposePurpose
The OfferPrice transaction set may return two different sets of content. Based on request attributes,
the response may initially provide additional à la carte ancillary services that are applicable and
available for the selected Offer.
If no ancillary services are available, the message returns a final pricing. If ancillary services are
available, the modified pricing request includes selected services and returns a final pricing that
includes service(s) selection.
The response message also returns multi-media content at the message level.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Request Offer based on one or more Offers ✔ -
Request Offer based on Origin and Destination ✔ -
Request Offer in the Context of a Ticket ✔ -
Ability to specify the Language, Currency for the
Response
✔ -
Filtering Alliances ✔ -
Baggage Criteria (Prepaid, Carry-on) ✔ -
Cabin Type ✔ -
Carrier ✔ -
Connections ✔ -
Fare Rules ✔ -
Flight Criteria ✔ -
Payment ✔ -
Pricing ✔ -
Program Criteria ✔ -
Promotion Criteria ✔ -
Seat Criteria ✔ -
Special Needs ✔ -
Trip Purpose ✔ -
Response Offers A Priced Offer ✔ -
Other Offers ✔ -
Commission ✔ -
Payment Info Used ✔ -
Promotions ✔ -
Baggage Disclosure ✔ -
Service ✔ -
Seats ✔ -
Other Return marketing text ✔ -
Message General Multilingual Support ✔ -
Inventory Guarantee ✔ -
Multi-Currency ✔ -
Rich Media Support ✔ -
OverviewOverview
Page: 26 of 377
Page: 27 of 377
OfferPrice Request ElementsOfferPrice Request Elements
This section documents the key elements for the OfferPrice request and how to correctly use these to
achieve the required functionality.
01. Transmitting an OfferPrice Request with Fare Waiver information01. Transmitting an OfferPrice Request with Fare Waiver information
The Seller may send an OfferPrice Request to the Airline with Fare Waiver information.
OfferPrice Response ElementsOfferPrice Response Elements
02. Transmitting an OfferPrice response with Fare Waiver information02. Transmitting an OfferPrice response with Fare Waiver information
The Airline (ORA) may transmit an OfferPrice response with Fare Waiver information.
Structure of the Invol ServicingStructure of the Invol Servicing
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
Page: 28 of 377
PurposePurpose
The SeatAvailability transaction set returns data used to construct respective seat maps with fully
integrated fees for any identified premium seats. The message also returns multi-media content at the
message level with media content references at the individual Service level.
ScopeScope
Used to display Services on a seat map before or after the creation of an Order.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core
Request for Seat availability in the context of an
Offer
✔ -
Request for Seat availability in the context of an
Order
✔ -
Request for Seat availability in the context of a
Passenger Segment
✔ -
Filtering Filter by Cabin Type ✔ -
Filter by Seat Type ✔ -
Filter by Service Type ✔ -
Filter by Trip Purpose Code ✔ -
Filter by Policy ✔ -
Response Returns a Seat Map with cabins ✔ -
Returns a la carte Offers ✔ -
Includes Baggage Allowances ✔ -
Includes Baggage Disclosures ✔ -
Includes Passenger Information ✔ -
Includes Seat Profiles ✔ -
Message General Inventory Guarantee ✔ -
Rich Content ✔ -
Multi language ✔ -
Groups ✔ -
Multi-Currency ✔ -
OverviewOverview
Page: 29 of 377
PurposePurpose
The purpose of ServiceList is to return a list of all applicable ancillary services that meet the Sellers
request qualifiers and flights. The message supports shopping for additional a la carte services to
complement any selected Offer, as well as shopping for specialty service items not generally included
in an initial Offer but rather based on service search filters, e.g. sports equipment specialty baggage
and unaccompanied minor fees. The message also returns multi-media content at both the message
and individual service levels identified in the Offer.
ScopeScope
In a distribution context, this message is used by the Airline Offer and/or Order Management System to
present relevant a la cate Offers to the Seller. For NDC interline, this message can be used to present
POA Offers to the ORA. Within an Order Management System, the Airline could have external Service
Providers, in which case this message can be used to provide relevant Offers from the Service
Provider to the Airlines Offer/Order Management System.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Accept an Offer as input for Services ✔ -
Accept an Order as input for Services ✔ -
Accept an Itinerary as input for Services ✔ -
Filter a la Carte Offers by specific Itinerary
Segment.
✔ -
Filter a la Carte Offers by specific Passengers. ✔ -
Filtering Alliances ✔ -
Baggage Criteria (Prepaid, Carry-on) ✔ -
Cabin Type ✔ -
Carrier ✔ -
Connections ✔ -
Fare Rules ✔ -
Flight Criteria ✔ -
Payment ✔ -
Pricing ✔ -
Program Criteria ✔ -
Promotion Criteria ✔ -
Seat Criteria ✔ -
Special Needs ✔ -
Trip Purpose ✔ -
Response Offers Return 'a la Carte' Offer(s) ✔ -
Baggage Allowance ✔ -
Baggage Disclosure ✔ -
Service ✔ -
Seats ✔ -
Other Return marketing text ✔ -
OverviewOverview
Page: 30 of 377
Message General Multilingual Support ✔ -
Inventory Guarantee ✔ -
Multi-Currency ✔ -
Rich Media Support ✔ -
Page: 31 of 377
OverviewOverview
This message pair is used to query the airline and return information around fares, conditions,
products and services including general compliance and regulatory information.
Note: Information returned within this message is not programmatically readable. Programmatically
readable and relevant rule information for the Seller relating to Change and Cancel fees (for example)
will be found within the relevant message whereever there is reference to an Offer or an Order. See
Offer and Order Rules.
Order Rules Request ElementsOrder Rules Request Elements
This section documents the key elements for OrderRules request and how to correctly use these to
achieve the required functionality.
There are three functions performed by this message which will return Fare information.
01. Requesting Fare Rules using an Itinerary01. Requesting Fare Rules using an Itinerary
A Seller can request fare rules and conditions for an itinerary, however note that this is not for a
specific itinerary for a passenger or in relation to any other segment of travel. Information returned is
simply for that product on that segment.
02. Requesting Specific Fare Rules using an Offer02. Requesting Specific Fare Rules using an Offer
A Seller can request specific fare rules and conditions for a customer itineray by passing in an Offer ID
(for the entire fare rules and conditions) or by filtering the fare rules to a specific Offer Item by sending
the Airline the Offer ID and the required Offer Item ID.
Order Rules CapabilitiesOrder Rules Capabilities
<iata:CoreRequest>
<iata:CoreRequest>
<iata:FareRef>
<iata:FareRef>
<iata:AirlineDesigCode>XB</iata:AirlineDesigCode>
<iata:AirlineDesigCode>XB</iata:AirlineDesigCode>
<iata:Arrival>
<iata:Arrival>
<iata:IATALocationCode>SIN</iata:IATALocationCode>
<iata:IATALocationCode>SIN</iata:IATALocationCode>
</iata:Arrival>
</iata:Arrival>
<iata:Dep>
<iata:Dep>
<iata:IATALocationCode>GVA</iata:IATALocationCode>
<iata:IATALocationCode>GVA</iata:IATALocationCode>
</iata:Dep>
</iata:Dep>
<iata:FareBasisCode>JBZDI</iata:FareBasisCode>
<iata:FareBasisCode>JBZDI</iata:FareBasisCode>
</iata:FareRef>
</iata:FareRef>
</iata:CoreRequest>
</iata:CoreRequest>
None Copy
NoteNote
This is not currently supported
Page: 32 of 377
03. Requesting Specific Fare Rules using an Order03. Requesting Specific Fare Rules using an Order
A Seller can request the full fare rules and conditions for an Order by supplying the Airline with an
Order ID. Note that the Seller cannot filter the response using an Order Item ID.
OrderRules Response ElementsOrderRules Response Elements
This section documents the key elements for OrderRules response and how to correctly use these to
achieve the required functionality.
01. Responding with Fare Rules01. Responding with Fare Rules
Regardless of the query in the OfferRules request, the response shall be consistant with the fare rule
information as below.
<iata:CoreRequest>
<iata:CoreRequest>
<iata:OrderRef>
<iata:OrderRef>
<iata:OrderID>XB0001A2B3C4D</iata:OrderID>
<iata:OrderID>XB0001A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:OrderRef>
</iata:OrderRef>
</iata:CoreRequest>
</iata:CoreRequest>
None Copy
<iata:Response>
<iata:Response>
<iata:OrderID>XB0001A2B3C4D</iata:OrderID>
<iata:OrderID>XB0001A2B3C4D</iata:OrderID>
<iata:Rules>
<iata:Rules>
<iata:AirlineDesigCode>XB</iata:AirlineDesigCode>
<iata:AirlineDesigCode>XB</iata:AirlineDesigCode>
<iata:Arrival>
<iata:Arrival>
<iata:IATALocationCode>SIN</iata:IATALocationCode>
<iata:IATALocationCode>SIN</iata:IATALocationCode>
</iata:Arrival>
</iata:Arrival>
<iata:Dep>
<iata:Dep>
<iata:IATALocationCode>GVA</iata:IATALocationCode>
<iata:IATALocationCode>GVA</iata:IATALocationCode>
</iata:Dep>
</iata:Dep>
<iata:FareBasisCode>JBZDI</iata:FareBasisCode>
<iata:FareBasisCode>JBZDI</iata:FareBasisCode>
<iata:FareRule>
<iata:FareRule>
<iata:FareRuleText>
<iata:FareRuleText>
<iata:RemarkText>FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
<iata:RemarkText>FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT FARE RULE TEXT
</iata:RemarkText>
</iata:RemarkText>
</iata:FareRuleText>
</iata:FareRuleText>
</iata:FareRule>
</iata:FareRule>
None Copy
Page: 33 of 377
</iata:Rules>
</iata:Rules>
</iata:Response>
</iata:Response>
Page: 34 of 377
PurposePurpose
The OrderReshop transaction set passes new shopping requests from a Seller to an ORA to replace
existing specified Order Items in an Order or for new shopping requests to add to an existing Order.
The ORA responds with new Offers within the context of the existing Order. The response will include
details of any additional collection or refund due against proposed changes (including a full
cancellation).
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core
Request a Reshop/price in the context of a
Booking Reference
✔ -
Request a Reshop/price in the context of an Order
ID
✔ -
Specify the Order Action Context ✔ -
Reprice an Order ✔ -
Reshop an Order ✔ -
Update a Passenger Name ✔ -
Update/Add/delete Order Items ✔ -
Filtering By Baggage Allowances ✔ -
By Currency ✔ -
By Inventory Guarantee ✔ -
By Pricing ✔ -
Response Advise of a change in fees ✔ -
Advise applicable commission ✔ -
Advise Marketing Messages ✔ -
Advise Payment information ✔ -
Return the repriced Offer ✔ -
Return multiple reshopped Offers ✔ -
Message General Inventory Guarantee ✔ -
Multi language ✔ -
Multi-Currency ✔ -
OverviewOverview
Page: 35 of 377
OrderReshop request ElementsOrderReshop request Elements
01. Transmitting an OrderReshop Request with Fare Waiver information01. Transmitting an OrderReshop Request with Fare Waiver information
The Seller may send an OrderReshop Request to the Airline with Fare Waiver information.
OrderReshop respond ElementsOrderReshop respond Elements
This section documents the key elements for the OrderReshop response and how to correctly use
these to achieve the required functionality.
02. Transmitting an OrderReshop response with Fare Waiver information02. Transmitting an OrderReshop response with Fare Waiver information
The Airline (ORA) may transmit an Order Reshop response with Fare Waiver information.
Structure of the Invol ServicingStructure of the Invol Servicing
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
Page: 36 of 377
OrderReshop Request ElementsOrderReshop Request Elements
This section documents the key elements for the OrderReshop request and how to correctly use these
to achieve the required functionality.
01. Transmitting an OrderReshop Request with Respend indicator01. Transmitting an OrderReshop Request with Respend indicator
When deleting a service, a Seller may send the OrderReshop request with the Respend indicator to
indicate if the Customer wishes the money to be refunded (Respend indicator = false) or respent
(Respend indicator = true).
XPath: IATA_OrderReshopRQ/Request/UpdateOrder/ReshopOrder/ServiceOrder/DeleteOrderItem
OrderReshop Response ElementsOrderReshop Response Elements
This section documents the key elements for the OrderReshop response and how to correctly use
these to achieve the required functionality.
02. Transmitting an OrderReshop Response with the Unchanged indicator02. Transmitting an OrderReshop Response with the Unchanged indicator
An Airline may return the OrderReshop response with the Unchanged indicator at service level to
indicate the Service(s) that remain(s) unchanged if the Customer decides to accept the reshop
response proposal.
Xpath: IATA_OrderReshopRS/Response/ReshopResults/ReshopOffers/Offer/DeleteOrderItem
Voluntary Servicing for full, partial cancellation and orderVoluntary Servicing for full, partial cancellation and order
modificationmodification
<UpdateOrder>
<UpdateOrder>
<ReshopOrder>
<ReshopOrder>
<ServiceOrder>
<ServiceOrder>
<DeleteOrderItem>
<DeleteOrderItem>
<OrderItemRefID>ORITM001</OrderItemRefID>
<OrderItemRefID>ORITM001</OrderItemRefID>
<RespendInd>true</RespendInd>
<RespendInd>true</RespendInd>
</DeleteOrderItem>
</DeleteOrderItem>
</ServiceOrder>
</ServiceOrder>
</ReshopOrder>
</ReshopOrder>
<RepriceOrder/>
<RepriceOrder/>
</UpdateOrder>
</UpdateOrder>
None Copy
<DeleteOrderItem>
<DeleteOrderItem>
<ExistingOrderItem>
<ExistingOrderItem>
<ExistingService>
<ExistingService>
<ServiceRefID>SVC01</ServiceRefID>
<ServiceRefID>SVC01</ServiceRefID>
<UnchangedInd>true</UnchangedInd>
<UnchangedInd>true</UnchangedInd>
</ExistingService>
</ExistingService>
<OrderItemRefID>ORITM001</OrderItemRefID>
<OrderItemRefID>ORITM001</OrderItemRefID>
None Copy
Page: 37 of 377
03. Transmitting an OrderReshop Response with the Price Differential, Differential03. Transmitting an OrderReshop Response with the Price Differential, Differential
Type code, Old Price, New Price and Grand Total.Type code, Old Price, New Price and Grand Total.
An Airline may return the OrderReshop response with the Price Differential, Differential Type code,
Old Price, New Price and Grand Total.
XPath: IATA_OrderReshopRS/Response/ReshopResults/ReshopOffers/Offer/DeleteOrderItem
</ExistingOrderItem>
</ExistingOrderItem>
…
…
</DeleteOrderItem>
</DeleteOrderItem>
<DeleteOrderItem>
<DeleteOrderItem>
<ExistingOrderItem>
<ExistingOrderItem>
<OrderItemRefID>ORDITM001</OrderItemRefID>
<OrderItemRefID>ORDITM001</OrderItemRefID>
</ExistingOrderItem>
</ExistingOrderItem>
<OfferItemID>OFITM001</OfferItemID>
<OfferItemID>OFITM001</OfferItemID>
<PriceDifferential>
<PriceDifferential>
<DifferentialTypeCode>Refund</DifferentialTypeCode>
<DifferentialTypeCode>Refund</DifferentialTypeCode>
<DiffPrice>
<DiffPrice>
<Price>
<Price>
<BaseAmount>-40.00</BaseAmount>
<BaseAmount>-40.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>-20.00</Amount>
<Amount>-20.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>-60.00</TotalAmount>
<TotalAmount>-60.00</TotalAmount>
</Price>
</Price>
</DiffPrice>
</DiffPrice>
<GrandTotalAmount>-60.0</GrandTotalAmount>
<GrandTotalAmount>-60.0</GrandTotalAmount>
<NewPrice>
<NewPrice>
<Price>
<Price>
<BaseAmount>25.00</BaseAmount>
<BaseAmount>25.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>15.00</Amount>
<Amount>15.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>40.00</TotalAmount>
<TotalAmount>40.00</TotalAmount>
</Price>
</Price>
</NewPrice>
</NewPrice>
<OldPrice>
<OldPrice>
<Price>
<Price>
<BaseAmount>65.00</BaseAmount>
<BaseAmount>65.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>35.00</Amount>
<Amount>35.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>100.00</TotalAmount>
<TotalAmount>100.00</TotalAmount>
</Price>
</Price>
</OldPrice>
</OldPrice>
None Copy
Page: 38 of 377
04. Transmitting an OrderReshop Response with Penalty reference04. Transmitting an OrderReshop Response with Penalty reference
An Airline may return the OrderReshop response with the Penalty reference.
XPath: IATA_OrderReshopRS/Response/ReshopResults/ReshopOffers/Offer/DeleteOrderItem
05. Transmitting an OrderReshop Response with Penalty net indicator05. Transmitting an OrderReshop Response with Penalty net indicator
An Airline may return the OrderReshop response with the Penalty net indicator to indicate if the
penalty has been netted or not.
XPath: IATA_OrderReshopRS/Response/DataList
XPath: IATA_OrderReshopRS/Response/ReshopResults/ReshopOffers/Offer/DeleteOrderItem
</PriceDifferential>
</PriceDifferential>
</DeleteOrderItem>
</DeleteOrderItem>
<DeleteOrderItem>
<DeleteOrderItem>
<ExistingOrderItem>
<ExistingOrderItem>
<OrderItemRefID>ORITM01</OrderItemRefID>
<OrderItemRefID>ORITM01</OrderItemRefID>
</ExistingOrderItem>
</ExistingOrderItem>
<OfferItemID>OFITM01</OfferItemID>
<OfferItemID>OFITM01</OfferItemID>
<PenaltyRefID>PEN001</PenaltyRefID>
<PenaltyRefID>PEN001</PenaltyRefID>
</DeleteOrderItem>
</DeleteOrderItem>
None Copy
<DataLists>
<DataLists>
<PenaltyList>
<PenaltyList>
<Penalty>
<Penalty>
<NetInd>true</NetInd>
<NetInd>true</NetInd>
<PenaltyID>PEN001</PenaltyID>
<PenaltyID>PEN001</PenaltyID>
<Price>
<Price>
<BaseAmount>20.00</BaseAmount>
<BaseAmount>20.00</BaseAmount>
<Totalmount>20.00</Totalmount>
<Totalmount>20.00</Totalmount>
</Price>
</Price>
</Penalty>
</Penalty>
</PenaltyList>
</PenaltyList>
</DataLists>
</DataLists>
None Copy
<DeleteOrderItem>
<DeleteOrderItem>
<ExistingOrderItem>
<ExistingOrderItem>
<OrderItemRefID>ORITM01</OrderItemRefID>
<OrderItemRefID>ORITM01</OrderItemRefID>
</ExistingOrderItem>
</ExistingOrderItem>
<OfferItemID>OFITM01</OfferItemID>
<OfferItemID>OFITM01</OfferItemID>
<PenaltyRefID>PEN001</PenaltyRefID>
<PenaltyRefID>PEN001</PenaltyRefID>
</DeleteOrderItem>
</DeleteOrderItem>
None Copy
Page: 39 of 377
PurposePurpose
OrderCreate is an outbound message from Seller/Aggregator to Airline (and ORA to POA if applicable)
that contains the details of a selected Offer and is used to request the creation of an Order by the
ORA (or POA). Within OrderCreate, full passenger information will be sent. Payment information may
or may not be included within the request from Seller/Aggregator to ORA.
OrderView returns up to date contents of an Order such as pricing information, conditions, time limits,
Order status and passenger information. When payment has been processed at the time of Order
Creation it also includes the status of this and, where they have already been issued, at least
accountable document references (and further accountable document data if required).
FeaturesFeatures
MessageMessage ComponentComponent FeatureFeature 18.218.2 ChangesChanges
Request Core
Supports creating an Order in the context of an
Order ID
✔ -
Supports Commission for a Seller ✔ -
Creating order from Offer Item IDs ✔ -
✔ -
Payment Single FOP ✔ -
Multiple FOP ✔ -
Payment Per Passenger ✔ -
Payment per Offer ✔ -
Payment by Document ✔ -
Payment by Bank Transfer ✔ -
Payment by Cash ✔ -
Payment by BSP Cash ✔ -
Payment by Cheque ✔ -
Payment by Direct Bill ✔ -
Payment by Loyalty Redemption ✔ -
Payment by Card ✔ -
Payment using 3D Secure ✔ -
Payment by Voucher ✔ -
Payment by Other ✔ -
Response See OrderView RS ✔ -
OverviewOverview
Page: 40 of 377
OrderCreate Request ElementsOrderCreate Request Elements
This section documents the key elements for the OrderCreate request and how to correctly use these
to achieve the required functionality.
01. Transmitting an OrderCreate request with multiple addresses at Destination01. Transmitting an OrderCreate request with multiple addresses at Destination
The Airline (ORA) may send an OrderCreate request to the Seller with multiple addresses at
destination.
Ability to Handle Multiple Types of ContactsAbility to Handle Multiple Types of Contacts
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044756496451</PhoneNumber>
<PhoneNumber>0044756496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>GB</CountryCode>
<CountryCode>GB</CountryCode>
<PostalCode>AA1 2BB</PostalCode>
<PostalCode>AA1 2BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>001156496451</PhoneNumber>
<PhoneNumber>001156496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>New York</CityName>
<CityName>New York</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>US</CountryCode>
<CountryCode>US</CountryCode>
<PostalCode>12345</PostalCode>
<PostalCode>12345</PostalCode>
<StreetText>2 Broad Street</StreetText>
<StreetText>2 Broad Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
None Copy
Page: 41 of 377
02. Transmitting an OrderCreate request with emergency contact Details02. Transmitting an OrderCreate request with emergency contact Details
The Airline (ORA) may send an OrderCreate request to the Seller with Emergency Contact Details.
<Pax>
<Pax>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<PaxID>PAX01</PaxID>
<PaxID>PAX01</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT001</ContactInfoID>
<ContactInfoID>CT001</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PRO</ContactTypeText>
<ContactTypeText>PRO</ContactTypeText>
<PostalCode>AA12BB</PostalCode>
<PostalCode>AA12BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT002</ContactInfoID>
<ContactInfoID>CT002</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044123497854</PhoneNumber>
<PhoneNumber>0044123497854</PhoneNumber>
None Copy
Page: 42 of 377
03. Transmitting an OrderCreate request with contact details for an unaccompanied03. Transmitting an OrderCreate request with contact details for an unaccompanied
minorminor
The Airline (ORA) may send an OrderCreate request to the Seller with contact details for an
unaccompanied minor.
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Mother</GivenName>
<GivenName>Mother</GivenName>
<IndividualID>IND01</IndividualID>
<IndividualID>IND01</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>006111111</PhoneNumber>
<PhoneNumber>006111111</PhoneNumber>
</Phone>
</Phone>
None Copy
Page: 43 of 377
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Father</GivenName>
<GivenName>Father</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044222222</PhoneNumber>
<PhoneNumber>0044222222</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT03</ContactInfoID>
<ContactInfoID>CT03</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>GrandFather</GivenName>
<GivenName>GrandFather</GivenName>
<IndividualID>IND03</IndividualID>
<IndividualID>IND03</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00443333333</PhoneNumber>
<PhoneNumber>00443333333</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT04</ContactInfoID>
<ContactInfoID>CT04</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Aunt</GivenName>
<GivenName>Aunt</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00144444444</PhoneNumber>
<PhoneNumber>00144444444</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
Page: 44 of 377
OrderCreate Request ElementsOrderCreate Request Elements
This section documents the key elements for the OrderCreate request and how to correctly use these
to achieve the required functionality.
01. Transmitting an OrderCreate request with Net Clearance Amount01. Transmitting an OrderCreate request with Net Clearance Amount
The Seller may send the OrderCreate request informing the Airline (ORA) with Net Clearance Amount
Net clearance amountNet clearance amount
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 45 of 377
PurposePurpose
The OrderChange transaction requests modifications to an Order by specifying which Order Items to
change and which Offer Items to replace them with. When the ORA has applied the change, the
updated view of the Order is returned.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core
Request change in the context of a Booking
Reference
✔ -
Request change in the context of an Order ID ✔ -
Change Order Items ✔ -
Advise the Acceptance of a Repriced Order ✔ -
Change Passengers ✔ -
Change to Passenger Groups ✔ -
Advise of the preferred Form of Payment to
refund to
✔ -
Response
See
OrderView
OverviewOverview
Page: 46 of 377
OrderChange Request ElementsOrderChange Request Elements
This section documents the key elements for the OrderChange request and how to correctly use
these to achieve the required functionality.
01. Transmitting an OrderChange request with multiple addresses at Destination01. Transmitting an OrderChange request with multiple addresses at Destination
The Airline (ORA) may send an OrderChange request to the Seller with multiple addresses at
destination.
Ability to Handle Multiple Types of ContactsAbility to Handle Multiple Types of Contacts
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044756496451</PhoneNumber>
<PhoneNumber>0044756496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>GB</CountryCode>
<CountryCode>GB</CountryCode>
<PostalCode>AA1 2BB</PostalCode>
<PostalCode>AA1 2BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>001156496451</PhoneNumber>
<PhoneNumber>001156496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>New York</CityName>
<CityName>New York</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>US</CountryCode>
<CountryCode>US</CountryCode>
<PostalCode>12345</PostalCode>
<PostalCode>12345</PostalCode>
<StreetText>2 Broad Street</StreetText>
<StreetText>2 Broad Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
None Copy
Page: 47 of 377
02. Transmitting an OrderChange request with emergency contact Details02. Transmitting an OrderChange request with emergency contact Details
The Airline (ORA) may send an OrderChange request to the Seller with Emergency Contact Details.
<Pax>
<Pax>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<PaxID>PAX01</PaxID>
<PaxID>PAX01</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT001</ContactInfoID>
<ContactInfoID>CT001</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PRO</ContactTypeText>
<ContactTypeText>PRO</ContactTypeText>
<PostalCode>AA12BB</PostalCode>
<PostalCode>AA12BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT002</ContactInfoID>
<ContactInfoID>CT002</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044123497854</PhoneNumber>
<PhoneNumber>0044123497854</PhoneNumber>
</Phone>
</Phone>
None Copy
Page: 48 of 377
03. Transmitting an OrderChange request with contact details for an03. Transmitting an OrderChange request with contact details for an
unaccompanied minorunaccompanied minor
The Airline (ORA) may send an OrderChange request to the Seller with contact details for an
unaccompanied minor.
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Mother</GivenName>
<GivenName>Mother</GivenName>
<IndividualID>IND01</IndividualID>
<IndividualID>IND01</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>006111111</PhoneNumber>
<PhoneNumber>006111111</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
None Copy
Page: 49 of 377
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Father</GivenName>
<GivenName>Father</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044222222</PhoneNumber>
<PhoneNumber>0044222222</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT03</ContactInfoID>
<ContactInfoID>CT03</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>GrandFather</GivenName>
<GivenName>GrandFather</GivenName>
<IndividualID>IND03</IndividualID>
<IndividualID>IND03</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00443333333</PhoneNumber>
<PhoneNumber>00443333333</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT04</ContactInfoID>
<ContactInfoID>CT04</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Aunt</GivenName>
<GivenName>Aunt</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00144444444</PhoneNumber>
<PhoneNumber>00144444444</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
Page: 50 of 377
04. Transmitting an OrderChange request with Net Clearance Amount04. Transmitting an OrderChange request with Net Clearance Amount
The Seller may send the OrderChange request informing the Airline (ORA) with Net Clearance Amount
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 51 of 377
OrderChange Request ElementsOrderChange Request Elements
This section documents the key elements for the OrderChange request and how to correctly use
these to achieve the required functionality.
01. Transmitting an OrderChange request with Net Clearance Amount01. Transmitting an OrderChange request with Net Clearance Amount
The Seller may send the OrderChange request informing the Airline (ORA) with Net Clearance Amount
Net Clearance AmountNet Clearance Amount
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 52 of 377
OrderChange Request ElementsOrderChange Request Elements
This section documents the key elements for the OrderChange request and how to correctly use
these to achieve the required functionality.
01. Transmitting an OrderChange Request with the Customer acceptance of the01. Transmitting an OrderChange Request with the Customer acceptance of the
planned schedule changeplanned schedule change
The Seller may send an OrderChange Request to the Airline with the Customer acceptance of the
Planned Schedule Change.
XPath: IATA_OrderChangeRQ/Request/ChangeOrder
Structure of the Invol servicingStructure of the Invol servicing
<ChangeOrder>
<ChangeOrder>
<AcceptChange>
<AcceptChange>
<OrderItemRefID>ORITM002</OrderItemRefID>
<OrderItemRefID>ORITM002</OrderItemRefID>
</AcceptChange>
</AcceptChange>
</ChangeOrder>
</ChangeOrder>
None Copy
Page: 53 of 377
PurposePurpose
The OrderChangeNotif transaction sends an unsolicited notification of a voluntary or involuntary
change to an Order.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Advise of Commission ✔ -
Send changes of the Order ✔ -
Send a list of changes associated to the
Order
✔ -
Advise changes of any related Tickets ✔ -
Response
See
Acknowledgement
OverviewOverview
Page: 54 of 377
OrderChangeNotif Request ElementsOrderChangeNotif Request Elements
This section documents the key elements for the OrderChangeNotif request and how to correctly use
these to achieve the required functionality.
01. Transmitting an OrderChangeNotif request with Net Clearance Amount01. Transmitting an OrderChangeNotif request with Net Clearance Amount
The Seller may send the OrderChangeNotif request informing the Airline (ORA) with Net Clearance
Amount
Net Clearance AmountNet Clearance Amount
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 55 of 377
OrderChangeNotif Request ElementsOrderChangeNotif Request Elements
This section documents the key elements for the OrderChangeNotif request and how to correctly use
these to achieve the required functionality.
01. Transmitting an OrderChangeNotif request with multiple change operation01. Transmitting an OrderChangeNotif request with multiple change operation
groups.groups.
The Airline (ORA) may include multiple sequences of order changes in one notification to the seller.
02. Transmitting an OrderChangeNotif request with name changes.02. Transmitting an OrderChangeNotif request with name changes.
The Airline (ORA) may notify the Seller of customer name changes.
Structure of the order change notificationStructure of the order change notification
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeOperationGroup>
<ChangeOperationGroup>
…
…
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<ChangeGroup>
<ChangeGroup>
<ChangeGroupSequenceNumber>2</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>2</ChangeGroupSequenceNumber>
<ChangeOperationGroup>
<ChangeOperationGroup>
…
…
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>OR001</OrderID>
<OrderID>OR001</OrderID>
</Notification>
</Notification>
None Copy
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2019-09-24T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2019-09-24T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>NAMECHG</ChangeTypeCode>
<ChangeTypeCode>NAMECHG</ChangeTypeCode>
<New>
<New>
<DataLists>
<DataLists>
<PaxList>
<PaxList>
<Pax>
<Pax>
<Individual>
<Individual>
<MiddleName>Jimmy</MiddleName>
<MiddleName>Jimmy</MiddleName>
<Surname>Smith</Surname>
<Surname>Smith</Surname>
</Individual>
</Individual>
None Copy
Page: 56 of 377
03. Transmitting an OrderChangeNotif request with phone number changes.03. Transmitting an OrderChangeNotif request with phone number changes.
The Airline (ORA) may notify the Seller of phone number changes.
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
</New>
</New>
<Old>
<Old>
<DataLists>
<DataLists>
<PaxList>
<PaxList>
<Pax>
<Pax>
<Individual>
<Individual>
<MiddleName>Jimy</MiddleName>
<MiddleName>Jimy</MiddleName>
<Surname>Smithy</Surname>
<Surname>Smithy</Surname>
</Individual>
</Individual>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
</Old>
</Old>
<ReasonCode>NAMECHG</ReasonCode>
<ReasonCode>NAMECHG</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>7</OrderVersion>
<OrderVersion>7</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>OR001</OrderID>
<OrderID>OR001</OrderID>
</Notification>
</Notification>
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>CONTACTCHG</ChangeTypeCode>
<ChangeTypeCode>CONTACTCHG</ChangeTypeCode>
<New>
<New>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT001</ContactInfoID>
<ContactInfoID>CT001</ContactInfoID>
<Phone>
<Phone>
<PhoneNumber>+1 567 888888</PhoneNumber>
<PhoneNumber>+1 567 888888</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
</New>
</New>
None Copy
Page: 57 of 377
04. Transmitting an OrderChangeNotif request with Payment status change.04. Transmitting an OrderChangeNotif request with Payment status change.
The Airline (ORA) may notify the Seller of a Payment status change.
<Old>
<Old>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT001</ContactInfoID>
<ContactInfoID>CT001</ContactInfoID>
<Phone>
<Phone>
<PhoneNumber>+1 234 555555</PhoneNumber>
<PhoneNumber>+1 234 555555</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
</Old>
</Old>
<ReasonCode>CONTACTCHG</ReasonCode>
<ReasonCode>CONTACTCHG</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>3</OrderVersion>
<OrderVersion>3</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
</Notification>
</Notification>
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>PAYMENTSTATUSCHG</ChangeTypeCode>
<ChangeTypeCode>PAYMENTSTATUSCHG</ChangeTypeCode>
<New>
<New>
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount/>
<Amount/>
<PaymentID>PAY001</PaymentID>
<PaymentID>PAY001</PaymentID>
<PaymentMethod>
<PaymentMethod>
<PaymentCard>
<PaymentCard>
<CardBrandCode>VI</CardBrandCode>
<CardBrandCode>VI</CardBrandCode>
</PaymentCard>
</PaymentCard>
</PaymentMethod>
</PaymentMethod>
<PaymentStatusCode>COMMITTED</PaymentStatusCode>
<PaymentStatusCode>COMMITTED</PaymentStatusCode>
<TypeCode>CC</TypeCode>
<TypeCode>CC</TypeCode>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
</New>
</New>
<Old>
<Old>
None Copy
Page: 58 of 377
05. Transmitting an OrderChangeNotif request with Flight Time change.05. Transmitting an OrderChangeNotif request with Flight Time change.
The Airline (ORA) may notify the Seller of a Flight Time change.
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount/>
<Amount/>
<PaymentID>PAY001</PaymentID>
<PaymentID>PAY001</PaymentID>
<PaymentMethod>
<PaymentMethod>
<PaymentCard>
<PaymentCard>
<CardBrandCode>VI</CardBrandCode>
<CardBrandCode>VI</CardBrandCode>
</PaymentCard>
</PaymentCard>
</PaymentMethod>
</PaymentMethod>
<PaymentStatusCode>ACCEPTED</PaymentStatusCode>
<PaymentStatusCode>ACCEPTED</PaymentStatusCode>
<TypeCode>CC</TypeCode>
<TypeCode>CC</TypeCode>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
</Old>
</Old>
<ReasonCode>PAYSTATUSUPD</ReasonCode>
<ReasonCode>PAYSTATUSUPD</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>0</OrderVersion>
<OrderVersion>0</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
</Notification>
</Notification>
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>SEGTIMECHG</ChangeTypeCode>
<ChangeTypeCode>SEGTIMECHG</ChangeTypeCode>
<New>
<New>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>2019-09-
<AircraftScheduledDateTime>2019-09-
24T21:20</AircraftScheduledDateTime>
24T21:20</AircraftScheduledDateTime>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>2019-09-
<AircraftScheduledDateTime>2019-09-
24T20:00</AircraftScheduledDateTime>
24T20:00</AircraftScheduledDateTime>
</Dep>
</Dep>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</New>
</New>
<Old>
<Old>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
None Copy
Page: 59 of 377
06. Transmitting an OrderChangeNotif request with Flight Number change.06. Transmitting an OrderChangeNotif request with Flight Number change.
The Airline (ORA) may notify the Seller of a Flight Number change.
<Arrival>
<Arrival>
<AircraftScheduledDateTime>2019-09-
<AircraftScheduledDateTime>2019-09-
24T22:05</AircraftScheduledDateTime>
24T22:05</AircraftScheduledDateTime>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>2019-09-
<AircraftScheduledDateTime>2019-09-
24T20:45</AircraftScheduledDateTime>
24T20:45</AircraftScheduledDateTime>
</Dep>
</Dep>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</Old>
</Old>
<ReasonCode>SCHEDCHNG</ReasonCode>
<ReasonCode>SCHEDCHNG</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>0</OrderVersion>
<OrderVersion>0</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
</Notification>
</Notification>
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>FLTNUMCHG</ChangeTypeCode>
<ChangeTypeCode>FLTNUMCHG</ChangeTypeCode>
<New>
<New>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>
XB456
XB456
</MarketingCarrierFlightNumberText>
</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</New>
</New>
<Old>
<Old>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>
XB123
XB123
</MarketingCarrierFlightNumberText>
</MarketingCarrierFlightNumberText>
None Copy
Page: 60 of 377
07. Transmitting an OrderChangeNotif request with Flight change (segment change)07. Transmitting an OrderChangeNotif request with Flight change (segment change)
The Airline (ORA) may notify the Seller of a Flight change (segment change).
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</Old>
</Old>
<ReasonCode>FLNUMCHG</ReasonCode>
<ReasonCode>FLNUMCHG</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>0</OrderVersion>
<OrderVersion>0</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
</Notification>
</Notification>
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>SEGCHG</ChangeTypeCode>
<ChangeTypeCode>SEGCHG</ChangeTypeCode>
<Old>
<Old>
<Order>
<Order>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
</Order>
</Order>
</Old>
</Old>
<New>
<New>
<Order>
<Order>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>CANCELLED</StatusCode>
<StatusCode>CANCELLED</StatusCode>
</Service>
</Service>
<Service>
<Service>
<PaxRefID>PAX001</PaxRefID>
<PaxRefID>PAX001</PaxRefID>
<ServiceAssociations>
<ServiceAssociations>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
</ServiceAssociations>
</ServiceAssociations>
<ServiceID>SVC002</ServiceID>
<ServiceID>SVC002</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
</Order>
</Order>
None Copy
Page: 61 of 377
08. Transmitting an OrderChangeNotif request with Route change (Change in08. Transmitting an OrderChangeNotif request with Route change (Change in
Departure/Arrival Information)Departure/Arrival Information)
The Airline (ORA) may notify the Seller of a route change (Change in Departure/Arrival Information).
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-02-14T16:40:00
2019-02-14T16:40:00
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>LHR</IATA_LocationCode>
<IATA_LocationCode>LHR</IATA_LocationCode>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-02-14T14:25:00
2019-02-14T14:25:00
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>GVA</IATA_LocationCode>
<IATA_LocationCode>GVA</IATA_LocationCode>
</Dep>
</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>
222
222
</MarketingCarrierFlightNumberText>
</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</New>
</New>
<ReasonCode>SEGCHNG</ReasonCode>
<ReasonCode>SEGCHNG</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>0</OrderVersion>
<OrderVersion>0</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
</Notification>
</Notification>
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>ARRCHG</ChangeTypeCode>
<ChangeTypeCode>ARRCHG</ChangeTypeCode>
<Old>
<Old>
<Order>
<Order>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
None Copy
Page: 62 of 377
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
</Order>
</Order>
</Old>
</Old>
<New>
<New>
<Order>
<Order>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>CANCELLED</StatusCode>
<StatusCode>CANCELLED</StatusCode>
</Service>
</Service>
<Service>
<Service>
<PaxRefID>PAX001</PaxRefID>
<PaxRefID>PAX001</PaxRefID>
<ServiceAssociations>
<ServiceAssociations>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
</ServiceAssociations>
</ServiceAssociations>
<ServiceID>SVC002</ServiceID>
<ServiceID>SVC002</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
</Order>
</Order>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>2019-02-
<AircraftScheduledDateTime>2019-02-
14T16:40:00Z</AircraftScheduledDateTime>
14T16:40:00Z</AircraftScheduledDateTime>
<IATA_LocationCode>LGW</IATA_LocationCode>
<IATA_LocationCode>LGW</IATA_LocationCode>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>2019-02-
<AircraftScheduledDateTime>2019-02-
14T14:25:00Z</AircraftScheduledDateTime>
14T14:25:00Z</AircraftScheduledDateTime>
<IATA_LocationCode>GVA</IATA_LocationCode>
<IATA_LocationCode>GVA</IATA_LocationCode>
</Dep>
</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>222</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>222</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</New>
</New>
</ChangeOperation>
</ChangeOperation>
</ChangeOperationGroup>
</ChangeOperationGroup>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
</ChangeGroup>
</ChangeGroup>
<OrderBaseline>
<OrderBaseline>
<Order>
<Order>
Page: 63 of 377
09. Transmitting an OrderChangeNotif request with the Current Order09. Transmitting an OrderChangeNotif request with the Current Order
The Airline (ORA) may notify the Seller of changes to the Order, optionally transmitting the Current
Order.
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<PaxRefID>PAX001</PaxRefID>
<PaxRefID>PAX001</PaxRefID>
<ServiceAssociations>
<ServiceAssociations>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
</ServiceAssociations>
</ServiceAssociations>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
<OwnerCode>XB<OwnerCode>
<OwnerCode>XB<OwnerCode>
</Order>
</Order>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>2019-02-
<AircraftScheduledDateTime>2019-02-
14T16:40:00Z</AircraftScheduledDateTime>
14T16:40:00Z</AircraftScheduledDateTime>
<IATALocationCode>LHR</IATALocationCode>
<IATALocationCode>LHR</IATALocationCode>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>2019-02-
<AircraftScheduledDateTime>2019-02-
14T14:25:00Z</AircraftScheduledDateTime>
14T14:25:00Z</AircraftScheduledDateTime>
<IATALocationCode>GVA</IATALocationCode>
<IATALocationCode>GVA</IATALocationCode>
</Dep>
</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>222</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>222</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</OrderBaseline>
</OrderBaseline>
</Notification>
</Notification>
<CurrentOrder>
<CurrentOrder>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
None Copy
Page: 64 of 377
10. Transmitting an OrderChangeNotif request with the Baseline Order10. Transmitting an OrderChangeNotif request with the Baseline Order
The Airline (ORA) may notify the Seller of changes to the Order, optionally transmitting the Baseline
Order.
2019-09-25T11:35:00Z
2019-09-25T11:35:00Z
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>LGW</IATA_LocationCode>
<IATA_LocationCode>LGW</IATA_LocationCode>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-09-25T10:15:00Z
2019-09-25T10:15:00Z
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>GVA</IATA_LocationCode>
<IATA_LocationCode>GVA</IATA_LocationCode>
</Dep>
</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>
222
222
</MarketingCarrierFlightNumberText>
</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
<OperatingCarrierFlightNumberText>
<OperatingCarrierFlightNumberText>
111
111
</OperatingCarrierFlightNumberText>
</OperatingCarrierFlightNumberText>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<Order>
<Order>
<OrderID>ZZ000XXABC123</OrderID>
<OrderID>ZZ000XXABC123</OrderID>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<PaxRefID>PAX001</PaxRefID>
<PaxRefID>PAX001</PaxRefID>
<ServiceAssociations>
<ServiceAssociations>
<ServiceDefinitionRef>
<ServiceDefinitionRef>
<FlightAssociations>
<FlightAssociations>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
</FlightAssociations>
</FlightAssociations>
</ServiceDefinitionRef>
</ServiceDefinitionRef>
</ServiceAssociations>
</ServiceAssociations>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
<OwnerCode>XB</OwnerCode>
<OwnerCode>XB</OwnerCode>
</Order>
</Order>
</CurrentOrder>
</CurrentOrder>
<OrderBaseline>
<OrderBaseline>
None Copy
Page: 65 of 377
11. Transmitting an OrderChangeNotif request with Flight Cancellation information11. Transmitting an OrderChangeNotif request with Flight Cancellation information
The Airline (ORA) may notify the Seller of a Flight Cancellation.
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-09-25T11:45:00Z
2019-09-25T11:45:00Z
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>LHR</IATA_LocationCode>
<IATA_LocationCode>LHR</IATA_LocationCode>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-09-25T10:15:00Z
2019-09-25T10:15:00Z
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>GVA</IATA_LocationCode>
<IATA_LocationCode>GVA</IATA_LocationCode>
</Dep>
</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>
222
222
</MarketingCarrierFlightNumberText>
</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
<OperatingCarrierFlightNumberText>
<OperatingCarrierFlightNumberText>
111
111
</OperatingCarrierFlightNumberText>
</OperatingCarrierFlightNumberText>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<Order>
<Order>
<OrderID>ZZ000XXABC123</OrderID>
<OrderID>ZZ000XXABC123</OrderID>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<PaxRefID>PAX001</PaxRefID>
<PaxRefID>PAX001</PaxRefID>
<ServiceAssociations>
<ServiceAssociations>
<ServiceDefinitionRef>
<ServiceDefinitionRef>
<FlightAssociations>
<FlightAssociations>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
</FlightAssociations>
</FlightAssociations>
</ServiceDefinitionRef>
</ServiceDefinitionRef>
</ServiceAssociations>
</ServiceAssociations>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
<OwnerCode>XB</OwnerCode>
<OwnerCode>XB</OwnerCode>
</Order>
</Order>
</OrderBaseline>
</OrderBaseline>
Page: 66 of 377
12. Transmitting an OrderChangeNotif request with Aircraft Type and Operating12. Transmitting an OrderChangeNotif request with Aircraft Type and Operating
Carrier changesCarrier changes
The Airline (ORA) may notify the Seller of an Aircraft Type and Operating Carrier Change.
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>SEGCANCEL</ChangeTypeCode>
<ChangeTypeCode>SEGCANCEL</ChangeTypeCode>
<New>
<New>
<Order>
<Order>
<OrderID>OR001</OrderID>
<OrderID>OR001</OrderID>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<ServiceID>SVC002</ServiceID>
<ServiceID>SVC002</ServiceID>
<StatusCode>REMOVED</StatusCode>
<StatusCode>REMOVED</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
</Order>
</Order>
</New>
</New>
<Old>
<Old>
<Order>
<Order>
<OrderID>OR001</OrderID>
<OrderID>OR001</OrderID>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<ServiceID>SVC002</ServiceID>
<ServiceID>SVC002</ServiceID>
<StatusCode>HK</StatusCode>
<StatusCode>HK</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
</Order>
</Order>
</Old>
</Old>
<ReasonCode>SEGCANCEL</ReasonCode>
<ReasonCode>SEGCANCEL</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>0</OrderVersion>
<OrderVersion>0</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>token</OrderID>
<OrderID>token</OrderID>
</Notification>
</Notification>
None Copy
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeOperationGroup>
<ChangeOperationGroup>
<ChangeOperation>
<ChangeOperation>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeDateTime>2001-12-17T09:30:47Z</ChangeDateTime>
<ChangeTypeCode>AIRCRAFTCHG</ChangeTypeCode>
<ChangeTypeCode>AIRCRAFTCHG</ChangeTypeCode>
<New>
<New>
<DataLists>
<DataLists>
None Copy
Page: 67 of 377
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<DatedOperatingLeg>
<DatedOperatingLeg>
<CarrierAircraftType>787</CarrierAircraftType>
<CarrierAircraftType>787</CarrierAircraftType>
</DatedOperatingLeg>
</DatedOperatingLeg>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</New>
</New>
<Old>
<Old>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<DatedOperatingLeg>
<DatedOperatingLeg>
<CarrierAircraftType>777</CarrierAircraftType>
<CarrierAircraftType>777</CarrierAircraftType>
</DatedOperatingLeg>
</DatedOperatingLeg>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
</Old>
</Old>
<ReasonCode>EQCHNG</ReasonCode>
<ReasonCode>EQCHNG</ReasonCode>
</ChangeOperation>
</ChangeOperation>
<OrderVersion>4</OrderVersion>
<OrderVersion>4</OrderVersion>
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderBaseline>
<OrderBaseline>
<DataLists>
<DataLists>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>
<Arrival>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-09-25T08:50:00Z
2019-09-25T08:50:00Z
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>LHR</IATA_LocationCode>
<IATA_LocationCode>LHR</IATA_LocationCode>
</Arrival>
</Arrival>
<Dep>
<Dep>
<AircraftScheduledDateTime>
<AircraftScheduledDateTime>
2019-09-25T07:30:00Z
2019-09-25T07:30:00Z
</AircraftScheduledDateTime>
</AircraftScheduledDateTime>
<IATA_LocationCode>GVA</IATALocationCode>
<IATA_LocationCode>GVA</IATALocationCode>
</Dep>
</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>
222
222
</MarketingCarrierFlightNumberText>
</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<OperatingCarrierInfo>
<OperatingCarrierInfo>
Page: 68 of 377
13. Transmitting an OrderChangeNotif request with Net Clearance Amount13. Transmitting an OrderChangeNotif request with Net Clearance Amount
The Seller may send the OrderChangeNotif request informing the Airline (ORA) with Net Clearance
Amount
<CarrierDesigCode>XC</CarrierDesigCode>
<CarrierDesigCode>XC</CarrierDesigCode>
</OperatingCarrierInfo>
</OperatingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<Order>
<Order>
<OrderID>OR001</OrderID>
<OrderID>OR001</OrderID>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM001</OrderItemID>
<OrderItemID>ORITM001</OrderItemID>
<Service>
<Service>
<PaxRefID>PAX001</PaxRefID>
<PaxRefID>PAX001</PaxRefID>
<ServiceAssociations>
<ServiceAssociations>
<ServiceDefinitionRef>
<ServiceDefinitionRef>
<FlightAssociations>
<FlightAssociations>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
</FlightAssociations>
</FlightAssociations>
</ServiceDefinitionRef>
</ServiceDefinitionRef>
</ServiceAssociations>
</ServiceAssociations>
<ServiceID>SVC001</ServiceID>
<ServiceID>SVC001</ServiceID>
<StatusCode>OPEN</StatusCode>
<StatusCode>OPEN</StatusCode>
</Service>
</Service>
</OrderItem>
</OrderItem>
<OwnerCode>XB</OwnerCode>
<OwnerCode>XB</OwnerCode>
</Order>
</Order>
</OrderBaseline>
</OrderBaseline>
<OrderID>ORD001</OrderID>
<OrderID>ORD001</OrderID>
</Notification>
</Notification>
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 69 of 377
Structure of the Invol servicingStructure of the Invol servicing
This section documents the key elements for the OrderChangeNotif request and how to correctly use
these to achieve the required functionality.
01. Transmitting an OrderChangeNotif request with indication that Customer01. Transmitting an OrderChangeNotif request with indication that Customer
Acceptance is needed following a Planned Schedule ChangeAcceptance is needed following a Planned Schedule Change
The Airline (ORA) may send an OrderChangeNotif request to the Seller with the indication that
Customer Acceptance is needed following a Planned Schedule Change.
XPath:oIATA_OrderChangeNotifRQ/Notification/ChangeGroup/ChangeOperationGroup/ChangeOper
ation/New/Order/OrderItem/SellerFollowUpAction
02. Transmitting an OrderChangeNotif request for an Order that has undergone a02. Transmitting an OrderChangeNotif request for an Order that has undergone a
Schedule Change including Fare Waiver informationSchedule Change including Fare Waiver information
The Airline may send the an OrderChangeNotif request for an Order that has undergone a planned
Schedule change including Fare Waiver information
XPath:oIATA_OrderChangeNotifRQ/Notification/ChangeGroup/ChangeOperationGroup/ChangeOper
ation/New/Order/OrderItem/FareDetail/FareWaiver
Structure of the Invol servicingStructure of the Invol servicing
<SellerFollowUpAction>
<SellerFollowUpAction>
<ActionCode>Accept</ActionCode>
<ActionCode>Accept</ActionCode>
<ActionCode>Cancel</ActionCode>
<ActionCode>Cancel</ActionCode>
<ActionCode>Reshop</ActionCode>
<ActionCode>Reshop</ActionCode>
<ActionInd>true</ActionInd>
<ActionInd>true</ActionInd>
<ActionActionTimeLimitDateTime>2019-09-30T14:00:00Z</ActionActionTimeLimitDateTime>
<ActionActionTimeLimitDateTime>2019-09-30T14:00:00Z</ActionActionTimeLimitDateTime>
<AirlineContactURI>www.airlinecontactpage.com</AirlineContactURI>
<AirlineContactURI>www.airlinecontactpage.com</AirlineContactURI>
<ConsequenceOfInactionCode>AutoAcceptance</ConsequenceOfInactionCode>
<ConsequenceOfInactionCode>AutoAcceptance</ConsequenceOfInactionCode>
</SellerFollowUpAction>
</SellerFollowUpAction>
None Copy
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
Page: 70 of 377
01. Transmitting an OrderChangeNotif request with multiple change operation01. Transmitting an OrderChangeNotif request with multiple change operation
groupsgroups
The Airline (ORA) may include multiple sequences of order changes in one notification to the seller.
Message CapabilitiesMessage Capabilities
<Notification>
<Notification>
<ChangeGroup>
<ChangeGroup>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>1</ChangeGroupSequenceNumber>
<ChangeOperationGroup>
<ChangeOperationGroup>
…
…
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<ChangeGroup>
<ChangeGroup>
<ChangeGroupSequenceNumber>2</ChangeGroupSequenceNumber>
<ChangeGroupSequenceNumber>2</ChangeGroupSequenceNumber>
<ChangeOperationGroup>
<ChangeOperationGroup>
…
…
</ChangeOperationGroup>
</ChangeOperationGroup>
</ChangeGroup>
</ChangeGroup>
<OrderID>OR001</OrderID>
<OrderID>OR001</OrderID>
</Notification>
</Notification>
None Copy
Page: 71 of 377
The OrderCancel transaction set requests the cancellation of a specified Order and returns
confirmation of cancellation.
The Seller, if the Customer wishes to proceed, can then send an Order Cancellation request to the
Airline. The Airline will reply with a confirmation in an Order Cancellation response.
The OrderCancel message may be used at a point at which the customer knows the cancellation
charges (for example after an OrderReshop where the Customer understands the impact of the
Cancellation).
OrderCancel Request ElementsOrderCancel Request Elements
Identifying the Order to CancelIdentifying the Order to Cancel
01. Requesting Cancellation01. Requesting Cancellation
The Seller may request a simple cancellation by simply providing the Order ID to be cancelled.
<iata:Request>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
</iata:Request>
Validating the Cancellation AmountValidating the Cancellation Amount
Not to be confused with quoting for the cancellation amount which will use the OrderReshop RQ/RS.
These validations ensure that nothing has changed from a quotation to the actual execution of the
Cancellation.
02. Requesting Cancellation with Expected Refund Amount02. Requesting Cancellation with Expected Refund Amount
The Seller, while requesting the airline to cancel the Order may also advise the airline the expected
refund amount. If the expected refund amount does not match that of the expected amount, the airline
may return an error or warning instead of cancelling the Order.
<iata:Request>
<iata:ExpectedRefundAmount>
<iata:TotalAmount CurCode="CHF">1000.00</iata:TotalAmount>
</iata:ExpectedRefundAmount>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
Message CapabilitiesMessage Capabilities
Order IDOrder ID
Note if you have a PNR Record Locator, best practice is to use the Order ID and Owner Code field (not the
BookingRef structure). Note that the Order ID is determined by the Carrier and shall come from another Order ID
response (for example, OrderRetrieve, OrderList)
Page: 72 of 377
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
</iata:Request>
03. Requesting Cancellation with Expected Loyalty Refund03. Requesting Cancellation with Expected Loyalty Refund
The Seller, while requesting the airline to cancel the Order may also advise the airline the expected
loyalty refund. If the expected refund does not match that of the expected loyalty amount, the airline
may return an error or warning instead of cancelling the Order.
iata:Request
iata:ExpectedRefundAmount
iata:LoyaltyUnitAmount1000</iata:LoyaltyUnitAmount>
iata:LoyaltyUnitNameP</iata:LoyaltyUnitName>
</iata:ExpectedRefundAmount>
iata:Order
iata:OrderIDXBXXX1A2B3C4D</iata:OrderID>
iata:OwnerCodeXB</iata:OwnerCode>
</iata:Order>
</iata:Request>
@(Info)PADIS Codest 6411)(Note the Codeset to use for the Miles or Points Unit is PADIS Codeset
6411)
Specifying the type of Refund to ReceiveSpecifying the type of Refund to Receive
04. Requesting Cancellation with Refund to Original Form of Payment04. Requesting Cancellation with Refund to Original Form of Payment
The Seller may request that any refund amount available after the cancellation is refunded to the
original form of payment of the Order.
<iata:Request>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:OrderCancelProcessing>
<iata:RefundPaymentMethodPref>
<iata:OriginalPaymentMethodInd>true</iata:OriginalPaymentMethodInd>
</iata:RefundPaymentMethodPref>
</iata:OrderCancelProcessing>
</iata:Request>
05. Requesting Cancellation with Refund to a Specific Form of Payment05. Requesting Cancellation with Refund to a Specific Form of Payment
The Seller may request the airline to change the form of refund to a specific form, for example, a
Payment Card as opposed to the original form of payment (if known).
Additional Detai lAdditional Detai l
Note that the Seller can add additional detail of the Refund Amount to include the Base Amount and specific
taxes, fees, and charges.
Page: 73 of 377
<iata:Request>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:OrderCancelProcessing>
<iata:RefundPaymentMethodPref>
<iata:PaymentCard>
<iata:CardHolderName>Andrew Blake</iata:CardHolderName>
<iata:CardNumber>4111111111111111</iata:CardNumber>
<iata:CardProductTypeCode>VA</iata:CardProductTypeCode>
<iata:ExpirationDate>2018-11-05+01:00</iata:ExpirationDate>
</iata:PaymentCard>
</iata:RefundPaymentMethodPref>
</iata:OrderCancelProcessing>
</iata:Request>
06. Requesting Cancellation with Refund to a Specific Form of Payment Type06. Requesting Cancellation with Refund to a Specific Form of Payment Type
A Seller may specify the type of payment method to refund to without specifying the details of that
method (the Airline may have this information on file).
<iata:Request>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:OrderCancelProcessing>
<iata:RefundPaymentMethodPref>
<iata:PaymentCard/>
</iata:RefundPaymentMethodPref>
</iata:OrderCancelProcessing>
</iata:Request>
07. Requesting Cancellation with Refund to Voucher07. Requesting Cancellation with Refund to Voucher
A seller could request a refund to a voucher for later use by the customer.
<iata:Request>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:OrderCancelProcessing>
<iata:RefundPaymentMethodPref>
<iata:Voucher>
<iata:ExpirationDate>2019-12-12</iata:ExpirationDate>
<iata:VoucherID>12345678910</iata:VoucherID>
</iata:Voucher>
</iata:RefundPaymentMethodPref>
</iata:OrderCancelProcessing>
Page: 74 of 377
</iata:Request>
Detailing the Reason for CancellationDetailing the Reason for Cancellation
08. Requesting Cancellation with a Reason08. Requesting Cancellation with a Reason
A Seller may request the airline to Cancel the Order for any such reason, in this example the Seller
advises the airline that the Passenger must cancel due to bereavement purposes (PADIS Codeset
REA, value 6 meaning Bereavement).
<iata:Request>
<iata:Order>
<iata:OrderID>XB0001A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:OrderCancelProcessing>
<iata:ReasonCode>6</iata:ReasonCode>
</iata:OrderCancelProcessing>
</iata:Request>
09. Requesting Cancellation with a Grace Period09. Requesting Cancellation with a Grace Period
A Seller may send a cancellation request within a grace period (for example a cooling off period of 24
hours) where a full refund may be required due to government regulations. The request shall be the
same as the example Request to Cancel an Order. However, the Seller needs to identify where it’s
located (using the Party Information) allowing the Airline can assess the request appropriately.
OrderCancel Response ElementsOrderCancel Response Elements
01. Cancellation01. Cancellation
The response section of the message shall specify the response details to the OrderCancel Request.
If the cancellation request was successful, the Airline to respond with the Order ID reference. If no
errors and warnings are provided the Sender shall assume that the order was successfully cancelled.
<iata:Response>
<iata:OrderRefID>XBXXX1A2B3C4D</iata:OrderRefID>
</iata:Response>
02. Cancellation with Cancellation Fee02. Cancellation with Cancellation Fee
The Airline may return advise on the cancellation fees that were calculated during the Order
Cancellation.
<iata:Response>
<iata:ChangeFees>
Ai rline ResponseAi rline Response
Note the Airline may return with a Warning advising the Seller to have the Customer provide further information,
for example, a doctor’s certificate may be required if PADIS Codeset 7 was sent.
Page: 75 of 377
<iata:AppCode>PDE</iata:AppCode>
<iata:CancelFeeInd>true</iata:CancelFeeInd>
<iata:PenaltyAmount CurCode="EUR">100.00</iata:PenaltyAmount>
<iata:TypeCode>Cancel</iata:TypeCode>
</iata:ChangeFees>
<iata:OrderRefID>XBXXX1A2B3C4D</iata:OrderRefID>
</iata:Response>
03. Cancellation with Residual Ticket Information03. Cancellation with Residual Ticket Information
The Airline may also return tickets in the response which may still have residual value with a
successful cancellation while also advising the Cancellation fees.
<iata:Response>
<iata:ChangeFees>
<iata:AppCode>PDE</iata:AppCode>
<iata:CancelFeeInd>true</iata:CancelFeeInd>
<iata:PenaltyAmount CurCode="EUR">100.00</iata:PenaltyAmount>
<iata:TypeCode>Cancel</iata:TypeCode>
</iata:ChangeFees>
<iata:OrderRefID>XBXXX1A2B3C4D</iata:OrderRefID>
<iata:TicketDocInfo>
<iata:Ticket>
<iata:Coupon>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponSeqNumber>1</iata:CouponSeqNumber>
<iata:CouponStatusCode>E</iata:CouponStatusCode>
<!--Optional:-->
<iata:CouponValidityPeriod>
<iata:Duration>P1Y4M2DT22H5M29S</iata:Duration>
<iata:EffectiveDate>2005-10-07</iata:EffectiveDate>
<iata:ExpirationDate>2010-03-07+01:00</iata:ExpirationDate>
</iata:CouponValidityPeriod>
<iata:FareBasisCode>JFBC</iata:FareBasisCode>
<iata:NonRefundableInd>false</iata:NonRefundableInd>
<iata:ValueAmount CurCode="CHF">10.00</iata:ValueAmount>
</iata:Coupon>
<iata:ReportingTypeCode>ORA</iata:ReportingTypeCode>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<!--Ticket-->
<iata:TicketNumber>00022212345678</iata:TicketNumber>
</iata:Ticket>
</iata:TicketDocInfo>
</iata:Response>
Page: 76 of 377
The OrderRetrieve transaction retrieves a specified Order that matches the request identifier for the
Order.
Order Retrieve is used to return an Order using a distinct criterion (such as Order ID, Booking Reloc,
Document Number) and is not used to search for Orders. Other criteria within the request are used for
validation purposes.
Order Retrieve is the only message that supports the request for an Order using something other than
an Order ID, for example, a Booking Reloc or Document Number, from this point onwards. If PNR’s
(shaped as Orders) are used, the Airline shall return the Reloc within the Order ID field for Sellers.
OrderRetrieve Request ElementsOrderRetrieve Request Elements
This section documents the key elements for the OrderRetrieve request and how to correctly use
these to achieve the required functionality.
01. Retrieving an Order using an Order ID01. Retrieving an Order using an Order ID
A Seller may retrieve a full snapshot of an Order using the Order Retrieve message simply by
specifying the Order ID.
02. Retrieving an Order using a Record Locator02. Retrieving an Order using a Record Locator
An Airline may return an Order using an airline internal PNR Reloc as opposed to an Order ID.
<iata:OrderFilterCriteria>
<iata:BookingRefFilterCriteria>
<iata:BookingEntity>
<iata:Carrier>
<iata:AirlineDesigCode>XB</iata:AirlineDesigCode>
</iata:Carrier>
</iata:BookingEntity>
<iata:BookingID>ABCDEF</iata:BookingID>
</iata:BookingRefFilterCriteria>
</iata:OrderFilterCriteria>
Order Retrieve CapabilitiesOrder Retrieve Capabilities
<iata:OrderFilterCriteria>
<iata:OrderFilterCriteria>
<iata:Order>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
</iata:Order>
</iata:OrderFilterCriteria>
</iata:OrderFilterCriteria>
None Copy
Order ID FormatOrder ID Format
Note, regardless of Airline or OMS Fulfilment of that Order, the Order ID shall be as per Resolution 777.
Page: 77 of 377
03. Retrieving an Order using a Document Number03. Retrieving an Order using a Document Number
An Airline may allow the Seller to request an Order to which a document is associated to, for example,
by using a Ticket Number
<iata:OrderFilterCriteria>
<iata:TicketDocFilterCriteria>
<iata:TicketNumber>00011122222222</iata:TicketNumber>
</iata:TicketDocFilterCriteria>
</iata:OrderFilterCriteria>
04. Retrieving an Order with Name Validation04. Retrieving an Order with Name Validation
An Airline may wish to use the name of a Passenger within the Order to validate the request to retrieve
the Order.
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:Individual>
<iata:GivenName>Andrew</iata:GivenName>
<iata:MiddleName>Frederick</iata:MiddleName>
<iata:Surname>Blake</iata:Surname>
</iata:Individual>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
05. Retrieving an Order with Email Validation05. Retrieving an Order with Email Validation
An Airline may choose to validate the request by asking the Seller to provide an email within the Order.
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:ContactInfo>
<iata:EmailAddress> <iata:EmailAddressText>standards@iata.org</iata:EmailAddressText>
</iata:EmailAddress>
</iata:ContactInfo>
<iata:PaxID>PAX-01</iata:PaxID>
Order IDOrder ID
Note the Airline shall return the Order with an Order ID (which may be a reloc). From this point on the Seller shall
use the Order ID element within other messages to interact with an Order
Page: 78 of 377
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
06. Retrieving an Order with Social Media Handle Validation06. Retrieving an Order with Social Media Handle Validation
An Airline may choose to validate the request by asking for the social media handle of a person within
the Order.
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:ContactInfo>
<iata:OtherAddress>
<iata:LabelText>facebook</iata:LabelText>
<iata:OtherAddressText>afbman</iata:OtherAddressText>
</iata:OtherAddress>
</iata:ContactInfo>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
07. Retrieving an Order with Phone Number Validation07. Retrieving an Order with Phone Number Validation
An Airline may choose to validate the request by asking for a phone number within the Order.
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:ContactInfo>
<iata:Phone>
<iata:PhoneNumber>+411234567890</iata:PhoneNumber>
</iata:Phone>
</iata:ContactInfo>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
08. Retrieving an Order with Address Validation08. Retrieving an Order with Address Validation
An Airline may choose to validate the request by asking for a component of the address to be verified.
Social Media CodesetSocial Media Codeset
Note there is no codset or reference to identify the Social Media platform, best practice is to use the main
domain name within the label text. For example ‘facebook.com’ equates to ‘facebook’, or unknown.
Page: 79 of 377
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:ContactInfo>
<iata:PostalAddress>
<iata:PostalCode>1207</iata:PostalCode>
</iata:PostalAddress>
</iata:ContactInfo>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
09. Retrieving an Order with Frequent Flyer Validation09. Retrieving an Order with Frequent Flyer Validation
An Airline may request to validate the request for Order retrieval using a Frequent Flyer Account
Number.
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:LoyaltyProgramAccount>
<iata:AccountNumber>1234567890</iata:AccountNumber>
<iata:Carrier>
<iata:AirlineDesigCode>XB</iata:AirlineDesigCode>
</iata:Carrier>
</iata:LoyaltyProgramAccount>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
Alternatively, the Airline may use a Loyalty Program Sign ID (for example and email address or
username which may be used instead)
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:LoyaltyProgramAccount>
<iata:SignInID>iatastandards</iata:SignInID>
</iata:LoyaltyProgramAccount>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
Page: 80 of 377
10. Retrieving an Order with Payment Card Validation10. Retrieving an Order with Payment Card Validation
An Airline may validate the request by requesting information about the Payment Card that was used
to create this Order.
<XML Snippet using the Order ID and the Payment Card Masked Number Field will be added here>
11. Retrieving an Order with Passport Number Validation11. Retrieving an Order with Passport Number Validation
An Airline may wish to validate the request by asking for the Passport Number of a Passenger within
the Order
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:FOID>
<iata:FOID_ID>N12345678</iata:FOID_ID>
<iata:FOID_TypeText>PP</iata:FOID_TypeText>
</iata:FOID>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
</iata:OrderFilterCriteria>
12. Retrieving an Order with ID Card Validation12. Retrieving an Order with ID Card Validation
An Airline may wish to validate the request by requesting that the Seller sends in an ID Card Number
of one of the Passengers within the Order.
<iata:OrderFilterCriteria>
<iata:Order>
<iata:OrderID>XB000A1B2C3D4</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
<iata:PaxFilterCriteria>
<iata:FOID>
<iata:FOID_ID>1234567890</iata:FOID_ID>
<iata:FOID_TypeText>NI</iata:FOID_TypeText>
</iata:FOID>
<iata:PaxID>PAX-01</iata:PaxID>
</iata:PaxFilterCriteria>
CreditCardVendorCodeCreditCardVendorCode
Note the CreditCardVendorCode references Resolution 728, paragraph 7.2.1
FOIDSFOIDS
Note that the term FOIDS should not be confused with the AIRIMP FOIDS, while similar, this is simply a
mechanism to transmit the information to the Airline.
Page: 81 of 377
</iata:OrderFilterCriteria>
FOIDSFOIDS
Note that the term FOIDS should not be confused with the AIRIMP FOIDS, while similar, this is simply a
mechanism to transmit the information to the Airline.
Page: 82 of 377
PurposePurpose
The OrderHistory transaction set requests the transaction history and audit trail for a specified Order.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Request Order History ✔ -
Request using Remarks ✔ -
Response Return an Order Reference ✔ -
Returns a collection of Actions that have been
applied to the Order
✔ -
OverviewOverview
Page: 83 of 377
OrderHistory Response ElementsOrderHistory Response Elements
This section documents the key elements for the OrderHistory response and how to correctly use
these to achieve the required functionality.
01. Viewing an Order History with multiple addresses at destination01. Viewing an Order History with multiple addresses at destination
The Airline (ORA) may send an OrderHistory response to the Seller with multiple addresses at
destination.
Ability to Handle Multiple Types of ContactsAbility to Handle Multiple Types of Contacts
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044756496451</PhoneNumber>
<PhoneNumber>0044756496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>GB</CountryCode>
<CountryCode>GB</CountryCode>
<PostalCode>AA1 2BB</PostalCode>
<PostalCode>AA1 2BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>001156496451</PhoneNumber>
<PhoneNumber>001156496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>New York</CityName>
<CityName>New York</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>US</CountryCode>
<CountryCode>US</CountryCode>
<PostalCode>12345</PostalCode>
<PostalCode>12345</PostalCode>
<StreetText>2 Broad Street</StreetText>
<StreetText>2 Broad Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
None Copy
Page: 84 of 377
02. Viewing an Order History with emergency contact details02. Viewing an Order History with emergency contact details
The Airline (ORA) may send an OrderHistory response to the Seller with emergency contact details.
<Pax>
<Pax>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<PaxID>PAX01</PaxID>
<PaxID>PAX01</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT001</ContactInfoID>
<ContactInfoID>CT001</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PRO</ContactTypeText>
<ContactTypeText>PRO</ContactTypeText>
<PostalCode>AA12BB</PostalCode>
<PostalCode>AA12BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT002</ContactInfoID>
<ContactInfoID>CT002</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044123497854</PhoneNumber>
<PhoneNumber>0044123497854</PhoneNumber>
</Phone>
</Phone>
None Copy
Page: 85 of 377
03. Viewing an Order History with contact details for an unaccompanied minor03. Viewing an Order History with contact details for an unaccompanied minor
The Airline (ORA) may send an OrderHistory response to the Seller with contact details for an
unaccompanied minor.
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Mother</GivenName>
<GivenName>Mother</GivenName>
<IndividualID>IND01</IndividualID>
<IndividualID>IND01</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>006111111</PhoneNumber>
<PhoneNumber>006111111</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
None Copy
Page: 86 of 377
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Father</GivenName>
<GivenName>Father</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044222222</PhoneNumber>
<PhoneNumber>0044222222</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT03</ContactInfoID>
<ContactInfoID>CT03</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>GrandFather</GivenName>
<GivenName>GrandFather</GivenName>
<IndividualID>IND03</IndividualID>
<IndividualID>IND03</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00443333333</PhoneNumber>
<PhoneNumber>00443333333</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT04</ContactInfoID>
<ContactInfoID>CT04</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Aunt</GivenName>
<GivenName>Aunt</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00144444444</PhoneNumber>
<PhoneNumber>00144444444</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
Page: 87 of 377
OrderHistory Response ElementsOrderHistory Response Elements
This section documents the key elements for the OrderHistory response and how to correctly use
these to achieve the required functionality.
01. Viewing an Order History with indication that Customer Acceptance is needed01. Viewing an Order History with indication that Customer Acceptance is needed
following a Planned Schedule Changefollowing a Planned Schedule Change
The Airline (ORA) may send an OrderHistory response to the Seller with the indication that Customer
Acceptance is needed following a Planned Schedule Change.
XPath:oIATA_OrderHistoryRS/Response/ChangeGroup/ChangeOperationGroup/ChangeOperation/N
ew/Order/OrderItem/SellerFollowUpAction
02. Viewing an Order History with Fare Waiver information02. Viewing an Order History with Fare Waiver information
The Seller may view an Order History with Fare Waiver information.
XPath:oIATA_OrderHistoryRS/Response/ChangeGroup/ChangeOperationGroup/ChangeOperation/N
ew/Order/OrderItem/FareDetail/FareWaiver
Structure of the Invol ServicingStructure of the Invol Servicing
<SellerFollowUpAction>
<SellerFollowUpAction>
<ActionCode>Accept</ActionCode>
<ActionCode>Accept</ActionCode>
<ActionCode>Cancel</ActionCode>
<ActionCode>Cancel</ActionCode>
<ActionCode>Reshop</ActionCode>
<ActionCode>Reshop</ActionCode>
<ActionInd>true</ActionInd>
<ActionInd>true</ActionInd>
<ActionActionTimeLimitDateTime>2019-09-30T14:00:00Z</ActionActionTimeLimitDateTime>
<ActionActionTimeLimitDateTime>2019-09-30T14:00:00Z</ActionActionTimeLimitDateTime>
<AirlineContactURI>www.airlinecontactpage.com</AirlineContactURI>
<AirlineContactURI>www.airlinecontactpage.com</AirlineContactURI>
<ConsequenceOfInactionCode>AutoAcceptance</ConsequenceOfInactionCode>
<ConsequenceOfInactionCode>AutoAcceptance</ConsequenceOfInactionCode>
</SellerFollowUpAction>
</SellerFollowUpAction>
None Copy
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
Page: 88 of 377
PurposePurpose
The OrderList transaction set retrieves a list of Orders that match one or more search criteria.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core Request for matching Orders ✔ -
OrderListParameters ✔ -
Filtering By Booking Reference ✔ -
By Carrier ✔ -
By Flight ✔ -
By Cancellation Date ✔ -
By Creation Date ✔ -
By Passengers ✔ -
By Passenger Groups ✔ -
By Payments ✔ -
By Services ✔ -
By Tickets ✔ -
By travel Date ✔ -
Response Return matched Orders ✔ -
OverviewOverview
Page: 89 of 377
PurposePurpose
OrderView returns up to date content of an Order such as pricing information, conditions, time limits,
Order status and passenger information.
When payment has been processed at the time of Order creation it also includes the status of this
and, where they have already been issued, at least accountable document references (and further
accountable document data if required).
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request
See various messages such as
OrderRetrieve, OrderCreate,
Order Change
Response Returns one to many Orders ✔ -
Returns the changes and
actions applied to the Order
previously
✔ -
Returns Marketing Text ✔ -
Returns Ticket Information ✔ -
✔ -
✔ -
Message General Inventory Guarantee ✔ -
Rich Content ✔ -
Multi language ✔ -
Groups ✔ -
Multi-Currency ✔ -
OverviewOverview
Page: 90 of 377
OrderView Response ElementsOrderView Response Elements
This section documents the key elements for the OrderView response and how to correctly use these
to achieve the required functionality.
01. Viewing an Order with multiple addresses at destination01. Viewing an Order with multiple addresses at destination
The Airline (ORA) may send an OrderView response to the Seller with multiple addresses at
destination.
Ability to Handle Multiple Types of ContactsAbility to Handle Multiple Types of Contacts
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044756496451</PhoneNumber>
<PhoneNumber>0044756496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>GB</CountryCode>
<CountryCode>GB</CountryCode>
<PostalCode>AA1 2BB</PostalCode>
<PostalCode>AA1 2BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>DES</ContactPurposeText>
<ContactPurposeText>DES</ContactPurposeText>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>001156496451</PhoneNumber>
<PhoneNumber>001156496451</PhoneNumber>
</Phone>
</Phone>
<PostalAddress>
<PostalAddress>
<CityName>New York</CityName>
<CityName>New York</CityName>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<CountryCode>US</CountryCode>
<CountryCode>US</CountryCode>
<PostalCode>12345</PostalCode>
<PostalCode>12345</PostalCode>
<StreetText>2 Broad Street</StreetText>
<StreetText>2 Broad Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
None Copy
Page: 91 of 377
02. Viewing an Order with emergency contact details02. Viewing an Order with emergency contact details
The Airline (ORA) may send an OrderView response to the Seller with emergency contact details.
<Pax>
<Pax>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT01</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<ContactInfoRefID>CT02</ContactInfoRefID>
<PaxID>PAX01</PaxID>
<PaxID>PAX01</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT001</ContactInfoID>
<ContactInfoID>CT001</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PostalAddress>
<PostalAddress>
<CityName>London</CityName>
<CityName>London</CityName>
<ContactTypeText>PRO</ContactTypeText>
<ContactTypeText>PRO</ContactTypeText>
<PostalCode>AA12BB</PostalCode>
<PostalCode>AA12BB</PostalCode>
<StreetText>1 Main Street</StreetText>
<StreetText>1 Main Street</StreetText>
</PostalAddress>
</PostalAddress>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT002</ContactInfoID>
<ContactInfoID>CT002</ContactInfoID>
<ContactPurposeText>EMG</ContactPurposeText>
<ContactPurposeText>EMG</ContactPurposeText>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044123497854</PhoneNumber>
<PhoneNumber>0044123497854</PhoneNumber>
</Phone>
</Phone>
None Copy
Page: 92 of 377
03. Viewing an Order with contact details for an unaccompanied minor03. Viewing an Order with contact details for an unaccompanied minor
The Airline (ORA) may send an OrderView response to the Seller with contact details for an
unaccompanied minor.
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
<PaxSegmentList>
<PaxSegmentList>
<PaxSegment>
<PaxSegment>
<Arrival>LHR</Arrival>
<Arrival>LHR</Arrival>
<Dep>GVA</Dep>
<Dep>GVA</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>123</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG001</PaxSegmentID>
<PaxSegmentID>SEG001</PaxSegmentID>
</PaxSegment>
</PaxSegment>
<PaxSegment>
<PaxSegment>
<Arrival>JFK</Arrival>
<Arrival>JFK</Arrival>
<Dep>LHR</Dep>
<Dep>LHR</Dep>
<MarketingCarrierInfo>
<MarketingCarrierInfo>
<CarrierDesigCode>XB</CarrierDesigCode>
<CarrierDesigCode>XB</CarrierDesigCode>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
<MarketingCarrierFlightNumberText>456</MarketingCarrierFlightNumberText>
</MarketingCarrierInfo>
</MarketingCarrierInfo>
<PaxSegmentID>SEG002</PaxSegmentID>
<PaxSegmentID>SEG002</PaxSegmentID>
</PaxSegment>
</PaxSegment>
</PaxSegmentList>
</PaxSegmentList>
</DataLists>
</DataLists>
<DataLists>
<DataLists>
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT01</ContactInfoID>
<ContactInfoID>CT01</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Mother</GivenName>
<GivenName>Mother</GivenName>
<IndividualID>IND01</IndividualID>
<IndividualID>IND01</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>006111111</PhoneNumber>
<PhoneNumber>006111111</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
None Copy
Page: 93 of 377
<ContactInfoID>CT02</ContactInfoID>
<ContactInfoID>CT02</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Father</GivenName>
<GivenName>Father</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<PaxSegmentRefID>SEG001</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>0044222222</PhoneNumber>
<PhoneNumber>0044222222</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT03</ContactInfoID>
<ContactInfoID>CT03</ContactInfoID>
<ContactPurposeText>EDP</ContactPurposeText>
<ContactPurposeText>EDP</ContactPurposeText>
<Individual>
<Individual>
<GivenName>GrandFather</GivenName>
<GivenName>GrandFather</GivenName>
<IndividualID>IND03</IndividualID>
<IndividualID>IND03</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00443333333</PhoneNumber>
<PhoneNumber>00443333333</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CT04</ContactInfoID>
<ContactInfoID>CT04</ContactInfoID>
<ContactPurposeText>EAR</ContactPurposeText>
<ContactPurposeText>EAR</ContactPurposeText>
<Individual>
<Individual>
<GivenName>Aunt</GivenName>
<GivenName>Aunt</GivenName>
<IndividualID>IND02</IndividualID>
<IndividualID>IND02</IndividualID>
<Surname>NAMEONE</Surname>
<Surname>NAMEONE</Surname>
</Individual>
</Individual>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<PaxSegmentRefID>SEG002</PaxSegmentRefID>
<Phone>
<Phone>
<ContactTypeText>PER</ContactTypeText>
<ContactTypeText>PER</ContactTypeText>
<PhoneNumber>00144444444</PhoneNumber>
<PhoneNumber>00144444444</PhoneNumber>
</Phone>
</Phone>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
<PaxList>
<PaxList>
<Pax>
<Pax>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT001</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT002</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT003</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<ContactInfoRefID>CT004</ContactInfoRefID>
<PaxID>PAX001</PaxID>
<PaxID>PAX001</PaxID>
</Pax>
</Pax>
</PaxList>
</PaxList>
</DataLists>
</DataLists>
Page: 94 of 377
OrderView Response ElementsOrderView Response Elements
This section documents the key elements for the OrderView response and how to correctly use these
to achieve the required functionality.
01. Transmitting an OrderView response with Net Clearance Amount01. Transmitting an OrderView response with Net Clearance Amount
The Seller may send the OrderView response informing the Seller with Net Clearance Amount
Net Clearance AmountNet Clearance Amount
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 95 of 377
OrderView Response ElementsOrderView Response Elements
This section documents the key elements for the OrderView response and how to correctly use these
to achieve the required functionality.
1. Viewing the Order with the Grand Total Amount, Netted Penalty and Price1. Viewing the Order with the Grand Total Amount, Netted Penalty and Price
DifferentialDifferential
An Airline may return the OrderView response with the Grand Total Amount, Netted Penalty and Price
Differential.
Xpath: IATA_OrderViewRS/Response/DataLists
XPath: IATA_OrderViewRS/Response/Order/OrderItem
OrderView Response ElementsOrderView Response Elements
<DataLists>
<DataLists>
<PenaltyList>
<PenaltyList>
<Penalty>
<Penalty>
<NetInd>true</NetInd>
<NetInd>true</NetInd>
<PenaltyID>PEN001</PenaltyID>
<PenaltyID>PEN001</PenaltyID>
<Price>
<Price>
<BaseAmount>15.00</BaseAmount>
<BaseAmount>15.00</BaseAmount>
<Totalmount>15.00</Totalmount>
<Totalmount>15.00</Totalmount>
</Price>
</Price>
</Penalty>
</Penalty>
</PenaltyList>
</PenaltyList>
</DataLists>
</DataLists>
None Copy
<OrderItem>
<OrderItem>
<DiffPrice>
<DiffPrice>
<Price>
<Price>
<BaseAmount>-40.00</BaseAmount>
<BaseAmount>-40.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>-20.00</Amount>
<Amount>-20.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>-45.00</TotalAmount>
<TotalAmount>-45.00</TotalAmount>
</Price>
</Price>
</DiffPrice>
</DiffPrice>
<GrandTotalAmount>-55.0</GrandTotalAmount>
<GrandTotalAmount>-55.0</GrandTotalAmount>
<OrderItemID>ORDITM001</OrderItemID>
<OrderItemID>ORDITM001</OrderItemID>
<PenaltyRefID>PEN001</PenaltyRefID>
<PenaltyRefID>PEN001</PenaltyRefID>
<Price>
<Price>
<BaseAmount>-25.00</BaseAmount>
<BaseAmount>-25.00</BaseAmount>
<TaxSummary>
<TaxSummary>
None Copy
Page: 96 of 377
02. Viewing the Order with the re-usable indicator02. Viewing the Order with the re-usable indicator
An Airline may return the OrderView response with the re-usable indicator.
Xpath: IATA_OrderViewRS/Response/Order/OrderItem
<Tax>
<Tax>
<Amount>-15.00</Amount>
<Amount>-15.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>-40.00</TotalAmount>
<TotalAmount>-40.00</TotalAmount>
</Price>
</Price>
</OrderItem>
</OrderItem>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM01</OrderItemID>
<OrderItemID>ORITM01</OrderItemID>
<Price>
<Price>
<BaseAmount>100.00</BaseAmount>
<BaseAmount>100.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>20.00</Amount>
<Amount>20.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>120.00</TotalAmount>
<TotalAmount>120.00</TotalAmount>
</Price>
</Price>
<ReusableInd>true</ReusableInd>
<ReusableInd>true</ReusableInd>
...
...
</OrderItem>
</OrderItem>
None Copy
Page: 97 of 377
OrderView Response ElementsOrderView Response Elements
This section documents the key elements for the OrderView response and how to correctly use these
to achieve the required functionality.
01. Viewing an Order with indication that Customer Acceptance is needed following01. Viewing an Order with indication that Customer Acceptance is needed following
a Planned Schedule Changea Planned Schedule Change
The Airline (ORA) may send an OrderView response to the Seller with the indication that Customer
Acceptance is needed following a Planned Schedule Change.
XPath: IATA_OrderViewRS/Response/Order/OrderItem/SellerFollowUpAction
02. Viewing an Order with Fare Waiver information02. Viewing an Order with Fare Waiver information
The Seller may view an Order with Fare Waiver information.
Xpath: IATA_OrderViewRS/Response/Order/OrderItem/FareDetail/FareWaiver
Structure of the Invol servicingStructure of the Invol servicing
<SellerFollowUpAction>
<SellerFollowUpAction>
<ActionCode>Accept</ActionCode>
<ActionCode>Accept</ActionCode>
<ActionCode>Cancel</ActionCode>
<ActionCode>Cancel</ActionCode>
<ActionCode>Reshop</ActionCode>
<ActionCode>Reshop</ActionCode>
<ActionInd>true</ActionInd>
<ActionInd>true</ActionInd>
<ActionActionTimeLimitDateTime>2019-09-30T14:00:00Z</ActionActionTimeLimitDateTime>
<ActionActionTimeLimitDateTime>2019-09-30T14:00:00Z</ActionActionTimeLimitDateTime>
<AirlineContactURI>www.airlinecontactpage.com</AirlineContactURI>
<AirlineContactURI>www.airlinecontactpage.com</AirlineContactURI>
<ConsequenceOfInactionCode>AutoAcceptance</ConsequenceOfInactionCode>
<ConsequenceOfInactionCode>AutoAcceptance</ConsequenceOfInactionCode>
</SellerFollowUpAction>
</SellerFollowUpAction>
None Copy
<FareWaiver>
<FareWaiver>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareRuleWaiverCode>CODE</FareRuleWaiverCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
<FareWaiverTypeCode>TYPE</FareWaiverTypeCode>
</FareWaiver>
</FareWaiver>
None Copy
Page: 98 of 377
OrderView Response ElementsOrderView Response Elements
This section documents the key elements for the OrderView response and how to correctly use these
to achieve the required functionality.
01. Viewing the Order with the Grand Total Amount, Netted Penalty and Price01. Viewing the Order with the Grand Total Amount, Netted Penalty and Price
DifferentialDifferential
An Airline may return the OrderView response with the Grand Total Amount, Netted Penalty and Price
Differential.
Xpath: IATA_OrderViewRS/Response/DataLists
XPath: IATA_OrderViewRS/Response/Order/OrderItem
Voluntary Servicing for full, partial cancellation and orderVoluntary Servicing for full, partial cancellation and order
modificationmodification
<DataLists>
<DataLists>
<PenaltyList>
<PenaltyList>
<Penalty>
<Penalty>
<NetInd>true</NetInd>
<NetInd>true</NetInd>
<PenaltyID>PEN001</PenaltyID>
<PenaltyID>PEN001</PenaltyID>
<Price>
<Price>
<BaseAmount>15.00</BaseAmount>
<BaseAmount>15.00</BaseAmount>
<Totalmount>15.00</Totalmount>
<Totalmount>15.00</Totalmount>
</Price>
</Price>
</Penalty>
</Penalty>
</PenaltyList>
</PenaltyList>
</DataLists>
</DataLists>
None Copy
<OrderItem>
<OrderItem>
<DiffPrice>
<DiffPrice>
<Price>
<Price>
<BaseAmount>-40.00</BaseAmount>
<BaseAmount>-40.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>-20.00</Amount>
<Amount>-20.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>-45.00</TotalAmount>
<TotalAmount>-45.00</TotalAmount>
</Price>
</Price>
</DiffPrice>
</DiffPrice>
<GrandTotalAmount>-55.0</GrandTotalAmount>
<GrandTotalAmount>-55.0</GrandTotalAmount>
<OrderItemID>ORDITM001</OrderItemID>
<OrderItemID>ORDITM001</OrderItemID>
<PenaltyRefID>PEN001</PenaltyRefID>
<PenaltyRefID>PEN001</PenaltyRefID>
<Price>
<Price>
<BaseAmount>-25.00</BaseAmount>
<BaseAmount>-25.00</BaseAmount>
None Copy
Page: 99 of 377
02. Viewing the Order with the re-usable indicator02. Viewing the Order with the re-usable indicator
An Airline may return the OrderView response with the re-usable indicator.
Xpath: IATA_OrderViewRS/Response/Order/OrderItem
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>-15.00</Amount>
<Amount>-15.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>-40.00</TotalAmount>
<TotalAmount>-40.00</TotalAmount>
</Price>
</Price>
</OrderItem>
</OrderItem>
<OrderItem>
<OrderItem>
<OrderItemID>ORITM01</OrderItemID>
<OrderItemID>ORITM01</OrderItemID>
<Price>
<Price>
<BaseAmount>100.00</BaseAmount>
<BaseAmount>100.00</BaseAmount>
<TaxSummary>
<TaxSummary>
<Tax>
<Tax>
<Amount>20.00</Amount>
<Amount>20.00</Amount>
</Tax>
</Tax>
</TaxSummary>
</TaxSummary>
<TotalAmount>120.00</TotalAmount>
<TotalAmount>120.00</TotalAmount>
</Price>
</Price>
<ReusableInd>true</ReusableInd>
<ReusableInd>true</ReusableInd>
…
…
</OrderItem>
</OrderItem>
None Copy
Page: 100 of 377
OrderSalesInformationNotif Request ElementsOrderSalesInformationNotif Request Elements
This section documents the key elements for the OrderSalesInformationNotif request and how to
correctly use these to achieve the required functionality.
01. Transmitting an OrderSalesInformationNotif request with Net Clearance Amount01. Transmitting an OrderSalesInformationNotif request with Net Clearance Amount
The Seller may send the OrderSalesInformationNotif request informing the Airline (ORA) with Net
Clearance Amount
Net Clearance AmountNet Clearance Amount
<PaymentFunctions>
<PaymentFunctions>
<PaymentProcessingSummary>
<PaymentProcessingSummary>
<Amount>100.00</Amount>
<Amount>100.00</Amount>
<PaymentID>A12F3465</PaymentID>
<PaymentID>A12F3465</PaymentID>
<PaymentMethod>
<PaymentMethod>
<Cash>
<Cash>
<SettlementData>
<SettlementData>
<NetClearanceAmount>90.00</NetClearanceAmount>
<NetClearanceAmount>90.00</NetClearanceAmount>
<RemittanceDate>2019-09-30</RemittanceDate>
<RemittanceDate>2019-09-30</RemittanceDate>
</SettlementData>
</SettlementData>
</Cash>
</Cash>
</PaymentMethod>
</PaymentMethod>
<TypeCode/>
<TypeCode/>
</PaymentProcessingSummary>
</PaymentProcessingSummary>
</PaymentFunctions>
</PaymentFunctions>
None Copy
Page: 101 of 377
OverviewOverview
This message is reserved for interline communication from the ORA to a POA. It serves to
communicate accountable document numbers (e.g. ET, EMDA, EMD-S) to the POA(s) identified in the
documents. It is an unsolicited message from ORA to POA, sending details of any new or changed
documents in the context of an existing Order.
The response is an acknowledgement that the notification has been received. The POA will then store
these numbers in its Order Management System alongside the corresponding Order and Service
details.
AirDocNotif AirDocNotif Request ElementsRequest Elements
01. ORA Advising POA that Documents have been issued01. ORA Advising POA that Documents have been issued
An ORA may send a message to the POA advising that documents have been issued in relation to an
Order Item or Service.
References PADIS Codeset 4405
Air Doc Notif CapabilitiesAir Doc Notif Capabilities
<iata:DocNotification>
<iata:DocNotification>
<iata:Coupon>
<iata:Coupon>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:OrderItem>
<iata:OrderItem>
<iata:OrderItemID>bb560735-9745-4793-a5d6-5b14fb02d09c</iata:OrderItemID>
<iata:OrderItemID>bb560735-9745-4793-a5d6-5b14fb02d09c</iata:OrderItemID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:Service>
<iata:Service>
<iata:PaxRefID>PAX-01</iata:PaxRefID>
<iata:PaxRefID>PAX-01</iata:PaxRefID>
<iata:ServiceID>bbe554f6-1ca3-42ab-91f7-6421c6679290</iata:ServiceID>
<iata:ServiceID>bbe554f6-1ca3-42ab-91f7-6421c6679290</iata:ServiceID>
</iata:Service>
</iata:Service>
</iata:OrderItem>
</iata:OrderItem>
</iata:Coupon>
</iata:Coupon>
<iata:Coupon>
<iata:Coupon>
<iata:CouponNumber>2</iata:CouponNumber>
<iata:CouponNumber>2</iata:CouponNumber>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:OrderItem>
<iata:OrderItem>
<iata:OrderItemID>aa560735-9745-4793-a5d6-5b14fb02d09c</iata:OrderItemID>
<iata:OrderItemID>aa560735-9745-4793-a5d6-5b14fb02d09c</iata:OrderItemID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:Service>
<iata:Service>
<iata:PaxRefID>PAX-01</iata:PaxRefID>
<iata:PaxRefID>PAX-01</iata:PaxRefID>
<iata:ServiceID>aae554f6-1ca3-42ab-91f7-6421c6679290</iata:ServiceID>
<iata:ServiceID>aae554f6-1ca3-42ab-91f7-6421c6679290</iata:ServiceID>
</iata:Service>
</iata:Service>
</iata:OrderItem>
</iata:OrderItem>
</iata:Coupon>
</iata:Coupon>
<iata:IssueDate>2008-07-09</iata:IssueDate>
<iata:IssueDate>2008-07-09</iata:IssueDate>
<iata:Order>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
None Copy
Page: 102 of 377
02. ORA Advising the POA of Changed Document Status02. ORA Advising the POA of Changed Document Status
An ORA may send a message to the POA to advise that the status of a document has changed. Note
the POA may already have the association of the coupon to the OrderItem and therefore does not
need this information again (as it’s a notif, and only changes are sent).
03. ORA Advising the POA of Cancelled Document03. ORA Advising the POA of Cancelled Document
An ORA may send a message to the POA to advise that a document has been cancelled. Note the
only difference from the previous scenario is the change of Coupon Status Code.
</iata:Order>
</iata:Order>
<iata:Pax>
<iata:Pax>
<iata:PaxID>PAX-01</iata:PaxID>
<iata:PaxID>PAX-01</iata:PaxID>
<iata:PTC>ADT</iata:PTC>
<iata:PTC>ADT</iata:PTC>
</iata:Pax>
</iata:Pax>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<iata:TicketNumber>00001112345678</iata:TicketNumber>
<iata:TicketNumber>00001112345678</iata:TicketNumber>
</iata:DocNotification>
</iata:DocNotification>
<iata:DocNotification>
<iata:DocNotification>
<iata:Coupon>
<iata:Coupon>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
</iata:Coupon>
</iata:Coupon>
<iata:Coupon>
<iata:Coupon>
<iata:CouponNumber>2</iata:CouponNumber>
<iata:CouponNumber>2</iata:CouponNumber>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
</iata:Coupon>
</iata:Coupon>
<iata:IssueDate>2008-07-09</iata:IssueDate>
<iata:IssueDate>2008-07-09</iata:IssueDate>
<iata:Order>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
</iata:Order>
<iata:Pax>
<iata:Pax>
<iata:PaxID>PAX-01</iata:PaxID>
<iata:PaxID>PAX-01</iata:PaxID>
<iata:PTC>ADT</iata:PTC>
<iata:PTC>ADT</iata:PTC>
</iata:Pax>
</iata:Pax>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<iata:TicketNumber>00001112345678</iata:TicketNumber>
<iata:TicketNumber>00001112345678</iata:TicketNumber>
</iata:DocNotification>
</iata:DocNotification>
None Copy
<iata:DocNotification>
<iata:DocNotification>
<iata:Coupon>
<iata:Coupon>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponNumber>1</iata:CouponNumber>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
</iata:Coupon>
</iata:Coupon>
<iata:Coupon>
<iata:Coupon>
<iata:CouponNumber>2</iata:CouponNumber>
<iata:CouponNumber>2</iata:CouponNumber>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
<iata:CouponStatusCode>O</iata:CouponStatusCode>
None Copy
Page: 103 of 377
</iata:Coupon>
</iata:Coupon>
<iata:IssueDate>2008-07-09</iata:IssueDate>
<iata:IssueDate>2008-07-09</iata:IssueDate>
<iata:Order>
<iata:Order>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OrderID>XBXXX1A2B3C4D</iata:OrderID>
<iata:OwnerCode>XB</iata:OwnerCode>
<iata:OwnerCode>XB</iata:OwnerCode>
</iata:Order>
</iata:Order>
<iata:Pax>
<iata:Pax>
<iata:PaxID>PAX-01</iata:PaxID>
<iata:PaxID>PAX-01</iata:PaxID>
<iata:PTC>ADT</iata:PTC>
<iata:PTC>ADT</iata:PTC>
</iata:Pax>
</iata:Pax>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<iata:TicketDocTypeCode>T</iata:TicketDocTypeCode>
<iata:TicketNumber>00001112345678</iata:TicketNumber>
<iata:TicketNumber>00001112345678</iata:TicketNumber>
</iata:DocNotification>
</iata:DocNotification>
Page: 104 of 377
This message response is reserved to reply to an unsolicited Notif to advise the sender that the
message was delivered.
Acknowledge Response ElementsAcknowledge Response Elements
01. A Successful Acknowledgement01. A Successful Acknowledgement
An Airline may return a successful acknowledgement of the message that was sent to it. A successful
response will include the status code of “OK”.
<iata:IATA_Acknowledgement>
<iata:Notification>
<iata:StatusCode>OK</iata:StatusCode>
</iata:Notification>
</iata:IATA_Acknowledgement>
02. An unsuccessful Acknowledgement02. An unsuccessful Acknowledgement
The airline will acknowledge receipt of the message and therefore if no message is received, there is
the error. Either the Seller gets an ‘OK’ response or no response at all.
Acknowledgement CapabilitiesAcknowledgement Capabilities
Page: 105 of 377
If Service delivery is not possible for any reason, this needs to be communicated to the OMS with the
corresponding status, and the Service in the Order is then updated with the new status. Any
subsequent process to rebook, refund or otherwise change a Service are to be handled as updates to
Order items in the OMS, which would then in turn trigger updates to the Accounting System.
Note that there are many scenarios that may cause Service delivery to be interrupted, and the flow
depicted here is one example.
Service Delivery Interruption:Service Delivery Interruption:
Service Delivery DeviationService Delivery Deviation
Page: 106 of 377
Any relevant changes made during the lifecycle of the Order must also be communicated to the
Accounting System.
OSIN triggered by Order modification:OSIN triggered by Order modification:
In the case of updates to the Accounting System using the OSIN, the message needs to contain two
versions of the Order: the old Order, and the new Order. The Accounting System can then use these
two images of the Order to identify the relevant changes.
Note that only changes to status “Delivered” must be notified to the Airline Accounting System. All
other status changes are not relevant.
Order ModificationOrder Modification
Page: 107 of 377
The ONE Order standard defines the necessary delivery processes and interactions to enable
purchased products and Services within Orders to be delivered and their delivery status tracked.
These Services may be flights or ancillary products, and can be delivered by the Airline itself or a
partner Airline, or by a contracted third-party Delivery Provider (e.g. ground handler, caterer, lounge
provider, etc.). The processes also support scenarios including Services not being delivered or
consumed. Example messages in this section show a simple request and response message pair.
More complex scenarios, including error cases, are provided in the section “Example Scenarios”.
As part of a transition path, the ONE Order Service Delivery messages are able to be implemented
independently of the ONE Order Accounting messages and business functions, however it is a
prerequisite that the Airline’s OMS must be using Orders.
IntroductionIntroduction
Page: 108 of 377
PurposePurpose
This message is intended to be used by the Delivery Provider to prepare for delivery of Services for
which it is responsible. The information provided by the message is used to support the delivery and
servicing by the relevant Delivery Provider.
The Delivery Provider requests information from the Airline’s OMS about a Service (including the
passenger’s entitlement) and its current status, and the Airline responds with all relevant information
about the Service to be delivered, along with the latest status. Note that the Airline may have changed
the status of the Service as a result of receiving the ServiceDelivery request, depending on internal
processes.
The criteria used to request this information may be singular, or batched for example per Passenger,
per Order/Service or flight. The Service Delivery response contains the full details of the Services in
the Order and all relevant flight information.
FeaturesFeatures
MessageMessage ComponentComponent FeaturesFeatures 18.218.2 ChangesChanges
Request Core
Accept an Order as input for Service Delivery
information
✔
Accept a flight as input for Service Delivery
Information
✔ -
Filtering By service type ✔ -
By airline code and flight number ✔ -
By equipment type ✔ -
By location code ✔ -
By departure date ✔ -
Response Service Provide service delivery information for an Order ✔ -
Provide service delivery information for a specific
flight
✔ -
Update service delivery information ✔ -
PurposePurpose
Page: 109 of 377
PurposePurpose
The Service Delivery Notification request is intended to be used by the OMS to inform Delivery
Providers about the Services to be delivered. This information may be sent for an individual
passenger, an Order, or may be provided for an entire flight or a given period of time. In case of
multiple Service delivery by a Delivery Provider the entire itinerary is sent with the message. Note that
the notification of Service delivery does not necessarily imply that Service delivery can be started.
This message is triggered by the Airline’s Order Management System to the Delivery Provider. Upon
completion of the message processing, the delivery partner has successfully been informed of the
Services that are to be delivered. For example, an Airline Order Management System may send flight
information (including passenger entitlement) and status to a ground handler. In case of multiple
Service delivery by a Delivery Provider the entire itinerary is sent with the message.
FeaturesFeatures
MessageMessage ComponentComponent FeatureFeature 18.218.2 ChangesChanges
Request Core
Accept an Order ID as input for Service Delivery
information
✔ -
Accept a flight as input for Service Delivery
Information
✔ -
Filtering By service type ✔ -
By airline code and flight number ✔ -
By equipment type ✔ -
By location code ✔ -
By departure date ✔ -
Response Service Acknowledge Service Delivery Notification ✔ -
OverviewOverview
Page: 110 of 377
PurposePurpose
The message may be used by a Delivery Provider to inform the Order Management System of
updates to the Service(s) that occur during the period of Service delivery, or used it can be used by
the Order Management System to inform the other carrier partner(s) of updates (in case of interlining).
This message is intended to be used for communicating necessary information related to the delivery
of a Service, such as providing the Order Management System with assigned baggage tag identifiers,
the weight of bags, seats assigned to passengers, advanced passenger information that may have
been collected and so on. The Order Management System then ensures that this data is stored for
later use (if necessary). Note that this Service is not intended to be used for the addition of new paid
Services, nor for any exchange of payment related information.
FeaturesFeatures
MessageMessage ComponentComponent FeatureFeature 18.218.2 ChangesChanges
Request Core
Accept an Order ID and Order Item as input for
Update Service Notification
✔ -
Accept the current status of an Order Item as input
for Update Service Notification
✔ -
Accept a delivery milestone as input for Update
Service Notification
✔ -
Accept baggage information as input for Update
Service Notification
✔ -
Filtering Not applicable - -
Response Service Acknowledge update of a service ✔ -
OverviewOverview
Page: 111 of 377
PurposePurpose
The Service Status Change Notification (SSCN) request message (ServiceStatusChangeNotifRQ) is
used to notify the Order Management System of any change in status to Services within an Order.
The status of a Service is used to track the ability of the Airline or Delivery Provider to deliver a
particular Service, and/or track whether a Service has been consumed. This message may be
triggered directly from a delivery process, but may also be triggered by an automated process, such
as the expiration of a time limit in which a service was to be consumed within. The Service Status
Change Notification message is used to advise the status of all Services (flights, flight-related
ancillaries, ground Services etc.) throughout the lifecycle of the Service.
The Service Status Change Notification request is used solely to advise of changes in status to a
Service. This may be the Delivery Provider confirming to the Order Management System that they are
able to provide a Service (e.g. lounge access).
The message can also be used to report a milestone event in the delivery of a particular Service, such
as a passenger being boarded, or accepted for boarding, a bag being loaded, a requested meal being
loaded on board etc. Therefore, reporting of a Service delivery milestone allows the progress of
Service delivery to be tracked from an operational perspective, supporting other operational
processes such as bag reconciliation and weight and balance tasks. However, the reporting of a
milestone event does not necessarily imply or trigger a change of the status of the Service (for
example, a passenger boarding does not trigger a status update for any flight Service).
FeaturesFeatures
MessageMessage ComponentComponent FeatureFeature 18.218.2 ChangesChanges
Request Core
Accept an Order ID and Service ID as input for
Service Status Change request
✔ -
Accept the current status of a service as input for
Service Status Change request
✔ -
Accept a delivery milestone of a service as input
for Service Status Change request
✔ -
Filtering Not applicable ✔ -
Response Service Acknowledge change of a service status ✔ -
OverviewOverview
Page: 112 of 377
The ONE Order business requirements define the necessary accounting processes and interactions
to enable purchased products and Services within Orders to be accounted for, depending on their
consumption status.
As part of a transition path, the ONE Order Accounting messages are able to be implemented
independently of the ONE Order Service Delivery messages and business functions, however it is a
prerequisite that the Airline’s OMS must be using Orders.
IntroductionIntroduction
Page: 113 of 377
Message SectionMessage Section
This section shall include message samples that clearly depicts how to implement/use key elements
in the applicable message(s) that meets the need of the required Business Functionalities.
Affected MessagesAffected Messages
OrderSalesInfoNotifRQ (OSIN)
OrderSalesInfoAccountingDocumentNotifRQ (OSIADN)
Message SamplesMessage Samples
01. Transmitting an OSIN request with penalty information01. Transmitting an OSIN request with penalty information
The Airline sends an OSIN message that includes penalty information to Accounting System.
02. Transmitting an OSIN request with penalty information (using lean schema02. Transmitting an OSIN request with penalty information (using lean schema
approach)approach)
The Airline sends an OSIN message that includes penalty information to Accounting System.
03. Transmitting an OSIN request with refundable information03. Transmitting an OSIN request with refundable information
The Airline sends an OSIN message that includes refundable information to Accounting System.
Voluntary Servicing Impact to AccountingVoluntary Servicing Impact to Accounting
<Samples to cover the following scenarios>
<Samples to cover the following scenarios>
sample to report/showcase a netted penalty related to order change
sample to report/showcase a netted penalty related to order change
sample to report/showcase a non-netter penalty related to an order change
sample to report/showcase a non-netter penalty related to an order change
sample to report/showcase a netted penalty related to an order cancellation
sample to report/showcase a netted penalty related to an order cancellation
sample to report/showcase a non-netter penalty related to an order cancellation
sample to report/showcase a non-netter penalty related to an order cancellation
None Copy
<Samples to cover the following scenarios in case of lean schema approach
<Samples to cover the following scenarios in case of lean schema approach
sample to report/showcase a netted penalty related to order change
sample to report/showcase a netted penalty related to order change
sample to report/showcase a non-netter penalty related to an order change
sample to report/showcase a non-netter penalty related to an order change
sample to report/showcase a netted penalty related to an order cancellation
sample to report/showcase a netted penalty related to an order cancellation
sample to report/showcase a non-netter penalty related to an order cancellation
sample to report/showcase a non-netter penalty related to an order cancellation
None Copy
<Sample cover the following scenarios >
<Sample cover the following scenarios >
Sample to report/showcase a partial refund of fare
Sample to report/showcase a partial refund of fare
Sample to report/showcase a partial refund of taxes
Sample to report/showcase a partial refund of taxes
None Copy
Page: 114 of 377
04. Transmitting an OSIN request with non-refundable information04. Transmitting an OSIN request with non-refundable information
The Airline sends an OSIN message that includes non-refundable information to Accounting System.
05. Transmitting an OSIN request with penalty and refundable information (using05. Transmitting an OSIN request with penalty and refundable information (using
lean schema approach)lean schema approach)
The Airline sends an OSIN message that includes both penalty and refundable information to
Accounting System.
06. Transmitting an OSIN request with penalty, refundable, and non-refundable06. Transmitting an OSIN request with penalty, refundable, and non-refundable
informationinformation
The Airline sends an OSIN message that includes penalty, refundable, and non-refundable information
to Accounting System.
<Samples to cover the following scenarios >
<Samples to cover the following scenarios >
Sample to report /showcase a withholding of partial fare value
Sample to report /showcase a withholding of partial fare value
Sample to report/showcase a withholding of taxes which are non-refundable
Sample to report/showcase a withholding of taxes which are non-refundable
None Copy
<Sample here>
<Sample here>
Repeat the above samples with aall the values
Repeat the above samples with aall the values
None Copy
<Sample here>
<Sample here>
Repeat the above samples with aall the values
Repeat the above samples with aall the values
None Copy
Page: 115 of 377
PurposePurpose
The Service Status Change Notification request message is also used by the OMS to advise the
Airline Accounting System of the final delivery status of a Service (delivered, removed, expired, not
claimed, failed to deliver). However, this message is only intended to be used to trigger the recognition
of revenues and/or trigger interline billing, based on the final delivery status of a Service. For other
interactions with the Accounting System, the OSIN message is to be used.
Reporting of Service usage provides the ability to perform revenue accounting for an ORA. It depends
on the fact that a Service has been delivered, or that a customer is no longer eligible for the Service.
For example, a passenger may have missed their flight and is not eligible to rebook onto another flight.
Reporting of Service usage allows the communication of adjustments in tax amounts between sales
and usage time, when calculated by the OMS.
FeaturesFeatures
MessageMessage ComponentComponent FeatureFeature 18.218.2
ChangeChange
fromfrom
previousprevious
Request Core
Accept an Order ID and Service ID as input for
Service Status Change request
X -
Accept the current status of a service as input for
Service Status Change request
X -
Accept a delivery milestone of a service as input
for Service Status Change request
X -
Filtering Not applicable X -
Response Service Acknowledge change of a service status X -
OverviewOverview
Page: 116 of 377
PurposePurpose
Order Closing Notification (OrderClosingNotifRQ) is used to inform an Accounting System that no
further updates are to be expected for an entire Order. Once an Order is closed, no further changes
can be made to it. Closed Orders may, however, still be retrieved.
Order Closing Notification is the only mechanism to set an Order to “CLOSED” status. After this, no
further changes may be made to an Order. Typically, an Order is only closed when all of the Services
in the Order have been delivered.
FeaturesFeatures
MessageMessage ComponentComponent FeatureFeature 18.218.2 ChangesChanges
Request Core
Accept an Order as input for Order Closing
Notification
✔ -
Filtering Not applicable - -
Response Service Acknowledge change of a Service status ✔ -
OverviewOverview
Page: 117 of 377
OverviewOverview
The Payload Attributes are used outside the context of the message to identify and group message
sets for debugging purposes.
Payload Attributes Request and Response ElementsPayload Attributes Request and Response Elements
Transaction IDTransaction ID
A universally unique identifier used to identify a transaction set. The Transaction ID is used by the
Seller to identify the outbound requesting message, the transaction ID is then echoed back by the
receiving party in the response.
This allows for both systems to find the message pair (RQ/RS) if one message is present. For
example, if the OrderViewRS returns an error, using the echoed back transaction ID, the requestor can
find the request that caused that error using that same Transaction ID.
OrderCreateRQOrderCreateRQ
OrderCreateRSOrderCreateRS
Correlation IDCorrelation ID
A universally unique identifier used to identify a set of messages that were used together. The
Correlation ID is generated by the Seller and echoed back by the Airline.
This is used to find all messages that led up to the point at which there was a potential failure or to
understand how a message flow was implemented. For example, if an Order fails, the OrderViewRS
will return a failure message and within the transaction element, the Correlation ID. By searching logs
for that Correlation ID, all messages from AirShopping, OfferPrice and OrderCreate can be found and
linked.
AirShoppingRQAirShoppingRQ
Transaction ManagementTransaction Management
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
None Copy
Page: 118 of 377
AirShoppingRSAirShoppingRS
OfferPriceRQOfferPriceRQ
OfferPriceRSOfferPriceRS
OrderCreateRQOrderCreateRQ
OrderCreateRSOrderCreateRS
LanguageLanguage
The Language, or Locale is used to request a specific language preference for the responding
message.
For example, a Seller requests the message response to be in French.
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>6379132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:TrxID>1119132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>1119132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:TrxID>1119132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>1119132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:TrxID>2229132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>2229132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:CorrelationID>b1159451-0b7c-4da8-9926-86f48ec48ab6</iata:CorrelationID>
<iata:TrxID>2229132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
<iata:TrxID>2229132c-6440-4bc1-b6ea-359b7222bfa7</iata:TrxID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
Page: 119 of 377
Or, Seller requests the response to be in Australian English.
The Airline responds with US English.
TimestampTimestamp
The sending or responding party may time stamp the message at the time that the message is ready
for transmission.
VersionVersion
Used for sending information to another party. Note that having the version of the message in the
message provides no benefit, however this may be used for other bilateral purposes (such as an
aggregator detailing a sourcing message version).
Retransmission IDRetransmission ID
Used for recovering a failed transaction, by requesting the Airline to re-send the initial response if it
recieved it.
Echo TokenEcho Token
Element has been deprecated and will be removed in 20.2.
SeqNumberSeqNumber
Element has been deprecated and will be removed in 20.2.
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:PrimaryLangID>fr-FR</iata:PrimaryLangID>
<iata:PrimaryLangID>fr-FR</iata:PrimaryLangID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:PrimaryLangID>en-AU</iata:PrimaryLangID>
<iata:PrimaryLangID>en-AU</iata:PrimaryLangID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:PrimaryLangID>en-US</iata:PrimaryLangID>
<iata:PrimaryLangID>en-US</iata:PrimaryLangID>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
<iata:PayloadAttributes>
<iata:PayloadAttributes>
<iata:Timestamp>2010-03-23T10:49:55+01:00</iata:Timestamp>
<iata:Timestamp>2010-03-23T10:49:55+01:00</iata:Timestamp>
</iata:PayloadAttributes>
</iata:PayloadAttributes>
None Copy
Page: 120 of 377
TrxStatusCodeTrxStatusCode
Element has been deprecated and will be removed in 20.2.
Page: 121 of 377
Use caseUse case
Use Case 1 Credit card payment involving commission.Use Case 1 Credit card payment involving commission.
The customer has selected a preferred Offer and the Seller is now requesting creation of an Order.
The customer is paying with credit card. The Seller is expecting a commission of 10%. The amount to
be paid is €150 and the commission to the Seller is €15. Since the payment is with credit card there
will be two data sets of PaymentInfo – one for the credit card receivables and one for the cash
settlement of the commission. The PaymentInfo related to the Credit Card dataset will have
receivables of €150 and payable of €0. The PaymentInfo related to the Cash dataset will have
receivables of €0 and payable of €15 resulting in Net Clearance Amount (negative)–€15. The Carrier
will then send request for clearance related to the cash payment method type so that the commission
obligation is settled via the settlement process.
Use Case 2 Cash payment involving commissionUse Case 2 Cash payment involving commission
The customer has selected a preferred Offer and the Seller is now requesting creation of an Order.
The customer is paying cash. The Seller is expecting a commission of 10%. The amount to be paid is
€150 and the commission to the Seller is €15. Since the payment method type is cash there will be
one PaymentInfo data set and it will indicate receivable of €150 and payable of €15, resulting in Net
Clearance Amount of €135. The Carrier will then send request for clearance for €135 to settle via the
settlement process. The remittance date is provided in the PaymentInfo and as such agreed to be 9
April 2019.
Use Case 3 Payment with EasyPay involving a commissionUse Case 3 Payment with EasyPay involving a commission
The customer has selected a preferred Offer and the Seller is now requesting creation of an Order.
The customer is paying cash, but the Seller is committing the sale with payment method type
EasyPay. The Seller is expecting a commission of 10%. In the OrderCreateRQ the Seller outlines
receivables for the Carrier of €150 and payable to the Seller €15 with Net Clearance Amount of €135.
The Carrier then asks the EasyPay platform for authorization for €135 not €150. The EasyPay
platform provides the authorization ID for the transaction guaranteeing €135 to the Carrier. The carrier
sends the Order View RS to confirm the sale and requests clearance for €135 including the
authorization ID from the EasyPay platform. The settlement manager immediately requests the transfer
of €135 from the EasyPay platform and transfers the funds to the Carrier.
NetClearanceAmount is not applicable when transactions are reported for settlement using DISH
reporting format, such as NDCLink. In such cases the carrier reports the “Amount” from the Payment
Processing Summary and any other related amounts such as commissions are reported separately.
Business FunctionsBusiness Functions
01. Inform Seller of Net Clearance Data
02. Inform Airline of Payment information including Net Clearance Amount
Net Clearance AmountNet Clearance Amount
Page: 122 of 377
Message FlowMessage Flow
Page: 123 of 377
Use CasesUse Cases
1. Airline reports penalty information to Accounting1. Airline reports penalty information to Accounting
“The passenger initiates change to the Order that resulted in the collection of penalty amounts. The
Airline needs to communicate the penalty information to Accounting.”
In this use case, the following scenarios are covered:
1. The passenger initiates full change to the order item (Full cancellation) that resulted in the
collection of penalty amount which is not-netted
2. The passenger initiates a full change to the order item (Full cancellation) that resulted in the
collection of the penalty which is netted
3. The passenger initiates partial change to the order item (Partial cancellation) that resulted in
the collection of penalty amount which is not-netted
4. The passenger initiates a partial change to the order item (Partial cancellation) that resulted in
the collection of the penalty which is netted
5. The passenger initiates Full change to the order item (Complete modification) that resulted in
the collection of penalty amount which is not-netted
6. The passenger initiates a partial change to the order (Complete Modification) that resulted in
the collection of the penalty which is netted
7. The passenger initiates partial change to the order (Partial Modification) that resulted in the
collection of penalty amount which is not-netted
8. The passenger initiates a partial change to the order (Partial cancellation) that resulted in the
collection of the penalty which is netted
For the listed scenarios, the following business function can be used:
• Report penalty to Airline Accounting
2. Airline reports refundable information to Accounting2. Airline reports refundable information to Accounting
“The passenger initiates change to the Order that resulted in the refund of some amount back to the
passenger. The Airline needs to communicate the refundable information to Accounting.”
In this use case, the following scenarios are covered:
1. The passenger initiates change to the Order that resulted in the partial refund for a portion of
the refundable fare and/or any applicable tax amount to the passenger
2. The passenger initiates change to the Order that resulted in the full refund of fare and/or tax
amount to the passenger
For the listed scenarios, the following business function can be used:
• Report refundable amounts to Airline Accounting
3. Airline reports non-refundable information to Accounting3. Airline reports non-refundable information to Accounting
“The passenger initiates change to the Order that resulted in the withholding of some amount back
from the passenger. The Airline needs to communicate the non-refundable information to Accounting.”
Voluntary Servicing Impact AccountingVoluntary Servicing Impact Accounting
Page: 124 of 377
In this use case, the following scenarios are covered:
1. The passenger initiates change to the Order that resulted in the withholding of a portion of the
fare and/or tax amount from the passenger
2. The passenger initiates change to the Order that resulted in the withholding of all portion of
the fare and/or tax amount from the passenger
For the listed scenarios, the following business function can be used:
• Report non-refundable amounts to Airline Accounting
Business FunctionsBusiness Functions
01. Report penalty to Airline Accounting
02. Report refundable amounts to Airline Accounting
03. Report non-refundable amounts to Airline Accounting
Message FlowMessage Flow
Page: 125 of 377
ScenarioScenario
"One traveller based in New York would like to buy a round-trip to Paris. He would like to get a
flat-bed seat to be able to sleep, and he would also like to purchase a baggage allowance. "
Business FunctionsBusiness Functions
1. Request a set of Offers based on Origin, Destination and defined dates
This function allows the Seller to request from an Airline a set of Offers based on Origins, Destinations
and defined dates. The Seller may provide additional qualifiers and context for which the Airline may
take into account in the content of the resulting Offers.
2. Build upsell Offers based on Origin, Destination and defined dates (optional)
This function allows the Airline to build additional upsell Offers that relate to Origin, Destination and
defined dates which may enhance the customer experience. The content of the resulting Offers may
depend on additional qualifiers and context that may be provided by the Seller.
3. Request detailed information about an Offer
This function allows the Seller to request detailed information about an Offer, including all price
breakdowns, terms & conditions, disclosure data.
4. Select Offer(s) to add to a shopping basket
iThis function allows the Seller to select Offer(s) and Offer Item(s) which they wish to progress with.
This allows the Airline to refine these Offer(s) and return a single Offer.
5. Request a new Offer based on the content of existing Offer(s) and on additional qualifiers and
context
This function allows the Seller to pass additional information (e.g. Frequent Flyer Info, Form of
Payment etc) so that an Airline can create a new contextualised Offer.
6. Build Upsell Offer(s) based on the content of other Offer(s)
This function allows the Airline to build additional Offers that relate to a baseline Offer which may
enhance the customer experience.
Message FlowMessage Flow
ShoppingShopping
Page: 126 of 377
Page: 127 of 377
ScenarioScenario
"One traveller based in New York would like to buy a round-trip to Paris. He would like to get a
flat-bed seat to be able to sleep, and he would also like to purchase a baggage allowance. The
traveller will first get approval to travel and in this scenario, they will commit to pay after any Price
Guarantee Time Limit has expired, or such guarantees were never originally made."
Business FunctionsBusiness Functions
1. Request a set of Offers based on Origin, Destination and defined dates
This function allows the Seller to request from an Airline a set of Offers based on Origins, Destinations
and defined dates. The Seller may provide additional qualifiers and context for which the Airline may
take into account in the content of the resulting Offers.
2. Build upsell Offers based on Origin, Destination and defined dates (optional)
This function allows the Airline to build additional upsell Offers that relate to Origin, Destination and
defined dates which may enhance the customer experience. The content of the resulting Offers may
depend on additional qualifiers and context that may be provided by the Seller.
3. Request detailed information about an Offer
This function allows the Seller to request detailed information about an Offer, including all price
breakdowns, terms & conditions, disclosure data.
4. Select Offer(s) to add to a shopping basket
iThis function allows the Seller to select Offer(s) and Offer Item(s) which they wish to progress with.
This allows the Airline to refine these Offer(s) and return a single Offer.
5. Request a new Offer based on the content of existing Offer(s) and on additional qualifiers and
context
This function allows the Seller to pass additional information (e.g. Frequent Flyer Info, Form of
Payment etc) so that an Airline can create a new contextualised Offer.
6. Build Upsell Offer(s) based on the content of other Offer(s)
This function allows the Airline to build additional Offers that relate to a baseline Offer which may
enhance the customer experience.
7. Create Order
This function is to allow the Seller to request that an Airline create an Order from a selection of
Offer(s) and Offer Item(s).
8. Retrieve Order (optional)
Shopping and Ordering with Deferred PaymentShopping and Ordering with Deferred Payment
TimeTime
Time period passes….. 5ms to 5 seconds to 5 hours to 5 days to 5 months.
Page: 128 of 377
This function allows the Seller to display the content of an Order.
9. Confirm the price of the Order Item(s) (optional)
This function is for a Seller to request that an Airline quotes and confirms the price of unpaid Order
Item(s).
10. Accept Repriced Offer(s) (optional)
This function allows the Seller to accept the new prices that were returned by the Airline and which will
be reflected in the Order after it is updated.
11. Add payment information into an existing Order
This function allows the Seller to add payment information into an existing Order, and optionally
associate this payment information with Order Item(s).
12. Commit to the Terms of the Order
This function allows the Seller to notify the Airline that they are ready to accept the Terms of the Order
/ OrderItem(s).
Message FlowMessage Flow
Page: 129 of 377
Page: 130 of 377
ScenarioScenario
"One traveller (Jane Smith, with a Frequent Flyer Number) based in London is shopping for a
round trip to New York. She would like to buy a baggage allowance and request a seat for her
flight from London to New York. The customer will commit to pay within a known Price Guarantee
Time Limit."
Business FunctionsBusiness Functions
1. Request a set of Offers based on Origin, Destination and defined dates
This function allows the Seller to request from an Airline a set of Offers based on Origins, Destinations
and defined dates. The Seller may provide additional qualifiers and context for which the Airline may
take into account in the content of the resulting Offers.
2. Build upsell Offers based on Origin, Destination and defined dates (optional)
This function allows the Airline to build additional upsell Offers that relate to Origin, Destination and
defined dates which may enhance the customer experience. The content of the resulting Offers may
depend on additional qualifiers and context that may be provided by the Seller.
3. Request detailed information about an Offer
This function allows the Seller to request detailed information about an Offer, including all price
breakdowns, terms & conditions, disclosure data.
4. Select Offer(s) to add to a shopping basket
This function allows the Seller to select Offer(s) and Offer Item(s) which they wish to progress with.
This allows the Airline to refine these Offer(s) and return a single Offer.
5. Request a new Offer based on the content of existing Offer(s) and on additional qualifiers and
context
This function allows the Seller to pass additional information (e.g. Frequent Flyer Info, Form of
Payment etc) so that an Airline can create a new contextualised Offer.
6. Build Upsell Offer(s) based on the content of other Offer(s)
This function allows the Airline to build additional Offers that relate to a baseline Offer which may
enhance the customer experience.
7. Request a la carte Offer(s) for ancillary services based on an existing Offer or Order
This function is to allow a Seller to request for a la carte Offer(s) for ancillary services based on an
existing Offer or Order. If the Seller has included additional qualifiers or preferences, the a la carte
Offers generated by the airline may take this into consideration.
8. Request a Seat Map and an a la carte Offer for seats based on an existing Offer or Order
Shopping and Ordering with Instant PaymentShopping and Ordering with Instant Payment
Page: 131 of 377
This function is to allow a Seller to request a seat map and an a la carte Offer for seats based on an
existing Offer or Order. If the Seller has included additional qualifiers or preferences, the a la carte
Offer(s) generated by the airline may take this into consideration.
9. Select Offer(s) to add to a shopping basket
This function allows the Seller to select Offer(s) and Offer Item(s) which they wish to progress with.
This allows the Airline to refine these Offer(s) and return a single Offer.
10. Build Upsell Offer(s) based on the content of other Offer(s)
This function allows the Airline to build additional Offers that relate to a baseline Offer which may
enhance the customer experience.
11. Create Order
This function is to allow the Seller to request that an Airline create an Order from a selection of
Offer(s) and Offer Item(s).
11a. Sub-Function: Add payment information as part of a new Order
This function allows the Seller to send payment information to the Airline.
11b. Sub-Function: Commit to the Terms of the Offer during ‘Create Order’
This function allows the Seller to notify the Airline that they are ready to accept the Terms of the Offer /
Offer Item(s).
Message FlowMessage Flow
Page: 132 of 377
Page: 133 of 377
ScenarioScenario
"A traveler has a paid Order for round-trip from Hong Kong to Los Angeles. The traveller is yet to
use any of his services. They would now like to depart on another date than the one initially
defined in the Order, they do not know which specific flights are available. There can be collection
of additional fees/penalties or refund depending on the new offer selected. In this case, any
commitment to pay or refund is done in a single step, it is not a delayed commitment scenario."
Business FunctionsBusiness Functions
1.Retrieve Order
This function allows the Seller to display the content of an Order.
2.Request a set of Reshop Offers based on Origin, Destination and/or defined dates as replacement
of specific OrderItem(s).
This function allows the Seller to request a set of Offers as a replacement of specific OrderItem(s).
The request takes into account new Origins, Destinations and/or defined dates. The content of the
resulting Reshop Offers may depend on additional qualifiers and context that may be provided by the
Seller.
3. Request detailed information on selected Reshop Offer(s)
This function allows the Seller to request detailed information about Reshop Offer(s), including all
price breakdowns, terms & conditions, disclosure data etc.
4.Select Reshop Offer(s) to add to a shopping basket
This function allows the Seller to select Reshop Offer(s) and Offer Item(s) which they wish to progress
with. This allows the Airline to refine these Offer(s) and return a single Reshop Offer.
5. Request a new Reshop Offer based on the content of existing Reshop Offer(s) and on additional
qualifiers and context
This function allows the Seller to pass additional information (e.g. Frequent Flyer Info, Form of
Payment etc) so that an Airline can create a new contextualised Reshop Offer.
6. Request Offer Item(s) to be added to an existing Order
This function is to allow the Seller to request that Offer Item(s) be converted into Order Item(s) within
an existing Order.
7. Cancel Order Item(s) from an existing Order
This function allows the Seller to request cancellation of selected Order Item(s) from an existing Order.
8. Add payment information into an existing Order
This function allows the Seller to add payment information into an existing Order, and optionally
associate this payment information with Order Item(s).
Change of ItineraryChange of Itinerary
Page: 134 of 377
Page: 136 of 377
ScenarioScenario
"One traveler based in Podgorica has a paid Order to travel to London. Before the start of the
journey, the traveler needs to cancel his travel plans, so he would like to cancel the existing Order
and get any refundable amount back."
Business FunctionsBusiness Functions
1. Retrieve Order (optional)1. Retrieve Order (optional)
This function allows the Seller to display the content of an Order.
2. Request refundable amount for existing Order Item(s)2. Request refundable amount for existing Order Item(s)
This function allows the Seller to request the refundable amount for existing Order Item(s) that the
Customer wishes to cancel.
3. Cancel Order3. Cancel Order
This function allows the Seller to request cancellation of an existing Order.
Message FlowMessage Flow
Full Order CancellationFull Order Cancellation
Page: 137 of 377
Page: 138 of 377
Use CasesUse Cases
Passenger initiated changesPassenger initiated changes
"The passenger contacts the Airline (ORA) directly and makes a change in the Order instead of
contacting the travel agent. The Airline (ORA) needs to communicate the changes to the Order.”
In this use case, the following scenario is covered:
• Notification of name and/or phone contact detail changes
Airline (ORA) initiated changesAirline (ORA) initiated changes
"The Airline (ORA) makes changes to the Order. The Airline (ORA) needs to communicate the
changes to the Order."
In this use case, the following scenario is covered:
• Notification of payment status changes
Airline (ORA) performs schedule changeAirline (ORA) performs schedule change
"The Airline (ORA) performs a schedule change. The Airline (ORA) needs to communicate the
changes to the Order. The Airline (ORA) notifies the following indicators/data: Airline URI, whether an
acceptance is needed, a time limit to accept the changes, consequence of inaction, and fare waiver
details (if applicable)."
In this use case, the following scenarios are covered:
• Notification of flight segment time changes (schedule change)
• Notification of flight segment number changes (schedule change)
• Notification of flight segment arrival and/or departure changes (schedule change)
• Notification of flight equipment changes (schedule change)
• Notification of flight cancellation (schedule change)
• Notification of flight changes (schedule change)
• Notification of Airline URI
• Notification of schedule change acceptance
• Notification of schedule change time limit
• Notification of schedule change consequence of inaction
• Notification of schedule change fare waiver (if applicable)
Business FunctionsBusiness Functions
01 . Inform seller of passenger name and/or contact details changes
02. Inform seller of payment status changes
03. Inform seller of flight segment time changes - schedule Change
04. Inform seller of flight number changes - Schedule Change
Structure of the Order Change NotificationStructure of the Order Change Notification
Page: 139 of 377
05. Inform Seller of flight arrival and/or departure changes - Schedule Change
06. Inform Seller of flight equipment changes - Schedule Change
07. Inform Seller of flight cancellation - Schedule Change
08. Inform seller of flight changes - Schedule Change
Message FlowMessage Flow
Passenger or Airline (ORA) initiated changes
This message flow applies to the following business functions:
• Inform Seller of passenger name and/or contact details changes
• Inform Seller of payment status changes
Airline (ORA) performs schedule change
This message flow applies to the following business functions:
• Inform Seller of flight segment time changes (Schedule Change)
• Inform Seller of flight arrival and/or departure changes (Schedule Change)
• Inform Seller of flight equipment changes (Schedule Change)
• Inform Seller of flight cancellation (Schedule Change)
• Inform Seller of flight changes (Schedule Change)
Technical CapabilityTechnical Capability
Multiple change operations in a group
Page: 140 of 377
Allows the notification of multiple change operations in separate groups. This allows implementers to
batch multiple change operations.
1. Implementers may send a single Order change per OrderChangeNotifRQ
2. Implementers may send multiple Order changes in a single group per OrderChangeNotifRQ
3. Implementers may send multiple groups of Order changes per OrderChangeNotifRQ
Triggers to batch change operations are not defined in this document.
Include Order snapshot (before or after an Order change is committed)
Allows the notification of the Order before (or after) an Order change has occurred. This allows
implementers to provide contextual data to receiving systems that cannot store Order details.
1. Implementers may send an Order change update without the Order snapshot
2. Implementers may send an Order change update with the Order snapshot
Page: 141 of 377
Use CasesUse Cases
The following use-cases are included in this section:
• Collection of multiple addresses at destination
• Collection of emergency contact details
• Collection of contact details for unaccompanied minor
Business FunctionsBusiness Functions
01. Provide address at destination
02. View address at destination
03. Provide emergency contact details
04. View emergency contact details
05.Provide contact details for an unccompanied minor
06. View contact details for an unaccompanid minor
Message FlowMessage Flow
Passenger or Airline (ORA) initiated changes
Ability to Handle Multiple Types of ContactsAbility to Handle Multiple Types of Contacts
Page: 142 of 377
Use CasesUse Cases
Airline (ORA) performs Planned Schedule ChangeAirline (ORA) performs Planned Schedule Change
“The Airline (ORA) performs Planned Schedule Change. The Airline (ORA) needs to communicate the
changes to the Order. The Airline (ORA) notifies the following indicators/data: Airline URI, whether an
acceptance is needed, a time limit to accept the changes, consequence of inaction, and FareWaiver
Code details (if applicable).”
In this use case, the following scenarios are covered:
Notification of flight segment time changes (Planned Schedule Change)
Notification of flight segment number changes (Planned Schedule Change)
Notification of flight segment arrival and/or departure changes (Planned Schedule Change)
Notification of flight equipment changes (Planned Schedule Change)
Notification of flight cancellation (Planned Schedule Change)
Notification of flight changes (Planned Schedule Change)
Notification of Airline URI
Notification of Planned Schedule Change acceptance
Notification of Planned Schedule Change time limit
Notification of Planned Schedule Change consequence of inaction
Notification of Planned Schedule Change FareWaiver code (if applicable)
Seller is informed of the Airline (ORA) Planned Schedule ChangeSeller is informed of the Airline (ORA) Planned Schedule Change
“After the Airline (ORA) performs the Planned Schedule Change, the Seller is informed (and aware)
that a Planned Schedule Change has occurred and requires acceptance.”
In this use case, the following scenarios are covered:
Seller is informed that an Order has undergone a Planned Schedule Change
Seller is informed a Planned Schedule Change acceptance is needed
Seller accepts Airline (ORA) Planned Schedule ChangeSeller accepts Airline (ORA) Planned Schedule Change
“After receiving the notification of Planned Schedule Change from Airline (ORA) and if an acceptance
is required, the Seller is able to accept the Planned Schedule Change.”
In this use case, the following scenario is covered:
Seller can accept a Planned Schedule Change
Seller rejects Airline (ORA) Planned Schedule ChangeSeller rejects Airline (ORA) Planned Schedule Change
After receiving the notification of Planned Schedule Change from Airline (ORA), the Seller is able to
reject the Planned Schedule Change and reshop for alternate solutions with the FareWaiver Code.”
In this use case, the following scenarios are covered:
Structure of the Invol ServicingStructure of the Invol Servicing
Page: 143 of 377
Seller can transmit the FareWaiver Code details during reshop
Seller can reshop with FareWaiver Code and Airline (ORA) can respond accordingly
Seller can cancel with FareWaiver Code and Airline (ORA) can respond accordingly
Seller can view the Order after accepting a reshop Offer
Business FunctionsBusiness Functions
01. Inform Seller of Planned Schedule Change and any required follow up actions
02. Acceptance of a Planned Schedule Change
03. Reshop following a Planned Schedule Change
04. Cancellation following a Planned Schedule Change
Message FlowMessage Flow
Page: 144 of 377
Use CasesUse Cases
Passenger initiated full cancellationPassenger initiated full cancellation
“The passenger contacts the Seller to request full cancellation of an Order, which means everything
that can be cancelled without specifying any selection of Services or passengers.”
In this use case, the following scenario is covered:
Cancellation of all Services from an Order
In case there is residual value due to the passenger, the following may apply:
Refund the residual value to passenger
Retain the residual value for future use
In case there is a penalty to be applied by the Airline (ORA), the following may apply:
Residual value or refund is applied towards penalty (net)
Residual value or refund is not applied towards penalty (penalty paid separately)
Passenger initiated partial cancellationPassenger initiated partial cancellation
“The passenger contacts the Seller to request the partial cancellation of an Order, which means that
the passenger selects specific Order item(s) or passenger(s) to cancel.”
Note:Note: The lowest granularity for partial cancellation is the Order Item. Removal of some
Services, while retaining other Services in the Order item(s), falls under Passenger initiatedPassenger initiated
changes to an Orderchanges to an Order use case.
In this use case, the following scenarios are covered:
Cancellation of flight(s) from an Order
Cancellation of passenger(s) from an Order
Cancellation of ancillary(ies) from an Order
In case there is residual value due to the passenger, the following may apply:
Refund the residual value to passenger
Retain the residual value for future use
In case there is a penalty to be applied by the Airline (ORA), the following may apply:
Residual value or refund is applied towards penalty (net)
Residual value or refund is not applied towards penalty (penalty paid separately)
Passenger initiated changes to an OrderPassenger initiated changes to an Order
“The passenger contacts the Seller to request changes to an Order that can result in any price
variation; change to an Order can be full or partial.
Voluntary Servicing for full,partial cancellation and orderVoluntary Servicing for full,partial cancellation and order
modificationmodification
Page: 145 of 377
Note:Note: This use case covers the removal of some Services while retaining other Services.
Cancellation of full or partial Order Items are detailed in the use cases: Passenger initiated full
cancellation or Passenger initiated partial cancellation.
In this use case, the following scenarios are covered:
Change of Service dates
Change of Service flights
Change of Service departure and/or arrival
Change of Service product (E.g. cabin, class, fare, family, etc.)
In case there is residual value due to the passenger, the following may apply:
Refund the residual value to passenger
Retain the residual value for future use
In case there is a penalty to be applied by the Airline (ORA), the following may apply:
Residual value or refund is applied towards penalty (net)
Residual value or refund is not applied towards penalty (penalty paid separately)
Passenger initiated cancellation (retaining Order for future use)Passenger initiated cancellation (retaining Order for future use)
“The passenger contacts the Seller to request a full or partial cancellation of an Order and wants to
retain the Order for future use. The passenger will return at a future point to request for refund or
reshop for new Service(s) - at which time, any financial impact will be determined in the subsequent
reshop flow.”
In this use case, the following scenarios are covered:
Full or partial cancellation for an Order, where the passenger does not know whether they will
request for new services or request for refund.
Note:Note: In the current transition period, it means that the Airline cancels the Order but retains any
applicable document(s).
Business FunctionsBusiness Functions
01. Transmit fare waiver at reshop
02. Respond to reshop request with the details of the order modification or cancellation - partial or full
03. Request full or partial Order cancellation; Airline (ORA) retains Order for future Reshop request
04. Inform Seller that request is extended to dependent Order Item(s)
05. Inform Seller if a penalty is netted or to be paid
06. Inform Seller about differential type
07. Inform Seller about what will happen to an existing Service should the Seller accept a reshopped
Offer Item
08. Commit to selected accepted reshop/delete Offer(s), confirm contact details and preferences
09. View the result of the order modification or cancellation (partial or full)
Page: 146 of 377
Message FlowMessage Flow
Page: 147 of 377
Page: 148 of 377
ScenarioScenario
" Schedule change (flight departure time change) and no re-accommodation is necessary .
None of the Services have been consumed. customer accepts change (no reshop).”
Business FunctionsBusiness Functions
1. Notify Seller of Changes to the Order1. Notify Seller of Changes to the Order
When a schedule change happens (eg flight departure time change), this function allows the ORA to
send an OrderChangeNotifRQ to the Seller and receive an Acknowledgement message in return. The
ORA must notify the Seller of Schedule Changes outside of the Operational window.
Message FlowMessage Flow
Schedule ChangeSchedule Change
Page: 149 of 377
Servicing Multi-passenger OrdersServicing Multi-passenger Orders
The following implementation guidelines illustrate how to service Orders that contain multiple
passengers, applicable to the following scenarios:
1. Ability for a seller to request a change for a subset of passengers in a multi-passenger Order
2. Ability for an airline to notify seller of an airline-initiated change that impacts a subset of
passengers in a multi-passenger Order
3. Ability for a seller to request that data is no longer shared between passengers contained in
the same Order for privacy reasons
These guidelines address communication between Sellers and Airlines. How the airlineT hese guidelines address communication between Sellers and Airlines. How the airline
manages the Order record in their Order Management System and subsequently anymanages the Order record in their Order Management System and subsequently any
impact on reservations and accountable documents is for an Airline to determine as part ofimpact on reservations and accountable documents is for an Airline to determine as part of
their own implementationtheir own implementation
For scenarios 1 and 2, as IATA NDC XML standards support non-homogeneous Orders, multiple
passengers can co-exist in the same Order while still having a distinct association to different
services.
For scenario 3,
Ability for a seller to request a change for a subset of passengers in a multi-Ability for a seller to request a change for a subset of passengers in a multi-
passenger Orderpassenger Order
In this scenario, a party of 2 have an Order traveling on the same itinerary. Passenger 1 wishes to
change their outbound flight to a different day than Passenger 2 but return on the original segment
together as a party of 2. The passengers would like to ensure their return flight is not negatively
impacted by this change and therefore remain seated together and known as a party of 2.
Original itinerary:
Pax 1 & 2 – 19DEC – MAD to NYC
Pax 1 & 2 – 30DEC – NYC to MAD
New itinerary:
Pax 1 – 19DEC – MAD to NYC
Pax 2 – 20 DEC – MAD to NYC
Pax 1 & 2 – 30DEC – NYC to MAD
For illustration purposes, the Order is structured as follows…
We have Order XX000A1B2C3D4 containing:
OrderItem 1
§ Service 1-1: Pax1-Seg1 (MAD-NYC)
§ Service 1-2: Pax1-Seg2 (NYC-MAD)
§ Service 1-3: Pax2-Seg1 (MAD-NYC)
§ Service 1-4: Pax2-Seg2 (NYC-MAD)
Servicing Multi-passenger OrderServicing Multi-passenger Order
Page: 150 of 377
01. Ability for a seller to re-shop for a subset of passengers01. Ability for a seller to re-shop for a subset of passengers
The seller will generate an OrderReshopRQ specifying the order items and passengers that are to be
reshopped. To achieve this, the seller must specify which Services are to be impacted by the change.
As a service is instantiated to a passenger, by specifying which services are to be impacted, by
association, the impacted passenger is specified.
Note: As a principle, the entire Order Item must be reshopped, and the Airline will re-evaluate the
entire Order Item when they receive this request. By specifying the impacted services, it is simply a
way for the Seller to indicate which services and passengers are to be impacted by the change. The
Seller should not expect the result of this interaction to be an Order Item that remains the same, simply
with updated Services. The result will be two new Offer Items, with the original itinerary and applicable
services for Pax1 in one OfferItem and a new itinerary for Pax2 in another Offer Item.
02.Ability for an airline to provide offers for changes to a subset of passengers02.Ability for an airline to provide offers for changes to a subset of passengers
The airline will generate an OrderReshopRS, returning the new, proposed OfferItems, one for Pax1
featuring the original itinerary and associated Services for Pax1, and a second for Pax2 with the new
itinerary with associated Services for Pax2.
03. Ability for a seller to request an Order change to a subset of passengers03. Ability for a seller to request an Order change to a subset of passengers
The seller will generate an OrderChangeRQ specifying the Offer(s) to be accepted.
04. Ability for an airline to respond to an Order change04. Ability for an airline to respond to an Order change
Page: 151 of 377
The airline will generate an OrderViewRS, returning all the data related to the Order, including details
of the new OrderItem, with Services relating to the original itinerary of Pax1, and the new itinerary of
Pax2.
Ability for a seller to request that data is no longer shared betweenAbility for a seller to request that data is no longer shared between
passengers contained in the same Order for privacy reasonspassengers contained in the same Order for privacy reasons
In this scenario, a party of 2 have an Order traveling on the same itinerary. Passenger 1 wishes to
stop sharing their personal information and itinerary with Passenger 2.
These guidelines address communication between Sellers and Airlines. How the airlineT hese guidelines address communication between Sellers and Airlines. How the airline
manages the Order record in their Order Management System and subsequently anymanages the Order record in their Order Management System and subsequently any
impact on reservations and accountable documents is for an Airline to determine as part ofimpact on reservations and accountable documents is for an Airline to determine as part of
their own implementation.their own implementation.
Note: The assumption is that the Seller has fully authenticated the identity of the passenger(s)
making the request, and that the Airline is happy to trust that the Seller has done so.
01. Ability for a seller to request whether or not there is an impact on the pricing of01. Ability for a seller to request whether or not there is an impact on the pricing of
an Order, where a subset of passengers no longer wish to share their data withan Order, where a subset of passengers no longer wish to share their data with
others in the same Orderothers in the same Order
The seller will generate an OrderReshopRQ specifying the passengers that no longer wish to share
their data with others in the same Order.
02. Ability for an airline to provide offers for changes to a subset of passengers02. Ability for an airline to provide offers for changes to a subset of passengers
The airline will generate an OrderReshopRS, returning new Offers and OfferItems, one for the
passenger(s) who requested that their data was no longer shared, and the other for the passenger(s)
who did not make the request. This will advise the Seller whether or not there is an impact on the
pricing of the Order.
03. Ability for a seller to request an Order change to a subset of passengers03. Ability for a seller to request an Order change to a subset of passengers
Assuming there is no impact on the pricing of the Order, the Seller will generate an OrderReshopRQ
specifying the passengers that no longer wish to share their data with others in the same Order.
Page: 152 of 377
04. Ability for an airline to respond to an Order change04. Ability for an airline to respond to an Order change
An airline will generate an OrderViewRS, returning all the data related to the two Orders, one Order
for the passenger(s) who requested that their data is no longer shared, and the other for the
passenger(s) that did not make the request.
Page: 153 of 377
During the delivery of flight and ancillary Services, it is key that the eligibility of a passenger for a
particular Service is always up to date, as well as the status of those Services. A number of messages
are used for the interactions between the Airline OMS
and the Delivery Provider, and Services can have a number of different statuses.
Service Delivery message flow:Service Delivery message flow:
IntroductionIntroduction
Page: 154 of 377
The delivery preparation process ensures that the Delivery Provider has all necessary information to
proceed with delivery of the required Services.
Delivery Preparation:Delivery Preparation:
Service delivery is commenced by a Service Delivery Notification message from the Airline OMS to the
Delivery Provider, or a Service Delivery Request from the Delivery Provider to the Airline. In both
cases, the Delivery Provider will then initiate Service delivery, which in turn will update the status of
each Service to be delivered.
Prepare Delivery – Service Delivery Notification:Prepare Delivery – Service Delivery Notification:
Prepare Delivery - Service Delivery Request:Prepare Delivery - Service Delivery Request:
Delivery PreparationDelivery Preparation
NoteNote
The AcknowlegmentRS message is expected as the response to any notification request message. This applies
to the ServiceDeliveryNotifRQ and ServiceDeliveryRQ mentioned in this section.
Page: 155 of 377
The outcome of this set of interactions should be that the Services are ready to be delivered (status
“READY TO DELIVER”). In case Services are not able to be delivered for any reason, Services may
be updated with a different status to indicate this. The possible statuses to be used are defined in the
"Definitions" section.
Note that since there are no changes that are relevant from a financial or accounting point of view,
there is no interaction between the Airline’s OMS and the Accounting System. If any Service should
not be able to be delivered, any interactions such as refunds would be triggered by a change to the
Order items, which would in turn trigger an update to the Accounting System.
Page: 156 of 377
During delivery of Services, the Delivery Provider needs to ensure that the delivery status is kept up to
date. Any interruptions to Service delivery must be reported to the Airline’s Order Management
System.
Service Delivery:Service Delivery:
Service Delivery:Service Delivery:
During Service delivery, the Service may have the following delivery statuses. For a complete
overview of Service delivery status transitions, see the “Service” section.
Typical Service Delivery State Transition:Typical Service Delivery State Transition:
If the Service delivery is interrupted in any way, the Airline Order Management System can be notified
of any changes using the same message flows. Similarly, any “milestone” events related to the
delivery of the Service may also be communicated using the same flow, for instance to record that the
passenger is at the airport, airside, at the lounge etc.
Service DeliveryService Delivery
NoteNote
The AcknowlegmentRS message is expected as the response to any notification request message. This applies
to the ServiceStatusChangeNotifRQ mentioned in this section.
Page: 157 of 377
During the delivery process, the Delivery Provider may also need to retrieve information related to the
Service. If this is necessary, the flow described in section “Delivery Preparation” can be used.
Page: 158 of 377
During the delivery process, information related to the delivery of the Service may be collected from
the passenger or generated by the Delivery Provider’s systems. This may include additional
passenger data such as passport or visa information collected, or baggage tag numbers generated
when luggage is checked in. Since the “Service Status Change Notification” request is only intended
to be used for updating the status of a Service, for such cases the “Update Service Notification”
request is used to update the Airline’s Order Management System. For such updates, no interaction
with the Accounting System is necessary. Cases such as the purchase of additional baggage at
check-in would trigger updates to Orders, which would in turn trigger updates to the Airline’s
Accounting System once payment has been taken. Delivery processes would then relay this update to
the Delivery Provider (see “Service Delivery RQ/RS” and “Service Delivery Notification RQ/RS”).
Update Service details with UpdateServiceNotification:Update Service details with UpdateServiceNotification:
Update of Services During DeliveryUpdate of Services During Delivery
NoteNote
The AcknowlegmentRS message is expected as the response to any notification request message. This applies
to the UpdateServiceNotifRQ mentioned in this section.
Page: 159 of 377
During the Order and Delivery processes, it is important that all relevant changes are communicated
to the Airline’s Accounting System. This allows the necessary accounting transactions to be initiated.
However, the Accounting System only needs to be informed when a financial commitment has been
made and the Airline has a liability for providing a Service. This happens when payment has been
received for items within an Order.
Interaction OMS to Accounting:Interaction OMS to Accounting:
IntroductionIntroduction
Page: 160 of 377
During the process of Order creation, the Airline Accounting System only needs to be informed when a
financial liability has been incurred. This happens when payment has been taken, and the Airline is
liable for delivering a Service for which it has received funds. To inform the Airline Accounting System,
the Airline OMS uses the Order Sales Notification Message (“OSIN”) message.
In cases where payment is not immediate, there is an Order created but no interaction between the
OMS and the Airline’s Accounting System. The interaction to the Accounting System only takes place
when the payment is taken, since prior to this point there has been no financial commitment.
Initial Order Notification to Accounting:Initial Order Notification to Accounting:
New Order CreationNew Order Creation
NoteNote
The AcknowlegmentRS message is expected as the response to any notification request message.This applies
to the OrderSalesInformationNotifRQ mentioned in this section.
Page: 161 of 377
As Services are consumed during the delivery process, the final delivery status (see section “Service”)
is reflected back to the Airline OMS by the Delivery Provider. This in turn triggers an update to the
Airline’s Accounting System.
Notify Final Service Status to Accounting:Notify Final Service Status to Accounting:
Service ConsumptionService Consumption
NoteNote
The AcknowlegmentRS message is expected as the response to any notification request message.This applies
to the ServiceStatusChangeNotifRQ mentioned in this section.
Page: 162 of 377
When all Services in an Order have been delivered (or not, depending on Service delivery), the
Airline’s Order Management System should notify the Accounting System that no further updates are
to be expected and the Order is closed. Note that Order closing is optional, since typically accounting
processes are triggered as individual Services are delivered.
Order ClosingOrder Closing
Page: 163 of 377
Inform Seller of Net Clearance DataInform Seller of Net Clearance Data
DescriptionDescription
The Airline (ORA) is able to inform the Seller of the Net
Amount that will be cleared at the time of settlement.
PreconditionsPreconditions
There must be an agreement for a sale between the
Customer and the Seller.
ProcessProcess
The Seller is able to follow their accounting process having
received the net clearance amount information
SuccessSuccess The Seller is informed of the net clearance
FailureFailure N/A
Inform Seller of Net Clearance DataInform Seller of Net Clearance Data
Page: 164 of 377
Inform Airline of Payment information including Net Clearance AmountInform Airline of Payment information including Net Clearance Amount
DescriptionDescription
The Seller provides the payment amount and based on
that the Seller includes the Net Clearance Amount which is
the amount to be settle between the two parties.
PreconditionsPreconditions
There must be an agreement for a sale between the
Customer and the Seller.
ProcessProcess
The Airline is able to compute the Net Clearance Amount
and this Amount is transmitted to the Settlement Manager
who will perform the clearance.
SuccessSuccess
The Settlement Manager has received the correct amount
to be cleared.
FailureFailure N/A
Inform Airline of Payment Information Including NetInform Airline of Payment Information Including Net
Clearance AmountClearance Amount
Page: 165 of 377
Build Upsell Offers based on Origin, Destination and defined datesBuild Upsell Offers based on Origin, Destination and defined dates
DescriptionDescription
This function allows the Airline to build additional upsell Offers that relate to
Origin, Destination and defined dates which may enhance the customer
experience. The content of the resulting Offers may depend on additional
qualifiers and context that may be provided by the Seller.
PreconditionsPreconditions
Seller knows the customer’s wished Origins, Destinations and dates
Seller may have additional qualifiers and context (e.g. PTC, service
criteria).
ProcessProcess
Seller transmits Origins, Destinations, dates, additional qualifiers and
context to the Airline
The Airline’s Offer Management System creates upsell Offers based on
the Origins, Destinations, dates and additional qualifiers and context
The Airline returns the upsell Offers to the Seller.
SuccessSuccess
Seller is in possession of upsell Offers that relate to a baseline Offer.
FailureFailure
The Airline is not able to answer to the request and no upsell Offer are
returned.
Build Upsell Offers based on Origin, Destination and definedBuild Upsell Offers based on Origin, Destination and defined
datesdates
Page: 166 of 377
Build Upsell Offer(s) based on the content of other Offer(s)Build Upsell Offer(s) based on the content of other Offer(s)
DescriptionDescription
This function allows the Airline to build additional Offers that relate to a baseline
Offer which may enhance the customer experience.
PreconditionsPreconditions
An Offer exists in the Airline’s Offer Management System (which implies
that the Offer Expiration Time Limit has not expired)
Seller knows the OfferID(s).
ProcessProcess
Seller transmits OfferID(s)
The Airline’s Offer Management System creates new Offer(s) based on
the existing Offer(s) which may contain additional services that may
enhance the customer experience
The Airline returns the upsell Offer(s) to the Seller.
SuccessSuccess
Seller is in possession of upsell Offer(s) that relate to a baseline Offer.
FailureFailure
The Airline is not able to answer to the request and no upsell Offers are
returned.
Build Upsell Offer(s) based on the content of other Offer(s)Build Upsell Offer(s) based on the content of other Offer(s)
Page: 167 of 377
Accept Repriced Offer(s)Accept Repriced Offer(s)
DescriptionDescription
This function allows the Seller to accept the new prices that were returned by the
Airline and which will be reflected in the Order after it is updated.
PreconditionsPreconditions
Seller has an Order ID
Seller has a Repriced Offer and knows the Response ID.
ProcessProcess
Seller sends the Shopping Response Ref ID and the Order ID
Airline deletes old Order Items and creates new Order Items with updated
prices from the Repriced Offer.
SuccessSuccess
Order is updated.
FailureFailure
General error.
Accept Repriced Offer(s)Accept Repriced Offer(s)
Page: 168 of 377
Request a la carte Offer(s) for ancillary services based on an existing Offer or OrderRequest a la carte Offer(s) for ancillary services based on an existing Offer or Order
DescriptionDescription
This function allows the Seller to request for an a la carte Offer for ancillary
services based on an existing Offer or Order. If the Seller has included additional
qualifiers or preferences, the a la carte Offer generated by the airline may take
this into consideration.
PreconditionsPreconditions
There is an existing Offer or Order
The Seller knows the OfferID or OrderID
Seller may have additional qualifiers and context (e.g. passenger data
such as Frequent Flyer number, payment criteria).
ProcessProcess
Seller tells the airline for which Offer or Order they would like ancillary
services returned. Seller could send additional qualifiers and context to
the Airline
Airline validates the request (message) for minimum information required
by that airline
Airline generates a new a la carte Offer, which may consider the Seller’s
specific request for ancillaries
Airline responds to Seller.
SuccessSuccess
Seller has an a la carte Offer for ancillaries that takes into consideration
additional qualifiers and context.
FailureFailure
No a la carte Offer is returned.
Request a la carte Offer(s) for ancillary services based on anRequest a la carte Offer(s) for ancillary services based on an
existing Offer or Orderexisting Offer or Order
Page: 169 of 377
Request a new Offer based on the content of an existing Offer and on additionalRequest a new Offer based on the content of an existing Offer and on additional
qualifiers and contextqualifiers and context
DescriptionDescription
This function allows the Seller to pass additional information (e.g. Frequent Flyer
Info, Form of Payment, etc.) so that an Airline can create a new contextualised
Offer.
PreconditionsPreconditions
An Offer exists in the Airline’s Offer Management System (which implies
that the Offer Expiration Time Limit has not expired)
Seller knows the OfferID
Seller has additional qualifiers and context (e.g. passenger data such as
Frequent Flyer number, payment criteria).
ProcessProcess
Seller transmits an OfferID, and additional qualifiers and context to the
Airline
The Airline’s Offer Management System creates a new Offer based on the
existing Offer plus the addition of other information
The Airline returns the new Offer to the Seller.
SuccessSuccess
Seller is in possession of an Offer that takes into consideration additional
qualifiers and context.
FailureFailure
The Airline is not able to answer to the request and an error is returned.
Request a new Offer based on the content of an existingRequest a new Offer based on the content of an existing
Offer and on additional qualifiers and contextOffer and on additional qualifiers and context
Page: 170 of 377
Request a new Reshop Offer based on the content of an existing Reshop Offer and onRequest a new Reshop Offer based on the content of an existing Reshop Offer and on
additional qualifiers and contextadditional qualifiers and context
DescriptionDescription
This function allows the Seller to pass additional information (e.g. Frequent Flyer
Info, Form of Payment, etc.) so that an Airline can create a new contextualised
Reshop Offer.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System
Seller knows the OrderID and Order Item ID(s) being replaced (optionally,
Seller has ServiceID(s) for the Services that the customer wants to keep)
A Reshop Offer exists in the Airline’s Offer Management System
Seller knows the Reshop OfferID
Seller has additional qualifiers and context (e.g. passenger data such as
Frequent Flyer number, payment criteria).
ProcessProcess
Seller transmits the OrderID, OrderItemID(s) being replaced, Reshop
Offer ID and any additional qualifiers and context to the Airline
The Airline’s Offer Management System creates a new Reshop Offer
based on the existing Reshop Offer plus the addition of other information
The Airline returns the new Reshop Offer to the Seller.
SuccessSuccess
Seller is in possession of a Reshop Offer that takes into consideration
additional qualifiers and context.
FailureFailure
The Airline is not able to answer to the request and an error is returned.
Request a new Reshop Offer based on the content of anRequest a new Reshop Offer based on the content of an
existing Reshop Offer and on additional qualifiers andexisting Reshop Offer and on additional qualifiers and
contextcontext
Page: 171 of 377
Request a Seat Map and an a la carte Offer for seats based on an existing Offer orRequest a Seat Map and an a la carte Offer for seats based on an existing Offer or
OrderOrder
DescriptionDescription
This function allows the Seller to request a seat map and an a la carte Offer for
seats based on an existing Offer or Order. If the Seller has included additional
qualifiers or preferences, the a la carte Offer generated by the Airline may take
this into consideration.
PreconditionsPreconditions
There is an existing Offer or Order
The Seller knows the OfferID or OrderID
Seller has additional qualifiers and context (e.g. passenger data such as
Frequent Flyer number, payment criteria).
ProcessProcess
Seller tells the airline for which Offer or Order they would like seat map
returned. Seller could send additional qualifiers and context to the Airline
Airline validates the request (message) for minimum information required
by that airline
Airline generates a seat map and a new a la carte Offer, which may
consider the Seller’s specific request for seats
Airline responds to Seller.
SuccessSuccess
Seller has a seat map and an a la carte Offer for seats that takes into
consideration additional qualifiers and context.
FailureFailure
No seat map or a la carte Offer is returned
Request a Seat Map and an a la carte Offer for seats basedRequest a Seat Map and an a la carte Offer for seats based
on an existing Offer or Orderon an existing Offer or Order
Page: 172 of 377
Request a set of Offers based on Origin, Destination and defined datesRequest a set of Offers based on Origin, Destination and defined dates
DescriptionDescription
This function allows the Seller to request from an Airline a set of Offers based on
Origins, Destinations and defined dates. The Seller may provide additional
qualifiers and context for which the Airline may consider the content of the
resulting Offers.
PreconditionsPreconditions
Seller knows the customer’s wished Origins, Destinations and dates
Seller may have additional qualifiers and context (e.g. PTC, service
criteria).
ProcessProcess
Seller transmits Origins, Destinations, dates, additional qualifiers and
context to the Airline
The Airline’s Offer Management System builds a set of Offers which may
partially or fully match the requested criteria
The Airline returns to the Seller the set of built Offers.
SuccessSuccess
Seller is in possession of a set of Offers which may partially or fully match
the requested criteria.
FailureFailure
The Airline is not able to answer to the request and an error is returned.
Request a set of Offers based on Origin, Destination andRequest a set of Offers based on Origin, Destination and
defined datesdefined dates
Page: 173 of 377
Request a set of Reshop Offers based on Origin, Destination and/or defined dates asRequest a set of Reshop Offers based on Origin, Destination and/or defined dates as
replacement of specific Order Item(s)replacement of specific Order Item(s)
DescriptionDescription
This function allows the Seller to request a set of Offers as a replacement of
specific Order Item(s). The request considers new Origins, Destinations and/or
defined dates. The content of the resulting Reshop Offers may depend on
additional qualifiers and context that may be provided by the Seller.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System and the Seller
has the Order ID
Seller has OrderItemID(s) for the Order Items that will be impacted by the
projected change (optionally, Seller has ServiceID(s) for the Services that
the customer wants to keep)
Seller knows the customer’s new desired Origins, Destinations and/or
dates
Seller may have additional qualifiers and context (e.g. PTC, service
criteria).
ProcessProcess
Seller sends to the Airline the OrderID, impacted OrderItemIDs and
optionally any ServiceIDs to be kept, the new desired Origins,
Destinations and/or dates, and any additional qualifiers and context
Airline creates new Reshop Offers corresponding to the search criteria
and returns them to the Seller.
SuccessSuccess
Airline returns to the seller a set of Reshop Offers corresponding to the
requested modifications
The Reshop Offers returned can incur: Additional collection (case 13A),
Refund (case 13b), No additional collection or no refund .
FailureFailure
The Airline is not able to answer to the request and an error is returned.
Request a set of Reshop Offers based on Origin,Request a set of Reshop Offers based on Origin,
Destination and/or defined dates as replacement of specificDestination and/or defined dates as replacement of specific
Order Item(s)Order Item(s)
Page: 174 of 377
Request detailed information about an OfferRequest detailed information about an Offer
DescriptionDescription
This function allows the Seller to request detailed information about an Offer,
including all price breakdowns, terms & conditions, disclosure data, etc.
PreconditionsPreconditions
An Offer exists in the Airline’s Offer Management System (which implies
that the Offer Expiration Time Limit has not expired)
Seller knows the OfferID.
ProcessProcess
Seller transmits an OfferID to the Airline
The Airline returns detailed information about the Offer to the Seller,
including all price breakdowns, terms & conditions, disclosure data, etc.
SuccessSuccess
Seller is in possession of the detailed information about the Offer.
FailureFailure
The Airline is not able to provide details about the Order and an error is
returned.
Request detailed information about an OfferRequest detailed information about an Offer
Page: 175 of 377
Request detailed information about a Reshop OfferRequest detailed information about a Reshop Offer
DescriptionDescription
This function allows the Seller to request detailed information about a Reshop
Offer, including all price breakdowns, terms & conditions, disclosure data, etc.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System
Seller knows the OrderID and Order Item ID(s) being replaced (optionally,
Seller has ServiceID(s) for the Services that the customer wants to keep)
Reshop Offer exists in the Airline’s Offer Management System (which
implies that the Offer Expiration Time Limit has not expired)
Seller knows the Reshop OfferID(s).
ProcessProcess
Seller transmits the OrderID, OrderItemID(s) being replaced, Reshop
OfferID to the Airline
The Airline returns detailed information about the Reshop Offer to the
Seller, including all price breakdowns, terms & conditions, disclosure
data, etc.
SuccessSuccess
Seller is in possession of the detailed information about the Reshop Offer.
FailureFailure
The Airline is not able to provide details about the Reshop Offer and an
error is returned.
Request detailed information about a Reshop OfferRequest detailed information about a Reshop Offer
Page: 176 of 377
Select Offer(s) to add to a shopping basketSelect Offer(s) to add to a shopping basket
DescriptionDescription
This function allows the Seller to select Offer(s) and Offer Item(s) which they wish
to progress with. This allows the Airline to refine these Offer(s) and return a
single Offer.
PreconditionsPreconditions
Offer(s) exist in the Airline’s Offer Management System (which implies that
the Offer Expiration Time Limit has not expired)
Seller knows the OfferID(s)
Seller knows the OfferItemID(s) that the customer has selected.
ProcessProcess
Seller transmits OfferID(s) and a selection of OfferItemIDs to the Airline
The Airline returns to Seller a single Offer based on the context of the
selected Offer Item(s).
SuccessSuccess
Seller is in possession of an Offer which contains the selected Offer
Item(s).
FailureFailure
The Airline is not able to provide an Offer which contains the selected
Offer Item(s) and an error is returned.
Select Offer(s) to add to a shopping basketSelect Offer(s) to add to a shopping basket
Page: 177 of 377
Select Reshop Offer(s) to add to a shopping basketSelect Reshop Offer(s) to add to a shopping basket
DescriptionDescription
This function allows the Seller to select Reshop Offer(s) and Offer Item(s) which
they wish to progress with. This allows the Airline to refine these Offer(s) and
return a single Reshop Offer.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System
Seller knows the OrderID and OrderItemID(s) being replaced (optionally,
Seller has ServiceID(s) for the Services that the customer wants to keep)
Reshop Offer(s) exist in the Airline’s Offer Management System
Seller knows the Reshop OfferID(s)
Seller knows the OfferItemID(s) that the customer has selected.
ProcessProcess
Seller transmits the OrderID, Order Item ID(s) being replaced, Reshop
OfferID(s) and Offer Item ID(s) to the airline
The Airline returns to Seller a Reshop Offer based on the context of the
selected Offer Item(s).
SuccessSuccess
Seller is in possession of a Reshop Offer which contains the selected
Offer Item(s).
FailureFailure
The Airline is not able to provide a Reshop Offer which contains the
selected Offer Item(s) and an error is returned.
Select Reshop Offer(s) to add to a shopping basketSelect Reshop Offer(s) to add to a shopping basket
Page: 178 of 377
Acceptance of a Planned Schedule ChangeAcceptance of a Planned Schedule Change
DescriptionDescription
The Seller indicates to the Airline (ORA) that the Customer
is accepting the Planned Schedule Change.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
The Airline (ORA) has performed a Planned Schedule
Change.
The Airline has informed the Seller of a Planned Schedule
Change and the available follow up actions, including
Accept.
ProcessProcess
The Seller send the acceptance of the Planned Schedule
Change to the Airline (ORA)
SuccessSuccess
The Airline (ORA) updates the Order so that the passenger
can consume the Service.
FailureFailure
The Order/Services are still in a disruption mode and the
passenger cannot consume the Service.
Acceptance of a planned schedule changeAcceptance of a planned schedule change
Page: 179 of 377
Add payment information into an existing OrderAdd payment information into an existing Order
DescriptionDescription
This function allows the Seller to add payment information into an existing Order,
and optionally associate this payment information with Order Item(s).
PreconditionsPreconditions
Seller has an Order ID
Seller has Order Item IDs (optionally)
Seller has payment information.
ProcessProcess
Seller sends payment information
Airline updates Order with payment information.
SuccessSuccess
Order has payment information.
FailureFailure
Order does not have payment information.
Add payment information into an existing OrderAdd payment information into an existing Order
Page: 180 of 377
Add Payment Information as part of a New OrderAdd Payment Information as part of a New Order
DescriptionDescription This function allows the Seller to send payment information to the Airline.
DependancyDependancy Create Order
PreconditionsPreconditions
Seller has selected Offer ID(s)
Seller has selected Offer Item ID(s) (optionally)
Seller has Payment Information.
ProcessProcess
Seller sends Payment Information
Airline adds Payment Information to the Order.
SuccessSuccess
Order has payment information.
FailureFailure
Order does not have payment information.
Add Payment Information as part of a New OrderAdd Payment Information as part of a New Order
Page: 181 of 377
Create OrderCreate Order
DescriptionDescription
This function allows the Seller to request that an Airline creates an Order from a
selection of Offer(s) and Offer Item(s).
PreconditionsPreconditions
There is not a pre-existing Order in relation to this transaction
Seller has Offer(s) that are ready to be converted into an Order
Seller knows the selected Offer Item ID(s)
Seller has minimum required passenger data.
ProcessProcess
Seller passes to the Airline the selected Offer ID(s), Offer Item ID(s) and
passenger data
Airline validates the request (message) for minimum information required
by that Airline
Airline creates new Order Items from the selected Offer Items in the newly
created Order
Airline responds to Seller.
SuccessSuccess
Order is created, inventory is held, and an Order ID is returned.
FailureFailure
Order is not created, error returned
Order is partially created, warning returned.
Create OrderCreate Order
Page: 182 of 377
Cancel OrderCancel Order
DescriptionDescription This function allows the Seller to request cancellation of an existing Order.
PreconditionsPreconditions
There is an existing Order
The Seller knows the OrderID that it’s requesting to be cancelled.
ProcessProcess
Seller tells the Airline which Order it would like to be cancelled
Airline validates the request (message) for minimum information required
by that airline.
Airline cancels the requested Order
If applicable, airline processes actions on accountable documents
Airline responds to Seller.
SuccessSuccess
Airline has cancelled the requested Order and if applicable, updated
accountable documents.
FailureFailure
The order has not been cancelled and / or if applicable the airline has not
processed actions on accountable documents.
Cancel OrderCancel Order
Page: 183 of 377
Cancel Order Item(s) from an existing OrderCancel Order Item(s) from an existing Order
DescriptionDescription
This function allows the Seller to request cancellation of selected Order Item(s)
from an existing Order.
PreconditionsPreconditions
There is an existing Order
The Seller knows the OrderID and the selected Order Item ID(s) that it’s
requesting to be cancelled.
ProcessProcess
Seller tells the Airline which Order Item(s) it would like to be cancelled
from an existing Order
Airline validates the request (message) for minimum information required
by that airline
Airline cancels the requested Order Item(s) from the existing Order
Airline responds to Seller.
SuccessSuccess
Airline has cancelled the requested Order Item(s) from the existing Order.
FailureFailure
No Order Items have been cancelled from the existing Order
Only some Order Items have been cancelled from the existing Order.
Cancel Order Item(s) from an existing OrderCancel Order Item(s) from an existing Order
Page: 184 of 377
Cancellation following a planned schedule changeCancellation following a planned schedule change
DescriptionDescription
The Seller indicates to the Airline (ORA) that the Customer is intending to
cancel the order.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management System
The Airline (ORA) has performed a Planned Schedule Change.
The Airline has informed the Seller of a Planned Schedule Change and the
available follow up actions, including Cancel.
ProcessProcess
The Seller sends the Cancellation request (including the FareWaiver Code if
this has been supplied by the Airline (ORA)); this may include option for
refund or respend at a later time.
SuccessSuccess
The Airline (ORA) validates the FareWaiver Code (if present)
The Airline (ORA) identifies that the Order has been disrupted.
Any reshop Offers are returned in accordance to the eligibility of the Airline’s
ORA Planned Schedule Change policy. (e.g. permitting the refund/respend
without a penalty)
FailureFailure
The Airline (ORA) fails to validate the FareWaiver Code (if present).
The Airline (ORA) does not identify that the Order has been disrupted.
Cancellation following a Planned Schedule ChangeCancellation following a Planned Schedule Change
Page: 185 of 377
Commit to the Terms of the OrderCommit to the Terms of the Order
DescriptionDescription
This function allows the Seller to notify the Airline that they are ready to accept
the Terms of the Order / Order Item(s).
PreconditionsPreconditions
Seller has an Order ID
Seller has the Order Item IDs that they are willing to commit
Airline has payment information.
ProcessProcess
Seller sends the commit request
Airline commits the Order
Airline returns confirmation of commitment (represented in multiple ways:
doc data, delivery status, payment status, etc.)
SuccessSuccess
The selected Order / Order Item(s) are committed.
FailureFailure
The selected Order / Order Item(s) are not committed
Only some of the selected Order Item(s) are committed.
Commit to the Terms of the OrderCommit to the Terms of the Order
Page: 186 of 377
Commit to the Terms of the Offer during ‘Create Order ’Commit to the Terms of the Offer during ‘Create Order ’
DescriptionDescription
This function allows the Seller to notify the Airline that they are ready to accept
the Terms of the Offer / Offer Item(s).
DependancyDependancy Create Order
PreconditionsPreconditions
Seller has selected Offer ID(s)
Seller has the Offer Item ID’s that they are willing to commit
Airline has payment information.
ProcessProcess
Seller sends the commit request
Airline commits the resulting Order Items in the Order being created
Airline returns confirmation of commitment (represented in multiple ways:
doc data, delivery status, payment status, etc.).
SuccessSuccess
The resulting Order / Order Item(s) are committed.
FailureFailure
The resulting Order / Order Item(s) are not committed
Only some of the resulting Order Item(s) are committed.
Commit to the Terms of the Offer during ‘Create Order’Commit to the Terms of the Offer during ‘Create Order’
Page: 187 of 377
Commit to selected accepted reshop/delete Offer(s), confirm contactCommit to selected accepted reshop/delete Offer(s), confirm contact
details and preferencesdetails and preferences
DescriptionDescription
This business capability covers following functionalities
mentioned in the message flow discussions. Several
functions can be triggered through a single commitment
(e.g. a change may invoke a cancellation of an item):
- Function: “Request Offer Item(s) to be added to an
existing Order”,
o To allow the Seller to request that Offer Item(s) be
converted into Order Item(s) within an existing Order
- Function: “Cancel Order Item(s) from an existing
Order”
o To allow the Seller to request cancellation of selected
Order Item(s) from an existing Order.
- Function: “Add payment information into an existing
Order”
o To allow the Seller to add payment information into an
existing Order, and optionally associate this payment
information with Order Item(s).
- Function: “Commit to the Terms of the Order”
o To allow the Seller to notify the Airline that they are
ready to accept the Terms of the Order / OrderItem(s).
This business capability also allows a seller to confirm
contact details of the customer at the time the servicing is
requested.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
Seller communicates intent to service partially or fully the
order
Airline (ORA) communicates some offers to the seller so
that passenger can select his servicing option.
ProcessProcess
When accepting a servicing offer the passenger may want
to provide or update his contact details so that the seller
can communicate them to the airline (ORA)
SuccessSuccess
The airline (ORA) receives passenger contact details from
the seller and update the order accordingly for subsequent
notifications
FailureFailure
The airline (ORA) does not receive passenger contact
details from the seller
Commit to selected accepted reshop/delete Offer(s), confirmCommit to selected accepted reshop/delete Offer(s), confirm
contact details and preferencescontact details and preferences
Page: 188 of 377
Confirm the price of the Order Item(s)Confirm the price of the Order Item(s)
DescriptionDescription
This function allows the Seller to request that an Airline quotes and confirms the
price of unpaid Order Item(s).
PreconditionsPreconditions
Seller has an Order ID
Seller has Order Item ID(s) that it wants to be priced (optionally)
The Price Guarantee Time Limit has expired.
ProcessProcess
Seller sends to the Airline the Order ID and optionally the Order Item ID(s)
to be priced, including any dependent Order Item(s)
Airline prices the Order Item(s) in the context of an Order.
SuccessSuccess
Prices in the Order still valid
There is a Repriced Offer.
FailureFailure
General error.
Confirm the price of the Order Item(s)Confirm the price of the Order Item(s)
Page: 189 of 377
Inform Seller of passenger name and/or contact details changesInform Seller of passenger name and/or contact details changes
DescriptionDescription
The Seller is notified of any Contact details and Name
change
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The passenger has changed the contact details
and/or name directly with the Airline (ORA)
ProcessProcess
Airline (ORA) communicates changes to the Seller’s
endpoint
SuccessSuccess Seller is informed of changes via OrderChangeNotifRQ
FailureFailure No OrderChangeNotifRQ sent to the Seller’s endpoint
Inform Seller of Passenger name and/or contact detailsInform Seller of Passenger name and/or contact details
changeschanges
Page: 190 of 377
Inform seller of payment status changesInform seller of payment status changes
DescriptionDescription
The Seller is notified of any payment status change, so the
traveler can be notified.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) changed the payment status
ProcessProcess
Airline (ORA) communicates changes to the Seller’s
endpoint
SuccessSuccess Seller is informed of changes via OrderChangeNotifRQ
FailureFailure No OrderChangeNotifRQ sent to the Seller’s endpoint
Inform Seller of Payment status changesInform Seller of Payment status changes
Page: 191 of 377
Inform seller of flight segment time changes (Schedule Change)Inform seller of flight segment time changes (Schedule Change)
DescriptionDescription
The Seller is notified of any flight time changes, so the
traveler can be notified.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) performs a schedule change to
update the flight time
ProcessProcess
Seller receives changes from the Airline (ORA)
o Seller receives Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, ReasonCode
(REA), ChangeTypeCode, and Fare Waiver (if applicable)
from Airline (ORA)
SuccessSuccess
Seller is informed of changes via OrderChangeNotifRQ
o The OrderChangeNotifRQ contains Airline URI,
SellerFollowUpIndicator, ActionTimeLimit,
ConsequenceOfInaction, REA, ChangeTypeCode, and
Fare Waiver (if applicable) to Seller’s endpoint
Any OrderViewRS returns or includes
o The Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, REA,
ChangeTypeCode, and Fare Waiver (if applicable)
FailureFailure
No OrderChangeNotifRQ sent to the Seller’s endpoint
OrderChangeNotifRQ sent to the Seller’s endpoint without
SellerFollowUpIndicator, ActionTimeLimit, REA,
ChangeTypeCode, and ConsequenceOfInaction (when
applicable)
Inform seller of flight segment time changes Inform seller of flight segment time changes (Schedule(Schedule
Change)Change)
Page: 192 of 377
Inform seller of flight number changes (schedule change)Inform seller of flight number changes (schedule change)
DescriptionDescription
The Seller is informed of any flight number changes, so the
traveler can be notified.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) performs a schedule change to
update the flight number
ProcessProcess
Seller receives changes from the Airline (ORA)
o Seller receives Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, ReasonCode
(REA), ChangeTypeCode, and Fare Waiver (if applicable)
from Airline (ORA)
SuccessSuccess
Seller is informed of changes via OrderChangeNotifRQ
o The OrderChangeNotifRQ contains Airline URI,
SellerFollowUpIndicator, ActionTimeLimit,
ConsequenceOfInaction, REA, ChangeTypeCode, and
Fare Waiver (if applicable) to Seller’s endpoint
Any OrderViewRS returns or includes
o The Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, REA,
ChangeTypeCode, and Fare Waiver (if applicable)
FailureFailure
No OrderChangeNotifRQ sent to the Seller’s endpoint
OrderChangeNotifRQ sent to the Seller’s endpoint without
SellerFollowUpIndicator, ActionTimeLimit, REA,
ChangeTypeCode, and ConsequenceOfInaction (when
applicable)
Inform Seller of flight number changes (Schedule Change)Inform Seller of flight number changes (Schedule Change)
Page: 193 of 377
Inform Seller of flight arrival and/or departure changesInform Seller of flight arrival and/or departure changes
DescriptionDescription
The Seller is notified of any arrival and/or departure
changes
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) changed the arrival and/or
departure details
ProcessProcess
Seller receives changes from the Airline (ORA)
o Seller receives Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, ReasonCode
(REA), ChangeTypeCode, and Fare Waiver (if applicable)
from Airline (ORA)
SuccessSuccess
Seller is informed of changes via OrderChangeNotifRQ
o The OrderChangeNotifRQ contains Airline URI,
SellerFollowUpIndicator, ActionTimeLimit,
ConsequenceOfInaction, REA, ChangeTypeCode, and
Fare Waiver (if applicable) to Seller’s endpoint
Any OrderViewRS returns or includes
o The Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, REA,
ChangeTypeCode, and Fare Waiver (if applicable)
FailureFailure
No OrderChangeNotifRQ sent to the Seller’s endpoint
OrderChangeNotifRQ sent to the Seller’s endpoint without
SellerFollowUpIndicator, ActionTimeLimit, REA,
ChangeTypeCode, and ConsequenceOfInaction (when
applicable)
Inform seller of flight arrival and/or departure changesInform seller of flight arrival and/or departure changes
(Schedule Changes)(Schedule Changes)
Page: 194 of 377
Inform Seller of flight equipment changes (Schedule Change)Inform Seller of flight equipment changes (Schedule Change)
DescriptionDescription The Seller is notified of any equipment changes
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) changed the equipment type
ProcessProcess
Seller receives changes from the Airline (ORA)
o Seller receives Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, ReasonCode
(REA), ChangeTypeCode, and Fare Waiver (if applicable)
from Airline (ORA)
SuccessSuccess
Seller is informed of changes via OrderChangeNotifRQ
o The OrderChangeNotifRQ contains Airline URI,
SellerFollowUpIndicator, ActionTimeLimit,
ConsequenceOfInaction, REA, ChangeTypeCode, and
Fare Waiver (if applicable) to Seller’s endpoint
Any OrderViewRS returns or includes
o The Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, REA,
ChangeTypeCode, and Fare Waiver (if applicable)
FailureFailure
No OrderChangeNotifRQ sent to the Seller’s endpoint
OrderChangeNotifRQ sent to the Seller’s endpoint without
SellerFollowUpIndicator, ActionTimeLimit, REA,
ChangeTypeCode, and ConsequenceOfInaction (when
applicable)
Inform Seller of flight equipment changes (ScheduleInform Seller of flight equipment changes (Schedule
Change)Change)
Page: 195 of 377
Inform seller of flight cancellation (Schedule Change)Inform seller of flight cancellation (Schedule Change)
DescriptionDescription The Seller is notified of any flight cancellation
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) cancelled flight without
passenger reaccommodation
ProcessProcess
Seller receives changes from the Airline (ORA)
o Seller receives Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, ReasonCode
(REA), ChangeTypeCode, and Fare Waiver (if applicable)
from Airline (ORA)
SuccessSuccess
Seller is informed of changes via OrderChangeNotifRQ
o The OrderChangeNotifRQ contains Airline URI,
SellerFollowUpIndicator, ActionTimeLimit,
ConsequenceOfInaction, REA, ChangeTypeCode, and
Fare Waiver (if applicable) to Seller’s endpoint
Any OrderViewRS returns or includes
o The Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, REA,
ChangeTypeCode, and Fare Waiver (if applicable)
FailureFailure
No OrderChangeNotifRQ sent to the Seller’s endpoint
OrderChangeNotifRQ sent to the Seller’s endpoint without
SellerFollowUpIndicator, ActionTimeLimit, REA,
ChangeTypeCode, and ConsequenceOfInaction (when
applicable)
Inform Seller of flight cancellation (Schedule Change)Inform Seller of flight cancellation (Schedule Change)
Page: 196 of 377
Inform seller of flight changes (Schedule Change)Inform seller of flight changes (Schedule Change)
DescriptionDescription The Seller is notified of any flight changes
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The Airline (ORA) makes changes to the flight
details
ProcessProcess
Seller receives changes from the Airline (ORA)
o Seller receives Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, ReasonCode
(REA), ChangeTypeCode, and Fare Waiver (if applicable)
from Airline (ORA)
SuccessSuccess
Seller is informed of changes via OrderChangeNotifRQ
o The OrderChangeNotifRQ contains Airline URI,
SellerFollowUpIndicator, ActionTimeLimit,
ConsequenceOfInaction, REA, ChangeTypeCode, and
Fare Waiver (if applicable) to Seller’s endpoint
Any OrderViewRS returns or includes
o The Airline URI, SellerFollowUpIndicator,
ActionTimeLimit, ConsequenceOfInaction, REA,
ChangeTypeCode, and Fare Waiver (if applicable)
FailureFailure
No OrderChangeNotifRQ sent to the Seller’s endpoint
OrderChangeNotifRQ sent to the Seller’s endpoint without
SellerFollowUpIndicator, ActionTimeLimit, REA,
ChangeTypeCode, and ConsequenceOfInaction (when
applicable)
Inform seller of flight changes (Schedule Change)Inform seller of flight changes (Schedule Change)
Page: 197 of 377
Inform seller of Planned Schedule Change and any required follow upInform seller of Planned Schedule Change and any required follow up
actionsactions
DescriptionDescription
The Seller is informed whether Acceptance from the
customer is needed after being notified of a Planned
Schedule Change
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
The Airline (ORA) has performed a Planned Schedule
Change.
ProcessProcess
Airline (ORA) Order Management System identifies the
Order has been involuntarily changed and that the Seller
has not yet “accepted” the changes.
Airline (ORA) Order Management System identifies a set of
follow up actions available for the Passenger to act upon
(Accept, Reshop, Cancel, Call Airline – with possible URL)
Airline (ORA) Order Management System identifies if there
is a time limit for the follow up action to be complete and
the consequence if not acted upon within the time limit.
E.g. Auto-acceptance by airline or Auto-cancellation by
airline
SuccessSuccess
OrderViewRS returns the SellerFollowUpIndicator with a
true value and relevant SellerFollowUpAction, and
ActionTimeLimit after a Planned Schedule Change and is
able to service the customer.
FailureFailure
OrderViewRS does not returns the SellerFollowUpIndicator
nor SellerFollowUpAction, ActionTimeLimit after a
Planned Schedule Change
Inform seller of planned schedule change and any requiredInform seller of planned schedule change and any required
follow up actionsfollow up actions
Page: 198 of 377
Inform Seller that request is extended to dependent Order Item(s)Inform Seller that request is extended to dependent Order Item(s)
DescriptionDescription
This function allows the Airline to inform when the list of
selected OrderItem(s) to be serviced (cancelled or
changed) was extended to include dependent items.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
Seller communicates intent to service part of the order,
providing the selection of OrderItems to be cancelled or
changed.
ProcessProcess
Airline (ORA) validates request for partial changes against
Passenger’s services selection.
SuccessSuccess
OrderReshopRS informs passenger that new offer
includes other services than the originally selected at
OrderReshopRQ
FailureFailure
OrderReshopRS fails to inform passenger that new offer
includes other Services (other than the originally selected
Service at OrderReshopRQ)
Inform Seller that request is extended to dependent OrderInform Seller that request is extended to dependent Order
Item(s)Item(s)
Page: 199 of 377
Inform Seller about differential typeInform Seller about differential type
DescriptionDescription
For each Offer Item, this function allows the Airline to
inform the Seller about amount differential type if this Offer
Item is chosen.
This indicator should be used for both cancellation and
change scenarios.
Several types of action are possible when the customer
selects a reshopped Offer.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
Seller communicates intent to service partially or fully the
order.
Servicing the order results in financial liability scenarios,
based on amount differentials.
Inform Seller about differential typeInform Seller about differential type
Page: 200 of 377
ProcessProcess
Airline (ORA) defines the financial liability scenario based
on the amount differentials that can be:
o AddCol” – the change will result into a new payment
from the customer (applies to change scenarios)
For this use case, the Airline should inform Seller about
amount details and the usual payment instructions
o Refund” - the change will result into a customer refund
(applies to cancellations and change scenarios)
For this use case, the airline should inform seller about the
action that will take place for payment: void if capture was
not yet triggered, refund if money is already captured by
the airline.
o Residual” - the change will result into a determined
amount kept by airline for future use (applies to
cancellations and change scenarios)
For this use case, the amount kept by the airline is
determined at this moment and can be communicated to
the seller
o Reusable” – the financial result of the change will be
determined when customer comes back to select new
journey options (applies to change scenarios when
customer does not yet know how to reuse the money)
For this use case, the amount that the agent can reuse
may not be known at this moment. It may be determined at
a later stage, when the customer chooses new travel
options. As a consequence, the airline should be able to
pass to the Seller a reusable amount indicator even if no
amount is communicated at this stage.
o EvenExchange” – the change does not have any
financial impact to the customer (applies to change
scenarios)
Amount differentials details may have to be present in case
the breakdown of the base, taxes, etc… differ but the total
remains the same.
o AddColAndRefund” – the change will result into both a
new payment from the customer and a customer refund
(applies to cancellation and change scenarios)
This use case is a combo of “AddCol” & “Refund” use
cases
o AddColAndResidual” – the change will result into both a
new payment from the customer and a determined amount
kept by airline for future use (applies to cancellation and
change scenarios)
o This use case is a combo of “AddCol” & “Residual” use
cases
SuccessSuccess
OrderReshopRS includes DiffentialType in any price
differential structure
Page: 201 of 377
FailureFailure
OrderReshopRS does not includes DiffentialType in any
price differential structure
Page: 202 of 377
Inform Seller about what will happen to an existing Service should theInform Seller about what will happen to an existing Service should the
Seller accept a reshopped Offer ItemSeller accept a reshopped Offer Item
DescriptionDescription
As a seller, when investigating servicing options for a given
Order Item, I need to know if an existing service will remain
untouched or will be cancelled should I accept this newly
reshopped Offer Item.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
Seller communicates intent to service partially or fully the
order.
ProcessProcess
While defining new travel offers, some services are
untouched by the servicing request
When the airline (ORA) communicates new travel offers,
the seller needs to identify untouched items to inform
passenger.
SuccessSuccess
For each Service returned in an Offer Item, the
OrderReshopRS message explicitly indicates if the Service
is untouched using UnchangedInd
FailureFailure
The OrderReshopRS message does not indicate whether
a Service is untouched or impacted should the passenger
accepts the returned Offer Item
Inform Seller about what will happen to an existing ServiceInform Seller about what will happen to an existing Service
should the Seller accept a reshopped Offer Itemshould the Seller accept a reshopped Offer Item
Page: 203 of 377
Inform Seller if a penalty is netted or to be paidInform Seller if a penalty is netted or to be paid
DescriptionDescription
For each penalty involved in a voluntary servicing action,
the airline should inform the seller if the penalty is netted
(i.e. taken from any amount that the Airline will owe to the
customer consequently to the servicing) or to be paid (i.e.
charged to the customer upfront any servicing action, and
even if customer benefits from a subsequent refund/
residual value).
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
Seller communicates intent to service partially or fully the
order.
Servicing the order incurs in a penalty fee.
ProcessProcess
Airline (ORA) processes the reshop offers and identifies
when a penalty can be netted or paid.
SuccessSuccess
OrderReshopRS explicitly describes if each penalty fees
are netted or should be collected/paid by the passenger
FailureFailure
OrderReshopRS does not describe if each penalty fees
are netted or should be collected/paid by the passenger
Inform Seller if a penalty is netted or to be paidInform Seller if a penalty is netted or to be paid
Page: 204 of 377
Provide address at destinationProvide address at destination
DescriptionDescription
The Seller provides the address at destination to the
Airline (ORA) in the request messages at Order creation or
modification time.
PreconditionsPreconditions The address at destination needs to be captured.
ProcessProcess
The Seller provides the address at destination to the
Airline (ORA).
SuccessSuccess
The Airline has stored the address at destination in the
Order.
FailureFailure N/A
Provide address at destinationProvide address at destination
Page: 205 of 377
Provide emergency contact detailsProvide emergency contact details
DescriptionDescription
The Seller provides the emergency contact details to the
Airline (ORA) in the request messages at Order creation or
modification time.
PreconditionsPreconditions Emergency contact details needs to be captured.
ProcessProcess
The Seller provides the emergency contact details to the
Airline (ORA).
SuccessSuccess
The Airline has stored the emergency contact details in the
Order.
FailureFailure N/A
Provide emergency contact detailsProvide emergency contact details
Page: 206 of 377
Provide contact details for an unccompanied minorProvide contact details for an unccompanied minor
DescriptionDescription
The Seller provides the contact details for an
unaccompanied minor to the Airline (ORA) in the request
messages at Order creation or modification time.
PreconditionsPreconditions
Contact details need to be captured for unaccompanied
minor.
ProcessProcess
The Seller provides the contact details for an
unaccompanied minor to the Airline (ORA).
SuccessSuccess The Airline has stored the contact details in the Order
FailureFailure N/A
Provide contact details for unaccompanied minorProvide contact details for unaccompanied minor
Page: 207 of 377
Retrieve OrderRetrieve Order
DescriptionDescription This function allows the Seller to display the content of an Order.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System
The Seller knows the Order ID.
ProcessProcess
Seller requests to retrieve Order from the Airline
Airline responds with the Order Information.
SuccessSuccess
The Order Information is returned to the Seller.
FailureFailure
Order cannot be accessed by the Seller.
Retrieve OrderRetrieve Order
Page: 208 of 377
Reshop following a Planned Schedule ChangeReshop following a Planned Schedule Change
DescriptionDescription
The Seller indicates to the Airline (ORA) that the Customer is intending to
seek alternatives for the Planned Schedule Change.
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management System
The Airline (ORA) has performed a Planned Schedule Change.
The Airline has informed the Seller of a Planned Schedule Change and the
available follow up actions, including Reshop.
ProcessProcess
The Seller sends the Reshop request (including the FareWaiver Code if this
has been supplied by the Airline (ORA))
SuccessSuccess
The Airline (ORA) validates the FareWaiver Code (if present)
The Airline (ORA) identifies that the Order has been disrupted.
Any reshop Offers are returned in accordance to the eligibility of the Airline’s
ORA Planned Schedule Change policy. (e.g. not charging penalty fee or
fare difference)
FailureFailure
The Airline (ORA) fails to validate the FareWaiver Code (if present).
The Airline (ORA) does not identify that the Order has been disrupted.
Reshop following a Planned Schedule ChangeReshop following a Planned Schedule Change
Page: 209 of 377
Request refundable amount for existing Order Item(s)Request refundable amount for existing Order Item(s)
DescriptionDescription
This function allows the Seller to request the refundable amount for existing
Order Item(s) that the Customer wishes to cancel.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System
The Seller knows the Order ID
Seller has the Order Item ID(s) for the Order Items that the Customer
wishes to cancel.
ProcessProcess
Seller sends to the Airline the Order Item ID(s) to be cancelled from the
existing Order
Airline calculates refundable amount for each selected Order Item.
SuccessSuccess
Seller is in possession of a Reshop Offer containing the refundable
amounts for all selected Order Item(s).
FailureFailure
The Airline is not able to return a Reshop Offer and an error is returned
The Airline can return a Reshop Offer containing the refundable amounts
for only some of the selected Order Item(s).
Request refundable amount for existing Order Item(s)Request refundable amount for existing Order Item(s)
Page: 210 of 377
Request Offer Item(s) to be added to an existing OrderRequest Offer Item(s) to be added to an existing Order
DescriptionDescription
This function allows the Seller to request that Offer Item(s) be converted into
Order Item(s) within an existing Order.
PreconditionsPreconditions
An Order exists in the Airline’s Order Management System
Seller knows the OrderID
There are new Offer(s) containing Offer Items which the Seller wishes to
convert into Order Items in an existing Order.
ProcessProcess
Seller tells the airline which Offer Items they would like to convert into
Order Items in an existing Order
Airline validates the request (message) for minimum information required
by that airline
Airline creates new Order Items from the selected Offer Items in the
existing Order
Airline responds to Seller.
SuccessSuccess
Airline has added new Order Items in an existing Order that reflects the
Seller’s selected Offer Items.
FailureFailure
No Offer Items are converted into Order Items within the existing Order
Only some Offer Items are converted into Order Items within the existing
Order.
Request Offer Item(s) to be added to an existing OrderRequest Offer Item(s) to be added to an existing Order
Page: 211 of 377
Respond to reshop request with the details of the order modification orRespond to reshop request with the details of the order modification or
cancellation (partial or full)cancellation (partial or full)
DescriptionDescription
Re-shopping response returned by the Airline including the
information for the Customer to understand the impacts of
the Order Modification or Cancellation (partial or full)
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
The Seller has initiated an Order Modification or
Cancellation (partial or full)
ProcessProcess
Airline (ORA) responds to the reshopping request with
eligible offers including:
o Old Price
o New Price
o Penalty if applicable (including the net indicator)
o Differential Price
o Pricing at passenger level
o The Reusable indicator (at Order Item level)
o Unchanged indicator (at Service level)
o The Void indicator (at Order Item level)
SuccessSuccess
Seller has received the eligible offer with the details for the
customer to make an informed decision on the next step
(e.g acceptance of the reshop offer)
FailureFailure N/A
Respond to reshop request with the details of the orderRespond to reshop request with the details of the order
modification or cancellation (partial or full)modification or cancellation (partial or full)
Page: 212 of 377
Request full or partial Order cancellation; Airline (ORA) retains Order forRequest full or partial Order cancellation; Airline (ORA) retains Order for
future Reshop requestfuture Reshop request
DescriptionDescription
The Seller can request to partially or fully cancel an Order
and to keep the Order available for future reshop. The
passenger will return at a future point to request for refund
or reshop for new Service(s) - at which time, any financial
impact will be determined in the subsequent reshop flow
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
The Order is purchased
There is one or more available services
ProcessProcess
Seller communicates cancellation request to the Airline
(ORA), indicating the passenger will return at a future point
to request refund or new services
Airline (ORA) knows there is value to be kept for future
reshop (re-spend or refund)
SuccessSuccess
OrderReshopRS Offers are returned with “reusable
indicator” (refer to business function “Inform Seller about
differential type”)
FailureFailure
No Offers with “reusable indicator” is returned at
OrderReshopRS
Request full or partial Order cancellation; Airline (ORA)Request full or partial Order cancellation; Airline (ORA)
retains Order for future Reshop requestretains Order for future Reshop request
Page: 213 of 377
Report penalty to Airline AccountingReport penalty to Airline Accounting
DescriptionDescription
The Airline is conveying the penalty information in the
OSIN/OSIADN to Airline’s Accounting System
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The passenger has changed the Order that
resulted in collection of at least one penalty amount
ProcessProcess
Airline communicates netted penalty information to Airline’s
Accounting System
Airline communicates non-netted penalty information to
Airline’s Accounting System
SuccessSuccess
Airline’s Accounting System is informed of the penalty
information resulting from the change in the Order
FailureFailure
OSIN/OSIADN message does not contain penalty
information where at least one penalty amount is collected
as a result of changing the Order
Airline’s Accounting system is not informed of the penalty
information provided in the OSIN/OSIADN
Report penalty to Airline AccountingReport penalty to Airline Accounting
Page: 214 of 377
Report refundable amounts to Airline AccountingReport refundable amounts to Airline Accounting
DescriptionDescription
The Airline is conveying the refundable information in the
OSIN/OSIADN to Airline’s Accounting System
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The passenger has changed the Order that
resulted in the refund of some amount back to the
passenger
ProcessProcess
Airline communicates full refundable information to Airline’s
Accounting System
Airline communicates partial refundable information to
Airline’s Accounting System
SuccessSuccess
Airline’s Accounting System is informed of the refundable
information resulting from the change in the Order
FailureFailure
OSIN/OSIADN message does not contain refundable
information where at least one penalty amount is collected
as a result of changing the Order
Airline’s Accounting system is not informed of the
refundable information provided in the OSIN/OSIADN
Report refundable amounts to Airline AccountingReport refundable amounts to Airline Accounting
Page: 215 of 377
Report non-refundable amounts to Airline AccountingReport non-refundable amounts to Airline Accounting
DescriptionDescription
The Airline is conveying the non-refundable information in
the OSIN/OSIADN to Airline’s Accounting System
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order
Management System
The passenger has changed the Order that
resulted in the withholding of some amount back
from the passenger
ProcessProcess
Airline communicates non-refundable information (withheld
base or tax amounts) to Airline’s Accounting System
SuccessSuccess
Airline’s Accounting System is informed of the non-
refundable information resulting from the change in the
Order
FailureFailure
OSIN/OSIADN message does not contain non-refundable
information where at least one penalty amount is collected
as a result of changing the Order
Airline’s Accounting system is not informed of the non-
refundable information provided in the OSIN/OSIADN
Report non-refundable amounts to Airline AccountingReport non-refundable amounts to Airline Accounting
Page: 216 of 377
Transmit fare waiver at reshopTransmit fare waiver at reshop
DescriptionDescription
Re-shopping by including Fare Waiver and Fare Waiver
Types
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
The Seller/Passenger has been provided with a fare
waiver code
The Airline (ORA)’s Order Management system is capable
of handling waiver codes
ProcessProcess
Airline (ORA) validates the fare waiver code and applies
the special conditions if the request meets the eligibility
conditions
Airline (ORA) responds to the reshopping request with
eligible offers
SuccessSuccess Seller receives eligible reshop offers
FailureFailure
FareWaiverCode is not validated
Airline (ORA) fails to respond to Reshopping request
Transmit fare waiver at reshopTransmit fare waiver at reshop
Page: 217 of 377
View emergency contact detailsView emergency contact details
DescriptionDescription
The Airline (ORA) returns the emergency contact details to
the Seller
PreconditionsPreconditions Emergency contact details have been captured.
ProcessProcess
The Airline (ORA) returns the emergency contact details to
the Seller.
SuccessSuccess The Seller can display the emergency contact details
FailureFailure N/A
View emergency contact detailsView emergency contact details
Page: 218 of 377
View contact details for an unaccompanied minorView contact details for an unaccompanied minor
DescriptionDescription
The Airline (ORA) returns the contact details for an
unaccompanied minor to the Seller
PreconditionsPreconditions
Contact details for an unaccompanied minor have been
captured.
ProcessProcess
The Airline (ORA) returns the contact details for an
unaccompanied minor to the Seller.
SuccessSuccess
The Seller can display the contact details for an
unaccompanied minor.
FailureFailure N/A
View contact details for unaccompanied minorView contact details for unaccompanied minor
Page: 219 of 377
View address at desinationsView address at desinations
DescriptionDescription
The Airline (ORA) returns the address at destination to the
Seller.
PreconditionsPreconditions Address at destination has been captured.
ProcessProcess
The Airline (ORA) returns the address at destination to the
Seller.
SuccessSuccess The Seller can display the address at destination.
FailureFailure N/A
View address at destinationView address at destination
Page: 220 of 377
View the result of the order modification or cancellation (partial or full)View the result of the order modification or cancellation (partial or full)
DescriptionDescription
After committing the Order modification or cancellation
(partial or full), the Seller can view the order with the
results
PreconditionsPreconditions
An Order exists in the Airline (ORA)’s Order Management
System
The Seller has committed an Order Modification or
Cancellation (partial or full)
ProcessProcess
Airline (ORA) returns the Order including:
o Grand Total (at Order Item level)
o Penalty if applicable including the net indicator (at
Order Item level)
o Differential Price (at Order Item level)
o Service Associations to the corresponding Accountable
documents (including EMD for the residual values)
o The Reusable indicator (at Order Item level)
o Unchanged indicator (at Service level)
o The Void indicator (at Order Item level)
o Payment transaction association to the Accounting
document (e.g. EMD coupon for the Penalty or Residual
Value)
SuccessSuccess
The Seller is able to view the result of the order
modification or cancellation (full or partial).
FailureFailure N/A
View the result of the order modification or cancellationView the result of the order modification or cancellation
(partial or full)(partial or full)
Page: 221 of 377
Within the Enhanced and Simplified Distribution messages, organizations sending messages can
identify themselves to the recipients downstream using the ‘Party’ element.
Each party that is responsible for generating and sending a message (Sender) may indicate who the
message is intended for (Recipient).
The AIDM defines the three party types as:
SenderSender - Information related to the party sending this message.
Recipient Recipient - Information related to the party receiving this message.
Participant Participant - Information related to parties relevant to the contents of this message.
Identifying an AggregatorIdentifying an Aggregator
An aggregator shall identify itself using an identifier (either bilaterally agreed or assigned by IATA) and
may also send its preferred name. Note that the Party structure requires the Sender (such as a
Seller), the below example simply shows an Aggregator Participant.
Identifying a Corporation Identifying a Corporation
A Corporation shall identify itself using an assigned identifier and may also send its preferred name, if
the Corporation has an IATA Number, they may also add this in the request.
Identifying Different OrganizationsIdentifying Different Organizations
Important NoteImportant Note
Please note the Party structure is under review within the industry groups and is likely to change in an upcoming
release.
Please note that current airline practices for seller identification are still covered by the standard and will be
considered during the revision of the new party structure.
<
<
Party
Party
>
>
<
<
Participant
Participant
>
>
<
<
Aggregator
Aggregator
>
>
<
<
AggregatorID
AggregatorID
>
>
AGG-01
AGG-01
</
</
AggregatorID
AggregatorID
>
>
<
<
Name
Name
>
>
Aggregator Company Name
Aggregator Company Name
</
</
Name
Name
>
>
</
</
Aggregator
Aggregator
>
>
</
</
Participant
Participant
>
>
</
</
Party
Party
>
>
Markup Copy
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
Corporation
Corporation
>
>
<
<
CorporateID
CorporateID
>
>
AAAA
AAAA
</
</
CorporateID
CorporateID
>
>
<
<
IATA_Number
IATA_Number
>
>
1234567890
1234567890
</
</
IATA_Number
IATA_Number
>
>
<
<
Name
Name
>
>
Corporate Name
Corporate Name
</
</
Name
Name
>
>
</
</
Corporation
Corporation
>
>
</
</
Sender
Sender
>
>
Markup Copy
Page: 222 of 377
Identifying a Seller Identifying a Seller
A Seller shall identify itself using the following patterns depending on the following scenarios.
Identifying an IATA Accredited Agency Identifying an IATA Accredited Agency
An IATA Accredited Agency shall be identified using the IATA Number within the IATA Number element.
IATA Numeric Code (IATA Number) are seven-digit identifier numbers assigned by IATA under
Passenger Agency Conference under Resolution 822, and used to identify places where Traffic
Documents are issued. They can also be used to identify airlines own points of sale or sales offices as
defined in Resolution 826.
Identifying an IATA TIDS Agency Identifying an IATA TIDS Agency
An IATA TIDS Agency shall be identified in the same Travel Agency structure, in the same way you
would identify any Agency, whereby the identifier used has been bilaterally agreed between the Airline
and Seller (using the Agency ID element).
Travel Industry Designators (TIDs) are seven-digit identifier numbers assigned by IATA under
Passenger Agency Conference Resolution 898. Using TIDs identifiers assigned by IATA ensures
consistent identification of agents and other intermediaries who do not have an identifier assigned
under the IATA Agency Accreditation program.
</
</
Party
Party
>
>
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
TravelAgency
TravelAgency
>
>
<
<
AgencyID
AgencyID
>
>
1234567
1234567
</
</
AgencyID
AgencyID
>
>
<
<
IATA_Number
IATA_Number
>
>
1234567
1234567
</
</
IATA_Number
IATA_Number
>
>
</
</
TravelAgency
TravelAgency
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Markup Copy
Important NoteImportant Note
The Agency ID element may also replicate the IATA Number unless bilaterally agreed.
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
TravelAgency
TravelAgency
>
>
<
<
AgencyID
AgencyID
>
>
1234567
1234567
</
</
AgencyID
AgencyID
>
>
</
</
TravelAgency
TravelAgency
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Markup Copy
Important NoteImportant Note
During the restructuring of the Party element in the upcoming releases, this will be further defined
Page: 223 of 377
Identifying a TIDS Agency working with an Accredited IATA AgencyIdentifying a TIDS Agency working with an Accredited IATA Agency
An IATA TIDS Agency shall be identified in the same Travel Agency structure, whereby the identifier
used has been bilaterally agreed between the Airline and Seller, using the Agency ID element. To
identify the IATA Accredited Agency the TIDS agency is working with, add the IATA Accredited Agency
to the IATA Number element, with the Agency ID being used for the TIDS Agency.
Identifying an Agency using an identifier assigned by the Airline (Bilateral)Identifying an Agency using an identifier assigned by the Airline (Bilateral)
A Seller shall identify itself using the identifier bilaterally agreed between the Airline and Seller using
the Agency ID element.
Advising the Airline of the Seller’s Name, or “Type”Advising the Airline of the Seller’s Name, or “Type”
Should your implementation require a Seller advising an Airline of its Name (e.g. “NDC Travel Agency
Ltd”), or its Type (e.g. “Online Travel Agency”), the Travel Agency structure may be modified as
follows:
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
TravelAgency
TravelAgency
>
>
<
<
AgencyID
AgencyID
>
>
1234567
1234567
</
</
AgencyID
AgencyID
>
>
<
<
IATA_Number
IATA_Number
>
>
5678901
5678901
</
</
IATA_Number
IATA_Number
>
>
</
</
TravelAgency
TravelAgency
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Markup Copy
Important NoteImportant Note
During the restructuring of the Party element in the upcoming releases, this will be further defined
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
TravelAgency
TravelAgency
>
>
<
<
AgencyID
AgencyID
>
>
Bilateral ID
Bilateral ID
</
</
AgencyID
AgencyID
>
>
</
</
TravelAgency
TravelAgency
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Markup Copy
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
TravelAgency
TravelAgency
>
>
<
<
AgencyID
AgencyID
>
>
1234567
1234567
</
</
AgencyID
AgencyID
>
>
<
<
IATA_Number
IATA_Number
>
>
1234567
1234567
</
</
IATA_Number
IATA_Number
>
>
<
<
Name
Name
>
>
Seller Name
Seller Name
</
</
Name
Name
>
>
<
<
TypeCode
TypeCode
>
>
OnlineTravelAgency
OnlineTravelAgency
</
</
TypeCode
TypeCode
>
>
</
</
TravelAgency
TravelAgency
>
>
</
</
Sender
Sender
>
>
Markup Copy
Page: 224 of 377
Identifying a specific Travel Agent within a SellerIdentifying a specific Travel Agent within a Seller
Should your implementation require identification of a specific Travel Agent within a Seller (i.e. the
individual responsible within that organization for initiating the request), the Travel Agency structure
may be modified as follows:
Identifying a Marketing, Operating Carrier, ORA, or POA Identifying a Marketing, Operating Carrier, ORA, or POA
An airline shall identify itself using its two or three digit primary or duplicate airline designator assigned
from the IATA Airline Coding Directory.
Airline identifying itself in a messageAirline identifying itself in a message
Airline identifying itself with the use of the controlled duplicate indicatorAirline identifying itself with the use of the controlled duplicate indicator
</
</
Party
Party
>
>
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
TravelAgency
TravelAgency
>
>
<
<
AgencyID
AgencyID
>
>
1234567
1234567
</
</
AgencyID
AgencyID
>
>
<
<
IATA_Number
IATA_Number
>
>
1234567
1234567
</
</
IATA_Number
IATA_Number
>
>
<
<
TravelAgent
TravelAgent
>
>
<
<
TravelAgentID
TravelAgentID
>
>
ABC123
ABC123
</
</
TravelAgentID
TravelAgentID
>
>
</
</
TravelAgent
TravelAgent
>
>
</
</
TravelAgency
TravelAgency
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Markup Copy
Important NoteImportant Note
The TravelAgentID may be assigned by the Airline/agreed bilaterally between Seller and Airline, or it may simply
be an identifier assigned by the Seller and stored by the Airline for future reference.
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
MarketingCarrier
MarketingCarrier
>
>
<
<
AirlineDesigCode
AirlineDesigCode
>
>
XB
XB
</
</
AirlineDesigCode
AirlineDesigCode
>
>
</
</
MarketingCarrier
MarketingCarrier
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Markup Copy
<
<
Party
Party
>
>
<
<
Sender
Sender
>
>
<
<
MarketingCarrier
MarketingCarrier
>
>
<
<
AirlineDesigCode
AirlineDesigCode
>
>
XB
XB
</
</
AirlineDesigCode
AirlineDesigCode
>
>
Markup Copy
Page: 225 of 377
<
<
DuplicateDesigInd
DuplicateDesigInd
>
>
true
true
</
</
DuplicateDesigInd
DuplicateDesigInd
>
>
<
<
Name
Name
>
>
IATA Airways
IATA Airways
</
</
Name
Name
>
>
</
</
MarketingCarrier
MarketingCarrier
>
>
</
</
Sender
Sender
>
>
</
</
Party
Party
>
>
Page: 226 of 377
Augmentation Points within the messages are undefined elements which allow any Implementer to add
any structure within the message for any defined purpose.
RequestRequest
This section documents the key elements for the Augmentation Points within the request.
01. Sending a Custom Structure to an Airline01. Sending a Custom Structure to an Airline
A seller may choose to send a bilateral or specific structure to an Airline as agreed. Any Structure can
be added to this element.
<iata:IATA_ServiceListRQ>
<iata:AugmentationPoint>
<other:BilateralStructure>
<other:Something/>
<other:Something/>
</other:BilateralStructure>
</iata:AugmentationPoint>
</iata:IATA_ServiceListRQ>
ResponseResponse
01. Receiving a Custom Structure from an Airline01. Receiving a Custom Structure from an Airline
An airline may choose to send a bilateral or specific structure to a seller as agreed. Any structure can
be added to this element.
<iata:IATA_ServiceListRS>
<iata:AugmentationPoint>
<other:BilateralStructure>
<other:Something/>
<other:Something/>
</other:BilateralStructure>
</iata:AugmentationPoint>
</iata:IATA_ServiceListRS>
Augmentation PointsAugmentation Points
NoteNote
Note, the above 'BilateralStructure' is an example only and will not be found in the standard.
NoteNote
Note, the above 'BilateralStructure' is an example only and will not be found in the standard.
Page: 227 of 377
The Airline Taxonomy is a shared language for Airlines to describe their products and services to
Sellers and a way for Sellers to optionally request specific features in an Offer.
View the Airline TaxonomyView the Airline Taxonomy
View the Airline Taxonomy Here
CodesetCodeset
The Taxonomy is a hierarchy of related items which is used to convey the context of the product or
service and can be found in this section
The Airline Taxonomy is a codeset managed by Airlines through the Standards Settings Governance.
Management of the Airline TaxonomyManagement of the Airline Taxonomy
During a release, the Standards Group can addadd items to the Airline Taxonomy at any time. Items can
only be changedchanged or removedremoved in a new release.
To request changes to the Airline Taxonomy, email standards@iata.org or contact a representitive
within the Offer Group.
Message CapabilitiesMessage Capabilities
To view how to implement this within the messages, see the Capabilities Page
Airline TaxonomyAirline Taxonomy
Page: 228 of 377
Taxonomy
ID
Parent
ID
Name Description Status
0000
Airline
Taxonomy
Endorsed
01
October
2019
0064 0000 Flight Any Product or Service related to a Flight
Endorsed
01
October
2019
00C8 0064 Servicing
Any Product or Service related to Servicing of
that Flight
Endorsed
01
October
2019
012C 00C8 Change
Any Product or Service relating to Change
Conditions
Endorsed
01
October
2019
0190 00C8 Refund
Any Product or Service relating to Refund
Conditions
Endorsed
01
October
2019
01F4 0064 Entertainment
Any Product or Service related to
Entertainment on board a Flight
Endorsed
01
October
2019
0258 01F4 WI-FI
Any Product or Service which is transmitted
through Wireless means
Endorsed
01
October
2019
02BC 01F4 Television
Any Product or Service which is plays Video
related Content
Endorsed
01
October
2019
0320 01F4 Games
Any Product or Service that relates to an
activity engaged in for fun
Endorsed
01
October
2019
0384 01F4 Internet
Any Product or Service that provides access
and content from the Word Wide Web
Endorsed
01
October
2019
03E8 01F4 Power
Any Product or Service that charges
Passenger Personal Devices
Endorsed
01
October
2019
044C 0064 Meal Any Product or Service which contains Food
Endorsed
01
October
2019
04B0 044C Breakfast
Any Product or Service which contains food
and is generally eaten first thing in the day
Endorsed
01
October
2019
Airline Taxonomy CodesetAirline Taxonomy Codeset
Page: 229 of 377
0514 044C Lunch
Any Product or Service which contains food
and is generally eaten mid-day
Endorsed
01
October
2019
0578 044C Dinner
Any Product or Service which contains food
and is generally eaten at the end of the day
Endorsed
01
October
2019
05DC 044C Snack
Any Product or Service which contains a small
amount of food eaten between meals
Endorsed
01
October
2019
0640 0064 Beverage Any Product or Service which is drinkable
Endorsed
01
October
2019
06A4 0640 Alcoholic
Any Product or Service which is drinkable and
contains Alcohol
Endorsed
01
October
2019
0708 0640 Non-Alcoholic
Any Product or Service which is drinkable
without Alcohol
Endorsed
01
October
2019
076C 0064
Medical
Equipment
Any Product or Service which aids the health
of a Passenger
Endorsed
01
October
2019
07D0 076C Oxygen
Any Product or Service which offers some
assistance to a Passenger
Endorsed
01
October
2019
0834 076C Stretcher
Any Product or Service which aids the
breathing of a Passenger
Endorsed
01
October
2019
0898 076C Wheelchair
Any Product or Service which transports a
Passenger Lying down
Endorsed
01
October
2019
08FC 076C Incubator
Any Product or Service which transports a
Passenger in a Controlled Environment
Endorsed
01
October
2019
0960 0064 Escort
Any Product or Service which accompanies a
Passenger
Endorsed
01
October
2019
09C4 0960 Minor
Any Product or Service which relates to
accompanying an individual
Endorsed
01
October
2019
0A28 0960 Adults
Any Product or Service which relates to
accompanying an minor
Endorsed
01
October
2019
Page: 230 of 377
0A8C 0960 Secured
Any Product or Service which relates to
accompanying a Prisoner or security
restricted individual
Endorsed
01
October
2019
0AF0 0960 Senior
Any Product or Service which relates to
accompanying a Senior
Endorsed
01
October
2019
0B54 0960 Medical
Any Product or Service which relates to
accompanying an individual for medical
purposes
Endorsed
01
October
2019
0BB8 0960 VIP
Any Product or Service which relates to
accompanying a VIP passenger
Endorsed
01
October
2019
0C1C 0960 Service Animal
Any Product or Service which relates to a
Service Animal which will accompany a
passenger
Endorsed
01
October
2019
0C80 0960
Emotional
Support Animal
Any Product or Service which relates to an
Emotional Service Animal which will
accompany a passenger
Endorsed
01
October
2019
0CE4 0064 Loyalty
Any Product or Service relating to Passenger
Loyalty
Endorsed
01
October
2019
0D48 0064 Upgrades
Any Product or Service relating to the
upgrade of a Passengers selected Product
Endorsed
01
October
2019
0DAC 0064 Charity
Any Product or Service which voluntarily gives
help to people or things in need
Endorsed
01
October
2019
0E10 0DAC Environment
Any Product or Service which voluntarily gives
help to the Environment
Endorsed
01
October
2019
0E74 0DAC Humanitarian
Any Product or Service which voluntarily gives
help to People
Endorsed
01
October
2019
0ED8 0064 Purchases
Any Product or Service which can be
purchased on board
Endorsed
01
October
2019
0F3C 0ED8 Duty Free
Any Product or Service which can be
purchased without duty
Endorsed
01
October
2019
0FA0 0064 Cabin Baggage
Any Product or Service which allows for
Standard Baggage in the Cabin
Endorsed
01
October
2019
Page: 231 of 377
1004 0FA0 Bag
Any Product or Service which denotes the
same of a standard bag
Endorsed
01
October
2019
1068 0FA0 Car Seat
Any Product or Service which allows for a Car
Seat within the Cabin
Endorsed
01
October
2019
10CC 0FA0 Stroller
Any Product or Service which allows for a
Stroller in the Cabin
Endorsed
01
October
2019
1130 0FA0 Cot
Any Product or Service which allows for a Cot
in the Cabin
Endorsed
01
October
2019
1194 0FA0 Pet
Any Product or Service which allows a Pet in
the Cabin
Endorsed
01
October
2019
11F8 0FA0 Excess
Any Product or Service which allows Standard
Excess Baggage in the Cabin
Endorsed
01
October
2019
125C 0FA0
Human
Remains
Any Product or Service which allows Human
Remains in the Cabin
Endorsed
01
October
2019
12C0 0FA0
Media
Equipment
Any Product or Service which allows for
Media Equipment in the Cabin
Endorsed
01
October
2019
1324 0FA0
Music
Equipment
Any Product or Service which allows for Music
Equipment to be transported
Endorsed
01
October
2019
1388 0FA0
Sports
Equipment
Any Product or Service which allows Spots
Equipment in the Cabin
Endorsed
01
October
2019
13EC 0064
Checked
Baggage
Any Product or Service which allows Standard
Baggage to be Checked
Endorsed
01
October
2019
1450 13EC Bag
Any Product or Service which denotes the
same of a standard bag
Endorsed
01
October
2019
14B4 13EC Car Seat
Any Product or Service which allows for a Car
Seat to be Checked
Endorsed
01
October
2019
1518 13EC Stroller
Any Product or Service which allows for a
Stroller to be Checked
Endorsed
01
October
2019
Page: 232 of 377
157C 13EC Cot
Any Product or Service which allows for a Cot
to be Checked
Endorsed
01
October
2019
15E0 13EC Pet
Any Product or Service which allows a Pet to
be Checked
Endorsed
01
October
2019
1644 13EC Excess
Any Product or Service which allows Standard
Excess Baggage to be Checked
Endorsed
01
October
2019
16A8 13EC
Human
Remains
Any Product or Service which allows Human
Remains to be Checked
Endorsed
01
October
2019
170C 13EC
Media
Equipment
Any Product or Service which allows for
Media Equipment to be Checked
Endorsed
01
October
2019
1770 13EC
Music
Equipment
Any Product or Service which allows for Music
Equipment to be transported
Endorsed
01
October
2019
17D4 13EC
Sports
Equipment
Any Product or Service which allows Spots
Equipment to be Checked
Endorsed
01
October
2019
1838 0064 Seat
Any Product or Service associated to a
Standard Seat
Endorsed
01
October
2019
189C 1838 Preferred
Any Product or Service associated to a
Preferred Seat
Endorsed
01
October
2019
1900 1838 Bassinet
Any Product or Service associated to a
Bassinet
Endorsed
01
October
2019
1964 0064 Assistance
Any Product or Service associated to general
Assistance being offered
Endorsed
01
October
2019
19C8 1964 Minor
Any Product or Service associated to general
Assistance being offered for Minors
Endorsed
01
October
2019
1A2C 1964 Adults
Any Product or Service associated to general
Assistance being offered for Adults
Endorsed
01
October
2019
1A90 1964 Senior
Any Product or Service associated to general
Assistance being offered for Seniors
Endorsed
01
October
2019
Page: 233 of 377
1AF4 0000 Airport Any Product or Service related to an Airport
Endorsed
01
October
2019
1B58 1AF4 Lounge Any Product or Service related to a Lounge
Endorsed
01
October
2019
1BBC 1B58 Amenities
Any Product or Service which is associated to
a Lounge Amenity
Endorsed
01
October
2019
1C20 1BBC Seating
Any Product or Service associated to Seating
within a Lounge
Endorsed
01
October
2019
1C84 1BBC Restrooms
Any Product or Service associated to
Restrooms within a Lounge
Endorsed
01
October
2019
1CE8 1BBC Shower
Any Product or Service associated to Shower
within a Lounge
Endorsed
01
October
2019
1D4C 1BBC Meal
Any Product or Service associated to Food
within a Lounge
Endorsed
01
October
2019
1DB0 1BBC Beverage
Any Product or Service associated to
Beverages within a Lounge
Endorsed
01
October
2019
1E14 1BBC Office
Any Product or Service associated to an
Office Space within a Lounge
Endorsed
01
October
2019
1E78 1BBC Internet
Any Product or Service associated to Internet
Connectivity within a Lounge
Endorsed
01
October
2019
1EDC 1BBC Sleeping
Any Product or Service associated to
Sleeping within a Lounge
Endorsed
01
October
2019
1F40 1B58 Location
Any Taxonomy which defines the location of
the Lounge (for example, prior to Security or
after)
Endorsed
01
October
2019
1FA4 1F40 Departure
Taxonomy to define that the Lounge is
available prior to Departure
Endorsed
01
October
2019
2008 1F40 Arrival
Taxonomy to define that the Lounge is
available after Arrival
Endorsed
01
October
2019
Page: 234 of 377
206C 1AF4 Terminal Any Product or Service related to a Terminal
Endorsed
01
October
2019
20D0 206C Amenities
Any Product or Service related to a Terminal
Amenity
Endorsed
01
October
2019
2134 20D0 Shower
Any Product or Service associated to Shower
within the Terminal
Endorsed
01
October
2019
2198 20D0
Food and
Beverage
Any Product or Service associated to Food
and Beverage within the Terminal
Endorsed
01
October
2019
21FC 20D0 Sleeping
Any Product or Service associated to
Sleeping within the Terminal
Endorsed
01
October
2019
2260 20D0 Shops
Any Product or Service associated to
Shopping within the Terminal
Endorsed
01
October
2019
22C4 20D0 Internet
Any Product or Service associated to granting
access to the World Wide Web
Endorsed
01
October
2019
2328 1AF4 Check In
Any Product or Service associated to Check
In
Endorsed
01
October
2019
238C 2328 Priority
Any Product or Service associated to Priority
Check In
Endorsed
01
October
2019
23F0 2328 Manual
Any Product or Service associated to a Check
in Desk
Endorsed
01
October
2019
2454 2328 Internet
Any Product or Service associated to the
passenger checking in online (mobile, website
etc)
Endorsed
01
October
2019
24B8 2328 Automated
Any Product or Service associated to
Automated Check In
Endorsed
01
October
2019
251C 2328 Kiosk
Any Product or Service associated to Kiosk
Check In
Endorsed
01
October
2019
2580 1AF4 Boarding
Any Product or Service associated to
Boarding
Endorsed
01
October
2019
Page: 235 of 377
25E4 2580 Priority
Any Product or Service associated to Priority
Boarding
Endorsed
01
October
2019
2648 1AF4 Security Any Product or Service associated to Security
Endorsed
01
October
2019
26AC 2648 Priority
Any Product or Service associated to Priority
Security
Endorsed
01
October
2019
2710 1AF4
Medical
Equipment
Any Product or Service which aids the
breathing of a Passenger
Endorsed
01
October
2019
2774 2710 Oxygen
Any Product or Service which transports a
Passenger lying down
Endorsed
01
October
2019
27D8 2710 Stretcher
Any Product or Service which transports a
Passenger in a Seat
Endorsed
01
October
2019
283C 2710 Wheelchair
Any Product or Service which transports a
Passenger using a Wheelchair
Endorsed
01
October
2019
28A0 2710 Incubator
Any Product or Service which transports a
Passenger in a Controlled Environment
Endorsed
01
October
2019
2904 1AF4 Escort
Any Product or Service which transports a
Passenger in a Controlled Environment
Endorsed
01
October
2019
2968 2904 Minor
Any Product or Service which relates to
accompanying an individual
Endorsed
01
October
2019
29CC 2904 Adults
Any Product or Service which relates to
accompanying an minor
Endorsed
01
October
2019
2A30 2904 Secured
Any Product or Service which relates to
accompanying a Prisoner or security
restricted individual
Endorsed
01
October
2019
2A94 2904 Senior
Any Product or Service which relates to
accompanying a Senior
Endorsed
01
October
2019
2AF8 2904 Medical
Any Product or Service which relates to
accompanying an individual for medical
purposes
Endorsed
01
October
2019
Page: 236 of 377
2B5C 2904 VIP
Any Product or Service which relates to
accompanying a VIP passenger
Endorsed
01
October
2019
2BC0 2904 Service Animal
Any Product or Service which relates to a
Service Animal which will accompany a
passenger
Endorsed
01
October
2019
2C24 2904
Emotional
Support Animal
Any Product or Service which relates to an
Emotional Service Animal which will
accompany a passenger
Endorsed
01
October
2019
2C88 0000 Ground
Any Product or Service relating to Ground
Services outside the Airport
Endorsed
01
October
2019
2CEC 2C88 Transport
Any Product or Service relating to Transport
Services outside the Airport
Endorsed
01
October
2019
2D50 2CEC Car Hire Any Product or Service relating to Car Hire
Endorsed
01
October
2019
2DB4 2CEC Taxi
Any Product or Service relating to renting a
Taxi
Endorsed
01
October
2019
2E18 2CEC Ride Share
Any Product or Service relating to Ride Share
Programs
Endorsed
01
October
2019
2E7C 2CEC Train
Any Product or Service relating to transport by
Rail
Endorsed
01
October
2019
2EE0 2CEC Boat
Any Product or Service relating to transport by
Boat
Endorsed
01
October
2019
2F44 2CEC Cruise
Any Product or Service relating to transport by
Cruise Liner
Endorsed
01
October
2019
2FA8 2CEC Bus
Any Product or Service relating to Bus or
Coach
Endorsed
01
October
2019
300C 2CEC Tour
Any Product or Service relating to Transport
via a Tour
Endorsed
01
October
2019
3070 2CEC Limo
Any Product or Service relating to transport by
Limousine
Endorsed
01
October
2019
Page: 237 of 377
30D4 2C88 Parking
Any Product or Service relating to Parking
offsite from the Airport
Endorsed
01
October
2019
3138 2C88 Accommodation
Any Product or Service relating to
Accommodation
Endorsed
01
October
2019
319C 0000 Journey
Any Product or Service not relating
specifically to a flight, ground or airport
service. For example holiday insurance.
Endorsed
01
October
2019
3200 319C Insurance
Any Product or Service relating to Insurance
outside the context of just a flight, airport or
ground
Endorsed
01
October
2019
3264 319C Visa Services
Any Product or Service relating to Visa
Services
Endorsed
01
October
2019
32C8 319C Book and Hold
Any Product or Service relating to Book and
Hold Services
Endorsed
01
October
2019
Page: 238 of 377
Request Services using the Airline TaxonomyRequest Services using the Airline Taxonomy
01. Requesting a Specific Service using the Airline Taxonomy01. Requesting a Specific Service using the Airline Taxonomy
A Seller may use the Airline Taxonomy (or bilateral) to request specific products or services within the
Offers to be returned. In this example, the Seller requests Offers with WIFI.
02. Requesting not to return Specific Services02. Requesting not to return Specific Services
A Seller may wish to filter the other way by specifically requesting that one or more services are not
returned. In this example, the Seller requests that the Airline does not return any Offers which have
alcoholic drinks included.
03. Requesting Multiple Services using the Airline Taxonomy03. Requesting Multiple Services using the Airline Taxonomy
The Seller may choose to have any Offer which contains any of the following services.
04. Requesting Services as Bilaterally Agreed between Parties04. Requesting Services as Bilaterally Agreed between Parties
A Seller may specifically request a service that has been bilaterally agreed between the Airline and the
Sellers previously. In this example, the Seller understands that the value ZZZA is a Pet Grooming
Service, which the Seller would like within the returned Offers.
Airline Taxonomy CapabilitiesAirline Taxonomy Capabilities
<iata:ShoppingCriteria>
<iata:ShoppingCriteria>
<iata:ServiceCriteria>
<iata:ServiceCriteria>
<iata:TaxonomyCode>0258</iata:TaxonomyCode>
<iata:TaxonomyCode>0258</iata:TaxonomyCode>
</iata:ServiceCriteria>
</iata:ServiceCriteria>
</iata:ShoppingCriteria>
</iata:ShoppingCriteria>
None Copy
<iata:ShoppingCriteria>
<iata:ShoppingCriteria>
<iata:ServiceCriteria>
<iata:ServiceCriteria>
<iata:IncludeInd>false</iata:IncludeInd>
<iata:IncludeInd>false</iata:IncludeInd>
<iata:TaxonomyCode>0258</iata:TaxonomyCode>
<iata:TaxonomyCode>0258</iata:TaxonomyCode>
</iata:ServiceCriteria>
</iata:ServiceCriteria>
</iata:ShoppingCriteria>
</iata:ShoppingCriteria>
None Copy
<iata:ShoppingCriteria>
<iata:ShoppingCriteria>
<iata:ServiceCriteria>
<iata:ServiceCriteria>
<iata:TaxonomyCode>0258</iata:TaxonomyCode>
<iata:TaxonomyCode>0258</iata:TaxonomyCode>
<iata:TaxonomyCode>01F4</iata:TaxonomyCode>
<iata:TaxonomyCode>01F4</iata:TaxonomyCode>
</iata:ServiceCriteria>
</iata:ServiceCriteria>
</iata:ShoppingCriteria>
</iata:ShoppingCriteria>
None Copy
Page: 239 of 377
Responding with Services within the Airline TaxonomyResponding with Services within the Airline Taxonomy
01. Responding with a Taxonomized Service01. Responding with a Taxonomized Service
An Airline may return a Service which is described using the Airline Taxonomy. In this example, the
Airline has returned Lounge as defined within the Airline Taxonomy. (Airport -> Lounge)
02. Responding with multiple Taxonomies for a Service02. Responding with multiple Taxonomies for a Service
An Airline can describe a service with multiple Taxonomies. Here, the Airline describes its Lounge as
having a Shower and Internet access.
03. Responding with Bilaterally agreed Taxonomies03. Responding with Bilaterally agreed Taxonomies
An Airline may not find an appropriate Taxonomy structure for its product and may choose to add its
own definitions to the structure bilaterally. In this example, the Airline is offering a Pet Grooming
Service onboard. They’ve used the Shared Taxonomy to describe Pet but used their own value to
describe it’s a Grooming Service.
This can be done by the airline assigning a value and detailing this within its developer guidance. The
Airline or Seller may, if they choose, bring this to the Standard Settings Group to add this in to the
Shared Taxonomy if desired.
<iata:ShoppingCriteria>
<iata:ShoppingCriteria>
<iata:ServiceCriteria>
<iata:ServiceCriteria>
<iata:TaxonomyCode>ZZZA</iata:TaxonomyCode>
<iata:TaxonomyCode>ZZZA</iata:TaxonomyCode>
</iata:ServiceCriteria>
</iata:ServiceCriteria>
</iata:ShoppingCriteria>
</iata:ShoppingCriteria>
None Copy
Bi lateral ContentBilateral Content
It is possible to use bilaterally agreed content, however the Airline Taxonomy can also be updated to include new
items to better describe a product or service.
<iata:ServiceTaxonomy>
<iata:ServiceTaxonomy>
<iata:DescText>Lounge Access</iata:DescText>
<iata:DescText>Lounge Access</iata:DescText>
<iata:TaxonomyCode>1B58</iata:TaxonomyCode>
<iata:TaxonomyCode>1B58</iata:TaxonomyCode>
</iata:ServiceTaxonomy>
</iata:ServiceTaxonomy>
None Copy
<iata:ServiceTaxonomy>
<iata:ServiceTaxonomy>
<iata:TaxonomyCode>1BBC</iata:TaxonomyCode>
<iata:TaxonomyCode>1BBC</iata:TaxonomyCode>
</iata:ServiceTaxonomy>
</iata:ServiceTaxonomy>
<iata:ServiceTaxonomy>
<iata:ServiceTaxonomy>
<iata:TaxonomyCode>1BBC</iata:TaxonomyCode>
<iata:TaxonomyCode>1BBC</iata:TaxonomyCode>
</iata:ServiceTaxonomy>
</iata:ServiceTaxonomy>
None Copy
Page: 240 of 377
04. Responding Airline Specific information around that Service04. Responding Airline Specific information around that Service
An Airline may also send additional information through a simply Key-value pair associated with a
Taxonomy value. In this example, the Airline states that it has Internet (via WI-FI) and choose to further
specify information around the Internet service Onboard. The Keys are values are not defined at an
industry level; this is up to the Airline to use.
Airlines Developer GuideAirlines Developer Guide
With a bilaterally agreed feature set, the airline should advise the integrators the expected Keys to be
delivered within a Taxonomy, simliar to the below example.
TaxonomyTaxonomy CodesetCodeset Feature KeyFeature Key Feature ValueFeature Value DescriptionDescription
Pet
Grooming
Service
BILATERAL MaxPetLength
Double
(expressed in
centimeters)
The maximum length of the pet
which can be groomed during a
flight.
Pet
Grooming
Service
BILATERAL MaxPetHeight
Double
(expressed in
centimeters)
The maximum height of the pet
which can be groomed during a
flight.
Pet
Grooming
Service
BILATERAL MaxPetWeight
Double
(expressed in
grams)
The maximum weight of the pet
which can be groomed during a
flight.
<iata:ServiceTaxonomy>
<iata:ServiceTaxonomy>
<iata:TaxonomyCode>ZZZA</iata:TaxonomyCode>
<iata:TaxonomyCode>ZZZA</iata:TaxonomyCode>
</iata:ServiceTaxonomy>
</iata:ServiceTaxonomy>
None Copy
<iata:ServiceTaxonomy>
<iata:ServiceTaxonomy>
<iata:DescText>Onboard Wi-Fi Internet Service</iata:DescText>
<iata:DescText>Onboard Wi-Fi Internet Service</iata:DescText>
<iata:ServiceFeature>
<iata:ServiceFeature>
<iata:CodesetCode>speed</iata:CodesetCode>
<iata:CodesetCode>speed</iata:CodesetCode>
<iata:CodesetNameCode>BILATERAL</iata:CodesetNameCode>
<iata:CodesetNameCode>BILATERAL</iata:CodesetNameCode>
<iata:ValueText>50</iata:ValueText>
<iata:ValueText>50</iata:ValueText>
</iata:ServiceFeature>
</iata:ServiceFeature>
<iata:ServiceFeature>
<iata:ServiceFeature>
<iata:CodesetCode>altitude</iata:CodesetCode>
<iata:CodesetCode>altitude</iata:CodesetCode>
<iata:CodesetNameCode>BILATERAL</iata:CodesetNameCode>
<iata:CodesetNameCode>BILATERAL</iata:CodesetNameCode>
<iata:ValueText>10000</iata:ValueText>
<iata:ValueText>10000</iata:ValueText>
<iata:TaxonomyCode>01F4</iata:TaxonomyCode>
<iata:TaxonomyCode>01F4</iata:TaxonomyCode>
</iata:ServiceTaxonomy>
</iata:ServiceTaxonomy>
None Copy
Page: 241 of 377
Traditionally, an entire copy of fare rules is sent to the Seller for them to navigate and understand the
requirements, eligibility and rules associated to the ‘Offer’, however this information is not always
needed, nor clear to the Seller.
In Offer and Order Management, only the rules associated to the Offer should be sent to the Seller,
not the internal information relating to the construction of the Offer.
The below table signifies the information (expressed as categoreis) that can be delivered to the Seller.
This information is delivered in various places within the messages. Some of which is detailed in this
section.
This information is not supported in the transmission from the Airline to the Seller as it is not required.
Offer and Order Conditions and RestrictionsOffer and Order Conditions and Restrictions
Page: 242 of 377
In many scenarios, there are multiple changes in conditions within a ‘Stage’, therefore Rules need to
be governed by an effective date to limit them within the section of the stage.
Take the following example in an Economy Offer:
1. Change is ‘free of charge’ up to 30 days prior to Departure
2. Change is 1 CHF from 30 days prior to Departure
3. No changes are allowed within 7 days of Departure
This can be modelled within 3 Rules using the EffectiveDate. The Effective Date is the point at which
the Rule starts. The Rule can end in two scenarios:
When the Stage ends (i.e. in the above scenario, when the Flight Departs)
When its overridden by another Rule with a later EffectiveDate.
Therefore the above would be modelled as below considering the flight scenario:
GVA -> SIN: Payment: 1st January 2019 and departing: 1st February 2019
Stages of a RestrictionStages of a Restriction
Page: 243 of 377
01. Advising Changes are not Possible01. Advising Changes are not Possible
An Airline advises that changes are not possible for the Offer or an Offer Item.
02. Advising Changes are possible with Restrictions02. Advising Changes are possible with Restrictions
An Airline advises that changes are possible for a specific period prior to departure, for fee.
03. Advising Changes are possible with Restrictions03. Advising Changes are possible with Restrictions
An Airline advises that changes are possible for a specific period prior to departure, within a range for
the fee.
Change RestrictionsChange Restrictions
<iata:ChangeRestrictions>
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>false</iata:AllowedModificationInd>
<iata:AllowedModificationInd>false</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Flight</iata:ChangeTypeCode>
<iata:ChangeTypeCode>Flight</iata:ChangeTypeCode>
<iata:DescText>Changes after Departure are not allowed.</iata:DescText>
<iata:DescText>Changes after Departure are not allowed.</iata:DescText>
<iata:JourneyStageCode>After Departure</iata:JourneyStageCode>
<iata:JourneyStageCode>After Departure</iata:JourneyStageCode>
</iata:ChangeRestrictions>
</iata:ChangeRestrictions>
None Copy
<iata:ChangeRestrictions>
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Flight</iata:ChangeTypeCode>
<iata:ChangeTypeCode>Flight</iata:ChangeTypeCode>
<iata:DescText>Change before departure will incur a change fee of 1 CHF.
<iata:DescText>Change before departure will incur a change fee of 1 CHF.
</iata:DescText>
</iata:DescText>
<iata:EffectiveDateTime>2020-12-17T09:30:47Z</iata:EffectiveDateTime>
<iata:EffectiveDateTime>2020-12-17T09:30:47Z</iata:EffectiveDateTime>
<iata:ExpirationDateTime>2020-12-19T09:30:47Z</iata:ExpirationDateTime>
<iata:ExpirationDateTime>2020-12-19T09:30:47Z</iata:ExpirationDateTime>
<iata:Fee>
<iata:Fee>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:ApproximateInd>false</iata:ApproximateInd>
<iata:ApproximateInd>false</iata:ApproximateInd>
<iata:DescText>Plus any additional fare difference</iata:DescText>
<iata:DescText>Plus any additional fare difference</iata:DescText>
</iata:Fee>
</iata:Fee>
<iata:JourneyStageCode>Before Departure</iata:JourneyStageCode>
<iata:JourneyStageCode>Before Departure</iata:JourneyStageCode>
</iata:ChangeRestrictions>
</iata:ChangeRestrictions>
None Copy
<iata:ChangeRestrictions>
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Flight</iata:ChangeTypeCode>
<iata:ChangeTypeCode>Flight</iata:ChangeTypeCode>
<iata:DescText>Change before departure will incur a change fee.</iata:DescText>
<iata:DescText>Change before departure will incur a change fee.</iata:DescText>
<iata:EffectiveDateTime TimeZoneCode="token">2020-12-
<iata:EffectiveDateTime TimeZoneCode="token">2020-12-
17T09:30:47Z</iata:EffectiveDateTime>
17T09:30:47Z</iata:EffectiveDateTime>
<iata:ExpirationDateTime TimeZoneCode="token">2020-12-
<iata:ExpirationDateTime TimeZoneCode="token">2020-12-
17T09:30:47Z</iata:ExpirationDateTime>
17T09:30:47Z</iata:ExpirationDateTime>
<iata:Fee>
<iata:Fee>
None Copy
Page: 244 of 377
04. Airline advises Changes using Stage Code04. Airline advises Changes using Stage Code
An Airline advises that changes after departure (due to no show) are allowed, but comes with a 100%
loss of fare.
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Name</iata:ChangeTypeCode>
<iata:DescText>Name Change Fee.</iata:DescText>
<iata:Fee>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
</iata:Fee>
</iata:ChangeRestrictions>
05. Advising a Seller of Name Change Rules05. Advising a Seller of Name Change Rules
Airline advises the Seller that name changes for this Offer (or Offer Item) is not allowed.
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>false</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Name</iata:ChangeTypeCode>
<iata:DescText>Name Changes are not allowed.</iata:DescText>
</iata:ChangeRestrictions>
06. Advising Name Changes06. Advising Name Changes
Airline advises the Seller that names changes are allowed for a price.
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Name</iata:ChangeTypeCode>
<iata:DescText>Name Change Fee.</iata:DescText>
<iata:Fee>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
</iata:Fee>
</iata:ChangeRestrictions>
Airline advises the Seller that name changes are included in the Offer (free).
<iata:ChangeRestrictions>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:ChangeTypeCode>Name</iata:ChangeTypeCode>
<iata:DescText>Name Change included.</iata:DescText>
</iata:ChangeRestrictions>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:ApproximateInd>true</iata:ApproximateInd>
<iata:ApproximateInd>true</iata:ApproximateInd>
<iata:DescText>from</iata:DescText>
<iata:DescText>from</iata:DescText>
</iata:Fee>
</iata:Fee>
<iata:JourneyStageCode>Before Departure</iata:JourneyStageCode>
<iata:JourneyStageCode>Before Departure</iata:JourneyStageCode>
</iata:ChangeRestrictions>
</iata:ChangeRestrictions>
Page: 245 of 377
01. Advising a Seller of Cancel and Refundability Rules01. Advising a Seller of Cancel and Refundability Rules
A Seller advises that cancellations are not possible, and that the Customer eill loose 100% of their
fare.
<iata:CancelRestrictions>
<iata:AllowedModificationInd>false</iata:AllowedModificationInd>
<iata:DescText>Cancellations after a no show are not permitted.</iata:DescText>
<iata:JourneyStageCode>No Show</iata:JourneyStageCode>
</iata:CancelRestrictions>
02. Advising the Seller that Cancellations after Departure are Possible02. Advising the Seller that Cancellations after Departure are Possible
Advising the Seller that cancellations after departure are possible and fully refundable to the Original
Form of Payment up until a certain date (expiration date).
<iata:CancelRestrictions>
<iata:AllowedModificationInd>true</iata:AllowedModificationInd>
<iata:DescText>Cancellations after departure are permitted.</iata:DescText>
<iata:ExpirationDateTime>2020-12-17T09:30:47Z</iata:ExpirationDateTime>
<iata:JourneyStageCode>After Departure</iata:JourneyStageCode>
<iata:Refund>
<iata:FixedAmount CurCode="CHF">1.00</iata:FixedAmount>
<iata:LevelTypeCode>Full</iata:LevelTypeCode>
<iata:PaymentTypeCode>OFOP</iata:PaymentTypeCode>
</iata:Refund>
</iata:CancelRestrictions>
Cancel RestrictionsCancel Restrictions
Page: 246 of 377
01. Advising a Seller of Optional StopOver Information01. Advising a Seller of Optional StopOver Information
The Offer Management System will evaluate the current itinerary (Offer) and determine if Stopovers
are allowed for that itinerary. If Stopovers are allowed, the Airline may return the locations within the
current itinerary and advise which ones have Stopovers.
The Seller can then request a new Offer including a Stopover if they wish.
02. Advising the Seller that Stopovers are Available02. Advising the Seller that Stopovers are Available
The Airline wishes to advise the Seller that the itinerary could contain a stopover however is not
descriptive as to what stopovers are allowed.
03. Advising the Seller the Max Number of Stopovers Available03. Advising the Seller the Max Number of Stopovers Available
The airline wishes to advise that Seller that stopovers are allowed and there is a maximum of two
stopovers available, which relate to both Passengers and will each cost 10 CHF.
The Airline wishes to advise the Seller only one stopover is allowed, however there are 2 options to
where this stopover can occur.
Stop Over InformationStop Over Information
Linking Stopover Information to an AirportLinking Stopover Information to an Airport
PaxSegmentRefID relates to the inbound segment. For example, if the itinerary is GVA-SIN-BNE and the
stopover is in SIN, the PaxSegmentRefID would link to the GVA-SIN segment.
<iata:StopOverRestrictions>
<iata:StopOverRestrictions>
<iata:AvailInd>true</iata:AvailInd>
<iata:AvailInd>true</iata:AvailInd>
</iata:StopOverRestrictions>
</iata:StopOverRestrictions>
None Copy
<iata:StopOverRestrictions>
<iata:StopOverRestrictions>
<iata:AvailInd>true</iata:AvailInd>
<iata:AvailInd>true</iata:AvailInd>
<iata:MaximumStopOversPermittedQty>2</iata:MaximumStopOversPermittedQty>
<iata:MaximumStopOversPermittedQty>2</iata:MaximumStopOversPermittedQty>
</iata:StopOverRestrictions>
</iata:StopOverRestrictions>
None Copy
<iata:StopOverRestrictions>
<iata:StopOverRestrictions>
<iata:AvailInd>true</iata:AvailInd>
<iata:AvailInd>true</iata:AvailInd>
<iata:ChargeableInd>true</iata:ChargeableInd>
<iata:ChargeableInd>true</iata:ChargeableInd>
<iata:MaximumStopOversPermittedQty>1</iata:MaximumStopOversPermittedQty>
<iata:MaximumStopOversPermittedQty>1</iata:MaximumStopOversPermittedQty>
<iata:StopOverLocation>
<iata:StopOverLocation>
<iata:DatedOperatingLegRefID>token</iata:DatedOperatingLegRefID>
<iata:DatedOperatingLegRefID>token</iata:DatedOperatingLegRefID>
<iata:MaximumDuration>P0Y0M0DT10H00M</iata:MaximumDuration>
<iata:MaximumDuration>P0Y0M0DT10H00M</iata:MaximumDuration>
<iata:PaxSegmentRefID>PAXSEG-01</iata:PaxSegmentRefID>
<iata:PaxSegmentRefID>PAXSEG-01</iata:PaxSegmentRefID>
</iata:StopOverLocation>
</iata:StopOverLocation>
None Copy
Page: 247 of 377
<iata:StopOverLocation>
<iata:StopOverLocation>
<iata:DatedOperatingLegRefID>token</iata:DatedOperatingLegRefID>
<iata:DatedOperatingLegRefID>token</iata:DatedOperatingLegRefID>
<iata:MaximumDuration>P0Y0M0DT10H00M</iata:MaximumDuration>
<iata:MaximumDuration>P0Y0M0DT10H00M</iata:MaximumDuration>
<iata:PaxSegmentRefID>PAXSEG-03</iata:PaxSegmentRefID>
<iata:PaxSegmentRefID>PAXSEG-03</iata:PaxSegmentRefID>
</iata:StopOverLocation>
</iata:StopOverLocation>
</iata:StopOverRestrictions>
</iata:StopOverRestrictions>
Page: 248 of 377
Advising a Seller of Unstructured InformationAdvising a Seller of Unstructured Information
Unstructured rules may also be communicated to the Seller at an Offer or Offer Item level using the
description within the Rule, this description can be used to describe a structured rule, or independent,
for example:
Unstructured InformationUnstructured Information
<iata:OfferItem>
<iata:OfferItem>
<iata:DescText>All Airline Offers are subject to change. If you change your booking,
<iata:DescText>All Airline Offers are subject to change. If you change your booking,
your new Offer may be different to the original Offer.</iata:DescText>
your new Offer may be different to the original Offer.</iata:DescText>
</iata:OfferItem>
</iata:OfferItem>
None Copy
Page: 249 of 377
Advising a Seller of a Masked FareAdvising a Seller of a Masked Fare
The Offer managmenet system can advise the Seller at the Offer time that an Order Price will be
masked to the Customer should the Customer query the price directly with the Airline.
The Airline will return a Masked Indicator advising the Seller that the Base Amount will not be shown to
the Customer.
Masked PriceMasked Price
<k:FarePrice>
<k:FarePrice>
<k:FarePriceMasked>true</k:FarePriceMasked>
<k:FarePriceMasked>true</k:FarePriceMasked>
<k:FarePriceType>
<k:FarePriceType>
<k:Price>
<k:Price>
<k:BaseAmount CurCode="CHF">10.00</k:BaseAmount>
<k:BaseAmount CurCode="CHF">10.00</k:BaseAmount>
<k:TaxSummary>
<k:TaxSummary>
<k:Tax>
<k:Tax>
<k:Amount CurCode="CHF">0.10</k:Amount>
<k:Amount CurCode="CHF">0.10</k:Amount>
<k:Country>
<k:Country>
<k:CountryCode>CH</k:CountryCode>
<k:CountryCode>CH</k:CountryCode>
</k:Country>
</k:Country>
<k:RefundInd>true</k:RefundInd>
<k:RefundInd>true</k:RefundInd>
<k:TaxCode>CH</k:TaxCode>
<k:TaxCode>CH</k:TaxCode>
<k:TaxTypeCode>Applied</k:TaxTypeCode>
<k:TaxTypeCode>Applied</k:TaxTypeCode>
</k:Tax>
</k:Tax>
<k:TotalTaxAmount CurCode="CHF">0.10</k:TotalTaxAmount>
<k:TotalTaxAmount CurCode="CHF">0.10</k:TotalTaxAmount>
</k:TaxSummary>
</k:TaxSummary>
<k:TotalAmount CurCode="CHF">10.10</k:TotalAmount>
<k:TotalAmount CurCode="CHF">10.10</k:TotalAmount>
</k:Price>
</k:Price>
</k:FarePriceType>
</k:FarePriceType>
</k:FarePrice>
</k:FarePrice>
None Copy
Page: 250 of 377
The Airline may advise the Seller of a specific type of Offer item which is being presented to the
Customer using the Ticket Designator.
This element is for use with Field 1 and Field 2 of the Fare Basis Code (as defined in Resolution 728)
For example:
Fare Basis Code: TFBC/WH, Ticket Designator: WH
Fare Basis Code: TFBC/CO, Ticket Designator: CO
Advising a Seller of a Fare Basis Code and Ticket DesignatorAdvising a Seller of a Fare Basis Code and Ticket Designator
An airline may have specific ticket designators used to differentiate its fares which may also signify
anything from private fares, wholesale, promotion or discounted fares.
If an airline has a designator, they shall split the designator into the Ticket Designator Code field and
add the Fare Basis Code to the Fare basis Code field.
While these fields are not restricted, the limitation within the ticketing standard is 11 alpha numeric
characters per field.
Ticket DesignatorTicket Designator
<iata:FareComponent>
<iata:FareComponent>
<iata:TicketDesignatorCode>WO</iata:TicketDesignatorCode>
<iata:TicketDesignatorCode>WO</iata:TicketDesignatorCode>
<iata:FareBasisCode>JFBC</iata:FareBasisCode>
<iata:FareBasisCode>JFBC</iata:FareBasisCode>
<iata:PriceClassRefID>J</iata:PriceClassRefID>
<iata:PriceClassRefID>J</iata:PriceClassRefID>
</iata:FareComponent>
</iata:FareComponent>
None Copy
Page: 251 of 377
Welcome to the Enhanced and Simplified Distribution GuideWelcome to the Enhanced and Simplified Distribution Guide
This website holds information and best practices to aid with implementations of Enhanced and
Simplified Distribution. This site is managed by the Offer and Order Standard Setting Groups.
DISCLAIMER: The information contained in this publication is subject to constant review in the light of
changing government requirements and regulations. No reader should act on the basis of any such
information without referring to applicable laws and regulations and/or without taking appropriate
professional advice. Although every effort has been made to ensure accuracy, the International Air
Transport Association shall not be held responsible for any loss or damage caused by errors,
omissions, misprints or misinterpretation of the contents hereof. Furthermore, the International Air
Transport Association expressly disclaims any liability to any person or entity in respect of anything
done or omitted, by any such person or entity in reliance on the contents of this publication.
No Part of this publication may be reproduced, recast, reformatted or transmitted in any form by any
means, electronic or mechanical, including photocopying, recording or any information storage and
retrieval system, without the prior written permission from:
Senior Vice President, Marketing and Commercial Services
International Air Transport Association
800 Place Victoria, P.O. Box 113
Montreal, Quebec, Canada H4Z 1M1
Display of Refundable Taxes at Time of ShoppingDisplay of Refundable Taxes at Time of Shopping
Page: 252 of 377
OverviewOverview
To comply with some sales tax regulations, the Seller may provide additional information about the
traveler and traveler’s Company (EmployerEmployer) for the Airlines use (such as in producing a tax invoice).
The Seller may fill in Sales Tax RegistrationSales Tax Registration data elements under ContactInfoContactInfo.
The below demonstrates how this information can be sent when creating or changing an Order.
Sending Additional Tax Information to an AirlineSending Additional Tax Information to an Airline
A Seller may send the Passengers Employer Tax Information as detailed below. This example shows a
passenger who works for ‘Adventure Company’ based in Geneva with a Sales Tax Registration ID.
Airline Confirming the Additional tax InformationAirline Confirming the Additional tax Information
Collection of Contact Information relating to Goods andCollection of Contact Information relating to Goods and
Services TaxServices Tax
<ContactInfoList>
<ContactInfoList>
<ContactInfo>
<ContactInfo>
<ContactInfoID>CONTACT-01</ContactInfoID>
<ContactInfoID>CONTACT-01</ContactInfoID>
<ContactTypeText>Business</ContactTypeText>
<ContactTypeText>Business</ContactTypeText>
<EmailAddress>
<EmailAddress>
<EmailAddressText>standards@</EmailAddressText>
<EmailAddressText>standards@</EmailAddressText>
</EmailAddress>
</EmailAddress>
<Employer>
<Employer>
<Name>Adventure PTY LTD</Name>
<Name>Adventure PTY LTD</Name>
<SalesTaxRegistration>
<SalesTaxRegistration>
<CityName>Geneva</CityName>
<CityName>Geneva</CityName>
<CountryCode>CH</CountryCode>
<CountryCode>CH</CountryCode>
<CountryDialingCode>+41</CountryDialingCode>
<CountryDialingCode>+41</CountryDialingCode>
<CountrySubDivisionName>GE</CountrySubDivisionName>
<CountrySubDivisionName>GE</CountrySubDivisionName>
<EmailAddressText>standards@</EmailAddressText>
<EmailAddressText>standards@</EmailAddressText>
<PhoneNumber>0712345678</PhoneNumber>
<PhoneNumber>0712345678</PhoneNumber>
<PostalCode>1207</PostalCode>
<PostalCode>1207</PostalCode>
<SalesTaxRegistrationID>AB1234567890</SalesTaxRegistrationID>
<SalesTaxRegistrationID>AB1234567890</SalesTaxRegistrationID>
<StreetText>Rue des Vollandes 9</StreetText>
<StreetText>Rue des Vollandes 9</StreetText>
</SalesTaxRegistration>
</SalesTaxRegistration>
</Employer>
</Employer>
<IndividualRefID>INDIVIDUAL-01</IndividualRefID>
<IndividualRefID>INDIVIDUAL-01</IndividualRefID>
<Individual>
<Individual>
<GivenName>FirstName</GivenName>
<GivenName>FirstName</GivenName>
<IndividualID>INDIVIDUAL-01</IndividualID>
<IndividualID>INDIVIDUAL-01</IndividualID>
<Surname>LastName</Surname>
<Surname>LastName</Surname>
<TitleName>Mr</TitleName>
<TitleName>Mr</TitleName>
</Individual>
</Individual>
</ContactInfo>
</ContactInfo>
</ContactInfoList>
</ContactInfoList>
None Copy
Page: 253 of 377
When a Seller retrieves an Order from an Airline, the Employer information, if present, may be found
echoed back with the same information.
Page: 254 of 377
The Airline may provide information relating to the commission that will be applied to the sale of an
Offer.
The Airlne may provide a commission percentage or set value within a Commission structure, not both.
An Airline may provide more than one commission structure with different Comission Codes, for
example the Airlne may send a ‘standad’ or ‘supplimental’ commission.
Commission Response ElementsCommission Response Elements
01. Airline Advises a Set Value Commmission01. Airline Advises a Set Value Commmission
An airline may advise the Seller that an Item has a set commission value.
02. Airline Advises a Percentage Commission02. Airline Advises a Percentage Commission
An Airline may advise the Seller that an Item has a set Commission percentage. If a percentage is
provided, the airline shall also provide the amount to which the percentage is applied to.
03. Airline Advises Commission Type03. Airline Advises Commission Type
An airline may advise the Seller the type of commission that is being applied to the Offer item using
the CommissionCode element
CommissionsCommissions
<iata:Commission>
<iata:Commission>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
</iata:Commission>
</iata:Commission>
None Copy
<iata:Commission>
<iata:Commission>
<iata:Percentage>1.00</iata:Percentage>
<iata:Percentage>1.00</iata:Percentage>
<iata:PercentageAppliedToAmount CurCode="CHF">1.0</iata:PercentageAppliedToAmount>
<iata:PercentageAppliedToAmount CurCode="CHF">1.0</iata:PercentageAppliedToAmount>
</iata:Commission>
</iata:Commission>
None Copy
<iata:Commission>
<iata:Commission>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:CommissionCode>STANDARD</iata:CommissionCode>
<iata:CommissionCode>STANDARD</iata:CommissionCode>
</iata:Commission>
</iata:Commission>
None Copy
Commission CodeCommission Code
Note there is no codeset for this element.
Page: 255 of 377
04. Airline Advises Multiple Commission Types04. Airline Advises Multiple Commission Types
An airline may send multiple commissions which would be applied.
<iata:Commission>
<iata:Commission>
<iata:CommissionCode>STANDARD</iata:CommissionCode>
<iata:CommissionCode>STANDARD</iata:CommissionCode>
<iata:Percentage>1.0</iata:Percentage>
<iata:Percentage>1.0</iata:Percentage>
<iata:PercentageAppliedToAmount CurCode="CHF">1.00</iata:PercentageAppliedToAmount>
<iata:PercentageAppliedToAmount CurCode="CHF">1.00</iata:PercentageAppliedToAmount>
</iata:Commission>
</iata:Commission>
<iata:Commission>
<iata:Commission>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:Amount CurCode="CHF">1.00</iata:Amount>
<iata:CommissionCode>SUPPLEMENTAL</iata:CommissionCode>
<iata:CommissionCode>SUPPLEMENTAL</iata:CommissionCode>
</iata:Commission>
</iata:Commission>
None Copy
Page: 256 of 377
It is common practice for a Seller to apply a margin to an Airline Offer before quoting a price to the
Customer.
This document describes the scenario in which the Seller is the Merchant of Record and the Airline
does not set the amount that is ultimately quoted to the Customer.
Out of Scope:
• Airline as Merchant of Record
• Airline sets the amount that is quoted to the Customer
01. Adding a Margin to an Offer01. Adding a Margin to an Offer
The process for the Seller to apply a margin to an Offer is possible by following the below process.
1. The Seller sends a Shopping Request to the Airline
2. The Airline responds with Offers and the price of each Offer, including applicable taxes, fees &
charges
3. The Seller may choose to add an additional amount (margin) to the Airline Offer and quote a
combined Airline Offer Price + Margin to the Customer
4. If the Seller wishes to proceed with the Order, the Seller asks the Airline to create an Order for
the amount quoted in the Airline Offer (less the margin),
5. The Seller collects payment from the Customer. The Seller can bill the customer for Airline
Price + Taxes, Fees & Charges + Margin in one single transaction
6. The Airline creates an Order for the amount agreed between Seller and Airline, including any
applicable taxes, fees and charges.
7. The Airline’s Order will not contain any record of the Seller’s margin
8. The Airline can mask the price so that it is not visible to the customer and can indicate to the
Seller that the price is masked, using the Price Mask Indicator
9. The Seller pays the Airline the agreed amount, the Airline Offer Price, via BSP/ARC
MarginsMargins
Page: 257 of 377
OverviewOverview
Time limits are a mechanism for the Airline to advise the Seller of upcoming events of expiry, for
example, the time when an Offer will expire, or when inventory will be removed if there has been no
commitment to the Order.
Time Limits should follow standard datetime and duration formats.
Time Limits within the Context of an OfferTime Limits within the Context of an Offer
Each of these time limits can be used in the context of any Offers within a message (e.g. Offer, A la
Carte Offer, Repriced Offer etc)
Offer Expiry Time LimitOffer Expiry Time Limit
The length of time an offer will persist in an airline’s offer management system for use in subsequent
transactions. Upon expiry, the expectation is that the offer is no longer retrievable, and the shopping
process must begin again. Note the presence of an Offer Time Limit does not indicate either a
guarantee of price or inventory against a given Offer item within the Offer.
Should the offer time limit expire, any other time limit also expires unless an Order has been created.
Advising an Offer ExpiryAdvising an Offer Expiry
An Airline may advise on the Seller of an Offer Expiry Time Limit at the **Offer Level **
Time LimitsTime Limits
Scope of ArticleScope of Article
Note the following Time Limits are out of scope of this document: Deposit Time Limit, Naming Time Limit,
Bilateral Time Limit and Inventory Gauarantee Time Limits.
Page: 258 of 377
Price Guarantee Time LimitPrice Guarantee Time Limit
The length of time the price of an offer item is guaranteed. In the absence of the price guarantee time
limit, the price is not guaranteed. Upon expiry, the price may no longer be guaranteed and either a
new shopping process should begin, or the offer should be repriced resulting in a new Offer.
Should the price guarantee time limit extend beyond Order creation, the remaining length of time
persists into the corresponding Order Item. The airline can increase the remaining length of time
beyond the original time limit should they wish to.
Note: Where a price guarantee time limit is applied, there is no guarantee that related inventory is
guaranteed by the airline against a given offer item.
Advising of a Price GuaranteeAdvising of a Price Guarantee
An Airline may return a Price Guarantee Time Limit at the Offer Item LevelOffer Item Level.
Payment Time Limit (as a Duration or DateTime)Payment Time Limit (as a Duration or DateTime)
This field is used to indicate the duration of time after Order creation that payment commitment is
required for an order item, or a static datetime in which payment commitment is required. If the
duration field has a value of 0 then then instant payment at order create is required. If no value is
returned, then no advice has been given.
For example:
PaymentTimeLimitDuration: PT48H3M6S - shows the amount of time.
PaymentTimeLimitDuration: PT0H0M0S - indicates instant payment is required.
PaymentTimeLimitDateTime: 2018-01-01 – shows a static payment commitment date time
For version 19.1, the Ticketing Time Limit was removed from the schemas, as if an Airline wishes to
communicate this information, it can be provided as a payment time limit.
<ALaCarteOffer>
<ALaCarteOffer>
<OfferExpirationTimeLimitDateTime>2004-06-
<OfferExpirationTimeLimitDateTime>2004-06-
25T14:36:56+02:00</OfferExpirationTimeLimitDateTime>
25T14:36:56+02:00</OfferExpirationTimeLimitDateTime>
<OfferID>GUID</OfferID>
<OfferID>GUID</OfferID>
</ALaCarteOffer>
</ALaCarteOffer>
None Copy
<ALaCarteOffer>
<ALaCarteOffer>
<!--...-->
<!--...-->
<ALaCarteOfferItem>
<ALaCarteOfferItem>
<OfferItemID>GUID</OfferItemID>
<OfferItemID>GUID</OfferItemID>
<!--...-->
<!--...-->
<PriceGuaranteeTimeLimitDateTime>2002-04-
<PriceGuaranteeTimeLimitDateTime>2002-04-
30T17:11:37+02:00</PriceGuaranteeTimeLimitDateTime>
30T17:11:37+02:00</PriceGuaranteeTimeLimitDateTime>
</ALaCarteOfferItem>
</ALaCarteOfferItem>
</ALaCarteOffer>
</ALaCarteOffer>
None Copy
Page: 259 of 377
The Payment Time Limit is contained within the Offer Item levelOffer Item level, for example an Airline can return the
following to indicate the duration of the payment time limit.
OR for indication of instant payment required:
OR to inform of a static payment time limit date time:
<iata:PaymentTimeLimitDuration>P1M7DT16H36M36S</iata:PaymentTimeLimitDuration>
<iata:PaymentTimeLimitDuration>P1M7DT16H36M36S</iata:PaymentTimeLimitDuration>
None Copy
<iata:ALaCarteOffer>
<iata:ALaCarteOffer>
<!--...-->
<!--...-->
<iata:ALaCarteOfferItem>
<iata:ALaCarteOfferItem>
<iata:OfferItemID></iata:OfferItemID>
<iata:OfferItemID></iata:OfferItemID>
<!--...-->
<!--...-->
<iata:PaymentTimeLimit>
<iata:PaymentTimeLimit>
<iata:PaymentTimeLimitDuration>P1M7DT16H36M36S</iata:PaymentTimeLimitDuration>
<iata:PaymentTimeLimitDuration>P1M7DT16H36M36S</iata:PaymentTimeLimitDuration>
</iata:PaymentTimeLimit>
</iata:PaymentTimeLimit>
<!--...-->
<!--...-->
</iata:ALaCarteOfferItem>
</iata:ALaCarteOfferItem>
</iata:ALaCarteOffer>
</iata:ALaCarteOffer>
None Copy
<iata:PaymentTimeLimitDuration>P1M7DT16H36M36S</iata:PaymentTimeLimitDuration>
<iata:PaymentTimeLimitDuration>P1M7DT16H36M36S</iata:PaymentTimeLimitDuration>
None Copy
<iata:ALaCarteOffer>
<iata:ALaCarteOffer>
<!--...-->
<!--...-->
<iata:ALaCarteOfferItem>
<iata:ALaCarteOfferItem>
<iata:OfferItemID></iata:OfferItemID>
<iata:OfferItemID></iata:OfferItemID>
<!--...-->
<!--...-->
<iata:PaymentTimeLimit>
<iata:PaymentTimeLimit>
<iata:PaymentTimeLimitDuration>PTM0DT0H0M0S</iata:PaymentTimeLimitDuration>
<iata:PaymentTimeLimitDuration>PTM0DT0H0M0S</iata:PaymentTimeLimitDuration>
</iata:PaymentTimeLimit>
</iata:PaymentTimeLimit>
<!--...-->
<!--...-->
</iata:ALaCarteOfferItem>
</iata:ALaCarteOfferItem>
</iata:ALaCarteOffer>
</iata:ALaCarteOffer>
None Copy
<iata:ALaCarteOffer>
<iata:ALaCarteOffer>
<!--...-->
<!--...-->
<iata:ALaCarteOfferItem>
<iata:ALaCarteOfferItem>
<iata:OfferItemID>GUID</iata:OfferItemID>
<iata:OfferItemID>GUID</iata:OfferItemID>
<!--...-->
<!--...-->
<iata:PaymentTimeLimit>
<iata:PaymentTimeLimit>
<iata:PaymentTimeLimitDateTime>2011-09-
<iata:PaymentTimeLimitDateTime>2011-09-
27T20:07:52</iata:PaymentTimeLimitDateTime>
27T20:07:52</iata:PaymentTimeLimitDateTime>
</iata:PaymentTimeLimit>
</iata:PaymentTimeLimit>
<!--...-->
<!--...-->
None Copy
Page: 260 of 377
Time Limits within the Context of an OrderTime Limits within the Context of an Order
Payment Time LimitPayment Time Limit
The time limit by which a commitment to pay must be made for the given Order Item. Upon expiry it is
expected that the Order item is removed from the Order. If no value is returned, then no advice has
been given.
For example:
PaymentTimeLimitDateTime: 2015-01-01T12:53:12Z - indicates the date time by which
payment commitment is required.
For version 19.1, the Ticketing Time Limit was removed from the schemas, as if an Airline wishes to
communicate this information, it can be provided as a payment time limit. Note that the Duration
Option is not available within the within an Order, as the Duration is relative to Order creation, hence
simply a datetime is used.
Requesting to place an Order on HoldRequesting to place an Order on Hold
A Seller may request to create an Order with the absence of payment.
Advising the Seller of the Payment Time LimitsAdvising the Seller of the Payment Time Limits
An Airline may return a Payment Time Limit element which is set at an Order Item levelOrder Item level.
</iata:ALaCarteOfferItem>
</iata:ALaCarteOfferItem>
</iata:ALaCarteOffer>
</iata:ALaCarteOffer>
<Order>
<Order>
<!--...-->
<!--...-->
<OrderID>XBXXX1A2B3C4D</OrderID>
<OrderID>XBXXX1A2B3C4D</OrderID>
<!--...-->
<!--...-->
<OrderItem>
<OrderItem>
<!--...-->
<!--...-->
<OrderItemID></OrderItemID>
<OrderItemID></OrderItemID>
<PaymentTimeLimitDateTime>2018-08-13T13:59:38Z</PaymentTimeLimitDateTime>
<PaymentTimeLimitDateTime>2018-08-13T13:59:38Z</PaymentTimeLimitDateTime>
<!--...-->
<!--...-->
</OrderItem>
</OrderItem>
</Order>
</Order>
None Copy
Page: 261 of 377
If an Airline decides to guarantee a price to the Seller/Customer, the Airline may wish to guarantee a
part of the total price.
As well, in such scenario, the price guarantee time limit should not exceed the payment time limit.
Payment time limit can be longer than the price guarantee time limit. If the price guarantee is expired, a
repricing is recommended before payment.
The Airline can either use the Price Guarantee Time Limit Date Time to specify that the price is
guaranteed without specifying (within the message) what part (if not all) of the Price is guaranteed. Or,
the airline can describe (and change) the guarantees depending on the pricing component (Amount,
Fee or Tax).
The Amount, Fee and Tax time limits only need to be taken into account if the Price Guarantee Time
Limit has been populated. If so, the Price Guarantee Time Limit shall be the maximum time limit for all
Tax, Amount and Fee limits
The below table shows two scenarios for guaranteeing a price to the Seller:
1. Within the Price Guarantee Time Limit, the Airline guarantees the total price (base amount,
surcharge and taxes) for a total of 30 minutes.
2. Within the Price Guarantee Time Limit, the Airline guarantees the Base fare and a Tax for 5
days, but only the other tax for 4 hours, and the surcharge for 30 minutes.
Granular Price Time LimitsGranular Price Time Limits
NoteNote
The breakdown of price guarantee within the Order can also be implemented in the Offer and vice versa.
Page: 262 of 377
Issue Issue
In May 2020, acting on behalf of its members across the banking and finance industry, UK Finance
published guidance for Strong Customer Authentication specific to the Travel & Hospitality sector.
Their guidance documentation states:
“This communication provides important information for businesses of all sizes looking to avoid
customers experiencing declined e-commerce transactions after the UK’s Strong Customer
Authentication enforcement deadline of 14 September 2021 and the EU’s deadline of the 31
December 2020. After this point card issuers will begin to decline non-compliant transactions. We
actively encourage participants outlined in the above section to read the content of this
communication and to get in touch with your payment provider (otherwise known as an acquirer or
gateway). This should be done with urgency due to the implementation lead times and testing
period required.”
The purpose of this change request is to ensure that NDC standards, practice and guidance relating
to customer authentication are in line with those of:
Other stakeholders in the value chain, for example:
Card schemes
Payment service providers
Digital wallet providers
Technology providers (in the wider payments space)
Others
Other entities in the travel and hospitality sectors, for example:
Travel agents
Hotels
Car hire providers
Others
So that airlines implementing the latest NDC standards do not experience an increase in declined e-
commerce transactions once enforcement commences. The new enforcement date is 14 September
2021 in the UK and 31 December 2020 across the rest of the EU. As a result, UK card issuers will be
required to decline all non-SCA-compliant transactions after 14 September 2021. In the run up to
these dates, some markets will introduce soft decline mechanisms for transactions above a certain
value. As a result, all airlines, sellers and technology providers using NDC and One Order:
Should be ready to support SCA in advance of these dates
Must be ready to support SCA from these dates
Business Requirements Business Requirements
Background Background
Strong Customer Authentication (SCA) is a set of rules that defines how individuals and businesses
confirm their identity when making purchases online using more than one of the following factors:
Secure Customer AuthenticationSecure Customer Authentication
Page: 263 of 377
Something you know – such as a password or phrase
Something you have – such as a token generator
Something you are – such as biometric data
Its purpose is to protect the individual or business making payment from experiencing payment fraud.
Following its implementation, individuals or businesses shopping online will need to undertake extra
steps to confirm their identity when paying.
All parties involved in a payment transaction are required to enable the payer to authenticate their
actions in a manner compliant with the underlying regulation. UK SCA determines 3 different scenarios
for the Travel & Hospitality Industry. These map to three existing industry models
ScenarioScenario DescriptionDescription
D etai l D etai l
Exi sti ng IndustryExi sti ng Industry
capab i li tycapab i li ty
AA T he Booking AgentThe Booking Agent
authenticates theauthenticates the
cardholder, and thecardholder, and the
supplier of thesupplier of the
travel & hospitalitytravel & hospitality
service collects theservice collects the
payment.payment.
In this scenario the
Booking Agent must
send the
authentication and
other associated
payment data to the
merchant (via
intermediaries) and
the merchant requests
payment authorization
to collect the funds
associated with the
booking or to get
confirmation of the
authenticated MIT
agreement from the
issuer
NDC with customer
payment
BB T he Booking AgentThe Booking Agent
authenticates theauthenticates the
cardholder andcardholder and
collects thecollects the
payment from thepayment from the
customer on behalfcustomer on behalf
of the Travel &of the Travel &
Hospitality supplier.Hospitality supplier.
In this scenario, the
Booking Agent after
authentication
requests the payment
authorization to collect
the funds associated
with the booking or to
get confirmation of the
authenticated MIT
agreement from the
issuer. It then passes
associated payment
data to the supplier to
enable it to collect any
additional payments it
is authorised to
collect, as Merchant
Initiated Transactions
(MITs), under the
terms of the booking
agreement with the
customer
GDS-intermediated
model
Example of Secure Customer AuthenticationExample of Secure C ustomer Authentication
A card issuer (e.g. a bank) may require a customer to enter a passcode they have provided via text message in
order to verify their purchase prior to payment authorization. If this step is not carried out, payment is likely to be
refused.
Page: 264 of 377
CC No authentication isNo authentication is
performed by theperformed by the
Booking Agent asBooking Agent as
the transaction isthe transaction is
out of scope (oneout of scope (one
leg out or MOT O, orleg out or MOT O, or
anonymous card) oranonymous card) or
qualifies for anqualifies for an
exemption (e.g.:exemption (e.g.:
secure corporatesecure corporate
payment) and thepayment) and the
supplier of thesupplier of the
travel & hospitalitytravel & hospitality
service collects theservice collects the
payment.payment.
In this scenario, the
data relative to the out
of scope/exemption
must be passed
onwards to the Travel
& Hospitality supplier
along with other
payment data for it to
perform its own
authorization request
as the merchant of
record.
Note: Note: BookingBooking
Agents should notAgents should not
request exemptionsrequest exemptions
at theat the
authentication stageauthentication stage
of transactions forof transactions for
which they are notwhich they are not
collecting the fundscollecting the funds
unless they have aunless they have a
specific agreementspecific agreement
with the travelwith the travel
supplier (thesupplier (the
merchant) and itsmerchant) and its
acquirer to doacquirer to do
so.so. This is essential
as the use of
exemptions is the
prerogative of the
merchant’s acquirer,
not that of an Agent.
The secure corporate
payment exemption
can generally be used
when the booking is
initiated from a
dedicated corporate
processes which is not
available to
consumers and which
is considered secure.
Typically only Travel
Management
Companies (TMC’s)
will be permitted to
use this exemption.
NDC with customer
payment ANDAND GDS-
intermediated model
This document outlines 4 key requirements for SCA within NDC:
1. An ability for an airline to determine whether authentication is required for a payment
2. An ability for a seller to initiate the authentication of a payer making a payment
3. An ability for an airline to create the authorization request for a payment made by an
NoteNote
It is assumed that a capability to determine whether a transaction falls into Category A or Category C is in
scope for NDC. Similarly, it is assumed that Category B is out of scope for NDC.
Page: 265 of 377
authenticated payer
4. An ability for an airline to request a seller to initiate the authentication request after
authorization
Whilst these requirements must be met across a number of different authentication / authorization
models, this document is only concerned with scenarios where the Seller Initiates Authentication on
behalf of the Airline who will authorise payment (Scenario A and C above). At present, this represents
two authentication models:
Seller authenticates via 3DS 2.x OR
Seller authenticates via another solution provided by a third party
Across two core payment flows
1. Shop -> Price -> Order -> Pay
2. Shop -> Price -> Pay -> Order
Requirements Requirements
1. Determine Need to Authenticate Payment 1. Determine Need to Authenticate Payment
A function to determine a need to authenticate has two core uses. One is to determine prior to
authorization whether to authenticate or not. The other is to determine how to authenticate when
authorization was refused with a ‘soft decline’, but decline indicates that authentication is required.
Requirement 1 outlines the former. The latter is outlined in requirement 4.
As a seller, I need to know if I must authenticate a payer or not so that an airline can create the
authorization request
As an airline, I need to determine what type of payment transaction a seller has initiated so that
I can determine whether authentication is needed before going to authorization
2. Authenticate Payer 2. Authenticate Payer
Once it has been determined that a customer needs to authenticate, a seller needs to initiate
authentication. This requirement assumes that the seller knows he should authenticate the customer
prior to a customer committing to pay for an order.
As an airline, I may need to provide information to the seller so that they can authenticate a
customer
As a seller, I need to authenticate a customer so that an airline can proceed to authorization
As a seller, I need to return information about the authentication to the airline so that they can
proceed to authorization
3. Authorize Payment by Authenticated payer 3. Authorize Payment by Authenticated payer
Once a customer has been authenticated, the airline will need to provide information about the
customer authentication in the authorization request.
NoteNote
As well as NDC messages between airline and sellers, OneOrder messages may need to be updated to
support Secure Customer Authentication. If necessary, this will be covered in a new CR.
Page: 266 of 377
As an airline, I need to receive the authentication attempt result from the seller so that I can
proceed to authorization
4. Communicate Need to Authenticate a Payment 4. Communicate Need to Authenticate a Payment
If either:
1. An Airline determines that a payer needs to be authenticated prior to attempting authorization
OR
2. An authorization is declined due to a lack of authentication (‘a soft decline’)
An airline should indicate to the seller that the payer must authenticate to complete the payment
transaction.
As an airline, I need to inform a seller that authentication is needed in order to proceed to
authorization of a given payment transaction
As a seller, I need to allow the payer to authenticate in order to complete a given payment
transaction
Business Process ModelBusiness Process Model
Page: 267 of 377
Business FunctionsBusiness Functions
Provide Card Authentication MethodProvide Card Authentication Method
InitiatorInitiator AirlineAirline
DescriptionDescription The Airline is providing Card Authentication method to the Seller
Action(s)Action(s) Inform
ActorsActors Airline Seller
DomainDomain Shop/Price
Key dataKey data Authentication method
3DS1.x
3DS2.x
Page: 268 of 377
ResultResult The seller knows the authentication method that would be needed to
authenticate a payer’s given payment method
Provide Card Authentication CriteriaProvide Card Authentication Criteria
InitiatorInitiator AirlineAirline
DescriptionDescription The Airline is providing Card Authentication Criteria to the seller
Action(s)Action(s) Inform
ActorsActors Airline Seller
DomainDomain Shop/Price
Key dataKey data Data identified in CR129
ResultResult The seller knows the authentication criteria needed to authenticate a payer
given their payment method
Provide Card Payment DetailsProvide Card Payment Details
InitiatorInitiator CustomerCustomer
DescriptionDescription The customer is providing the Card Payment details to the seller
Action(s)Action(s) Pay
ActorsActors Payer Seller
DomainDomain Order
Key dataKey data Card number
Expiry date
Card Verification Value
ResultResult The payer is able to provide Payment Card information to the seller
Provide Card Payment DataProvide Card Payment Data
InitiatorInitiator SellerSeller
DescriptionDescription The seller is providing Card Payment details to the airline
Action(s)Action(s) Pay
ActorsActors Seller Airline
DomainDomain Order
Key dataKey data Card number/ Token Number
Card Brand
Card expiry date
CVV2/CVC2 value
ResultResult The seller is able to pass Payment Card information to the airline
Page: 269 of 377
Provide Card Authentication DataProvide Card Authentication Data
InitiatorInitiator SellerSeller
DescriptionDescription The Seller is providing Card Authentication data to the airline
Action(s)Action(s) Pay
ActorsActors Seller Airline
DomainDomain Order
Key dataKey data Data identified in CR129
Data specified by UKFA
Payment Trx Channel Code
Card Number Collection
Code
Payer Authentication
Exemption Code
Payer Authentication Failure
To Complete Code
Authentication Token Value
ResultResult The seller is able to pass authentication data to the airline
Provide Card Payment Status DataProvide Card Payment Status Data
InitiatorInitiator AirlineAirline
DescriptionDescription The Airline provides payment status information back to the seller
Action(s)Action(s) Pay
ActorsActors Airline Seller
DomainDomain Order
Key dataKey data Order action success
Order action failure
OrderID (Optional)
Payment action success
Payment action failure
Payment ID (Optional)
ResultResult The airline has received an authorization approval code or an error code and the
seller is informed of the payment status
Request Payer AuthenticationRequest Payer Authentication
InitiatorInitiator AirlineAirline
DescriptionDescription The airline notifies the seller that a payment requires that the payer must
authenticate before authorisation will succeed
Action(s)Action(s) Pay
ActorsActors Airline Seller
Page: 270 of 377
DomainDomain Order
Key dataKey data Payment ID (Optional)
Order ID (Optional)
Data outlined in “ProvideProvide
Card AuthenticationCard Authentication
Criteria”Criteria”
ResultResult The seller knows that a payer must authenticate for a given payment transaction to
proceed.
Data ModelData Model
New ElementsNew Elements
New Value TypesNew Value Types
Page: 271 of 377
IssueIssue
In May 2020, acting on behalf of its members across the banking and finance industry, UK Finance
published guidance for Strong Customer Authentication specific to the Travel & Hospitality sector.
In order to meet the requirements of this guidance, the customer payment group initiated a package of
changes introduced in CR199 – Secure Customer Authentication CR199 – Secure Customer Authentication to ensure that airlines
implementing the latest NDC standards do not experience an increase in declined e-commerce
transactions once enforcement commences.
The purpose of this CR is to provide a sample package that will allow implementors to understand
how to back port these capabilities into augmentation points within earlier versions of the schema
Business RequirementsBusiness Requirements
1. Integrate SCA capabilities into previous schema1. Integrate SCA capabilities into previous schema
As an airline using existing NDC functionality, I need additional capabilities not currently available to
me in order to meet the Secure Customer Authentication requirements outlined in CR199
2. Provide a worked example outlining how to integrate into a previous2. Provide a worked example outlining how to integrate into a previous
schemaschema
As an airline using existing NDC functionality, I need guidance as to how I could augment my current
messages to provide additional capabilities
Business Process ModelBusiness Process Model
See Secure Customer Authentication for guidance
Business FunctionsBusiness Functions
See Secure Customer Authentication for guidance
Data ModelData Model
See Secure Customer Authentication for guidance
Example PackagesExample Packages
17.2 Example and Guidance17.2 Example and Guidance
Backport_SecurePayment_17.2_v1.0_rc2.zip
18.1 Examples and Guidance18.1 Examples and Guidance
Backport_SecurePayment_18.1_v1.0_rc1.zip
Secure Customer Authentication BackportSecure Customer Authentication Backport
Page: 272 of 377
Page: 273 of 377
Targeting release 17.2 and onwards Targeting release 17.2 and onwards
What is a Voucher in Offers and Orders? What is a Voucher in Offers and Orders?
A voucher in offers and orders is understood to be a reference to stored value in an airlines internal
system which can be used later. Vouchers do not have specific definitions in the Offer and Order
messages apart from when selecting your payment method where a Voucher is explicitly defined.
Vouchers can be fulfilled by the Airline and within the Offer and Order messages using one of three
similar, but different ways:
Using an Electronic Miscellaneous Document (EMD-S)
Using a Ticket
Using an asset that is not an Order.
Support for Vouchers in Offers and Orders Support for Vouchers in Offers and Orders
This section describes the guidelines around using the existing standard flows for consuming a
voucher programmatically using the Offer and Order messages of the Enhanced Distribution
Standards to create or modify an existing Order. This section addresses more into details the following
three scenarios:
1. Re-shopping an existing Order using a Document (Ticket or EMD) 1. Re-shopping an existing Order using a Document (Ticket or EMD)
This scenario assumes an existing Order is still available and retrievable in the airlines OMS via the
Offer and Order messages. In this scenario, the Seller simply re-shops for new flights and services
using the standard re-shopping flows.
2. Paying for a new Order using a Document in an existing order (Ticket or2. Paying for a new Order using a Document in an existing order (Ticket or
EMD) EMD)
This scenario assumes there is no current Order and a new Order needs to be created. This follows
the same standard flow to create a new order with deferred payment. At this stage, an Order is
created, and the Voucher can be consumed using Order Change following the same flow as the first
scenario.
3. Paying for a new Order Using an asset that is not an Order 3. Paying for a new Order Using an asset that is not an Order
Voucher can be used as a form of payment for any sale done on NDC channel using the classic initial
sale flow.
VouchersVouchers
Important NoteImportant Note
Please note that this implementation guidance has been produced based on the 17.2 and 18.1 release to aid
airlines in programmatically consuming vouchers for changing or creating new Orders. This guidance may also
be used in later releases if appropriate. Also note that the use of Vouchers within the standard is under review for
future enhancements to cater for better distribution, delivery and accounting processes.
Page: 274 of 377
Paying for an Existing Order using a Document (Ticket or EMD) Paying for an Existing Order using a Document (Ticket or EMD)
An existing Order can be changed using the current Offer and Order re-shopping messages using the
current Change of Itinerary flow, see this flow on the Implementation Guide website.
Initially the airline could send an OrderChangeNotif advising the Seller there was a change to the
Order and a Ticket or EMD is available for reuse. The Seller could then, at a later stage, retrieve the
Order from the airline to refresh the Order prior to making the customers desired change. The change
flow would commence using OrderReshop. The Customer would choose their new flights as per
normal to which the Seller would forward the request to the airline including the Customers voucher
information in OrderReshopRQ. The airline can return the price differential taking into account the
voucher value when returning new Offers. Once the Customer has selected the new Offer, the Offer
can be sent through OrderChangeRQ with any additional payment information, if required, to execute
this change. The OrderViewRS message will return the updated Order and ticket information. If there
is any residual value on the voucher (be it an EMD or Ticket) this can also be shown in the response,
at this stage.
Additional Information needed from the SellerAdditional Information needed from the Seller
OrderReshopRQ: OrderReshopRQ: Requires the Seller to add the document Information to the request including the
document number, document type and associated passenger.
OrderChangeRQ: OrderChangeRQ: If the Voucher is a document then no additional information is needed in Payment
Method, as the document information will already be known by the airline from the selected Offer.
OrderViewRS: OrderViewRS: Airline may send back the previously exchanged tickets with the ‘Exchanged’ status
along with any new documents which show a residual value after the Order has been purchased.
Suggested Preconditions Suggested Preconditions
The Airline is not holding inventory
The Airline has the original
Order Suggested Message FlowOrder Suggested Message Flow
The below flow is a guideline based off the standard Change of Itinerary flow found on the
Implementation Guide.
Important NoteImportant Note
While the first two scenarios were based on the exchanging of the underlying tickets, an asset that is not an
Order can also be used for this scenario if preferred. Additionally, the airline can use a Ticket or EMD if preferred
while using the third scenario if preferred.
Page: 275 of 377
Paying for a New Order using a Document in an existing order (Ticket orPaying for a New Order using a Document in an existing order (Ticket or
EMD) EMD)
A new Order can be created using the current Offer and Order shopping flow as described on the
Implementation Guide for shopping and ordering using deferred payment. Initially the Seller would
shop for flights and ancillaries as per normal up to the point of order creation, where the Seller would
then use the deferred payment flow. The Seller would create the order without payment and receive
the Order information in OrderViewRS along with a payment time limit.
At this stage, the same flow is used as Paying for an Existing Order using a Document (Ticket or
EMD); the Seller will send in the document information using OrderReshop to get the differential
between the document value and the amount owing for the Order. The airline may need the document
number, document type, and the association with the passenger.
Once the Customer confirms the intention to commit, OrderChange can be used to change the Order
with the selected Offer and any additional payment required.
The OrderViewRS message will return the updated Order and ticket information. If there is any
residual value on the voucher (be it an EMD or Ticket) this can also be shown in the response, at this
stage.
Additional Information needed from the Seller Additional Information needed from the Seller
OrderReshopRQ:OrderReshopRQ: Requires the Seller to add the document Information to the request including the
document number, document type and associated passenger.
OrderChangeRQ:OrderChangeRQ: If the Voucher is a document then no additional information is needed in Payment
Method, as the document information will already be known by the airline from the selected Offer.
OrderViewRS: OrderViewRS: Airline may send back the previously exchanged tickets with the ‘Exchanged’ status
along with any new documents which show a residual value after the Order has been purchased.
Page: 276 of 377
Suggested PreconditionsSuggested Preconditions
The Airline is not holding inventory
The Airline has no existing Order
Suggested Message Flow Suggested Message Flow
The below flow is a guideline based off the standard Shopping and Ordering with Deferred Payment
and Change of Itinerary flow found on the Implementation Guide.
Paying for a new Order Using an asset that is not an Order Paying for a new Order Using an asset that is not an Order
As an additional scenario, any airlines using vouchers outside the context of an Order may simply use
the standard payment flow. A new Order can be created using the current Offer and Order shopping
flow (AirShopping, OfferPrice, OrderCreate).
The Seller would shop for flights and ancillaries as per normal. When the Seller would provide the
payment methods (either OrderCreate or OrderChange) he can simply add the Voucher as a Form of
Payment along with any additional form of payments needed.
The OrderViewRS message will return the updated Order. If the airline is using NDCLink, the reporting
of the payment should note that the value of the voucher is already stored on the airline side (and not
treated as cash) by simply providing a specific (airline internal) Form of payment.
Page: 277 of 377
In case the voucher is supported by a document outside of the Order context, the airline should take
the appropriate actions to close the documents (most likely through an internal refund).
Suggested Message Flow Suggested Message Flow
Payment at OrderCreate Payment at OrderCreate
Payment at OrderChangePayment at OrderChange
Displaying Voucher Rules or Conditions Displaying Voucher Rules or Conditions
If the Voucher is a Ticket or EMD, the rules associated to the Voucher can be returned with Penalty
information within the referenced Penalty List (within data lists) from the Ticket.
Rules can be added to the Penalty structure. The Penalty Attributes and the
Penalty/ApplicableFeeRemarks elements should be used to define the applicable rules associated to
this voucher.
Retrieving Voucher Information 17.2 to 18.1 Retrieving Voucher Information 17.2 to 18.1
Page: 278 of 377
If the Voucher is a Ticket or EMD, the Seller may request the retrieval of the document using
OrderRetrieveRQ, to which the Airline will return an OrderViewRS with the TicketDocInfo and any
related Order.
In 17.2 and later the Order is required when returning OrderViewRS. If you have an Order, the Airline
shall return the order, however for this scenario, if no Order is available, the Order/Order Items
element may be seen as optional.
If there is no Order and the Airline decides to not return any Order Items, then the Airline needs to
state this by returning dummy data in the Order element. Airline to set the Order ID as ‘dummy’.
If the Airline does not return an Order, the flow “Paying for a New Order using a Document (Ticket or
EMD)” should be used to create and pay for an Order. If the order is returned, the Seller can use the
flow “Paying for an Existing Order using a Document (Ticket or EMD)” to re-shop.
Please note that the order is required to be returned from 19.2 onwards.
Not Supported Not Supported
Within the Offer and Order messages, there has not previously been a requirement to support the
creation of a Voucher without the previous cancellation of an Order (for example to buy an ad-hoc
voucher for a gift). Additionally, there has not been a need to specifically return the status of a voucher
outside the context of an Order for a voucher status or current balance; however, this can be achieved
through the TicketDocInfo structures if the Voucher is an Electronic Document.
Page: 279 of 377
IntroductionIntroduction
Special Service Requests (SSR) are best described as snippets or strings of information in an Airline
Reservations System that are formatted for programmatic use and ingestion to describe a service or
additional piece of information that is required about the passenger. Initially SSR’s were used for
special requests (such as a wheelchair request) at the Airport and are only sent to carriers
participating in the Itinerary prior to travel. However, their flexibility has lead them to be used for a
variety of purposes over the years and are used to store non service related items, such as email
addresses, postal address, GST information, disabled information etc. In the move to distribution over
XML using the standards set forth by the Offers and Orders Groups, the notion of a traditional ‘SSR’
as a formatted string does not conform to the transmission standards of today where XML, JSON or
other is being used.
This section describes how the SSR information should be modelled and carried through new
distribution messages.
The benefit of mapping the SSR information into the model allows for:
A standardized way for Sellers to request and receive services
A richer model for information to be broadcast and received
The ability for a Seller to interact with a carrier using a PSS and SSRs and a Carrier using an
Order Management system in the same manor
Minimal impact for a Seller if an airline changes their internal service delivery fulfilment.
This section will detail how SSR’s that are used today and how they should be mapped to an XML
message for Sellers and interline parties to understand and use. The use of an SSR within the context
of an XML message will enable the reconstruction of an SSR on either side. There is no loss of
information, but a standardized way to communicate this information across parties.
OverviewOverview
Page: 280 of 377
CategorisationCategorisation
SSR’s have been broken into multiple categories to best determine their mapping to an XML message.
The following categories have been created and used to describe the function of the SSR within
Enhanced Distribution.
ServiceService
An SSR will be defined as a Service if it:
A SSR that delivers a ‘service on demand’ and which may follow through as a service item in
an Order Management system.
An SSR that does not require specific information over that of a ServiceDefinition as modelled
in the AIDM.
All Service SSR’s will be mapped to a Service Item using the format set forth in Service items Section.
Note that a Servi ce may also requi re ‘Informati on’ and has been descri bed so withi n theNote that a Service may al so require ‘Informati on’ and has been descri bed so wi thi n the
Servi ces Secti on.Servi ces Secti on.
InformationInformation
A SSR that does not deliver a specific service to the passenger.
A SSR that has specific data requirements outside the scope of a ServiceDefinition.
All Information SSR’s will be mapped depending on their attributes in existing elements or added to the
Offers or Order Group queues to add missing information. Each implementation will be specific as they
require specific information.
Information SSR’s can be further Categorized into the following areas:
Offer Related,
Payment Related,
Passenger Related (Info or Preference).
ObsoleteObsolete
A SSR that is no longer relevant within Enhanced Distribution (for example a some of the OTHS
SSR’s that are used today as a messaging vehicle to call for action from Airlines to Agents).
Airline OwnAirline Own
Airline specific SSR’s will not be mapped within, however the principle for mapping (service /
Information etc) should be treated as the same.
SSR CategorisationSSR Categorisation
Page: 281 of 377
OtherOther
SSR's that do not fit in the above categories.
Page: 282 of 377
This page contains the SSR’s which have been identified as a service and will be documented within
this section.
SSRSSR SSR nameSSR name
RequestRequest
ContextContext
ResponseResponse
ContextContext
ServiceService
CategorisationCategorisation
StructureStructure
AOXY Airline Supplied Oxygen
Passenger
Preference
Service Medical
AVIH Animal in Hold
Passenger
Preference
Service Baggage
AVML Vegetarian Hindu meal
Passenger
Preference
Service Meal
BBML Baby meal
Passenger
Preference
Service Meal
BIKE Bicycle
Passenger
Preference
Service Baggage
BLML Bland meal
Passenger
Preference
Service Meal
BLND Blind Passenger
Passenger
Info
Service Passenger
BSCT Bassinet/carrycot/baby basket
Passenger
Preference
Service Seat
BULK Bulky Baggage
Passenger
Preference
Service Baggage
CBBG Cabin Baggage
Passenger
Preference
Service Baggage
CHML Child meal
Passenger
Preference
Service Meal
COUR Courier
Passenger
Preference
Service Baggage
DBML Diabetic meal
Passenger
Preference
Service Meal
DEAF Deaf Passenger
Passenger
Info
Service Passenger
DPNA
Disabled passenger with intellectual or
developmental disability needing
assistance
Passenger
Info
Service Passenger
ESAN
Passenger with Emotional
Support/Psychiatric Assistance Animal in
Cabin
Passenger
Preference
Service Baggage
EXST Extra seat
Passenger
Preference
Service Seat
FPML Fruit Platter meal
Passenger
Preference
Service Meal
FRAG Fragile Baggage
Passenger
Preference
Service Baggage
FQTU
Frequent traveler requesting redemption
for upgrade at the same time as obtaining
accrual
Passenger
Preference
Offer Loyalty
GFML Gluten intolerant
Passenger
Preference
Service Meal
List of Service SSRsList of Service SSRs
Page: 283 of 377
HNML Hindu meal
Passenger
Preference
Service Meal
KSML Kosher meal
Passenger
Preference
Service Meal
LCML Low calorie meal
Passenger
Preference
Service Meal
LFML Low fat meal
Passenger
Preference
Service Meal
LSML Low salt meal
Passenger
Preference
Service Meal
MAAS Meet and assist
Passenger
Preference
Service Other
MEQT Medical Equipment
Passenger
Info
Service Medical
MOML Moslem meal
Passenger
Preference
Service Meal
NLML Low lactose meal
Passenger
Preference
Service Meal
NOML No meal
Passenger
Preference
Service Meal
PDBG Prepaid baggage (chargeable)
Passenger
Preference
Service Baggage
PDCO Carbon Offset (chargeable)
Passenger
Preference
Service TBC
PDFF Frequent Flyer (chargeable)
Passenger
Preference
Service Passenger
PDIE In-Flight Entertainment (chargeable)
Passenger
Preference
Service IFE
PDLG Lounge (chargeable)
Passenger
Preference
Service Lounge
PDML Meal/beverage (chargeable)
Passenger
Preference
Service Meal
PDPT Pets (chargeable)
Passenger
Preference
Service Baggage
PDRO Rule override (chargeable)
Passenger
Preference
Service TBC
PDSB Standby (chargeable)
Passenger
Preference
Service TBC
PDST Store (chargeable)
Passenger
Preference
Service TBC
PDUG Upgrades (chargeable)
Passenger
Preference
Service Loyalty
PDUM Unaccompanied Minor (Chargeable)
Passenger
Info
Offer PDUM
PETC Animal in Cabin
Passenger
Preference
Service Baggage
POXY Passenger Own Oxygen
Passenger
Preference
Service Medical
PPOC Personal Portable Oxygen Concentrator
Passenger
Preference
Service Medical
RVML Vegetarian raw meal
Passenger
Preference
Service Meal
SFML Seafood meal
Passenger
Preference
Service Meal
Page: 284 of 377
SEAT Seat Request
Passenger
Preference
Service Seat
SPML Special meal
Passenger
Info
Service Meal
STCR Stretcher Passenger
Passenger
Preference
Service Medical
SVAN Passenger with Service Animal in Cabin
Passenger
Info
Service Baggage
UMNR Unaccompanied minor
Passenger
Info
Service Other
VGML Vegetarian vegan meal
Passenger
Preference
Service Meal
VJML Vegetarian Jain meal
Passenger
Preference
Service Meal
VLML Vegetarian lacto-ovo meal
Passenger
Preference
Service Meal
VOML Vegetarian oriental meal
Passenger
Info
Service Meal
WCBD Wheelchair - Non-spillable battery
Passenger
Info
Service Medical
WCBW Wheelchair - Wet cell battery
Passenger
Info
Service Medical
WCHC
Wheelchair - C for Cabin (Passenger
totally immobile)
Passenger
Info
Service Medical
WCHR
Wheelchair - R for Ramp (Passenger can
ascend/descend steps and make own way
to/from cabin seat but requires wheelchair
for distance to/from aircraft)
Passenger
Info
Service Medical
WCHS
Wheelchair - S for Stairs (Passenger
cannot ascend/descend steps, but is able
to make own way to/from cabin seat)
Passenger
Info
Service Medical
WCLB Wheelchair - Lithium ion battery
Passenger
Info
Service Medical
WCMP Wheelchair - Manual power
Passenger
Info
Service Medical
WCOB On-board Wheelchair (provided by airline)
Passenger
Preference
Service Medical
WEAP Weapon
Passenger
Preference
Service Baggage
XBAG Excess baggage
Passenger
Preference
Service Baggage
Page: 285 of 377
All Service categorized SSR’s will be defined accordingly to the below mapping from the AIDM Model.
Note that each SSR needs to be added to its own containing Offer Item Section, in order for the
SSR/Service to be cancelled.
ObjectObject ElementElement SSR ElementSSR Element ExampleExample
ServiceDefinition OwnerCode Airline or CRS Designator BB
ServiceDefinition ServiceCode SSR Element Code Airline Own Designated Identifier
ObjectObject ElementElement SSR ElementSSR Element ExampleExample
Service PaxRefID Name Element -1BLAKE/ANDREW
Service PaxSegmentRefID Flight Segment or Flight Leg BNESYDBB123Y6SEP
Service Status Code Action/Status/Advice Code NN
ObjectObject ElementElement DescriptionDescription
SSRSSR
ElementElement
ExampleExample
N/A N/A
Service items are unique to each and every service
so they can be delivered and accounted for.
Therefore a new service will be created for each and
every service.
Number
of
services
1
N/A N/A
Service items are unique to each and every service
so they can be delivered and accounted for.
Therefore a new service will be created for each and
every service.
Number
of
services
-1-
ObjectObject ElementElement DescriptionDescription
SSRSSR
ElementElement
ExampleExample
TBC TBC
Depending on the SSR, this could simply be a Name
of a service, in which case it would be mapped to the
Name Field in the AIDM, or a Description in which
case it would be mapped to the Description field.
Free
Text
.FREE
TEXT
Service Category MappingService Category Mapping
Page: 286 of 377
Business FunctionBusiness Function
To advise the airline of a passenger travelling with a bike. This will allow the airline to determine the
pricing and the acceptance on the aircraft.
TypeType
Service
ScopeScope
Seller <-> Airline
Airline <-> Airline
SSR ExampleSSR Example
Mapping in Enhanced DistributionMapping in Enhanced Distribution
SSRSSR SSR ElementSSR Element NDC XPathNDC XPath ReqReq
BIKE SSR Element Code ServiceDefinition/ServiceCode Y
PA Airline or CRS Designator ServiceDefinition/OwnerCode Y
NN2 Action/Status/Advice Code Service/StatusCode Y
JFKLGW0002B 15NOV Flight Segment or Flight Leg Service/PaxSegmentRefID Y
-1GRI/LOGN Name Element Service/PaxRefID Y
Notes:
Example shows NN2 for two bikes. This would be treated as 2 Services.
BIKE should be considered baggage and fall under all rules that support baggage.
OrderCreateRQ/Request/CreateOrder/CreateOrderItem/OfferItemType/BaggageItem
BIKEBIKE
SSR BIKE PA NN2 JFKLGW0002 B15NOV-1GRI/LOGN
SSR BIKE PA NN2 JFKLGW0002 B15NOV-1GRI/LOGN
None Copy
Page: 287 of 377
Business FunctionBusiness Function
Used to communicate to the Seller (ORA) that Oxygen is available for a specific flight
TypeType
Service
SSR ExampleSSR Example
Enhanced Distribution MappingEnhanced Distribution Mapping
Within enhanced distribution, this information will be represented by a Service for that specific flight
segment. If the oxygen is not confirmed at time of order creation, the Service Item can be updated
(confirmed) at a later stage which the Seller being advised via OrderViewRS or OrderChangeNotif.
However there is no structure available in schema to request Oxygen, there is a need to create a
secondary confirmation by the DP of oxygen for a specific flight
Not currently supported in Enhanced Distribution. If you have a requirement for this SSR, please email
standards@iata.orgstandards@iata.org.
AOXYAOXY
SSR AOXY LH KK1 FRAKUL0782C10OCT-1HILTON/OLAMRS.LH MEDA RQST PENDING AUTHORIZATION
SSR AOXY LH KK1 FRAKUL0782C10OCT-1HILTON/OLAMRS.LH MEDA RQST PENDING AUTHORIZATION
None Copy
Page: 288 of 377
This page contains the SSR’s which have been identified as an information and will be documented
within this section. Some SSRs are not currently supported by the Enhanced Distribution.
SSRSSR SSR NameSSR Name
RequestRequest
ContextContext
ResponseResponse
ContextContext
ACKI Automated Check-In
N/A Airline
Process
Order Info
CHLD Child
Passenger
Info
Offer
CLID Client Identification
Passenger
Info
Order Info
CRUZ Cruise Passenger
Passenger
Info
Offer
CTCE Passenger contact information e-mail address
Passenger
Info
Order Info
CTCM Passenger contact information mobile phone number
Passenger
Info
Order Info
CTCR Passenger contact information refused N/A N/A
DCRW Crew Booking
Passenger
Info
Offer
DEPA Deportee—accompanied by an escort
Passenger
Info
Offer
DEPU Deportee—unaccompanied
Passenger
Info
Offer
DOCA API—Passenger Address Information
Passenger
Info
Offer Info
DOCO API—Passenger Other Supplementary Information
Passenger
Info
Offer Info
DOCS API—Passenger Travel Document
Passenger
Info
Offer Info
EPAY Electronic Payment Authorisation
Payment
Info
Payment
Info
FOID Form of Identification
Passenger
Info
Order Info
FQTR Frequent traveller award redemption journey
Passenger
Info
Offer
FQTS Frequent traveller service benefit information
Passenger
Preference
Offer
FQTV Frequent traveller mileage program information
Passenger
Info
Order Info
GPST Group Seat Request
Passenger
Info
Offer
GRPS
Passenger travelling together over one or more segments
utilising a common identity assigned by the booking Member
Passenger
Info
Offer
GSTA Goods and Services Tax Business Address
Passenger
Info
Offer
GSTE Goods and Services Tax Business E-mail
Passenger
Info
Offer
GSTN Goods and Services Tax Number
Passenger
Info
Offer
List of Information SSRsList of Information SSRs
Page: 289 of 377
GSTP Goods and Services Tax Business Phone Number(s)
Passenger
Info
Offer
HRIC Human Remains in Cabin
Passenger
Info
Advice
INAD Inadmissible Passenger
Passenger
Info
Offer
INFT Infant
Passenger
Info
Offer
LANG Specify language(s) spoken
Passenger
Info
Offer
NRSB Non-Revenue Standby Passenger
Passenger
Preference
Offer
PCTC Passenger emergency contact information
Passenger
Info
Order Info
RFTV Reason for Travel
Passenger
Info
Order Info
SEAT Pre-reserved seat requested
Passenger
Preference
Offer
SEMN Ship’s Crew—Seamen
Passenger
Info
Offer
SLPR Berth/Bed in the cabin but excludes stretcher
Passenger
Preference
Offer
TKTL Ticketing Time Limit N/A Advice
TLAC Time Limit Auto Cancel Exemption N/A Advice
TWOV Transit/transfer without Visa
Passenger
Info
Advice
Page: 290 of 377
Business FunctionBusiness Function
Automated check-in is a service provided by the Member where a passenger will automatically be
checked in after the flight enters the check-in window. It is recommended to assign a seat in advance
if possible. If no seat was selected, a seat may be assigned during the check-in process. The
passenger may have the opportunity to change his seat before departure. After the check-in process
the boarding pass is sent to the passenger. There are two options for receiving the boarding pass; the
Member will send the boarding pass to either an e-mail address or mobile phone number.
If the boarding pass needs to be sent to an e-mail address, the following formats can be requested:
1. PDF File
2. Mobile Boarding Pass
3. Mobile Boarding Pass pushed to the airline’s App.
If the boarding pass needs to be sent to a mobile phone number, the following formats can be
requested:
1. Mobile Boarding Pass
2. Mobile Boarding Pass pushed to the airline’s App.
The preferred delivery method, either e-mail or mobile device, is specified in the request. The
standard of delivering the boarding pass is the presence of the SSR CTCE or CTCM.
The SSR ACKI is used to request automated check-in. The formatted free text of this SSR contains
the preferred delivery method as well as the format of the boarding pass.
TypeType
Service
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number andNumber and
Type ofType of
CharactersCharacters
ExamplesExamples
(a) Element Identifier SSR 3a SSR
(b) SSR Element Code 4a ACKI
ACKIACKI
SSR ACKI US NN1 PHLLAX0797F14FEB.CTCM/MBP
SSR ACKI US NN1 PHLLAX0797F14FEB.CTCM/MBP
None Copy
SSR ACKI US NN1 LAXPHL0796F21FEB.CTCM/MBP
SSR ACKI US NN1 LAXPHL0796F21FEB.CTCM/MBP
None Copy
Page: 291 of 377
(c)
Airline Designator (3 character codes are
preceded by an oblique)
2an or 3a US or /USA
(d) Action Code 2a NN
(e) Number of services (without leading zeros) 1n 1
(f) Departure Airport 3a PHL
(g) Arrival Airport 3a LAX
(h) Flight number (with leading zeros) 4n 797
(i) RBD 1a F
(j) Date 2n 3a 14-Feb
(k)
If applicable, Name Element, preceded by a
hyphen
Refer to Name
Element
-1PURVIS/DERYLMRS
paragraph
(l)
Boarding pass delivery preference preceded by
a period (mandatory)
4a .CTCM or .CTCE
(m)
Boarding pass format preference preceded by
an oblique (mandatory)
3a /MBP
In conjunction with CTCE: PDF- PDF File MBP-
Mobile boarding pass APP-Mobile boarding
pass pushed to App.
In conjunction with CTCM: MBP-Mobile
boarding pass APP-Mobile boarding pass
pushed to App.
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Partially Supported.
A Service can be used to offer automated check-in to the passenger as a preference. However the
collection of their boarding pass preferences has not currently been modelled.
If you require this please contact standards@iata.orgstandards@iata.org to add this to the enhanced distribution
messages.
Page: 292 of 377
Business FunctionBusiness Function
To advise that the Passenger is a child.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number and Type ofNumber and Type of
CharactersCharacters
ExampleExample
(a) Supplementary Identifier (Mandatory) 3a SSR
(b)
Special Service Requirement Code
(Mandatory)
4a CHLD
(c) Airline Designator (Mandatory) 2an or 3a A4, QF or ABC
(d)
Action/Status/Advice Code
(Mandatory)
2a HK
(e)
Number in Party (1) for this SSR
(Mandatory)
1n 1
(f)
Separator (Mandatory, if date of birth
follows)
Oblique /
(g) Date of Birth (ddmmmyy) (Optional) 2n 3a 2n 05-Jan-01
(h)
Hyphen (Mandatory, if associated
name follows)
hyphen —
(i)
PNR Associated Name including
Number in party
1ALLEYNE/JENNIFER
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/AgeMeasure
CHLDCHLD
SSR CHLD KL HK1/05JAN01-1GATINET/MATTHIEU MSTR
SSR CHLD KL HK1/05JAN01-1GATINET/MATTHIEU MSTR
None Copy
SSR CHLD QF HK1/03JAN98-1VANSTAEN/GUILHERME MSTR
SSR CHLD QF HK1/03JAN98-1VANSTAEN/GUILHERME MSTR
None Copy
Page: 293 of 377
Business FunctionBusiness Function
Used to store the Client Identification Number.
AssumptionsAssumptions
CLID is used by the airlines to send a unique ID assigned to a corporation so that employees
of that corporation can receive the negotiated private fare or service.
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number andNumber and
Type ofType of
CharactersCharacters
MandatoryMandatory
oror
OptionalOptional
ExamplesExamples
(a) Element Identifier SSR 3a Mandatory SSR
(b) SSR Element Code 4a Mandatory CLID
(c)
Airline Designator (3 character
codes are preceded by an oblique)
(YY not permitted)
2an or 3a Mandatory KL
(d)
Status code followed by an oblique
(/)
2a Mandatory HK/
(e) Fixed Text Max. 25an Mandatory ABC000NL
(f) Tier level preceded by a period Alpha or numeric Optional .GOLD
(g)
If applicable, Name Element,
preceded by a hyphen
Refer to Name
Element
paragraph
Mandatory -1SURNAME/NAME
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: IATA_OrderCreateRQ/Party/Participant/Corporation/CorporateID
CLIDCLID
SSR CLID KL HK/ABC000NL.GOLD-1SMIT/BRIAN
SSR CLID KL HK/ABC000NL.GOLD-1SMIT/BRIAN
None Copy
Page: 294 of 377
Business FunctionBusiness Function
Used to identify that the passenger is a Cruise Passenger (either connecting from or connecting to a
Cruise)
TypeType
Passenger Information
SSR ExampleSSR Example
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
CRUZCRUZ
SSR CRUZ DL HK/ATLMIA1125Y09MAY.CARNIVAL CRUISE
SSR CRUZ DL HK/ATLMIA1125Y09MAY.CARNIVAL CRUISE
None Copy
Page: 295 of 377
Business FunctionBusiness Function
To transmit and store the passengers email address within the Order.
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
Due to the limited character set within EDIFACT the below table describes the mapping to parse the
email from EDIFACT to and XML friendly email address.
Use // (double slash) in place of @ (at sign), use “..” (double dot) in place of “_” (underscored) and
use “./” (dot slash) where a–(dash) is needed in E-mail address.
Source TextSource Text Transform toTransform to
// @
.. _
./ -
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Mapping of the Passengers email shall go into the EmailAddress Element of the ContactInfo Object
and linked to the Pax Object:
EmailEmail
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/ContactInfoList/ContactInfo/EmailAddress
PassengerPassenger
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax
CTCECTCE
SSR CTCE LH HK1/C.CULLINANE//FREEWEB./INC.COM-1CULLINANE/CARRIMRS
SSR CTCE LH HK1/C.CULLINANE//FREEWEB./INC.COM-1CULLINANE/CARRIMRS
None Copy
SSR CTCE LH HK1/MICHELLE..DIVA//NOBILTY.ORG/DE-1DIVA/MICHELLEMRS
SSR CTCE LH HK1/MICHELLE..DIVA//NOBILTY.ORG/DE-1DIVA/MICHELLEMRS
None Copy
Page: 296 of 377
Business FunctionBusiness Function
To transmit and store the passengers telephone number within the Order.
TypeType
Passenger Information
SSR Example
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Mapping of the Passengers Telephone number shall go into the Phone Element of the ContactInfo
Object and linked to the Pax Object:
PhonePhone
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/ContactInfoList/ContactInfo/Phone
PassengerPassenger
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax
CTCMCTCM
SSR CTCM LH HK1/12021234567-1CULLINANE/CARRIMRS
SSR CTCM LH HK1/12021234567-1CULLINANE/CARRIMRS
None Copy
SSR CTCM LH HK1/496987654321/DE-1DIVA/MICHELLEMRS
SSR CTCM LH HK1/496987654321/DE-1DIVA/MICHELLEMRS
None Copy
Page: 297 of 377
Business FunctionBusiness Function
To provide advice from the Seller to the Airline advising the passenger has declined to provide contact
information.
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
SSR CTCR AirlineCode StatusCode “REFUSED”
Mapping in Enhanced DistributionMapping in Enhanced Distribution
This does not map to Enhanced Distribution, if not details are provided this will evident in the XML
message. The Airline will determine via message validation if the information provided is sufficient or
not.
CTCRCTCR
SSR CTCR BA HK1/REFUSED
SSR CTCR BA HK1/REFUSED
None Copy
Page: 298 of 377
Business FunctionBusiness Function
Used to identify crew bookings on partner bookings (as bilaterally agreed).
TypeType
Passenger Information
AssumptionAssumption
SSR does not need to relate to the specific segment, but to the Order
SSR ExampleSSR Example
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
DCRWDCRW
SSR DCRW DL HK1 DTWSLC1173Y10AUG-1CREW/ONE
SSR DCRW DL HK1 DTWSLC1173Y10AUG-1CREW/ONE
None Copy
Page: 299 of 377
Business FunctionBusiness Function
To advise that passenger is a deportee travelling accompanied with an escort.
TypeType
Passenger Information
AssumptionsAssumptions
N/A
SSR ExampleSSR Example
SSR StructureSSR Structure
Not documented in AIRIMP.
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
The use of PTC is a possible solution. Not specifically supported in Enhanced Distribution. If you have
a requirement for this SSR, please email standards@iata.orgstandards@iata.org.
DEPADEPA
SSR DEPA
SSR DEPA
None Copy
Page: 300 of 377
Business FunctionBusiness Function
To advise that passenger is an unaccompanied deportee.
TypeType
Passenger Information
AssumptionsAssumptions
N/A
SSR ExampleSSR Example
SSR StructureSSR Structure
No documented in AIRIMP
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
The use of PTC is a possible solution. Not specifically supported in Enhanced Distribution. If you have
a requirement for this SSR, please email standards@iata.orgstandards@iata.org
DEPUDEPU
SSR DEPU
SSR DEPU
None Copy
Page: 301 of 377
Business FunctionBusiness Function
This SSR is used to transmit and store Advanced Passenger Information Address which is sometimes
required by the departure or arrival authorities.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
A passenger's residence address is 1600 Smith Street, Houston, Texas 77001, United States of
America:
SSR StructureSSR Structure
ComponentsComponents
Number andNumber and
Type ofType of
CharactersCharacters
ExamplesExamples
(a) Supplementary Identifier 3a SSR
(b) Special Service Requirement Code 4a DOCA
(c) Airline Designator 2an or 3a CO or /ABB
(d) Status Code 2a HK
(e) Number in Party for this SSR 1-3n 1
(f)
Segment: The segment and flight data must be the same
as shown in a segment element
(i) Boarding Point 3a LHR
(ii) De-planing Point 3a JFK
(iii) Flight Number 4n 234
(iv) Class of Service 1a F
(v) Date (DDMMM) 5an 03-Oct
(g) Type of Address 1a /R
D = destination, R = residence
(h) Country 1-3a /USA
(i) Address Details Max. 35an
/1600 SMITH
STREET
(j) City Max. 35a /HOUSTON
(k) State/Province/County Max. 35a /TX
(l) Zip Code/Postal Code 17an /77001
DOCADOCA
SSR DOCA CO HK1MADLHR0455Y28JUN/R/US/1600 SMITH STREET/HOUSTON/TX/
SSR DOCA CO HK1MADLHR0455Y28JUN/R/US/1600 SMITH STREET/HOUSTON/TX/
SSR DOCA CO ///77001
SSR DOCA CO ///77001
None Copy
Page: 302 of 377
(m) Infant Indicator 1a /I
I = Infant (if an infant not occupying seat)
(n) Name Information
(If the address information does not apply to all
passengers in the PNR, follow with a hyphen and
passenger name field for whom the element applies.)
(i) Hyphen (-) Hyphen -
(ii) PNR Associated Name Including number in party
1STEVENSON/
JOHNMR
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/ContactInfoList/ContactInfo
Page: 303 of 377
Business FunctionBusiness Function
This SSR is used to transmit and store supplementary information of Advanced Passenger Information
which is sometimes required by the departure or arrival authorities.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
A passenger requiring two Visa documents for this PNR:
A passenger supplies a United States Redress number for this PNR:
SSR StructureSSR Structure
ComponentsComponents
Number andNumber and
Type ofType of
CharactersCharacters
ExamplesExamples
(a) Supplementary Identifier 3a SSR
(b) Special Service Requirement Code 4a DOCO
(c) Airline Designator 2an or 3a AA or /ABC
(d) Status Code 2a HK
(e) Number in Party for this SSR 1-3n 1
(f)
Segment: The segment and flight data must be the same
as shown in a segment element
(i) Boarding Point 3a LHR
(ii) De-planning Point 3a JFK
(iii) Flight Number 4n 234
DOCODOCO
SSR DOCO BA HK1MADLHR0455Y28JUN//V/9891404/LONDON/14MAR03/
SSR DOCO BA HK1MADLHR0455Y28JUN//V/9891404/LONDON/14MAR03/
SSR DOCO BA ///US-1STEVENSON/JOHNMR
SSR DOCO BA ///US-1STEVENSON/JOHNMR
None Copy
SSR DOCO BA HK1MADLHR0455Y28JUN//V/586D4FF/WASHINGTON/23AUG01/
SSR DOCO BA HK1MADLHR0455Y28JUN//V/586D4FF/WASHINGTON/23AUG01/
SSR DOCO BA ///GB-1STEVENSON/JOHNMR
SSR DOCO BA ///GB-1STEVENSON/JOHNMR
None Copy
SSR DOCO AA HK1JFKLAX0001Y28JUN//R/1234567890123///US
SSR DOCO AA HK1JFKLAX0001Y28JUN//R/1234567890123///US
SSR DOCO AA ///-1CADE/BOBBI
SSR DOCO AA ///-1CADE/BOBBI
None Copy
Page: 304 of 377
(iv) Class of Service 1a F
(v) Date (DDMMM) 5an 03-Oct
(g) Place of Birth Max. 35a
/AMBER HILL
GBR
(h) Supplementary Travel Information Type 1a /V
Visa Number ... V
Redress Number ... R
Known Traveler Number ... K
(i) Supplementary Travel Information Number Max. 25an /9891404
(j) Place of Issue Max. 35a /LONDON
(k) Issue Date 7an /14MAR03
DDMMMYY
(l)
Country/State for which the Supplementary Travel
Information is applicable
1-3a /USA
(m) Infant Indicator 1a /I
I = Infant (if an infant not occupying seat)
(n) Name Information
(If the address information does not apply to all
passengers in the PNR, follow with a hyphen and
passenger name field for whom the element applies.)
(i) Hyphen (-) Hyphen -
(ii) PNR Associated Name Including number in party
1STEVENSON/
JOHNMR
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/IdentityDoc
Page: 305 of 377
Business FunctionBusiness Function
This SSR is used to transmit and store Advanced Passenger Information is sometimes required by the
departure or arrival authorities.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
Mr. John Stevenson is travelling with an American identity card number A23145890 and a
Singaporean Passport number S78654091.
Note: These example have been split into two lines as the first line exceeds the maximum limit of 69
characters.
SSR StructureSSR Structure
ComponentsComponents
NumberNumber
and Typeand Type
ofof
CharactersCharacters
ExamplesExamples
(a) Supplementary Identifier 3a SSR
(b) Special Service Requirement Code 4a DOCS
(c) Airline Designator 2an or 3a AA or /ABC
(d) Status Code 2a HK
(e) Number in Party for this SSR 1n 1
(f)
Segment: The segment and flight data must be the same
as shown in a segment element
(i) Boarding Point 3a LHR
(ii) De-planing Point 3a JFK
(iii) Flight Number 4n 234
(iv) Class of Service 1a F
(v) Date (DDMMM) 5an 03-Oct
DOCSDOCS
SSR DOCS BA HK1MADLHR0455Y28JUN/P/SGP/S78654091/SGP/12JUL64/M/23OCT05/
SSR DOCS BA HK1MADLHR0455Y28JUN/P/SGP/S78654091/SGP/12JUL64/M/23OCT05/
SSR DOCS BA ///STEVENSON/JOHN/RICHARD-1STEVENSON/JOHNMR
SSR DOCS BA ///STEVENSON/JOHN/RICHARD-1STEVENSON/JOHNMR
SSR DOCS BA HK1LHRLAX0269Y01JUL/C/US/A23145890/SG/12JUL64/M/12JUL04/
SSR DOCS BA HK1LHRLAX0269Y01JUL/C/US/A23145890/SG/12JUL64/M/12JUL04/
SSR DOCS BA ///STEVENSON/JOHN/RICHARD-1STEVENSON/JOHNMR
SSR DOCS BA ///STEVENSON/JOHN/RICHARD-1STEVENSON/JOHNMR
SSR DOCS BA HK1LAXAKL7302Y03JUL/P/SGP/S78654091/SGP/12JUL64/M/23OCT05/
SSR DOCS BA HK1LAXAKL7302Y03JUL/P/SGP/S78654091/SGP/12JUL64/M/23OCT05/
SSR DOCS BA ///STEVENSON/JOHN/RICHARD-1STEVENSON/JOHNMR
SSR DOCS BA ///STEVENSON/JOHN/RICHARD-1STEVENSON/JOHNMR
None Copy
Page: 306 of 377
(g) Travel Document Type 1-2a /I
Approved non-standard identity documents used for travel
(as defined by the issuing Country/State) ... F
Identity Card (as defined by the issuing Country/State) ... A
Identity Card (as defined by the issuing Country/State) ... C
Identity Card (as defined by the issuing Country/State) ... I
Military ID ... M
Passport Card ... IP
Passenger Passport ... P
(h) Travel Document Issuing Country/State 1-3a /USA
(i) Travel Document Number Max. 15an /D23145890
(j) Passenger Nationality 1-3a /USA
(k) Date of Birth 7an /12JUL64
DDMMMYY
(l) Gender of Passenger 1-2a /M
F = female, M = male, FI = female infant, MI = male infant
and
U = Undisclosed Gender
(m) Travel Document Expiry Date ((1))DDMMMYY 7an /12JUL04
(n) Travel Document Surname ((1)) Max. 30a /STEVENSON
(o) Travel Document First Given Name ((1)) Max. 30a /JOHN
(p) Travel Document Second Given Name ((1)) Max. 30a /RICHARD
(q)
If multi-passenger passport and this SSR is for the primary
passport holder, include the letter (H)
1a /H
(r) Name Information
(If the primary travel document information does not apply
to all passengers in the PNR, follow with a hyphen and
passenger name field for whom the element applies.)
(i) Hyphen (-) Hyphen -
(ii) PNR Associated Name Including number in party
1STEVENSON/
JOHNMR
(1) As it appears on the official travel document, including only alpha characters and spaces.
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/IdentityDoc
Page: 307 of 377
Business FunctionBusiness Function
EPAY SSR used to transmit and store payment information such as Credit Card or Voucher
Information etc.
## Assumptions
N/A
TypeType
Payment Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number and Type ofNumber and Type of
CharactersCharacters
ExamplesExamples
(a) Supplementary Identifier SSR
(b) Special Service Requirement Code EPAY
(c)
Action Identifier—airline participating in
service
TF
(d)
Action code followed by number in party for
this SSR
NN1
(e) Payment type 2an AP
Valid payment types are:
AP—Account payment;
AC—Airline card;
CC—Credit card;
CP—Coupon payment;
VP—Voucher payment.
(f) Payment reference /123456789
(g)
Name (optionally) if not for all passengers
(preceded by hyphen)
-
1JONES/MARYMRS
(h) Free text (preceded by period) .FREE TEXT
EPAYEPAY
SSR EPAY TF NN1 AP/123456789
SSR EPAY TF NN1 AP/123456789
None Copy
SSR EPAY TF NN1 AP/123456789-1JONES/MARYMRS.PROMOTION
SSR EPAY TF NN1 AP/123456789-1JONES/MARYMRS.PROMOTION
None Copy
SSR EPAY TF NN3 VP/AB12345QC-3FULLER/ABBYMRS/BOBMR/JONATHANMSTR
SSR EPAY TF NN3 VP/AB12345QC-3FULLER/ABBYMRS/BOBMR/JONATHANMSTR
None Copy
Page: 308 of 377
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Information such as Credit card, vouchers etc will be transmitted via the below XPath and can be
mapped to the SSR EPAY if required.
XPath:XPath: OrderCreateRQ/Request/PaymentInfo
Page: 309 of 377
Business FunctionBusiness Function
Used to define the Form of ID of passenger check-in identification.
AssumptionsAssumptions
N/A
TypeType
Passenger Identification Form
SSR ExampleSSR Example
The two-character code for type of ID is a two-character alpha code that includes:
CC (credit card);
DL (driver's license);
FF (frequent flyer);
PP (passport);
NI (national identity);
CN (confirmation number or Record Locator);
TN (ticket number);
ID (locally defined ID number).
Notification that passport will be used as form of identification for Passenger Check-in Identification:
Notification that a photo Texas (TX) driver's license, with number specified, will be used as Form of
Identification for Passenger Check-in Identification:
Notification that Frequent Traveller Card will be used as Form of Identification for Passenger Check-in
Identification:
Notification that a truncated Diners Club Credit Card number will be used as Form of Identification for
Passenger Check-in Identification.
FOIDFOID
SSR FOID LH HK1/PP-1JOHNSON/GAYLE
SSR FOID LH HK1/PP-1JOHNSON/GAYLE
None Copy
SSR FOID LH HK1/DLTX9P123ABC456-1KAYOUM/CARYMRS
SSR FOID LH HK1/DLTX9P123ABC456-1KAYOUM/CARYMRS
None Copy
SSR FOID LH HK1/ FF LH 992222901234561-1SEXTON/AMY
SSR FOID LH HK1/ FF LH 992222901234561-1SEXTON/AMY
None Copy
Page: 310 of 377
Notification that a truncated Credit Card number will be used as a form of identification at check-in for
two passengers travelling together.
Notification that a Frequent Traveller Card will be used as a form of identification at check-in for all
passengers within the PNR:
Notification that a Frequent Traveller Card will be used to as form of identification at check-in for
several passengers travelling together causing a continuation line.
SSR StructureSSR Structure
ComponentsComponents
Number and type ofNumber and type of
CharactersCharacters
ExamplesExamples
(a) Element Identifier 3a SSR
(b) SSR Code 4a FOID
(c)
Airline Designator (3 character codes are
preceded with an oblique)
2an or 3a KL
(d) Action/Status/Advice Code 2a HK
(e) Number of services (without leading zeros) 1-3n 1
(f) Separator start of structured text 1 /
(g) Structured text, as applicable PP1234567
(h)
If applicable, Name Element preceded by a
hyphen
Refer to Name Element
paragraph
-1RED/PETER
MUCRM1A
MUCRM1A
.SWIRM1G
.SWIRM1G
SWI1G QWERTY/ABC/57256802/STO/1G/T/SE
SWI1G QWERTY/ABC/57256802/STO/1G/T/SE
1SUNDSFJORD/YNGVAR
1SUNDSFJORD/YNGVAR
SK0909Y10JUN CPHEWR HK1
SK0909Y10JUN CPHEWR HK1
SK0910Y20JUN EWRCPH HK1
SK0910Y20JUN EWRCPH HK1
SSR FOID SK HK1/ CC DC
SSR FOID SK HK1/ CC DC
361412XXXX3434-1SUNDSFJORD/YNGVAR
361412XXXX3434-1SUNDSFJORD/YNGVAR
None Copy
UCRM1A
UCRM1A
.SWIRM1G
.SWIRM1G
SWI1G QWERTY/ABC/57256802/STO/1G/T/SE
SWI1G QWERTY/ABC/57256802/STO/1G/T/SE
1ALLEYNE/JENNIFER MISS 1PERKINS/JOANNA MRS
1ALLEYNE/JENNIFER MISS 1PERKINS/JOANNA MRS
SK0909Y10JUN CPHEWR HK2
SK0909Y10JUN CPHEWR HK2
SK0910Y20JUN EWRCPH HK2
SK0910Y20JUN EWRCPH HK2
SSR FOID SK HK2/CCVI492912XXXXXX6789
SSR FOID SK HK2/CCVI492912XXXXXX6789
None Copy
SSR FOID AF HK34/FFAF103827162
SSR FOID AF HK34/FFAF103827162
None Copy
SSR FOID IB HK4/FFIB135847361-1CORKING/STEPHEN 1MATTHEWS/DOMINIC
SSR FOID IB HK4/FFIB135847361-1CORKING/STEPHEN 1MATTHEWS/DOMINIC
SSR FOID IB ///2GUBERT/LAURENT/NEO MSTR
SSR FOID IB ///2GUBERT/LAURENT/NEO MSTR
None Copy
Page: 311 of 377
(i)
If applicable, free text, preceded by a period
character.
As defined .FREE TEXT
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/FOID
Page: 312 of 377
Business FunctionBusiness Function
FQTR is used for redemption journeys for which mileage credit should not be accrued
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
Example 1—Message advising redemption journey:
Example 2—Message selling free transportation to NW:
Example 3—an SSR item advising the tier level of a frequent traveller entitled to service
benefits while travelling on a redemption journey:
SSR StructureSSR Structure
ComponentsComponents
NumberNumber
and Typeand Type
ofof
CharactersCharacters
ExamplesExamples
(a) Element Identifier SSR 3a SSR
(b) SSR Element Code 4a
FQTV (or FQTU,
FQTS, FQTR)
(c) Airline Designator 2an or 3a UA
(d) Status Code 2a HK
(e) Number of services 1a 1
(f) Departure Airport 3a FRA
(g) Arrival Airport 3a ORD
(h) Flight number (with leading zeros) 4n 6500
(i) RBD 1a C
FQTRFQTR
SSR FQTR QF HK1 MELSYD 0004Y14APR-1BURNSIDE/DAISYMS.QF0260119
SSR FQTR QF HK1 MELSYD 0004Y14APR-1BURNSIDE/DAISYMS.QF0260119
None Copy
SSR FQTR NW SS1 BOSJFK 3707Y30SEP-1FERNANDES/ANNAMRS.KL 2405990082/FREE
SSR FQTR NW SS1 BOSJFK 3707Y30SEP-1FERNANDES/ANNAMRS.KL 2405990082/FREE
None Copy
SSR FQTR AC HK1 YYZYUL859Y20APR-1RUF/UWE.LH192001234567891/G
SSR FQTR AC HK1 YYZYUL859Y20APR-1RUF/UWE.LH192001234567891/G
None Copy
Page: 313 of 377
(j) Date 2n 3a 12-Oct
(k) If applicable, Name Element preceded by a hyphen
Refer to
Name
Element
paragraph
1NAME/FIRSTNAME
(l)
Passenger's "Frequent Traveller" identification
(airline code and account number) preceded by a
period
Max. 25an .LH192001234567891
(m)
Passenger's "Frequent Traveller" tier level (free flow
text, alpha or numeric, can be one or more
characters) preceded by an oblique (/) (e.g. "GC" (11)
for Gold, "S" (2) for Silver, PLATINUM for Platinum.
Max. 35an /GC
/2
/PLATINUM
Mapping in Enhanced DistributionMapping in Enhanced Distribution
FQTR is an internal process and therefore not a feature to be supported in Enhanced Distribution.
Page: 314 of 377
Business FunctionBusiness Function
FQTS plus FQTV are used in the event that a frequent traveller wishes to both accrue miles in one
airline's scheme and also be recognised for the reason of service benefits through a different airline's
scheme.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number andNumber and
Type ofType of
CharactersCharacters
ExamplesExamples
(a) Element Identifier SSR 3a SSR
(b) SSR Element Code 4a
FQTV (or FQTU,
FQTS, FQTR)
(c) Airline Designator 2an or 3a UA
(d) Status Code 2a HK
(e) Number of services 1a 1
(f) Departure Airport 3a FRA
(g) Arrival Airport 3a ORD
(h) Flight number (with leading zeros) 4n 6500
(i) RBD 1a C
(j) Date 2n 3a 12-Oct
(k)
If applicable, Name Element preceded by a
hyphen
Refer to Name
Element
paragraph
1NAME/FIRSTNAME
(l)
Passenger's "Frequent Traveller" identification
(airline code and account number) preceded by
a period
Max. 25an .LH192001234567891
Mapping in Enhanced DistributionMapping in Enhanced Distribution
FQTSFQTS
SSR FQTS BA HK/BA 12345678-MARCMR
SSR FQTS BA HK/BA 12345678-MARCMR
None Copy
Page: 315 of 377
Multiple Loyalty Programs can be added in the Enhanced Distribution request, however there is
currently no support for the passenger to choose which program to accrue points, and which program
to use the benefits from
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/LoyaltyProgramAccount – to add
multiple accounts to order
Page: 316 of 377
Business FunctionBusiness Function
To store the Passengers Frequent Flyer Details. If FQTV is only to be used it will be assumed to be for
both mileage accrual and service benefits within the Airline.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number andNumber and
Type ofType of
CharactersCharacters
ExamplesExamples
(a) Element Identifier SSR 3a SSR
(b) SSR Element Code 4a
FQTV (or FQTU,
FQTS, FQTR)
(c) Airline Designator 2an or 3a UA
(d) Status Code 2a HK
(e) Number of services 1a 1
(f) Departure Airport 3a FRA
(g) Arrival Airport 3a ORD
(h) Flight number (with leading zeros) 4n 6500
(i) RBD 1a C
(j) Date 2n 3a 12-Oct
(k)
If applicable, Name Element preceded by a
hyphen
Refer to Name
Element
paragraph
1NAME/FIRSTNAME
(l)
Passenger's "Frequent Traveller" identification
(airline code and account number) preceded by
a period
Max. 25an .LH192001234567891
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/LoyaltyProgramAccount
FQTVFQTV
SSR FQTV DL HK/DL 12345-JONES/JAMES
SSR FQTV DL HK/DL 12345-JONES/JAMES
None Copy
SSR FQTV UA HK1 FRAORD 6500C12OCT-1RUF/UWE.LH192001234567891
SSR FQTV UA HK1 FRAORD 6500C12OCT-1RUF/UWE.LH192001234567891
None Copy
Page: 317 of 377
Business FunctionBusiness Function
To advise that passenger is travelling as a part of group.
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
Group name is used in place of the individual names of all passengers:
Group seats (names unknown, group total 40):
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/PaxGroup
GRPS/GPSTGRPS/GPST
SSR GRPS PA TCP40 SITA/TOUR
SSR GRPS PA TCP40 SITA/TOUR
None Copy
SSR GRPS/DAN TCP255 WORLDSPAN/TOUR
SSR GRPS/DAN TCP255 WORLDSPAN/TOUR
None Copy
SSR GPST LX NN40AMSGVA0795Y14FEB.30N10S
SSR GPST LX NN40AMSGVA0795Y14FEB.30N10S
None Copy
Page: 318 of 377
Business FunctionBusiness Function
To transmit and store the Goods and Services Business Address of the Passengers’ Business from
the Seller to the Airline
AssumptionsAssumptions
N/A
TypeType
Organisation Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number and TypeNumber and Type
of Charactersof Characters
ExamplesExamples
(a) Element Identifier 3a SSR
(b) SSR Service Code 4a GSTA
(c)
Airline Designator (3 character codes are
preceded with an oblique)
2an or 3a AI or /AIC
(d) Status Code 2a HK
(e) Number of services (without leading zeros) 1-2n 1
(f) Country 1-3a /IND
(g) Address Line 1 Max. 35 an
/11 FLOOR ONE
HORIZON CENTER
(h) Address Line 2 Max. 25 an
/SECTOR 43 DLF PH
V
(i) City Max. 25 an /CHENNAI
(j) State or Province or County Max. 25 an /TAMIL NADU
(k) Zip Code or Postal Code 17an /602024
(l)
If applicable, Name Element preceded by
a hyphen
Refer to Name
Element paragraph
-1MEEKS/SOPHIEMS
GSTAGSTA
SSR GSTA AI HK1/IND/11 FLOOR ONE HORIZON CENTER/SECTOR 43 DLF PH V/
SSR GSTA AI HK1/IND/11 FLOOR ONE HORIZON CENTER/SECTOR 43 DLF PH V/
None Copy
SSR GSTA AI ///CHENNAI/TAMIL NADU/603024-1MEEKS/SOPHIEMS
SSR GSTA AI ///CHENNAI/TAMIL NADU/603024-1MEEKS/SOPHIEMS
None Copy
SSR GSTA AI HK1/IND/18 RAGHUVANSHI MILLS COMP//MUMBAI/
SSR GSTA AI HK1/IND/18 RAGHUVANSHI MILLS COMP//MUMBAI/
None Copy
SSR GSTA ///MAHARASHTRA - 1BRYANT/TEDDYMR
SSR GSTA ///MAHARASHTRA - 1BRYANT/TEDDYMR
None Copy
Page: 319 of 377
Mapping in Enhanced DistributionMapping in Enhanced Distribution
This SSR is information, no service being delivered. Structure TBD with GSTA/GSTP/GTSE
Page: 320 of 377
Business FunctionBusiness Function
To transmit and store the Goods and Services Business Email of the Passengers’ Business from the
Seller to the Airline
AssumptionsAssumptions
N/A
TypeType
Organisation Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number and Type ofNumber and Type of
CharactersCharacters
ExamplesExamples
(a) Element Identifier 3a SSR
(b) SSR Service Code 4a GSTE
(c)
Airline Designator (3 character codes are
preceded with an oblique)
2an or 3a AI or /AIC
(d) Status Code 2a HK
(e)
Number of services (without leading
zeros)
1-2n 1
(f) Country 1-3a /IND
(g) Business Email Max. 35an /GST.INFO//IBMGST.IN
(h)
If applicable, Name Element preceded by
a hyphen
Refer to Name
Element paragraph
-1MEEKS/SOPHIEMS
Note: Use // (double slash) in place of @ (at sign), use “..” (double dot) in place of “_” (underscore),
and use “./” in place of a “-” in email addresses.
Mapping in Enhanced DistributionMapping in Enhanced Distribution
This SSR is information, no service being delivered. Structure TBD with GSTA/GSTP/GTSE
GSTEGSTE
SSR GSTE AI HK1/IND/GST.INFO//IBMGST.IN-1MEEKS/SOPHIEMS
SSR GSTE AI HK1/IND/GST.INFO//IBMGST.IN-1MEEKS/SOPHIEMS
None Copy
Page: 321 of 377
Business FunctionBusiness Function
To transmit and store the Goods and Services Tax Number of the Passengers’ Business from the
Seller to the Airline
AssumptionsAssumptions
N/A
TypeType
Organisation Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number and Type ofNumber and Type of
CharactersCharacters
ExamplesExamples
(a) Element Identifier 3a SSR
(b) SSR Service Code 4a GSTN
(c)
Airline Designator (3 character codes are
preceded with an oblique)
2an or 3a AI or /AIC
(d) Status Code 2a HK
(e) Number of services (without leading zeros) 1-2n 1
(f) Country owning GST 1-3a /IND
(g) GST Number Max. 20an /22AAAAA0000A1Z5
(h)
Name of Company whose GST number is
provided
Max. 35an /IBM
(i)
If applicable, Name Element preceded by a
hyphen
Refer to Name
Element paragraph
-1MEEKS/SOPHIEMS
Mapping in Enhanced DistributionMapping in Enhanced Distribution
This SSR is information, no service being delivered. Structure TBD with GSTA/GSTP/GTSE
GSTNGSTN
SSR GSTN AI HK1/IND/22AAAAA0000A1Z5/IBM-1MEEKS/SOPHIEMS
SSR GSTN AI HK1/IND/22AAAAA0000A1Z5/IBM-1MEEKS/SOPHIEMS
None Copy
SSR GSTN AI HK1/IND/12ABCDA0000A1Z6/ECLIPSE-1BRYANT/TEDDYMR
SSR GSTN AI HK1/IND/12ABCDA0000A1Z6/ECLIPSE-1BRYANT/TEDDYMR
None Copy
Page: 322 of 377
Business FunctionBusiness Function
To transmit and store the Goods and Services Business Phone Number(s) of the Passengers’
Business from the Seller to the Airline
AssumptionsAssumptions
N/A
TypeType
Organisation Information
SSR ExampleSSR Example
SSR StructureSSR Structure
ComponentsComponents
Number and Type ofNumber and Type of
CharactersCharacters
ExamplesExamples
(a) Element Identifier 3a SSR
(b) SSR Service Code 4a GSTP
(c)
Airline Designator (3 character codes are
preceded with an oblique)
2an or 3a AI or /AIC
(d) Status Code 2a HK
(e) Number of services (without leading zeros) 1-2n 1
(f) Country 1-3a /IND
(g) First Business Telephone Max. 15n /91 033 45229023
(h) Second Business Telephone Max. 15n /91 07582 22144
(i)
If applicable, Name Element preceded by a
hyphen
Refer to Name
Element paragraph
-1MEEKS/SOPHIEMS
Mapping in Enhanced DistributionMapping in Enhanced Distribution
This SSR is information, no service being delivered. Structure TBD with GSTA/GSTP/GTSE
GSTPGSTP
SSR GSTP AI HK1/IND/9103345229023/9107582221443-1MEEKS/SOPHIEMS
SSR GSTP AI HK1/IND/9103345229023/9107582221443-1MEEKS/SOPHIEMS
None Copy
SSR GSTP AI HK1/IND/9103345229023-1MEEKS/SOPHIEMS
SSR GSTP AI HK1/IND/9103345229023-1MEEKS/SOPHIEMS
None Copy
Page: 323 of 377
Business FunctionBusiness Function
To advise that passenger is admissible (who is refused admission to a State by its authorities).
TypeType
Passenger Information
AssumptionsAssumptions
N/A
SSR ExampleSSR Example
SSR StructureSSR Structure
No documented in AIRIMP
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
The use of PTC is a possible solution. Not specifically supported in Enhanced Distribution. If you have
a requirement for this SSR, please email standards@iata.org.standards@iata.org.
INADINAD
SSR INAD
SSR INAD
None Copy
Page: 324 of 377
Business FunctionBusiness Function
To advise that the Passenger is an infant (who is occupying/not occupying the seat).
AssumptionsAssumptions
N/A
TypeType
Passenger Information
SSR ExampleSSR Example
Infant not occupying a Seat:
Infant Occupying a Seat:
SSR StructureSSR Structure
SSR Structure
1. Infant not occupying a Seat:
Enter a supplementary SSR item using the SSR code “INFT”, two character airline designator, action
code and the number 1, segment information, then (if needed, according to SSR rules) a hyphen
followed by the passenger number and name who is responsible for the infant. After the last field
(either the segment information or the passenger name), enter a period (.) which must be followed by
the infant name (surname/first-name), space, and date of birth (ddmmmyy). This may be followed with
a space and other alpha-numeric free text information.
2. Infant Occupying a Seat:
Enter a supplementary SSR item using the SSR code “INFT”, two character airline designator, action
code and the number 1, segment information, a hyphen followed by the passenger number and name
of the infant, then a period (.), which must be followed only by the infant's date of birth (ddmmmyy),
space, and the text OCCUPYING SEAT.
Mapping in Enhanced DistributionMapping in Enhanced Distribution
INFTINFT
SSR INFT IB NN1 MADMIA 6123Y20JUN.CAPPA/CLARA 04FEB05
SSR INFT IB NN1 MADMIA 6123Y20JUN.CAPPA/CLARA 04FEB05
None Copy
SSR INFT IB NN1 MADMIA 6123Y20JUN-1CLARKE/HALEY MISS.04FEB05 OCCUPYING SEAT
SSR INFT IB NN1 MADMIA 6123Y20JUN-1CLARKE/HALEY MISS.04FEB05 OCCUPYING SEAT
None Copy
Page: 325 of 377
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
XPath:XPath: IATA_OrderCreateRQ/Request/DataLists/PaxList/Pax/AgeMeasure
Page: 326 of 377
Business FunctionBusiness Function
To advise the Airline the language spoken by the Passenger
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
None supplied
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Enhanced Distribution supports the sending of multiple languages within the Pax Element to signify
the language of that Passenger.
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/LangUsage
LANGLANG
LANG UA HK/MIAJFK0026Y29OCT.PSGR SPEAKS ZULU ONLY
LANG UA HK/MIAJFK0026Y29OCT.PSGR SPEAKS ZULU ONLY
None Copy
Page: 327 of 377
Business FunctionBusiness Function
To advise that the passenger is non-revenue
AssumptionsAssumptions
Seller (ORA) to identify passenger as non-revenue
Airline to respond with appropriate Offer as bilaterally agreed
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
Components of this SSR are:
Supplementary Item Identifier SSR;
Special Service Requirement Code TWOV;
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
Not specifically supported in Enhanced Distribution. If you have a requirement for this SSR, please
email standards@iata.orgstandards@iata.org.
NRSBNRSB
Segment Element ... NW750Y 25MAY MSPDTW SA2/11201407
Segment Element ... NW750Y 25MAY MSPDTW SA2/11201407
None Copy
Segment Element ... NW745Y 29MAY DTWMSP SA2/15111607
Segment Element ... NW745Y 29MAY DTWMSP SA2/15111607
None Copy
Supplementary Element ... SSR NRSB NW HK2/31OCT95DL12A
Supplementary Element ... SSR NRSB NW HK2/31OCT95DL12A
None Copy
Page: 328 of 377
Business FunctionBusiness Function
To transmit and store the name and telephone number of an Emergency Contact within the Order.
Passenger provided contact name may be an entity (such as a travel agency name) or a personal
name. The contact should not be a person travelling on the covered flight.
TypeType
Passenger Information
SSR ExampleSSR Example
SSR StructureSSR Structure
Enter a supplementary element using the code SSR, code PCTC, two-character airline designator,
advice code HK, and oblique (/), passenger provided contact name, oblique (/), country name or two-
character alpha ISO country code of the contact country followed by the telephone number.
Mapping in Enhanced DistributionMapping in Enhanced Distribution
To use the ContactType element, however this is not specifically defined.
PCTCPCTC
SSR PCTC JK HK/SUSAN RORY/US12345678900-1RORY/DAVIDMR.WIFE
SSR PCTC JK HK/SUSAN RORY/US12345678900-1RORY/DAVIDMR.WIFE
None Copy
SSR PCTC CO HK/BEVERLYS TRAVEL SERVICE/NL312026264219.ONFILE
SSR PCTC CO HK/BEVERLYS TRAVEL SERVICE/NL312026264219.ONFILE
None Copy
SSR PCTC ZY HK/ROBERT CORY/US18373123455-1BAKER/VIRGINIAMS
SSR PCTC ZY HK/ROBERT CORY/US18373123455-1BAKER/VIRGINIAMS
None Copy
Page: 329 of 377
Business FunctionBusiness Function
To advise about passenger’s reason to travel to Cuba. An SSR code specific to Cuba-bound
itineraries with a "Reason for Travel" sub code must be present in the PNR at the passenger level to
meet Cuba travel requirements.
TypeType
Passenger Information
AssumptionsAssumptions
N/A
SSR ExampleSSR Example
SSR StructureSSR Structure
There are a total of 13 reasons for travel to Cuba.
Reason for Travel DefinitionReason for Travel Definition CodeCode
1 family visits; FAMLY
2
official business of the U.S. government, foreign governments, and certain
intergovernmental organizations;
GOVMT
3 journalistic activity; JOURN
4 professional research or professional meetings; PRORM
5 educational activities and people to people exchanges; EDUCA
6 religious activities; RELIG
7
public performances, clinics, workshops, athletic and other competitions, and
exhibitions
PERFO
8 support for the Cuban people; SUPRT
9 humanitarian projects; HUMAN
10 activities of private foundations or research or educational institutes; PRIRM
11 exportation, importation, or transmission of information or information materials; INFOR
12 certain authorized export transactions. EXPRT
13 OFAC specific license (followed by number) LICEN
When using the reason LICEN, an oblique (/) should be used to separate LICEN and the license number. Where other
reasons are used, do not include an oblique.
RFTVRFTV
SSR RFTV DL HK1 ATLHAV 0123 C 01JUL-1EDWARDS/PATRICIAMS.FAMLY
SSR RFTV DL HK1 ATLHAV 0123 C 01JUL-1EDWARDS/PATRICIAMS.FAMLY
None Copy
SSR RFTV DL HK1 ATLHAV 0123 C 01JUL-1EDWARDS/PATRICIAMS.LICEN/CT20161234567
SSR RFTV DL HK1 ATLHAV 0123 C 01JUL-1EDWARDS/PATRICIAMS.LICEN/CT20161234567
None Copy
Page: 330 of 377
ComponentsComponents
Number and TypeNumber and Type
of Charactersof Characters
ExamplesExamples
(a) Element Identifier 3:00 AM SSR
(b) SSR Element Code 4:00 AM RFTV
(c)
Airline or CRS Designator (3 character
codes are preceded with an oblique)
2 an or 3a DL or /ABB
(d) Status Code 2:00 AM HK
(e) Number of services (without leading zeros) 1 n 1
(f) Departure Airport 3:00 AM ATL
(g) Airport Arrival 3a HAV
(h) Flight number (with leading zeros) 4 n 123
(i) RBD 1a Y
(j) Date 2n 3a 30-Jun
(k)
If applicable, Name element, preceded by
a hyphen
Refer to Name
Element paragraph
-1EDWARDS/PATRICIA
(l) Reason for travel 7A LICEN
(m)
License Number (when applicable)
preceded by an oblique
25 an /CT20161234567
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Not currently supported in Enhanced Distribution. If you have a requirement for this SSR, please email
standards@iata.org.standards@iata.org.
Page: 331 of 377
Business FunctionBusiness Function
To advise the Airline of the Passengers Seat Preference
TypeType
Passenger Information
AssumptionsAssumptions
N/A
SSR ExampleSSR Example
Example 1—Smoking seat/Window:
Example 2—No smoking seat:
Example 3—Specific seat request:
Example 4—Non smoking aisle seat, suitable for lap infant:
Mapping in Enhanced DistributionMapping in Enhanced Distribution
The following mandatory codes specify a section within an aircraft compartment:
N—Non-smoking Seat;
S—Smoking Seat.
SEATSEAT
SSR SEAT CO NN3MCIDEN0719Y15NOV.SW
SSR SEAT CO NN3MCIDEN0719Y15NOV.SW
None Copy
SSR SEAT CO NN3MCIDEN0719Y15NOV.N
SSR SEAT CO NN3MCIDEN0719Y15NOV.N
None Copy
SSR SEAT CO NN3MCIDEN0719Y15NOV.23A23B23C
SSR SEAT CO NN3MCIDEN0719Y15NOV.23A23B23C
None Copy
SSR SEAT CO NN3MCIDEN0719Y15NOV.NAI
SSR SEAT CO NN3MCIDEN0719Y15NOV.NAI
None Copy
Page: 332 of 377
Location Codes are optional and follow the zone code. They may be one or two characters in the
following sequence:
W—Window Seat
A—Aisle Seat
B—Bulkhead Seat
B—Bulkhead Seat
C—Chargeable Seat (bilateral agreement)
E—Exit Row Seat
F—Non Chargeable Seat (bilateral agreement)
H(1)— Handicapped Seat
I—Passenger With Infant
L—Leg Space Seat (bilateral)
M(1)—Medically Okay to Travel
R—Rear-Facing Seat (bilateral agreement)
U—Unaccompanied Minor
P—Extra seat for comfort - Arm rest can be raised
(1) Requires a separate Supplementary Element defining the medical or handicapped status of
passenger.
Seller to Airline Request:
TBC
Airline to Seller Response:
TBC
NDC message SeatAvailabilityRQ/RS can be used to achieve the selection of the seat service. This
SSR is requesting a type of seat and if available to reserve it.
Page: 333 of 377
Business FunctionBusiness Function
To advise that the passenger is a Seaman from a Ships crew.
AssumptionsAssumptions
The Seller/ORA can identify the passenger as a Seaman.
The Airline can respond with an appropriate offer.
SSR ExampleSSR Example
SSR SEMN
SSR StructureSSR Structure
Components of this SSR are:
Supplementary Item Identifier SSR;
Special Service Requirement Code SEMN;
Mapping in Enhanced DistributionMapping in Enhanced Distribution
XPath:XPath: OrderCreateRQ/Request/DataLists/PaxList/Pax/PTC
Not specifically supported in Enhanced Distribution. If you have a requirement for this SSR, please
email standards@iata.org.standards@iata.org.
SEMNSEMN
Page: 334 of 377
Business FunctionBusiness Function
To advise that there is a Berth/Bed in the Cabin (excluding a stretcher).
TypeType
Offer Information
AssumptionsAssumptions
To advise the Seller that the Offer has a different product (of a Berth/Bed)
SSR ExampleSSR Example
SSR StructureSSR Structure
Components of this SSR are:
Supplementary Item Identifier SSR;
Special Service Requirement Code SLPR;
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Not specifically supported in Enhanced Distribution however this can be portrayed through Offer
information and rich content. If you have a specific requirement for this SSR, please email
standards@iata.orgstandards@iata.org.
SLPRSLPR
SSR SLPR
SSR SLPR
None Copy
Page: 335 of 377
Business FunctionBusiness Function
To advise of the ticketing time limit of the booking prior to ticketing.
TypeType
Ticketing (Payment) Function
SSR ExampleSSR Example
SSR StructureSSR Structure
BOGRMAV
.ZRHRMLX 031540
Record Locator.............. ZRHLX AB 1458BC
Name Element.............. 1VALDERRAMA/J MR
Segment Element.......... AV070F 17AUG BOGFRA SS1/1105 0705/1
Supplementary Element
(ticketing time limit) ....... SSR TKTL AV SS/BOG 1700/12AUG
Supplementary Element…OSI AV CTCH BOG 242159
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Mapping of the Ticketing Time Limit into an Enhanced Distribution Message can be found:
XPath:XPath:
OrderViewRS/Response/DataLists/ServiceDefinitionList/ServiceDefinition/PaymentTimeLimitDateTime
DateTime needs to be as per the Contract, for example: 2015-01-13T13:59:38Z
Notes
As of 19.1 this node will be moved up to the Order Item Level.
TKTLTKTL
SSR TKTL AV SS/BOG 1700/12AUG
SSR TKTL AV SS/BOG 1700/12AUG
None Copy
Page: 336 of 377
Business FunctionBusiness Function
Based on RP1768a—Mandatory Fare Quote and Enforced Ticket Time Limit, a Member may exempt a
PNR from automatic cancellation by a Member/CRS.
TypeType
Operational Function
SSR ExampleSSR Example
SSR StructureSSR Structure
Components of this SSR are:
Supplementary Item Identifier SSR;
Special Service Requirement Code TLAC;
Action Identifier—enter the airline designator of the Members/CRS to take action;
Oblique
The airline designator of the airline authorising the exemption;
The word EXEMPT
Free text area (optional)—shall be preceded by a period (.).
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Not currently supported in Enhanced Distribution. If you have a requirement for this SSR, please email
standards@iata.org.standards@iata.org.
TLACTLAC
SSR TLAC 1G/KL EXEMPT.DUE TO SCHEDULE CHANGE
SSR TLAC 1G/KL EXEMPT.DUE TO SCHEDULE CHANGE
None Copy
Page: 337 of 377
Business FunctionBusiness Function
To advise that the passenger is travelling without a Visa.
TypeType
Passenger Information
SSR ExampleSSR Example
SSR TWOV ...
SSR StructureSSR Structure
Components of this SSR are:
Supplementary Item Identifier SSR;
Special Service Requirement Code TWOV;
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Not currently supported in Enhanced Distribution. If you have a requirement for this SSR, please email
standards@iata.orgstandards@iata.org.
TWOVTWOV
Page: 338 of 377
Business FunctionBusiness Function
To advise the Airline that the Passenger is a minor and unaccompanied by an adult.
PDUM is a chargeable SSR for unaccompanied minors.
TypeType
Passenger Information
AssumptionsAssumptions
N/A
SSR ExampleSSR Example
Mapping in Enhanced DistributionMapping in Enhanced Distribution
Information required for the Airline to determine this is the presence of one passenger in the booking
along with the Age of that passenger. The Airline can respond with an appropriate Offer and
Information.
Seller to Airline Request:Seller to Airline Request:
Age of Passenger to be completed: OrderCreateRQ/Request/DataLists/PaxList/Pax/Birthdate
Presence of one passenger in the request.
Airline to Seller Response:Airline to Seller Response:
Offer Returned
UMNR/PDUMUMNR/PDUM
SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07
SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07
None Copy
Page: 339 of 377
This page contains the SSR’s which have been identified as obsolete due to the limit usage of their
function and will not be documented within this section.
If you use this SSR within Enhanced and Simplified Distribution, please email standards@iata.org.standards@iata.org.
SSRSSR SSR NameSSR Name
SSR SSR Name
ADMD Advise Electronic Miscellaneous Document Number
ADPI Advise Passenger Security Information
ADTK Advise if ticketed
ASVC Additional Service
ASVX EMD document number in back-up message for EDIFACT System Cancel
AUTK Authorise Ticketing of PNR
CKIN Other check-in advise for groups
ETLP Only used by DCS systems - RP1707b, RP1708, RP1719d
FRAV First Available
GRPF Group Fare data
GRPK Group space passive notification
IROP Irregular Operations
MCOA MCO Number
MEDA Medical Case
NAME Name change caused segment status change
NSSA No Smoking Aisle Seat
NSSB No Smoking Bulkhead Seat
NSSR No Smoking Rear-Facing Seat
NSST No Smoking Seat
NSSW No Smoking Window Seat
OTHS Other actionable information
PDGT Ground Transportation and Non Air Services (Chargeable)
PDTS Travel Services (Chargeable)
RLOC Record Locator
RQST Seat Request—include specific number or preference
SMSA Smoking Aisle Seat
SMSB Smoking Bulkhead Seat
SMSR Smoking Rear-Facing Seat
SMST Smoking Seat
SMSW Smoking Window Seat
SPEQ Sports Equipment
TKNA Ticket number - Automated
TKNC Ticket number - TCN
TKNE Ticket number - Electronic
TKNM Ticket number - Manual
TKNR Notification that an electronically ticketed reservation has been changed
TKNX ET document number in back-up message for EDIFACT System Cancel
List of Obsolete SSRs (from the perspective of EnhancedList of Obsolete SSRs (from the perspective of Enhanced
and Simplified Distribution)and Simplified Distribution)
Page: 340 of 377
The Airline Industry Data Model (AIDM) and its output of XML schemas defines a service as a
ServiceDefintion to which a list of ServiceDefintions can be added into a message.
A ServiceDefinition describes the service that can be offered but gives no context to that of a
passenger or a flight.
Within the Offer or the Order, a Service element allows the ServiceDefinition to be referenced to the
Passenger and the Segment as well as other related ServiceDefinitions.
Using a Service to instantiate a ServiceDefinition with realted Passenger and Flight Information
(optionally) we can construct many of the SSRs we have today.
This section details the current ServiceDefinition and the mapping to an Automated SSR Format.
Description of a non-flight serviceDescription of a non-flight service
OverviewOverview
Page: 341 of 377
Instantiation of a ServiceInstantiation of a Service
Page: 342 of 377
Within the standard there are various fields which are not restricted within the schema but refer to the
PADIS Codeset.
There are a few reasons for this, namely:
A change to an enumeration type will require an update to the schema contract
A field may have a set of codes used within the industry, but also open to bilateral codes if
required.
This is a directory of the PADIS codesets when referred to from the annotations within the schemas.
As the PADIS Codeset refers to messages which could be used for other XML and/or EDIFACT
messages, this directory specifies which codes are appliciable to the Enhanced and Simplified
Distribution (EaSD) messages and is the main guide for referral purposes. For example, if a Codeset
that is being used by an EaSD message is updated by another industry group, while relevant to that
Codeset, it may have no business need within EaSD. Therefore, this section details the enumerations
that are appliciable to these messages.
This section is broken down into the following sections:
Categorisation: Codesets that categoris products or services
Status Codesets: That define the status of various products, services, offers or orders
Warnings and Errors; Codesets that define specific errors or warnings
Other: Codesets that do not fit into the above categories
For example a schema annotation would say to refer to PADIS codeset 9873:
Which refers to:
CodeCode DescriptionDescription
Used in E&SUsed in E&S
SchemasSchemas
1 First class, Highest class of service (First Class Category) Yes
2
Second class, Medium class of service (Business Class
Category)
Yes
3
Third class, lowest class of service (all economy/coach class
categories)
Yes
4 Economy/coach premium Yes
5 Economy/coach Yes
6 Economy/coach discounted Yes
7 All Yes
CodesetsCodesets
Page: 343 of 377
For more information, please see: https://www.iata.org/services/finance/Pages/ttbs.aspx
TTBS Ticket Tax Box ServiceTTBS Ticket Tax Box Service
Page: 344 of 377
International Payment CardsInternational Payment Cards CodeCode
American Express AX
Discover Card DS
Diners Club DC
China UnionPay UP
Japan Credit Bureau JC
Mastercard CA
Universal Air Travel Plan (UATP) TP
VISA International VI
Resolution 728Resolution 728
Page: 345 of 377
1001 - Document/message name, coded1001 - Document/message name, coded
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1001 Document/message name, coded1001 Document/message name, coded
Page: 346 of 377
1153 - Reference qualifier1153 - Reference qualifier
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Unique passenger reference identification Active
2 Passenger sequence number Active
3 Passenger standby number Active
4 Passenger boarding security number Active
5 Passenger ticket number Active
6 Passenger confirmation number Active
7 Date of birth Active
700 Exceptional PNR Security Identification Active
701 Agency grouping identification Active
702 Ticketing data Active
703 Message number for free text Active
704 Message sequence identifier Active
705 Last meal sequence/order number Active
706 Gate extension number Active
707 Mobil unit number Active
A Account/Product reference number Active
B Business Active
F Fax Active
H Home Active
P Passenger/traveller reference number Active
S Segment/service reference number Active
XX Not known Active
1153 Reference qualifier1153 Reference qualifier
Page: 347 of 377
1245 - Status indicator, coded1245 - Status indicator, coded
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
0 Direct Active
1 Indirect Active
2 Verified fare information Active
3 Reissued flown involuntary indicator Active
700 Fare basis may vary by carrier Active
701 Fares based on passenger type and/or discount input Active
702 Fares include US transportation tax where applicable Active
1245 Status indicator, coded1245 Status indicator, coded
Page: 348 of 377
4183 - Special condition, coded4183 - Special condition, coded
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
A Air transportation Active
B Surface transportation/non air services Active
C Baggage Active
D Financial impact Active
E Airport services Active
F Merchandise Active
FL Flight number restriction may apply Active
G Inflight services Active
I Reserved for individual airline use Active
RB Missing or incorrect reservations booking designator (RBD) Active
RE Booking/ticketing conditions may apply Active
RO
User specified reservations booking designator (RBD) has been
overridden
Active
SR Other sales restrictions (e.g.: passenger, point of sale, etc.) Active
4183 Special condition, coded4183 Special condition, coded
Page: 349 of 377
6353 - Number of units qualifier6353 - Number of units qualifier
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Agent discount AD75N1 Active
10 Electronic ticket discount - child Active
11 Electronic ticket discount - adult Active
12 Electronic ticket discount - infant Active
13 Employee Not filed ZED fare Active
14 ZED employee - adult Active
15 ZED employee - infant Active
16 ZED - common law spouse of employee/retiree Active
17 ZED - children under 24 years of age Active
18 ZED - employee or retiree parent Active
19 ZED - employee child Active
2 Adult with discount restrictions Active
20 ZED - employee sibling Active
21 ZED - employee adult of married employee Active
22 ZED - partner adult of single employee Active
23 ZED - partner companion Active
24 ZED - parent of married employee Active
25 ZED - parent of single employee Active
26 ZED - sibling of adult of single employee Active
27 ZED - common-law spouse - opposite sex Active
28 ZED - common-law spouse - same sex Active
29 ZED - widow or widowers adult employee Active
3 Assistant member of European Parliament Active
30 Zonal employee discount Active
31 Weekender fare Active
32 Family plan - infant Active
33
Blend of government travel or government contract ormilitaryor category
Z fares
Active
34 Child - must include age 2 to 11 on ticket for child discount Active
35 Infant accompanied by a youth Active
36 Infant with a seat - resident Active
37 Infant without a seat - resident Active
38 Inclusive tour infant without a seat Active
39 Inclusive tour infant with a seat Active
4 Card carrying holder or holders Active
40 Labor or worker infant with a seat Active
41 Military infant with a seat Active
42 Military infant without a seat Active
43 Contract bulk - adult Active
44 Contract bulk - child Active
45 Contract bulk - infant without a seat Active
6353 Number of units qualifier6353 Number of units qualifier
Page: 350 of 377
46 Contract bulk - infant with a seat Active
47 Contract bulk - infant May not be a bulk free Active
48 Journalist of European Cabinet Active
49 Journalist of European Committee Active
5 Card carrying member Active
50 Loyalty management group Active
51 Government employee on leave Active
52 Military - basic training graduate Active
53 Member of European Parliament Active
54 Blend of Category Z fares Active
55 Military incentive certificates Active
56 Non-revenue standby Active
57 Negotiated fare - unrestricted rules Active
58 Parent Active
59 Private fare - adult Active
6 Discount cardholder France and overseas depts Active
60 Registered domestic partner Active
61 Registered travel companion Active
62 Senior discounted companion Active
63 Spouse of European Parliament Active
64 Sports passenger Active
65 Restricted tour conductor Active
66 Passenger agreed upsell Active
7 Leisure cardholder with France Active
700 Abonnement Active
701 Accompanied child Active
702 Accompanying adult Active
703 Adult charter Active
704 Agent discount Active
705 Air or Sea fares Active
706 Border Area Argentina Active
707 Charter Active
708 Charter - Adult Active
709 Charter - Youth Active
70A Total number of passengers Active
70B Number of unique passenger types Active
70C Total number of passenger types Active
70D Total number of segments priced Active
70E Number of stopovers applied to fare breakpoint Active
70F Number of surcharges applied to fare breakpoint Active
70G Total number of taxes Active
70H Total number of passenger facility charges PFC Active
70I Total number ZP Active
70J Total number of fare calculation or surcharges charges Active
70K Flight group number Active
70L Tax Active
70M Surcharges Active
70N PFCs Active
70O ZPs Active
70P Number of unique PTCs Active
Page: 351 of 377
70Q Total PTCs Active
70R Number of stopovers Active
70S Airline staff standby Active
70T Bereavement Active
70U Family plan infant discount Active
70V Group - own use Active
70W Military dependents Active
70X Military group Active
70Y Non-resident Active
70Z Disabled person Active
710 Charter - Child Active
711 Child discounts Active
712 City or County Government travel Active
713 Clergy Standby Active
714 Companion Fare Active
715 Companion Fare - Prime Active
716 Companion Partner Active
717 Companion with age requirement Active
718 County Government employee Active
719 Coupon Active
71A Blind passenger Active
71B Baggage Active
71C Adult contract fare Active
71D Airline employee buddy standby fare Active
71E Clergy discount Active
71F Commuter fare Active
71G Convention fare Active
71H Coupon discounted fare Active
71I Child standby Active
71J Emigrant fare Active
71K Government inter state fare Active
71L Group school party Active
71M Inclusive tour child Group Active
71N Inclusive tour adult Group Active
71O Incentive certificate fare Active
71P Internet fare Active
71Q Journalist of EUR parliament Active
71R Labor adult Active
71S Military or DOD not based in the USA Active
71T Passenger occupying two seats Active
71U Patients traveling for medical treatment Active
71V Pilgrim fare Active
71W Pilgrim fare Saudi Arabia Active
71X Student standby Active
71Y Senior citizen with age requirement Active
71Z University employee Active
720 Department of Defense Active
721 Diplomat Active
722 Disabled Unable to work Finland Active
723 Discover the Country (Argentina) Active
Page: 352 of 377
724 Economy Discount Active
725 Eighty percent disabled persons Active
726 Family Plan Active
727 Family Plan Children Discount Active
728 Family Plan France Active
729 Family member - 1st accompanying Active
72A Visit USA adult Active
72B Passenger checked in Active
72C Passenger not checked in Active
72D Passenger checked in via ITCI Active
72E Negotiated fare passenger Active
72F Number of meals loaded Active
730 Family member - 2nd accompanying Active
731 Females Traveling Alone in France Active
732 Foreign Worker discount Active
733 Foreign Worker Infant discount Active
734 Foreign Worker Children discount Active
735 Frequent traveler Active
736 Frequent traveler -adult Active
737 Frequent traveler - child Active
738 Government Active
739 Government and Military Category Z Active
740 Government Child Active
741 Government Contract Active
742 Government Dependent Active
743 Government Exchange Active
744 Government Infant Active
745 Government order Germany Active
746 Government State fares Active
747 Government Transportation ordered Active
748 Group Child Active
749 Group Infant Active
750 Group - undefined Active
751 Group visit another country adult Active
752 Group visit USA Active
753 Head of family Active
754 IATA = Air or Surface Active
755 Inclusive Tour Child Individual Active
756 Inclusive Tour Infant Active
757 Inclusive Tour undefined Active
758 Independent tour Active
759 Individual early retirement Finland Active
760 Individual inclusive tour Active
761 Individual Ships Crew Active
762 Indonesian War Veteran Discount Fare Active
763 Indonesian Parliament Discount Fare Active
764 Industry Active
765 Infant discount Active
766 Infant without seat Active
767 Infant with seat Active
Page: 353 of 377
768 Job Corp trainee Active
769 Military charter Active
770 Military child Active
771 Military confirmed Active
772 Military dependents stationed inside USA Active
773 Military dependents stationed outside USA Active
774 Military DOD based in USA Active
775 Military family Active
776 Military inclusive tour Active
777 Military infant Active
778 Military Job Corps Active
779 Military parents or parents in-laws Active
780 Military personnel based in USA Active
781 Military personnel based out USA Active
782 Military recruit Active
783 Military reserve Active
784 Military reserve on active duty Active
785 Military retired Active
786 Military retired dependent Active
787 Military spouse Active
788 Military standby Active
789 Mini Fare Argentina Active
790 Missionary Active
791 Missionary Spouse Active
792 NATO or SHAPE personnel Active
793 Negative Band Intersectors Argentina Active
794 Other accompanying family member Active
795 Press Active
796 Pseudo resident Active
797 Refugee Active
798 Resident Active
799 Resident Abonnement Active
8 Carnet coupon travel Active
800 Resident Adult Active
801 Resident Child Active
802 Resident family plan child Active
803 Resident family plan head family Active
804 Resident family plan infant Active
805 Resident family plan youth Active
806 Resident family plan 2nd adult Active
807 Resident government Active
808 Resident group Active
809 Resident infant Active
810 Resident Senior Citizens Active
811 Resident Student Active
812 Resident youth Active
813 Retiree wholly domestic Argentina Active
814 Seaman Active
815 Seaman fares Active
816 Seaman Government Order Active
Page: 354 of 377
817 Second Passenger Active
818 Senior citizen confirmed Active
819 Senior citizen discount Active
820 Senior citizen standby Active
821 Special Active
822 Special Interior Fare Argentina Active
823 Spouse Fares Active
824 Standby Active
825 State government employees Active
826 Student discount Active
827 Student Excellence Discount Fare (Indonesia) Active
828 Student Government Order Active
829 Swiss Journalist Active
830 Teachers fares Active
831 Teacher Wholly domestic Active
832 Time-saver Fares Active
833 Tour Guide Conductor Active
834 Traveling with cello Active
835 Unaccompanied child Active
836 Undefined Active
837 Visit USA child Active
838 War Veteran Unable to work Active
839 Youth confirmed Active
840 Youth Discount Active
841 Youth standby Active
842 Youth student Active
843 Labor child Active
844 Labor infant Active
845 80 percent disabled person Finland Active
846 Second passenger for example companion Active
847 Disabled, unable to work Finland Active
848 Government discount Germany Active
849 Individual early retirement Finland Active
850 Special interior fare Argentina Active
851 Border area fare Argentina Active
852 Intra country restricted fares (Argentina) Active
853 Adult with age restriction Active
854 Frequent flyer companion Active
855 Frequent flyer preferred Active
856 Visit friends or relatives Active
857 List of alternates Active
9 Child of European Parliament member Active
A Adult Active
BS Block space Active
C Child Active
CP Corporate Active
DPI Total deplaned for this flight leg Active
F Female Active
G Group Active
I Individual Active
Page: 355 of 377
IF infant female Active
IM infant male Active
IN Infant Active
IZ Individual within a group Active
L Airport lounge member Active
M Male Active
ML Number of meals served Active
MX Maximum number of flights desired Active
N Military Active
NC Number of columns Active
NL Number of lines Active
PX Number of seats occupied by passengers on board Active
S Same surname Active
SP Standby positive Active
SS Standby space available Active
T Frequent traveler Active
TA Total seats available to assign Active
TC Total cabin class or compartment capacity Active
TCA
Total cabin or compartment seats with acknowledgment pending for
seats
Active
TD Number of ticket or document numbers Active
TF Total number of flight/value coupons Active
TS Total seats sold Active
TU Total seats unassigned Active
TUA Total unassigned seats with acknowledgment pending for seats Active
U Unknown Active
UM Unaccompanied Minor Active
WCH Wheelchair assistance Active
X Unspecified Active
Page: 356 of 377
9800 - Reservation booking designator9800 - Reservation booking designator
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 All cabin classes Active
A First Class Discounted Active
B Coach Economy Discounted Active
C Business Class Active
D Business Class Discounted Active
E
Shuttle Service (No reservation allowed. Seat to be confirmed at check-
in.)
Active
F First Class Active
G Conditional Reservation Active
H Coach Economy Discounted Active
J Business Class Premium Active
K Thrift Active
L Thrift Discounted Active
M Coach Economy Discounted Active
P First Class Premium Active
Q Coach Economy Discounted Active
R Supersonic Active
S Standard Class Active
T Coach Economy Discounted Active
U Shuttle Service (No reservation needed. Seat Guaranteed) Active
V Thrift Discounted Active
W Coach Economy Premium Active
Y Coach Economy Active
9800 Reservation booking designator9800 Reservation booking designator
Page: 357 of 377
9873 - Cabin class of service, coded9873 - Cabin class of service, coded
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 First class, Highest class of service (First Class Category) Active
2 Second class, Medium class of service (Business Class Category) Active
3
Third class, lowest class of service (all economy/coach class
categories)
Active
4 Economy/coach premium Active
5 Economy/coach Active
6 Economy/coach discounted Active
7 All Active
9873 Cabin class of service, coded9873 Cabin class of service, coded
Page: 358 of 377
9888 - Form of payment identification9888 - Form of payment identification
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
CA Cash Active
CC Credit Card Active
CK Check Active
EF Electronic funds transfer Active
IEP Easy pay Active
9888 Form of payment identification9888 Form of payment identification
Page: 359 of 377
9932 - Facility type, coded9932 - Facility type, coded
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Movie Active
10 Short feature video Active
11 No duty free sales Active
12 In-seat power source Active
13 Internet access Active
14 Unassigned Active
15 Inseat Video Player/Library Active
16 Lie-flat seats Active
17 Additional services Active
18 Wi-Fi Active
19 Lie-flat seat first Active
2 Telephone Active
20 Lie-flat seat business Active
21 Lie-flat seat premium economy Active
22 110V AC power Active
23 110V AC power first Active
24 110V AC power business Active
25 110V AC power premium economy Active
26 110V AC power economy Active
27 USB power Active
28 USB power first Active
29 USB power business Active
3 Entertainment on demand Active
30 USB power premium economy Active
31 USB power economy Active
32 Mobile wireless phone service Active
4 Audio programming Active
5 Live TV Active
6 Reservation booking service Active
7 Duty free sales Active
700 Meal service Active
701 Entertainment Active
8 Smoking Active
9 Non-smoking Active
99 Amenities subject to change Active
ABU Aerobus Active
AIR Air side Active
BAG Baggage Area Active
BEL Conveyor Belt Active
BUS Bus Active
9932 Facility type, coded9932 Facility type, coded
Page: 360 of 377
CAT Catering Active
CHK Check-in area Active
CLN Cleaning Active
COU Check-in counter Active
CRW crew bus Active
CUB Curbside Active
FIR fire-engine equipment Active
FUE Re-Fuelling Active
GAN Gangway Active
GTE Gate area Active
ICE De-icing equipment Active
JET Jetway Active
LIT Lighting Active
LND Land side Active
LOU Boarding Lounge Active
LUG Luggage Active
PAN Remote de-ice plan Active
PAR Parking area or stand Active
PIE Pier Active
POW Ground Power Active
PUB Public area Active
SAT Satellite Active
SHU Shuttle Active
STD Stand Active
STF Staff in-terminal (e.g. breakroom or operational room) Active
TAN Tank truck Active
TER Terminal Active
TOW Tow tractor with towbar Active
TWB Tow tractor without towbar Active
WAS A/C washing equipment Active
WAT Fresh water equipment Active
Page: 361 of 377
9970 - Product details qualifier9970 - Product details qualifier
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Reservations classes (PRBD) Active
2 Physical configuration (ACV) Active
3 Blocked Seats and/or blocked unit load devices Active
4 First cabin choice Active
5 Second cabin choice Active
6 Default cabin choice Active
7 Requested RBD cabin Active
8 Default to any cabin Active
BAS Base Active
CLB Club Class Active
CTA Common Tariff Area Active
DOM Domestic Active
ECO Economy Class Active
EQP Equipment Active
FST First Class Active
INT International Active
OB Offered by booking class Active
OC Offered by cabin class Active
PAR Parking Active
PER Personnel Active
SB Sold by booking class Active
SC Sold by cabin class Active
SCH Schengen Active
SHU Shuttle Active
TRB Transborder Active
9970 Product details qualifier9970 Product details qualifier
Page: 362 of 377
FHT - Flight haul typeFHT - Flight haul type
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Long-haul 6 hrs plus Active
2 Medium-haul 3-6 hrs Active
3 Short-haul up to 3 hrs Active
FHT Flight haul typeFHT Flight haul type
Page: 363 of 377
FST - Flight segment typeFST - Flight segment type
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Open Active
2 Passive Active
3 Service (passive service segment) Active
FST Flight segment typeFST Flight segment type
Page: 364 of 377
IPT - Instant purchase typeIPT - Instant purchase type
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Purchase using certificate credit Active
2 Ticketless purchase immediately charged to credit card Active
3 Not an instant purchase Active
4 Purchase is charged via digital wallet Active
5 Simultaneous with time of ticketing Active
IPT Instant purchase typeIPT Instant purchase type
Page: 365 of 377
SFB - Service fee basisSFB - Service fee basis
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1
Option directly applied to fare. Applicable when using method F when
applying an option directly to a fare-not used in an EMD solution.
Active
2
Baggage only. Item was charged a % of a fare fee calculation for
excess baggage on the weight system.
Active
3
Item is not available/ applicable due to FQTV status or chosen price
class.
Active
4
Item is free of charge due to FQTV status, free baggage allowance, or
chosen price class.
Active
5 Not applicable Active
6 Surcharge Active
SFB Service fee basisSFB Service fee basis
Page: 366 of 377
TDT - Touchpoint device typeTDT - Touchpoint device type
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Agent terminal Active
10 Tablet Native App Active
2 Web browser Active
3 Airport kiosk Active
4 Mobile device Active
5 Other Active
6 Unknown Active
7 Mobile Web Browser Active
8 Mobile Native App Active
9 Tablet Web Browser Active
TDT Touchpoint device typeTDT Touchpoint device type
Page: 367 of 377
TTT - Touchpoint transactionTTT - Touchpoint transaction
Note this is a subset of the ATSB Codeset and contains the only the Codeset values identified as
being used in the Enhanced and Simplified Distribution Messages
CodeCode DescriptionDescription NotesNotes StatusStatus
1 Order or buy Active
10 Site referral Active
11 Other Active
12 Unknown Active
2 Check-in Active
3 Flight information Active
4 Gate inquiry Active
5 In-flight Active
6 Post ticketing Active
7 Post-flight Active
8 Pre-flight Active
9 Shop Active
TTT Touchpoint transactionTTT Touchpoint transaction
Page: 368 of 377
SSIM Chapter 8 - MCT StandardsSSIM Chapter 8 - MCT Standards
Your browser does not support PDF.click here to download
MCT User GuideMCT User Guide
Your browser does not support PDF.click here to download
MCT Technical GuideMCT Technical Guide
Your browser does not support PDF.click here to download
Submission Example TemplateSubmission Example Template
carrier-submission-example-template.xlsx
MCT GuidesMCT Guides
Page: 370 of 377
Before getting access, it is will be worthwhile understanding the followingBefore getting access, it is will be worthwhile understanding the following
aspects :aspects :
The AIDM model resides in one central repository
The modeling tool used is “Enterprise Architect” (EA) from Sparx Systems,
The EA software needs to be installed on the user’s workstation, in an MS Windows environment,
The AIDM repository is located on a server in the cloud, accessed from the work-station EA software
through http,
For read-only users, Sparx offers a version called EA Lite, free of license. We recommend EA Lite for
reviewers of AIDM who do not intend to create of modify models in EA,
Users intending to create or modify or export models in/from EA need to install the full EA product,
requiring a license. Unless they already have a license, IATA will allocate one from a set of keys
provided for free by Sparx, for the purpose of contributing to the AIDM.
Steps to get accessSteps to get access
1. Decide if you need update or read access,
2. If applicable (see above lines), get a license key from the AIDM Administrator,
3. Install EA on your workstation,
4. Get an EA user-id and connection info from the AIDM Administrator,
5. If looking at work in progress, get briefed on where to find what.
Dowloading EA and getting a user-idDowloading EA and getting a user-id
To install EA :To install EA :
EA Lite can be downloaded and installed direclty from the Sparx web page :
http://www.sparxsystems.com, latest version 15.1
https://www.sparxsystems.com/products/ea/15.1/index.html
Note : installation takes about 1 hour, and requires admin rights to your workstation.
Contact the AIDM Administrator to create a user-id (xxxxx) for you to access the repository with the
activation code. Note that even with EA full, the user may have either update or read-only rights
depending on your current needs.
If you already have EA on your workstation (because it’s used in your company) :
If you already have version 13.5 or higher, and Corporate Edition, then just use it to access the AIDM,
Otherwise you can either upgrade or have two versions of EA co-installed on the same workstation ;
our AIDM Administrator can tell you how.
To access the cloud repository :To access the cloud repository :
1. On the EA Start Page : click on “Connect to Cloud”
2. On the Cloud Connection window : Name= <enter a name that has meaning to you; anything
will do> URL= https://datamodel.iata.org ; ModelName= datamodel ; can leave UserName &
Password empty
3. On the Login to EA Repository window : UserID=xxxxx; Password=12345
4. Inside EA: you may then want to change your password.
AIDM Getting Access to the Modeling RepositoryAIDM Getting Access to the Modeling Repository
Page: 373 of 377
Page: 374 of 377
** AIDM Modeling Guidelines and Technology Best Practice** AIDM Modeling Guidelines and Technology Best Practice
Documentation **Documentation **
These files contains the latest standards and best practices endorsed by the Architecture and
Technology Strategy Board for passenger standards development. Included standards and best
practices:
StandardStandard DescriptionDescription
AIDM Modeling
Guidelines
IATA rules and guidelines for the development of airline messaging standards in
AIDM pillars (Business, Information, Technology) and layers 4 layers
(Contextual, Conceptual, Logical, Physical). Separate guideline document do
exist for each of the partitions defined by the pillar and layer.
IATA XML Best
Practices
IATA rules and guidelines for the production of XML schemas and messages
IATA Open Air
API Standards
and Best
Practices
IATA rules and guidelines for the use of RESTful API technology in the airline
industry, and an API ecosystem conformant to the standards
Reference
Communication
Model
*The Systems and Communications Reference (SCR) is a multi-volume set of
documents which describes the protocols, standards and implementation issues
related to inter system communications for the airline and aeronautical
communities. It is the definitive reference for airlines, vendors, travel partners,
network service providers and others who wish to participate in such inter-system
communication. *
AIDM Modeling GuidelinesAIDM Modeling Guidelines
Page: 375 of 377
Airline Industry Data Model (AIDM) Methodology and Tool (LIVE virtualAirline Industry Data Model (AIDM) Methodology and Tool (LIVE virtual
classroom)classroom)
AboutAbout
Learn Airline Industry Data Model (AIDM) rationale, concepts, structure and methodology. The AIDM
enables the generation of interoperable and easy to use messaging standards, with consistent
definitions and format of data exchanges and faster time to market for new or changed data exchange
standards. AIDM is an integrated living model, developed with SPARX Systems Enterprise Architect
(EA), a powerful visual modeling platform. In AIDM, all information is stored in one repository. Users of
the model can view, extend and adapt definitions contained in the model. You will learn how to
navigate the AIDM and find parts of the model you can leverage for designing and implementing your
companies’ IT systems or data exchange components, as well as how to influence and tune AIDM
repository contents and messaging standards generated.
Virtual Course Content:Virtual Course Content:
Airline Industry Data Model (AIDM) Methodology and Tool (Virtual Classroom)
Physical Course Content:Physical Course Content:
Airline Industry Data Model (AIDM) Methodology and Tool (Classroom, 3 days)
AIDM Training DetailsAIDM Training Details
PoweredbyDocument360
Page: 377 of 377
