Tokenize on Response Using Preset Profiles

E-commerce sites send a "Reservation with card data" request to a predefined and set third party (the integration will be done by PCI Booking).
Once the e-commerce site initializes the request, the third party will send a response, with the card data.
The e-commerce site will receive the card URI that was saved in the database.
We recommend that you first review the guide for this method.

Once the response from the third party is received in PCI Booking. the card details will be extracted from the message body and tokenized, the card details in the message will be masked and the token URI will be added to the response header (the header field will be X-pciBooking-cardUri).


Access Token Vs. Session Token

Between the two options of using the Access Token or the Session Token, we would recommend using the Access Token.


Multiple Authentication Methods allowed

This method accepts multiple forms of authentication methods (Session Token and Access Token). If more than one authentication method is provided, the Session Token will take precedence.


CVV Retention Policy

Remember to set the CVV Retention Policy for this token.

Click Try It! to start a request and see the response here!