Ticketing and Carrier-Imposed Fees Reference Manual. Version 7

Transcription

1 Ticketing and Reference Manual Version 7

2 Ticketing and Reference Manual Version 7 August Airline Tariff Publishing Company. All rights reserved.

3 Table of Contents Table of Contents Ticketing Fees Introduction to Ticketing Fees... 1 Ticketing Fee Data... 2 Service Sub Code... 2 Sequencing... 4 Effective/Discontinue Dates... 5 Ticketing Fee Organization... 6 Ticketing Fees... 7 Ticket Dates... 8 Fare Basis and Frequent Flyer Status... 9 Journey Geographic Location Bank Identifier (Form of Payment) Pricing/Ticketing Input Request Security Ticketing Fees Examples Example 1. Ticket Dates, Amount, and Public Distribution Example 2. Free, Location, and Private Distribution Example 3. F Type Sub Code, Locations 1 and 2 and Percent Example 4. T Type Sub Code, Amount and Account Code Example 5a. Identifying Credit Card Types Example 5b. Identifying Credit Card Types Example 6. Multiple Credit Card Types Example 7. Multiple Form of Payments within a Single Transaction Example 8. Multiple Sequences with Various Data Figure 1: Order of Sequences... 4 iii December 2015

4 Table of Contents Introduction to... 1 Data Organization... 1 Service Record Key Data... 3 Service Type Code... 3 Sequencing... 3 Effective/Discontinue Dates... 3 Record S1 Provisions... 5 Fees/Journey... 5 Sector/Portion of Travel Note Text Table Examples Validating Carrier Concurrence Table Validating Carrier Effective and Discontinue Dates Marketing Carrier Table Fee Collection and Marketing Carrier Table Example 1. Travel Dates/Ticket Dates/Point of Ticket Example 2. Journey Locations/Return To Origin Example 3. Journey Locations With Via Point Example 4. Journey Locations/Sector Locations (Without Directionality) Example 5. Journey Locations/Sector Locations (With Directionality) Example 6. Portion of Travel Locations/Stopover Exception Time (Without Directionality) 21 Example 7. Portion of Travel Locations with International/Domestic Tag Example 8. Carrier Flight Restrictions/Passenger type/no charge Example 9. Sector Locations/Domestic/International Tag/No charge Example 10. Portion of Travel Locations/RBD Example 11. Portion of Travel Locations/Fare Basis Example 12. Percent Fee/International/Domestic Tag Example 13. Itinerary Sector Counts For Fee Application Using Stopover/Connection Points Figure Figure Figure Figure iv 21 August 2017

5 Frequently Asked Questions Table of Frequently Asked Questions This table is organized by topic discussed within this document. A page reference is provided to navigate you to the answer for your query. Ticketing Fees First Steps What is Ticketing Fees?... T-1 What are Sub Codes?... T-2 Can I specify that data is private?... T-18 Are there any coding examples for Ticketing Fees?... T-21 Ticketing Fees Specific Fields and Processing What is the system assumption for Ticketing Fees?... T-1 Are ticketing fees refundable?... T-2 How can fees be expressed?... T-7 How are Ticket Dates used?... T-8 Can I specify that Ticketing Fees are based on a Frequent Flyer Status?... T-10 Why is concurrence needed?... T-11 How are the Journey Geo Locs used?... T-12 What is the Ticket Designator Table for?... T-16 What is Private Distribution?... T-18 Do I need to include myself in the security table if I am the owning carrier?... T-18 FAQ-1 1 April 2015

6 Ticketing Fees What is Ticketing Fees? Introduction to Ticketing Fees ATPCO is leading the industry in automating the collection, distribution, and pricing of service fees. The latest addition to this suite of tools is Ticketing Fees. The ticketing fee product is used for instructing pricing systems how to collect ticketing/credit card service fees on a carriers behalf when they are the ticketing or validating carrier. Ticketing Fees supports both public and private distribution needs and is controlled by the validating carrier for each original ticket. Ticketing Fees uses an ATPCO Service Fees S4 record to control the application of the ticketing/credit card fees based on Travel Dates, Ticket Issue Date, Ticketing Channel, Journey Locations, Account Code, Ticket Designator, Passenger Type, and Fare Basis/Fare Basis Owner, and Frequent Flyer Status. These fees are not interlineable; however, marketing carrier interline travel is permitted on the tickets that are validated against this record. What is the system assumption for Ticketing Fees? If processing cannot resolve to an applicable Record S4 for the validating carrier on the ticket being processed, then the assumption is that there are no Ticketing Fees applicable to that ticket. Once processing resolves to an applicable Record S4 (within each unique Sub Code), the fee specified applies to the ticket. Currently, Ticketing Fees data only applies for initial ticket issuance (except for T-type sub codes T90 T99 that apply to voluntary reissue tickets only) and does not apply to revalidated, reissued, or exchanged tickets. T-1 28 March 2009

7 Ticketing Fees What are Sub Codes? Ticketing Fee Data Service Sub Code Sub Codes are defined by the industry and can be descriptive in their naming standard. The first character of the Sub Code identifies the type of fee applicable for the record. An F indicates a Form of Payment fee, a T indicates a Ticketing Process fee, and an R indicates a Requested Service Fee. Use the Sub Code appropriate for the type of service to which you want Ticketing Fees applied. For example, for paper tickets, you will use R05 which is defined as Paper Ticket. Are ticketing fees refundable? All Ticketing Fees are considered consumed at the time of ticket purchase and therefore are not refundable. For Form of Payment (F-type code), the second character is a letter C, which means credit card or charge card, and the third character is a letter A or a numeric number. The letter A indicates any credit card, and a specific number indicates that the credit card must begin with that number. For example, Sub Code FCA indicates any credit card is used, but Sub Code FC5 indicates that only credit cards beginning with the number 5 can be used (for example, ). Note: There is no plan initially to have any other code but C (credit) in the second character, and the numbers established represent all known initial digits of credit card numbers. If there is a business need to have a different second character or additional number, this will not be a quick change. Processing logic for the new Sub Code will have to be analyzed and reviewed by the industry. Upon approval, GDS systems will be given at least 2 months from issuance of bulletin to institute logic for a new Sub Code. Debit cards are not included in this phase because they are frequently only recognized in country of issuance. For the Requested Service Type Sub Code (R-type code), the combination of the second and third character uniquely defines the Sub Code and can be numeric, numeric/alpha, or alphanumeric. The second and third characters have no ATPCO-defined meaning; however, you should use each Sub Code for the purpose it is intended, as described in this reference manual. For example, if you need to assess Ticketing Fees for courier charge, use the applicable Sub Code defined for courier charge (R02). When you have a Ticketing Fee that is not a credit card fee or a requested service fee and that applies to original ticket issuance, use the T01 T20 values. T01 T20 fees apply only when a ticket is originally issued and are ignored when a ticket is reissued. When you need to apply a Ticketing Fee to a ticket that is a reissue transaction, either from Category 31 (Voluntary Reissues) or otherwise indicated as a reissue transaction by your GDS, use the Sub Codes T90 T99. The Sub Codes T90 T99 apply when a ticket is reissued. Fees that applied to original transactions are not applied when a ticket is reissued; therefore, T01 T20 Sub Codes are ignored when processing a reissue transaction. T-2 28 March 2009

8 Ticketing Fees When you have Ticketing Fees that apply when the passenger makes certain requests, such as requesting a paper ticket, use the R- type Ticketing Codes to identify the specific request. The valid R- types are shown below. Sub code Definition R01 Overnight Delivery Charge R02 Courier Charge R03 Tour Package Delivery R04 Travel Visa Acquisition Charge R05 Paper Ticket R07 Unaccompanied Minor (UMR) R08 Private Jet Ticketing 1 R09 Private Jet Ticketing 2 T-3 28 March 2009

9 Ticketing Fees Sequencing Within each unique Service Fees Sub Code, you should organize your Ticketing Fees data from most specific to least specific for the purpose of matching the itinerary being priced. Examine locations and other qualifying data to ensure you have the data positioned in the appropriate place to achieve the expected pricing results. Among the sequences within a Service Fees Sub Code, the relationship is OR. The relationship of the data within a sequence is AND, meaning that all the conditions must be qualified to apply the fee. Once a Sub Code sequence is matched, the system will not check the rest of the sequences for the same Service Fees Sub Code, but it will check the next unique Service Fees Sub Code for data to apply. Multiple unique Service Fees Sub Codes sequences may be applied to the ticket being validated. Sub Code Travel Effective Travel Discontinue LOC 1 Journey Origin Journey LOC1 LOC2 BIII Amount/ Percent CUR Sequence Number FC1 01AUG06 X LAX USD FC1 01AUG06 X NYC USD FC1 01AUG USD Figure 1: Order of Sequences Figure 1 illustrates the sequencing concept. The following is an explanation of the data. The first sequence is for journeys originating in LAX on/after 1 August 2006, apply a USD charge for all credit cards starting with 1. The second sequence is for journeys originating NYC for on/after 1 August 2006, apply a USD charge for all credit cards starting with 1. The third sequence is for all locations that are not previously addressed, on/after 1 August 2006, apply a USD 5.00 charge for all credit cards starting with 1. The LAX and NYC sequence must be positioned above the more general sequence ( ) because it applies to all locations and is for the same Sub Code. If the LAX and NYC provisions are positioned after the generic sequence, subscribers will apply the USD 5.00 in sequence and never apply the USD in the LAX and NYC sequence. This is because once the system finds a match within a Sub Code, it will not look for additional matches within the same Sub Code, only in different Sub Codes. T-4 28 March 2009

10 Ticketing Fees Effective/Discontinue Dates When Ticketing Fees data is distributed, it becomes available for pricing immediately after being received and loaded by subscribers. The Effective and Discontinue Dates control the application of provisions that will apply based on the travel date of the passenger. The travel date is considered the departure date from the journey origin. The journey s departure date must be on or between the range defined by the Effective and Discontinue date in order for the fee to be applied. Additionally, you can further control the application of the provision based on itinerary ticket issuance requirements (First and Last Ticket Dates). See the Ticket Dates section for more information. T-5 28 March 2009

11 Ticketing Fees Ticketing Fee Organization The Ticketing Fee data is organized in this manner: Ticketing Fees Fees Commercial Name Ticket Dates Fare Basis and Frequent Flyer Status Fare Basis and Frequent Flyer Status Apply When Specified Fare Basis Appears Carrier Journey Locations Journey Origin Location 1/Location 2 Via Location Travel Wholly Within Location Bank Identifier Pricing/Ticketing Input Request Passenger Type Ticket Designator Table Account Code Table Security Private Private Distribution Security Table T-6 28 March 2009

12 Ticketing Fees Ticketing Fees How can fees be expressed? Fees The ticketing fee can be expressed as free, as a specified amount, as a percentage of the total amount charge to a credit card, or as the base fare depending on the type fee. When specifying an amount or percentage, you can indicate whether the charge includes tax. When specifying a percentage, you can further define that the fee collected will not exceed a maximum amount. When specifying the service is free, you can indicate whether or not this should be shown on the passenger s receipt. Percentages are applied differently according to the type of Sub Code they are used with. When a percentage is specified with a Form of Payment (F-type) Sub Code, it is a percentage of the total amount charged on the credit card. When a percentage is specified with a Ticketing (T-type) or a Requested Service (R-type) Sub Code, it is a percentage of the converted base amount (as displayed in the Equivalent Fare Paid field in the e-ticket record). If there is no converted base amount, then it is a percentage of the Base Fare amount. For the Reissue Ticketing Fees Sub Codes T90 T99, the converted base amount and base fare amount information will be obtained from the new ticket. Commercial Name You can use this field to indicate a commercial name for the Service Type Code used in the record. This is used for display purposes only and has no impact how Ticketing Fees are applied. T-7 28 March 2009

13 Ticketing Fees How are Ticket Dates used? Ticket Dates You can use Ticket Dates to further control the application of the fee based on the current dates in which the passenger ticket is being issued. You can define that the Ticketing Fees provision applies for tickets issued on/after a specific date (first ticket date) or on/before a specific date (last ticket date) or during a specific date range (first and last ticket dates) The Ticket Dates can be earlier than the Effective and Discontinue Travel Dates of the segment because the fare can be ticketed before travel begins. See the Effective/Discontinue Date section for more information. T-8 28 March 2009

14 Ticketing Fees Fare Basis and Frequent Flyer Status These fields are used to identify a Fare Basis and the associated significant (primary) carrier(s) required on the ticket or the Frequent Flyer Status for which the provision applies. The relationship among these fields is AND, meaning that all conditions must be met simultaneously. When this group of fields is used for Frequent Flyer Status, the Carrier (Fare Basis) has no application. Fare Basis You can restrict the application of the fee based on the value coded in the Fare Basis Box of the ticket. You must know how this data is displayed on the ticket in order to achieve the right results. In addition to alphanumeric characters, you can also use the special characters slash (/), hyphen (-), and asterisk (*). These characters can be used together to achieve different results. See the chart on the next page for examples. Slash (/): A slash is used to separate the fare class from the ticket designator. Up to two slashes (/) may be present in order to identify a first and second ticket designator. Anything preceding the slash (or the left-most slash if two are present) represents the fare class; anything after the slash represents the ticket designator. Hyphen (-): A hyphen is used as a wildcard to represent any alphanumeric characters in the fare class portion of the Fare Basis Code. Use this if you want to qualify multiple fare classes. This is the same type of concept that is used in Automated Rules. The hyphen can never be used to match a slash entry (ticket designator). When a hyphen is present with no slash, the Fare Basis Code on the ticket cannot have a ticket designator. The hyphen cannot be used to replace a number when immediately following or preceding character is also a number. For example, QH-12 matches QHAB12, QH33Z12, and QH12, but does not match QH312, QHAB123 or QH123M Asterisk (*): An asterisk is used as a wildcard to represent any alphanumeric characters in the ticket designator portion of the fare basis. Up to 2 asterisks are permitted. Edits only permit an asterisk wildcard when preceded (directly or indirectly) by a slash (/). An asterisk is never used to match the fare class portion of the Fare Basis. Use this if you want to qualify multiple ticket designators. Note: It is important that you verify that your GDS can handle ticket designators and can process wildcards. The following chart illustrates how a Fare Basis entry in Service Fees matches to a corresponding entry in Fare Basis Box of the ticket: Ticketing Record Entry Ticket Fare Basis Box Entry Match (Yes/No) QHXAP/CH QHXAP/CH YES (exactly as entered) QHXAPCH QHX/APCH QHXAP/ID/CH QHXAP/ID/CH YES (exactly as entered) NO (fare class doesn t match and no ticket designator) NO (fare class doesn t match and ticket designator doesn t match) T-9 28 March 2009

15 Ticketing Fees Ticketing Record Entry Ticket Fare Basis Box Entry QHXAPID/CH QHXAP/IDCH Match (Yes/No) NO (fare class doesn t match) NO (ticket designator doesn t match) QA7-CH QA7CH YES (hyphen does not require a character to be present) QA7ECH YES (hyphen allows E) QA70CH NO (hyphen cannot replace a number; 7 does not match to 70) K/CH/ID* K/CH/ID5 YES (fare class and ticket designator match and asterisk matches other characters) K/CN K/CH9 NO (ticket designator doesn t match) NO (fare class matches but ticket designator doesn t match) BAP/*/30 BAP//30 NO (asterisk directly following a slash requires a character to be present) BA/SR/30 BAP/37/ID NO (fare class does not match) NO (ticket designator does not match) -/* YAP/CH YES (contains a slash, hyphen allows characters before slash, and the asterisk allows the characters after the slash) YAP YAP/ID/CH NO (entry does not contain a ticket designator) YES (contains a slash, hyphen allows characters in front of slash, and asterisk allows slash and characters at the end) -//* YAP/ID NO (does not contain two ticket designators) Q//CN Q/ID/CH YES (hyphen allows characters before slashes, contains both slashes as entered, and asterisk allows characters after the slashes) NO (slashes are not adjacent) Can I specify that Ticketing Fees are based on a Frequent Flyer Status? Frequent Flyer Status Frequent Flyer Status is used to specify that the Ticketing Fees data applies based on the passenger s status within your Frequent Flyer Program. If this field is blank, then no Frequent Flyer Status restrictions apply. Use 1 to indicate the highest ranking or level for your program (such as the most elite), 2 as the second highest, and so forth, with 9 being the lowest level (a general member of your Frequent Flyer Program). This number represents the minimum status required for the Ticketing Fee data to apply. For example, if you indicate level 4, the record applies to anyone who has at least a level 4 or greater status (1, 2, 3, or 4). If you indicate level 9 then the record applies to all levels (1 9). Note: It is your responsibility to ensure that the subscriber and all parties involved know how the status numbers equate to your organization s Frequent Flyer programs. This may require messaging between the parties involved to define the status number accurately. T March 2009

16 Ticketing Fees Apply When Specified Fare Basis Appears The values in this field are used for either the Fare Basis or Frequent Flyer Status. When used for Fare Basis, this field specifies whether the data in the Carrier and the Fare Basis field are required on every sector of the ticket or at least one sector of the ticket. When used for Frequent Flyer Status, this field indicates that the value specified in the Fare Basis/Status field is a Frequent Flyer Status. Carrier (Fare Basis) This field is used in combination with a fare basis and only when the fare basis is not associated to the significant carrier or validating carrier (the owner of the Ticketing Fees Record) but is the fare basis of another carrier as indicated herein. Note: The Carrier field cannot be used in combination with a Frequent Flyer Status, and edits are in place to prevent this. Why is concurrence needed? To indicate that another carrier s fare must be on the ticket to qualify as a match to this sequence, ATPCO requires prior written concurrence from that carrier. Concurrence data is maintained by ATPCO only, and edits are in place to prevent carriers being specified if concurrence is not authorized. When the fare basis is a joint fare, the carrier indicated will apply to either carrier of the joint fare. When the following data is used in combination with the Fare Basis field, it is applied as in this manner: Carrier Apply When the Specified Fare Basis Appears on Result Blank At least one coupon At least one coupon of the ticket must be on the Specified Fare Basis and the significant (primary) carrier of the Fare Basis is the Validating Carrier (Ticketing Fees owner) Blank All coupons Every coupon of the ticket must be on the Specified Fare Basis and the significant (primary) carrier of the Fare Basis must be the Validating Carrier (Ticketing Fees owner) XX At least one coupon At least one coupon of the ticket must be on the Specified Fare Basis and the Specified Carrier (XX). XX All coupons Every coupon of the ticket must be on the Specified Fare Basis and the Specified Carrier (XX). Note: The Ticketing Fees owner is not assumed to be a possible significant primary carrier when another carrier is specified; therefore, the ticketing fee owner must also be specified in another record if the intent is to allow itself as a primary carrier. T March 2009

17 Ticketing Fees Journey Geographic Location The Journey Geographic Location fields are used to identify specific geographic restrictions for the journey. The relationship among the journey geographic provisions is AND. Location 1/Location 2 may be defined as an Area, Zone, Nation, State, City, or a User Zone Table. How are the Journey Geo Locs used? Zone Table (178) provides the ability to define a group of geographic points based on your individual business needs. This is commonly referred to as a user-defined zone. A geographic location can be indicated as a City, State, Nation, Zone, or Area. Data providers creating their own zone tables is not a new concept. At times, customers have specific business needs to identify groups of markets that all share the same application and thus should be established in a single set that is different from the standard ATPCO zones. When these situations occur, the customer may either create multiple records to identify each market or consolidate multiple markets that will have similar conditions into a unique zone. Locations can be specified between two user-defined zones, between a user-defined zone and a standard geographic specification, or between two standard geographic specifications. When both locations are coded, the journey must match a location in each field. There is not a one-to-one relationship but a one-to-many for the locations specified. For example, if Zone Table 1 contains BOS/CHI/NYC and Zone Table 2 contains IE/FR/IT, the resulting location matches are BOS IE/FR/IT, CHI IE/FR/IT, and NYC IE/FR/IT. It is not necessary to create a Zone Table if current ATPCO-defined zones are equivalent to the geographical locations needed. Zone Table 178 can be used instead of or in combination with the current geographic location fields. You can identify the journey as follows: Location 1 Journey Origin allows you to specify that the data in the Location 1 field identifies a journey origin or turnaround/destination point. Location 1/Location 2 allows you to target specific journeys Via Location allows you to specify the via location points on the journey Travel Wholly Within allows you to restrict the journey to travel wholly within a specified location Location 1 and Location 2 Use Location 1 and Location 2 to restrict the origin and turnaround point or destination point of your journey. The term turnaround point applies to round-trip journeys, while the term destination point applies to one-way journeys. If you want to be specific on which location is the journey origin or the journey turnaround point/destination point, indicate your preference by selecting the Location 1 is Journey Origin indicator. If nothing is specified in Location 2, then all journeys that originate from Location 1 would apply. Location 1 Journey Origin Select the Location 1 Is Journey Origin provision to indicate that Location 1 is the Journey Origin, or leave it blank to indicate that Location 1 is either the journey origin or the Journey Turnaround/Journey Destination. T March 2009

18 Ticketing Fees When you indicate that Location 1 is the journey origin point, then it follows that Location 2, if present, is the turnaround point/destination point. When you leave this provision blank, then Location 1 can be either origin or turnaround point or destination point. The following charts provide an explanation on how to use the location fields in conjunction with the indicator Location 1 Journey Origin. The round-trip journey chart is separate from the one-way journey chart. For Round-Trip Journeys Location 1 Location 2 Is Origin Indicated? Result TPE LAX Yes Specifies a RT journey that originates in TPE with a turnaround point in LAX TPE Blank Yes Specifies a RT journey that originates in TPE with no restriction on turnaround point TPE LAX No Specifies a RT journey that originates in TPE with turnaround point of LAX, or the reverse, origin LAX and turnaround point TPE LAX TPE No The above result can also be achieved when locations are swapped TPE Blank No Specifies a RT journey where TPE can be the origin or the turnaround point For One-Way Journeys Location 1 Location 2 Is Origin Indicated? Result TPE LAX Yes Specifies a OW journey that originates in Location TPE with a destination point in LAX TPE Blank Yes Specifies a OW journey that originates in Location TPE with no restriction on destination point TPE LAX No Specifies a OW journey that originates in TPE with a destination point of LAX, or the reverse, origin LAX and destination TPE LAX TPE No The above result can also be achieved when locations are swapped TPE Blank No Specifies a OW journey where the origin or destination is TPE Travel Via Location Use the Travel Via Location if you require the passenger to travel via a specific location. The Via Location refers to a ticketed point on the journey that is neither a journey origin, a journey turnaround, nor a journey destination. The via point can on the inbound or outbound only or be on both outbound and inbound portion. The via location may be a connection or a stopover and must exist between Journey Location 1 and Location 2 when present. T March 2009

19 Ticketing Fees Travel Wholly Within Location Use Travel Wholly Within Location to indicate that all ticketed points of the journey must be within the location specified including the journey origin, journey turnaround, and journey destination points. T March 2009

20 Ticketing Fees Bank Identifier (Form of Payment) The Form of Payment Bank Identifier Bin Number further defines the specific credit card fee such as MasterCard or Bank of America Visa. This field cannot be used with Ticketing or Requested Sub Code types, because it has no application. The first six characters of all credit card forms of payment can be used to identify the category of the entity that issued the credit card, the card brand (such as VISA), and the card issuer (such as Bank of America). You can use an asterisk (*) as a wildcard value in the second through sixth characters in order to specify any number in its place. For example, value 12**** may be entered to indicate that at least one form of payment must be a card with a Bin Number starting with 12, value 1234** to indicate any card starting with 1234, or value 1***** to indicate any card starting with 1. When used in combination with a Form of Payment type Sub Code, there is no cross-edit in place to require that a BIN number must begin with the same number as the Form of Payment number. For example, if you specify FC4 and BIN number 6*****, then your provisions will never be applied because they contradict each other. When the Sub Code does not specify a form of payment and the Bank Number Identifier Bin Number is blank, there are no form of payment requirements and any form of payment can be applied. T March 2009

21 Ticketing Fees Pricing/Ticketing Input Request The following provisions are applied against the input command that priced the ticket (the requested passenger type, ticket designator, and account code) and are not applied against the actual fare selected. Passenger Type This field is used to specify that the Ticketing Fees data applies based on the passenger type used in the input request; this does apply to the passenger type of the fare. Passenger Type mapping also applies, meaning that if passenger type CNN (accompanied child), it will map (apply) to any child/infant passenger type used in the request. When the Passenger Type is Blank there are no passenger type requirements for the Ticketing Fees; the fee will apply to all passenger types used in the input command. Note: ADT (Adult) passenger type can not be used in the Passenger Type field in Ticketing Fees and an edit prevents this coding. What is the Ticket Designator Table for? Ticket Designator Table Use this table to specify the Ticket Designator(s) that must be used in the pricing or combined pricing/ticketing input command. Ticket Designators are made up of 1 to 10 alphanumeric characters. Additionally, an asterisk (*) wildcard value can also be used to represent any alphanumeric set of characters in the Ticket Designator. If the Ticket Designator Table has no data, there are no restrictions on the Ticket Designator input command. The following rules apply for the asterisk wildcard value: If used, the asterisk may appear only once, anywhere in the Ticket Designator The asterisk cannot be used to replace a number when the immediately following or preceding character in the Ticket Designator is also a number. Example: DE*16 matches DEC16, DEC33Z16, and DE3C16, but does not match DEC316, or DEC163 When the asterisk is in the beginning or the middle, there is an assumed asterisk at the end. Example: *Q15 matches ABQ15XX and ABQ15XX50 When the asterisk is in the beginning it must be replaced with at least one character and cannot be left blank. When it is in the middle or the end, it does not have to be replaced by a character. Example: *ZZ33 does not match ZZ33AB but does match to QZZ33A; QZZ*3 matches to QZZ3, QZZA3X; and QXZ7* matches to QXZ7, QXZ7YQ An asterisk may be present alone, with no other alphanumeric characters. When used alone, this indicates that at least one Ticket Designator must be in the input command (any ticket designator) in order to apply the data. Example: * matches ABCD, QZZ45, or any ticket designator used, but does not match to blank on the input command T March 2009

22 Ticketing Fees Account Code Table This table provides the ability to positively specify Account Codes that should be compared to the Account Codes in a pricing or combined pricing/ticketed command. Account Codes are made to up of 1 to 20 characters (alphanumeric plus asterisk). If used, the asterisk acts as a wildcard (see below) and may appear only once, anywhere in the Account Code. When no Account Code Table exists, there are no restrictions on the account Code. The relationship among the different account codes within the table is OR. When an asterisk (*) wildcard is used to represent any alphanumeric string of characters in the Account Code, the following rules apply for the asterisk wildcard value: The asterisk cannot be used to replace a number when the immediately following or preceding character in the Account Code is also a number. Example: AB*12 matches ABC12, ABC33Z12, and AB3C12, but does not match ABC312, AB312, AB123, or ABC123 When the asterisk is in the beginning or the middle there is an assumed asterisk at the end. Example: *C21 matches ABC21XX and ABC21XX50; AB*ZZ matches ABCZZ21, AB123ZZQ, and ABCZZQ1 When the asterisk is in the beginning it must be replaced with at least one character and cannot be left blank. When it is in the middle or the end, it does not have to be replaced by a character. Example: *AB12 does not match AB123; AB*ZZ matches ABZZ and ABCZZ; ABC* matches ABC and ABCDE12 An asterisk may be present alone, with no other alphanumeric characters. This indicates that at least one Account Code must be in the input command in order for the data to apply. If the input command does not contain an Account Code, then the data will not apply. Example: * matches ABCD and QZZ45 T March 2009

23 Ticketing Fees Security Can I specify that data is private? Public/Private You can indicate that the data in each sequence is public data or private data for the purposes of ATPCO distribution, subscriber (GDS) display, and security within the ATPCO application. It is assumed that the validating carrier can display its own private data. If this field is blank, the record is public and available to all subscribers. Subscribers can permit anyone with access to their system to display the data. When this field is specified, the record is private and will only be distributed subscribers you authorize. For private records, you must include a security table indicating who the data is available for sell. Subscribers will only make the data available to the locations/entities specified in the Security Table. What is Private Distribution? Private Distribution In many other applications, you must send an instruction to ATPCO to specify private distribution information, which is maintained by ATPCO in the ATPCO Data Distribution Control Directory (G30). With Ticketing Fees, ATPCO is providing you the capability within each segment to enter your own distribution information. Ticketing Fees does not use the ATPCO Data Distribution Control G30 Directory to hold this information. You have control over your distribution needs without having to instruct ATPCO. You also have the ability to specify the same or different private distribution information in each segment. Use this field to specify which subscribers can receive the private data. GDSs and carriers (including owning carrier) must be current subscribers and have a valid entry in the ATPCO G30 directory in order to be specified. If a carrier is specified, a GDS must also be specified. It is not necessary to specify yourself (the owning carrier) in the Private Distribution field to receive the data, but you must be a subscriber in order to receive it. Do I need to include myself in the security table if I am the owning carrier? Security Table For private data, a Security Table (183) is required. The Security Table specifies the only entities that can display and sell the Ticketing Fee data (point of sale). It is assumed the Ticketing Fees owning carrier can always display its own data, however; you must include yourself in the Security Table in order to use the Ticketing Fee data in the market place. For public data, a security table is not required and there are no restrictions on where and to whom the Ticketing Fees data applies when the Security Table is blank. When a security table is present, then the Ticketing fee data applies only to the entities specified. The relationship of the data within a single row is AND, meaning all conditions must be applied together. The relationship of data across rows is OR, meaning conditions across rows are independent (apply this or apply this). Within the security table you can specify the following: Travel Agencies Carriers T March 2009

24 Ticketing Fees GDS (Global Distribution System) Duty/Function Codes Geographic Locations Airline Specific Codes ERSP Numbers (Electronic Reservation Services Provider) IATA Travel Agency Numbers LNIATA (Line IATA Number/CRT Address) Pseudo/Travel Agency Codes Carrier/GDS Department Codes Department Identifier When Travel Agency is specified, Ticketing Fee data applies to any travel agency (including online agencies and traditional brick and mortar agencies). The Carrier field in the Security Table is used to further define other security data. The fees are controlled by and accrue to the validating carrier (owning carrier of the record); therefore, you cannot specify a carrier other than the owning carrier of the record. When you specify a GDS, it applies to anyone using the specified GDS system. This includes all travel agencies and owning carrier with access to the GDS system. If the intent is to apply this information to only travel agencies with access to the GDS system, then you must specify Travel Agency in combination with the GDS (within the same row of data). The Duty/Function code specifies that the ticketing agent must be signed in using the specified duty/function code of the Carrier/GDS indicated. You must specify a carrier or GDS when Duty/Function contains data because the Duty/Function codes definition is GDS/carrier specific. Examples of Duty Function codes are GS (General Sells) and SU (Supervisor). You can indicate that the Ticketing Fees apply to specific locations by specifying geographic points (Area, Zone, Country, or State). When used in combination with other security data (within the same row), then geographic points apply only to the specified ticketing entity in that location. Airline-Specific Security Type codes are a generic specification used to identify a large group of airline locations. The definition of these locations is dependent upon the data in the Carrier and GDS fields, as follows: If a carrier or GDS is not specified, the airline locations apply to locations of the Ticketing Fees Record owner: RES = All reservation centers for the Ticketing Fees Record owner ATO = All airline ticket offices for the Ticketing Fees Record owner CTO = All city ticket offices for the Ticketing Fees Record owner WEB = Web site for the Ticketing Fees Record owner If a carrier is specified, the airline locations apply to locations of the carrier specified (only the Ticketing Fees Record owner can be specified): RES = All reservation centers for the specified carrier ATO = All airline ticket offices for the specified carrier T March 2009

25 Ticketing Fees CTO = All city ticket offices for the specified carrier WEB = Web site for the specified carrier If a GDS is specified, the airline locations apply to locations of the Ticketing Fees Record owner using the specified GDS: RES = All reservation centers for the Ticketing Fees Record owner on the specified GDS ATO = All airline ticket offices for the Ticketing Fees Record owner on the specified GDS CTO = All city ticket offices for the Ticketing Fees Record owner on the specified GDS WEB = Web site for the Ticketing Fees Record owner on the specified GDS Note: It is up to each subscriber to determine how to identify the locations indicated by the RES, ATO, CTO, and WEB codes. Before using any of the above codes in Security Table 183, you should verify with subscribers that they are able to identify the locations. The following are other Security Type codes used to who/where the Ticketing Fees data is applicable for: Security Types Pseudo City Code Travel Agency IATA Travel Agency Number Department/Identifier (requires an applicable carrier/gds code) Carrier/GDS Department Code (requires an applicable carrier/gds code) Electronic Reservation Service Provider (ERSP) LNIATA Number (Line IATA Number, CRT/Terminal Address) Values Up to six-character alphanumeric code Eight-digit numeric IATA-assigned agency code Up to a seven-digit code indicating the airline department or CRS agency/department with leading zeros. If you type 123, the system will automatically add lead in zeros ( ) Up to six alphanumeric characters The eight-digit IATA-assigned ERSP code. Up to eight alphanumeric characters. Note: The IATA Travel Agency Code requires an eight-digit number in which the eighth digit is a check digit. If only seven digits are provided, the system will automatically place a 9 at the end of the number (for example, if is entered, it will become ) T March 2009

26 Ticketing Fees Are there any coding examples for Ticketing Fees? Ticketing Fees Examples These examples illustrate different types of Ticketing Fee data entry intent. Assume that the following applies when carrier XX is the validating carrier (Ticketing Fees Record owner), unless otherwise specified. It is assumed the Ticketing Fees owning carrier can always display its own data, however; you must remember to include yourself in the Security Table in order to utilize the Ticketing Fee data in the market place. Example 1. Ticket Dates, Amount, and Public Distribution Sub Code First Ticket Last Ticket Amount/ Percent CUR Private FC1 01JUL06 01FEB USD FC1 02FEB07 01FEB USD Private Distribution Result: A credit card fee of USD 5.00 applies for credit card numbers starting with 1, and when the departure from the priced/ticketed journey origin is on/after 01JUL06 and on/before 01FEB07. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data. Example 2. Free, Location, and Private Distribution Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 FC1 LAX 123 Security Table No Charge Amount/ Percent CUR Private Free Shown on receipt X 1A Private Distribution Security Table 123 GDS 1A Security Type Code Number Department Identifier Result: For Department/Identifier using the Amadeus (1A) GDS system, no credit card fee applies for credit card numbers starting with 1. The data is allowed to be distributed to 1A. The data is available for display and sell by Department Identifier using the 1A GDS system. The data owner XX can display the data, but is not eligible to use the data in the market place because they did not include themselves in the security table. T March 2009

27 Ticketing Fees Example 3. F Type Sub Code, Locations 1 and 2 and Percent Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 Amount/ Percent FC5 X LON Area Private Private Distribution Result: Apply a credit card fee of 5 percent of the total amount charged to credit card numbers starting with 5 when the priced/ticketed journey origin is LON and the journey turnaround/destination is Area 3. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data. In this example, if the amount charged to the credit card was EUR , the fee would be EUR Example 4. T Type Sub Code, Amount and Account Code Sub Code Amount/ Percent CUR T USD 1789 Account Code Table 1789 Account Code Table AB6789 AB BB Account Code Table Private Private Distribution Result: A ticket issuance fee of USD 5.00 applies for account codes AB6789, AB123, or 12356BB. There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data. T March 2009

28 Ticketing Fees Example 5a. Identifying Credit Card Types Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 BIN Amount/ Percent CUR Private FCA 4023** 5.00 USD Private Distribution Result: A credit card fee of USD 5.00 applies for credit card BIN numbers starting with There is no restriction on distribution, so all subscribers are eligible to receive the data and there is no restriction on who can display and sell the data. In this case, if a customer uses a Visa credit card with number , as a form of payment, then a USD 5.00 fee will be applied. Example 5b. Identifying Credit Card Types Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 BIN Amount/ Percent CUR Private FC USD Private Distribution Result: A credit card fee of USD 5.00 applies for credit card numbers starting with 4. There is no restriction on distribution, so all subscribers are eligible to receive the data. In this case, if a customer uses a Visa credit card number then a USD 5.00 fee will be applied. If both the FCA and FC4 Sub Codes are present together, then the customer will be charged a total of because the Sub Codes are unique and both identify that the charge applies for the type of credit card being used. If your intent is to apply only one charge for the same type of credit card then you should only specify this using the generic FCA code and BIN number, or use the FC number specific Sub Code, but not both. An example using FCA with a BIN number is shown in Example 7. T March 2009

29 Ticketing Fees Example 6. Multiple Credit Card Types Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 BIN Amount/ Percent CUR Private FCA 40**** 5.00 USD FC USD FC USD Private Distribution Result: The FCA sequence states that a credit card fee of USD 5.00 applies for credit card BIN numbers starting with 40. There is no restriction on distribution, so all subscribers are eligible to receive the data. The FC5 sequence states that a credit card fee of USD 3.00 applies for credit cards starting with 5. There is no restriction on distribution, so all subscribers are eligible to receive the data. The FC6 sequence states that a credit card fee of USD 7.00 applies for credit cards starting with 6. There is no restriction on distribution, so all subscribers are eligible to receive the data. In this case if a Visa credit card number and another card that starts with 5 and a third card that starts with 6 is used. All three credit card charges will be applied for a total of USD If your intent is to apply only one charge for the same type of credit card, use only the generic FCA code and BIN number so you can organize the credit card fees in the order they should be applied (highest or lowest). An example using the FCA with a BIN number is shown in Example 7. T March 2009

30 Ticketing Fees Example 7. Multiple Form of Payments within a Single Transaction Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 BIN Amount/ Percent CUR Private FCA 40**** 5.00 USD FCA 5***** 3.00 USD FCA 6***** 7.00 USD Private Distribution Result: The first FCA sequence states that a credit card fee of USD 5.00 applies for credit card BIN numbers starting with 40. There is no restriction on distribution, so all subscribers are eligible to receive the data. The second FCA sequence states that a credit card fee of USD 3.00 applies for credit card BIN numbers starting with 5. There is no restriction on distribution, so all subscribers are eligible to receive the data. The third FCA sequence states that a credit card fee of USD 7.00 applies for credit card BIN numbers starting with 6. There is no restriction on distribution, so all subscribers are eligible to receive the data. If three different credit cards are used (matching BIN numbers 40, 5, and 6) within a single transaction, only one credit card fee will be applied because they are all within the same Sub Code. In the case above, the USD 5.00 fee would be applied. If your intent is to charge the highest fee of the three, then you need to position the sequence with the highest fee before the other fees. For example, in the above situation, you would need to position the USD 7.00 for BIN numbers starting with 6 above the other fees and BIN numbers in order to apply the highest fee. T March 2009

31 Ticketing Fees Example 8. Multiple Sequences with Various Data Rows Sub Code LOC 1 Journey Origin Journey LOC1 L OC2 BIN Amount/ Percent CUR Private Private Distribution Account Code Table Security Table Fare Basis/ Status When Fare Basis Appears on 1 FCA Free, Not Shown on Receipt F- All Coupons 2 FCA Free, Shown on Receipt 3 Frequent Flyer Status 3 FCA 41**** 8.00 USD X XS/IA FCA 4***** USD X XS/1A FCA 41**** 6.00 USD 6 FCA 4***** 8.00 USD 7 FCA 5.00 USD 8 R USD 9 T06 X US 5.00 USD 10 T USD 11 T USD Account Code Table 558 AB*12 Security Table 123 Row Travel Agency Carrier GDS Duty Function Type Location Security Type Code Number 1 1A N US 2 X XS 3 XX Airline Specific Code RES Security Table 234 Row Travel Agency Carrier GDS Duty Function Type Location Security Type Code Number 1 XX Airline Specific Code RES T March 2009

32 Ticketing Fees Result: (For this example, assume XX is the validating carrier). The row number below refers to the row number of the main data, not the additional tables. Row 1 When all coupons on the ticket contain an XX fare basis beginning with F, there is no credit card fee and this is not shown on the receipt. Row 2 When the passenger s Frequent Flyer Status is at least 3 (passengers with frequent flyer levels 1, 2, or 3), there are no credit card fees and this is shown on the receipt. Row 3 For points of sale located in the US using the 1A GDS system, a credit card fee of USD 8.00 applies for credit card BIN numbers starting with 41 for account code AB6789. For account codes matching AB*12 (the asterisk is a wildcard and can replaced by one or more characters), a credit card fee of USD 8.00 applies for credit cards starting with BIN number 41, for points of sale located in the US using the Amadeus (1A) GDS system. The data is allowed to be distributed to 1A and XS. The data is available for display and sale by US locations using the 1A GDS system, for travel agencies only using the XS GDS system, and for carrier XX (data owner) reservation (RES) centers. Row 4 For points of sale located in the US using the 1A GDS system, a credit card fee of USD applies for credit card BIN numbers starting with 4 for account code AB*12. The data is allowed to be distributed to 1A and XS. The data is available for display and sale by US locations using the 1A GDS system, for travel agencies only using the XS GDS system, and for carrier XX (data owner) reservation (RES) centers. Note: Positioning of data is very important. The data in Rows 2 and 3 are the same except for the BIN number and the fee. If the provision for BIN number 4 is positioned ahead of the provision for Bin number 41, the GDS would match any credit card starting with 4 (including 41) and apply the USD fee instead of the fee that should be charged for cards starting with 41. Row 5 A credit card fee of USD 6.00 applies for credit cards starting with BIN number 41. There is no restriction on distribution, so all subscribers are eligible to receive the data. Row 6 A credit card fee of USD 8.00 applies for credit cards starting with BIN number 4. There is no restriction on distribution, so all subscribers are eligible to receive the data. Note: Just as in Rows 2 and 3, positioning of the data is very important. Ensure you position the data in order of most specific to least specific. In this case, 41 is more specific than 4 and so appears first. Row 7 A credit card fee of USD 5.00 applies for any credit card. There is no restriction on distribution, so all subscribers are eligible to receive the data. T March 2009