Online Travel Agencies (OTAs) such as Booking.com, Expedia, etc. provide a web-based application programming interface (API) through which Channel Managers, hotels and other hospitality services such as rental car companies retrieve booking information.
The retrieved booking information contains credit card account numbers.
Comply with the Payment Card Industry Data Security Standard (PCI-DSS) requirements by removing the credit card account number from the Channel Manager’s data flow.
Channel Managers receive booking orders from multiple online travel agencies (OTAs) such as Booking.com, Expedia, Travel Advisor, etc. The returned order information contains credit card account numbers. The Channel Manager services need to remove the credit card account numbers from their data flow to meet PCI requirements.
ASI's Proxy4pci service addresses the Channel Manager's PCI security requirements. The Channel Manager's communications with the Online Travel Agency flow through the Proxy4pci service which replaces the credit card account number with an AuricVault® token, thus removing the credit card account number from the Channel Manager’s environment. Our service then securely stores the data.
Before switching to the Proxy4pci service, the Hotel Channel Manager sent requests for new bookings directly to the Online Travel Agency. The responses had plaintext credit card account numbers.
The Proxy4pci service tokenizes the Online Travel Agency’s responses.
The Proxy4pci tokenized data flow.
- The Channel Manager (or Hotel) sends an Online Travel Agency request to the Auric Proxy4pci service looking for customer reservations.
- The proxy service forwards that request to the Online Travel Agency.
- The Online Travel Agency responds with booking information.
- The proxy service scans the response and sends all the plaintext credit card account numbers to the AuricVault® service.
- The AuricVault® service securely stores the credit card account number and returns an AuricVault® token to the Proxy4pci service.
- TheProxy4pci service replaces the credit card account number with the token, then returns the tokenized response to the Channel Manager.
- The tokenized data is retrieved by an individual hotel, B&B, lodging facility, or car rental agency.
- The hotel sends the token to the AuricVault® service and,
- receives back the original (detokenized) credit card account number.
- Removing the credit card account numbers from the OTA response reduces Channel Managers PCI footprint.
- Hotels, management services, and other hospitality vendors can use other Auric services to:
- retrieve or process the credit card number securely within their facility.
- pass the credit card number to client lodging facilities via an embedded iFrame.
- convert the AuricVault® token to a specific payment processor's token using the Token Swap option.
- process payments with the Payments Passthrough option.
NOTE: The Proxy4pci service is in closed Beta. Please contact sales@AuricSystems.com to request access.