OXI Credit Card Vault Handling

The Credit Card Vault functionality can only be activated by the IFC > Credit Card Vault application function, which is hidden. Please contact your regional office to get this application function activated and to find out more details.

OXI Credit Card Vault Overview

In OXI, new functionality has been added to store the Unique ID of the Credit Card Vault functionality as well as the last 4 digits of the credit card number (to be used for identification) and an expiration date for the Unique ID. A new interface message to retrieve the Unique ID based on the credit card number and vice versa. Subsequently all transactions related to that customer's charge will communicate using this Unique ID. See Credit Card Vault for further details on the functionality of this feature.

Note: The last four digits of the credit card number and the expiration date are used in for identification purposes only and remain visible on screens throughout the application.

OXI Match and Merge and Reservation Updates have been impacted in the following manner:

New/Updated Incoming Profile from OXI - Match and Merge

• External System receives the Unique ID at time of creation
• Profile is downloaded from OXI with a Unique ID already attached
• Unique ID is then compared to existing IDs in the system
• Profile match and merge continues as normal
• If the EFT system is down, no credit card number will be stored nor will it be used for matching purposes

New/Updated Incoming Reservation from OXI - Match and Merge

• External CRS receives the Unique ID at time of creation
• Reservation is downloaded from OXI with a Unique ID already attached
• Unique ID is then compared to existing IDs in the system
• Reservation is updated/created as normal
• If the EFT system is down, no credit card number will be stored nor will it be used for matching purposes

Outgoing Reservation Updates to 3rd Party CRS Systems

• Reservation is updated in OPERA and an update is sent to the external 3rd party CRS system
• EFT system is called to retrieve the credit card number based on the Unique ID
• Credit card number is returned, inserted into the outgoing message, and sent to the CRS system via HTTPS connection
• Credit Card number is removed from memory and never stored in the database
• If the EFT is down, outgoing message will need to be queued until the EFT system is back up

OXI Processor

The OXI Processor has been enhanced to perform credit card information mapping when the Credit Card Vault functionality is enabled. OXI Messages have been modified in the following manner:

Inbound Message Processing

When the vault functionality is enabled, the message will contain the associated vault key(s), as the end point would have performed the credit card mapping prior to storing the message in database. Processing code will pass these keys to OPERA for storage and/or processing. When the Credit Card Vault functionality is disabled, plain credit card data remains in the message as it currently does.

Outbound Message Processing

When the Credit Card Vault functionality is enabled, vault keys of all associated credit cards will be obtained from OPERA and will be provided with the message to the destination to reverse lookup the plain credit card information and embed it in the outgoing message. When the Credit Card Vault functionality is disabled, plain credit card information would be present in the original message as is current functionality.

Message Types

Message types that are affected by the Credit Card Vault functionality include, but are not limited to:

• Reservation
• Profile
• Financial Transaction
• Lookup
• Enrollment