PCI Shield | PCI Booking

PCI Shield

Whatever your position in the distribution chain you must store credit card information weeks, sometimes months to guarantee hotel reservations, thus credit card data is retained for the duration of the sale.  Using PCI Shield will not only simplify compliance, but will protect customers credit card data and protect the company brand.

PCI Shield uses all PCI Bookings applications, tools and APIs to address the specific requirements of each player in the distribution chain and their specific work-flow

Tokenization

On-the-fly Tokenization

Eliminates multiple Payment Gateway tokenization schemas that are incompatible with each other.

Pull tokenization request (Inbound on-the-fly HTTP Request)

Allows interception of incoming API requests, capturing card data, encrypting and storing on secure PCI Booking servers. A token is then sent to the eCommerce server with the card data masked.

Tokenization push (On-the-fly inbound HTTP Responses)

Allows interception of returned API responses and relaying them to the API requester. Captured card data is encrypted and stored on secure PCI Booking servers and a token is sent to the eCommerce server with the card data masked.

iFrame Payment Capture (Tokenization)

Secure iFrame Payment Capture

Customizable forms that are displayed on the lodging’s brand website. iFrame allows card data to be entered, tokenized and stored on secure PCI Booking servers. The secure data is then passed to the customer server. This provides the means to collect payment information on a hosted system without exposing the underlying Application Systems to PCI Scope.

Content Delivery Network (CDN)

Timely iFrame page loading, regardless of server location, is ensured through the use of the PCI Booking CDN. Abandoned bookings as a result of excessive page loading times are eliminated.

Token Replacement

Token Replacement – On-the-fly

Allows the distribution channel to use the card data in the API requests to 3rd parties by providing a token.  Distribution channels can use the end customer card in the API requests to third parties such as payment gateways or suppliers (hotels, car rentals, airlines) without the need to be exposed to the card data itself.

Multiple card payments with single token

the solution allows the use of a single token (card) for sending multiple destinations saving up to 90% in card processing fees.  A captured (and tokenized) card can be used for real time payment to multiple parties such as any supplier associated with a booking.  i.e. airlines, car rental companies, car rental firms, payment gateways etc.  CVV details may be included in requests.  Captured cards may also include security code data.

Card Storage

Secure Card Storage

Card data can be stored for an unlimited time on PCI Booking Servers. This will provide better service to returning customers by enabling quick check-in and check-out processes.

Secure Card Storage Controls

Addition and deletion of cards in storage is controlled by the customer. This enables a flexible card retention policy.

Secure Card Storage Query

Ability to query existing card data stored on PCI Booking Servers by custom references. Allows easy listing of cards related to a specific end-customer and enables the end-customer to select an already stored card without the need to maintain sensitive data on internal systems.

Control 3rd Party Access to Card Data

Allow third suppliers such as hotels to use the card data already captured by the distribution channel.  The same card can be used multiple times for different bookings with different suppliers.

Compliance with EU Directive