Sabre has recently announced two changes related to the way credit card information is entered into PNRs (passenger name records) and displayed in IURs (interface user records, or “interface files”). This article explains how these changes ClientBase, Trams Back Office and Tres.
Tres Users:
For information about how these changes affect Tres, please see Sabre Form of Payment Wallet Functionality (FOP) and Credit Card Anonymization (Tres).
Form of Payment Wallet Functionality (FOP)
Form of Payment (*FOP) functionality Sabre affects how credit card numbers and other forms of payment are entered into PNRs and how agents reference them during the booking process. For more information about the Form of Payment Wallet functionality, please refer to Sabre Central (Sabre login required).
Effects: ClientBase
When *FOP functionality is enabled in your agency’s PCC, you will need to update your ClientBase merge-to-PNR rules to merge credit card information using the new format. The format depends on whether your agency is in the United States or elsewhere:
For the United States:
[[FOP*«Code»«Number»¥«Expiration»][¥CH¥«Name on Account»]][§CC/N/«Name on Account»][§CC/A/«Address Line 1»][ «Address Line 2»][ «Apt/Suite»][§CC/C/«City», «State»][§CC/Z/«Zip»]
For Canada and other countries:
[[FOP*«Code»«Number»¥«Expiration»][5¥CH¥«Name on Account»]][§CC/N/«Name on Account»][§CC/A/«Address Line 1»][ «Address Line 2»][ «Apt/Suite»][§CC/C/«City», «Province»][§CC/P/«Zip»]For more information about updating merge-to-PNR rules, please see Sabre Merge to PNR: Setup and Example Format Rules.
Effects: Trams Back Office
Trams Back Office does not use the information stored directly in the form of payment fields, so this has minimal impact on TBO interface.
Payment Card Anonymization of Remarks
Sabre is continuing to enhance its internal controls to further guard against the unauthorized inclusion of payment card information (PCI). This enhanced control will provide added security with anonymization (removal) of potential payment card data should it inadvertently be placed in unsecured free text PNR fields. For more information, please refer to Sabre Central (Sabre login required).
This means that only masked forms of credit card information will be included in interface user records (IURs), except card numbers entered into Sabre accounting lines. Anonymized card numbers will only include the first two digits and the last four digits of the account number, with the middle digits being replaced with “0’s”. For example, the card number “4444333322221111” will display as “44000000001111”, much as credit cards are masked in Trams Back Office and ClientBase, where the same card number displays as “VI44-XXXX-1111”.
It is important to note that the masking only affects card numbers that are not entered into the form of payment section of Sabre accounting lines. There is a TJR option that controls whether card numbers entered into Sabre accounting lines interface as the full card number or in the masked format.
If your agency has the recommend TJR setting IURCCMASK¥NEVER, the full card number will continue to interface for those bookings. If you do not want the masked format for all card numbers, change the TJR option to IURCCMASK¥ON.
Effects: ClientBase
ClientBase does not import payment information from Sabre, so this change does not affect ClientBase users.
Effects: Trams Back Office
All card numbers except those entered into Sabre accounting lines will interface in the new masked format. This includes card numbers that store deposit and guarantee information in PNR hotel and car segments, and card numbers entered into PNR remarks and accounting line free-flow text areas.
The primary effect for Trams and Tres users is that when entering CC Merchant payments, the card number must be entered into an accounting line to interface to TBO so they can be submitted for merchant authorization. In the free-text portion of the accounting line, include the descriptor *CP4 (payment method “CC Merchant”), and *XP(card expiration date), for example:
AC(segment type and number)/(vendor ID)/(invoice descriptor)/(commission)/(base fare)/(taxes)/(payment application)/CC(card type and number)/1-*CP4*XP0131
Example: ACOTH1/SVCFEE/FEE/35.00/35.00/0.00/ALL/CCVI4444333322221111/1-*CP4*XP0131
Additional Information
Sabre has prepared several resources on Sabre Central that explain these changes. Please refer to the following article for more information. A Sabre login is required to access this information: