4 Secure Payment Data Processing


Tokenization Workflow

This section outlines how a Central Reservation System (CRS) uses OHIP and OPI Cloud to securely tokenize and transmit payment data using OPI Cloud Payment Tokens. The tokenization workflow ensures that credit card data is processed in a PCI-compliant manner using certified Property Payment Service Providers (PSP).

This image shows the tokenization workflow.


1.1 CRS Tokenizes Using Property PSP through OHIP Tokenization API

The CRS initiates tokenization by calling the OHIP Tokenization API. This request is forwarded to OPI Cloud, which then routes the tokenization request to the appropriate Property PSP already certified with OPI Cloud.


1.2–1.3 Tokenization Request Propagation

OHIP relays the tokenization request to OPI Cloud. OPI Cloud then communicates with the correct PSP to generate a secure payment token.


2.1 CRS Sends Reservation with OPI Cloud Token

Once tokenization is complete, the CRS sends a reservation to OHIP that includes the OPI Cloud Payment Token.


2.2 Booking Is Created in OPERA Cloud

Using the OPI Token, OHIP creates the booking in OPERA Cloud, associating it with the tokenized payment details.


Refer to the Reservations Credit Card Payment Methods Implementation Guide for additional information and operation samples.