Channel managers and distribution

Pass cards from OTAs to properties without storing them

Pass guest card details from OTA bookings to each property without storing them. Cards in OTA booking messages are tokenized as they arrive, and properties receive them in the format their systems expect. Your platform holds tokens.

Four people working at computer screens in a bright, sunlit office

Where card data goes

Cards become tokens on the way in, and cards again on the way out

Diagram: 1, an OTA sends a booking with a card; PCI Booking intercepts it and keeps the card in its vault. 2, your channel manager receives the booking with a token. 3, your channel manager sends the booking on with the token. 4, PCI Booking puts the card back and the PMS receives the booking with the card.
Diagram: 1, an OTA sends a booking with a card; PCI Booking intercepts it and keeps the card in its vault. 2, your channel manager receives the booking with a token. 3, your channel manager sends the booking on with the token. 4, PCI Booking puts the card back and the PMS receives the booking with the card.

What changes for your platform

Tokenize, deliver, answer partner demands

Tokenize inbound OTA messages

Booking messages from OTAs come to PCI Booking first, by API or HTTP. The card is swapped for a token on arrival, so your platform receives the booking with a token in place of the card number.

Deliver to the PMS in its format

Send the booking on to the property with the token in it. We put the card back in place of the token and deliver it to the property's PMS or booking system in the format it expects, or show it to authorised hotel staff in a secure form.

Answer partner PCI demands

Partners ask for proof of PCI compliance before they send cards. PCI Booking is a PCI DSS Level 1 service provider. We send you our Attestation of Compliance on request, and partners accept it on its own.

Capabilities that solve it

The parts of PCI Booking a channel manager uses

FAQ

Questions channel manager teams ask

Do OTAs need to change how they send bookings?

No. Partners keep their own systems and formats: JSON, XML, plain text or URL parameters, with their own encryption and signing. We capture the card on the way in.

How do properties receive the card?

In the format their system expects, or on screen for hotel staff, behind a one-time password. Properties that also use PCI Booking can receive a token instead.

Can we charge on behalf of properties?

Yes. Keep each property's payment provider details in one account and charge through the right one on each transaction, with one API across 120+ integrations.

What does this do to our PCI DSS scope?

Card data comes to us, not to your platform. That reduces your PCI DSS scope and simplifies your annual audit. We send our Attestation of Compliance on request.

Related: Receive cards from partners · Share cards with staff and suppliers · All industries