OTAs and booking engines

Get guest cards to hotels and suppliers without holding them

The guest pays on your site. The card goes to the hotel, the supplier or your own payment provider. Your systems keep a token.

Woman on a leather sofa typing on a laptop, with a cup of coffee on the table

Where card data goes

The guest pays on your site. The card goes where the booking goes.

Diagram: a guest pays on your site; the card goes to the PCI Booking vault; it goes out to the hotel by display link and to the supplier; your platform holds tokens.
Diagram: a guest pays on your site; the card goes to the PCI Booking vault; it goes out to the hotel by display link and to the supplier; your platform holds tokens.

What changes for your platform

Capture the card, deliver it, charge it

Capture on your site

A hosted card form inside your booking page, in your branding and languages, with 3D Secure. The card goes straight to the vault and your site gets a token.

Deliver to hotels

Send the hotel a secure display link instead of an email. Forward the card to the hotel's system in the format it expects. Or share a token with a hotel that uses PCI Booking.

Charge, or pass on virtual cards

Charge the guest through your own provider, with one API across 120+ integrations. Pass virtual cards on to hotels and suppliers.

Capabilities that solve it

The parts of PCI Booking an OTA uses

FAQ

Questions OTA teams ask

How does the hotel see the guest's card?

We send the hotel a secure link. Authorised staff open it, confirm with a one-time password and view the card in a secure form. The card is not emailed and does not pass through your systems, and showing it to the hotel adds nothing to your PCI scope.

Can we send cards to suppliers that have their own systems?

Yes. We forward the card to any approved system in the format it expects. The major OTAs, channel managers and GDSs have ready-made profiles. For any other system, your request carries a token placeholder and we put the card in on the way out.

Can we charge the guest ourselves?

Yes. Charge, pre-authorize, capture, refund or void through your own payment provider with one API, across 120+ integrations.

Will guests notice anything different?

The hosted card form sits inside your booking page, in your branding and languages, and supports 3D Secure 2. Guests stay on your site.