PCI Booking provides a simple, Restful, API to perform all actions regarding a credit card.

PCI Booking is made up of several application areas. This developers site contains a guide and a reference manual for each application area.

  • The guides allow software architects and designers to have a broad view on the system operation and easily pick up those components which can fit the best different application scenarios.
  • The reference manuals allow developers to have a clear understanding of which methods are available, what input parameters are required for each method and the expected results of each.

Capture and send card details to your hotels

When you work with your hotels via PCI Booking (by either using the Fully Branded Portal or by using the Branded Card Display Iframe), you will need to capture the card in PCI booking, associate the card with the property and then send the property a notification that they can access the card.

This guide will demonstrate an example of this process:

Step 1. Tokenize the card in PCI Booking

The first step in the process would be to tokenize the card with PCI Booking. You can use any one of the several methods that PCI Booking offers for tokenization:

The end result of any of the above methods is that the card will be tokenized in PCI Booking and you will hold the card token (A URI to the card details).

Step 2. Associating the card with the property

In order to allow the property to access the card details, you will need to first "associate" the card token with the property.
This can be achieved in one of two ways:

  1. Some of PCI Bookings' tokenization methods (such as the Store method, Tokenization in Response, Universal Tokenization and Tokenization via Card Capture) allow you to provide the merchant (the ID of the property in PCI Booking) that the resulting token should be associated with.
  2. PCI Booking offers a dedicated associate method to individually associate an existing token with a merchant.

Step 3. Send the card to the proeprty

While the fist two steps are unrelated to the chosen implementation, the following step is somewhat different between the Fully Branded Portal and the Branded Card Display Iframe.

Fully Branded Portal:

If you have chosen to use the Fully Branded Portal, then the card details is sent to the property within a reservation message which is then displayed to the property within the Portal. When the message is "received" in the portal, an email notification is automatically sent from PCI Booking to the property's email address with a notification that they had received a new reservation and a link to the reservation message itself.

  • In order to send the reservation message, you will need to submit a "message" through the PCI Messaging service.

Branded Card Display iframe:

If you have chosen to use the Branded Card Display Iframe, then the card details are displayed in the iframe within your portal and you will need to either send the property with a link directly to the page displaying the card details (read more on displaying the card details in the iframe) or direct the property to your portal and display a list of tokens that they can view and following their selection, display the card details in the iframe.

Capture and send card details to your hotels


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.