Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Please see below Document for Sabre updates. TMC Action is required!!

Note: These are Sabre updates not Deem

Update as of Aug 12th, 2024

Dear Sabre Partner:

 We recently received a notice from Sabre with updated dates.  Please see the new dates below.  These are subject to change based on new information from Sabre Deem can enable this functionality prior to the dates below. Please log a Deem Support ticket to have this enabled. 

 There are three very important changes coming from Sabre that require TMCs action. These are major updates to the way a TMC processes FOP. Make sure you read the SAN-16331 from Sabre and that your agency is ready for these impactful changes. It is critical that your Sabre automation team reviews these changes.  

Deem will have a configuration setting if you want to unmask the form of payment and use the system default entry of that will leverage the new Sabre Wallet format (FOP).  Please log a ticket to have this enable. If you want to continue with the masked form of payment you will need to update your PNR Edits. Please reach out to your internal Sabre contact to help you with this (if needed). 

If you want to start using the Sabre Wallet you will need to:  

Activate the PNAPNR option in your TJR (format: W/PNRPNR#ON) and test that PNR data is going to your backoffice properly.  

When you activate this setting today, a 5- entry will result in the FOP going into the Sabre Wallet (to display: *FOP, not *5). This behavior will persist until September, but will be removed by Sabre at the time they enact the last phase of SAN-16331 (September 30th). 

By this time, you must be passing FOP using the FOP formats; 5- will no longer be an accepted input. 

 

September 30th  

Only Sabre Wallet is supported as the FOP entry 5- entry will be restricted 

Deem will enable FOP for all sites 

 Customers that have a business need to send payment card data to their backoffice should refer to the following SANs to learn of an alternative solution available using the form of payment Wallet (*FOP): 

SAN 17007 - Form of Payment Wallet (*FOP) New Use Type for Interface Record 

SAN 17009 - Interface User Record (IUR - New MX Record for form of payment Wallet (*FOP) 

Also, please note changes to CCVIEW in SAN 17020. For EPRs without this keyword, the FOP data will be obfuscated during PNR creation/modification (prior to end transact). 

Thanks

Deem Customer Success

 

  • No labels