PCI Booking stores payment card details for travel platforms and sends them on to hotels, suppliers and payment providers, so your systems hold tokens instead of card numbers. We're at WTM London 2026, 3 to 5 November at ExCeL London. Naseer Ahmad (Global Head of Commercial & Partnerships) is attending.
Why meet with us
If card details pass through your platform, between OTAs, channel managers, PMSs, hotels and suppliers, every system they touch is in your PCI DSS scope. Each new partner or market adds another place to protect and more for your annual audit to cover. PCI Booking takes the card in, keeps it in a PCI DSS Level 1 vault and sends it where it needs to go, so your systems only ever hold tokens.
What we can discuss
- A smaller PCI DSS scope: how much smaller your scope gets when card data stays in our vault, and what your annual assessment still covers
- Cards from partners: cards from OTAs, channel managers and GDS, by API or file, replaced by tokens on arrival
- Charging through any provider: charge, pre-authorize or refund through 120+ integrations from the vault, with each hotel on its own payment provider
- Sharing cards with hotels and suppliers: showing a card to hotel staff by one-time link, and sending it to a supplier system in the format it expects
If you're attending WTM London, send us your details on this page to meet Naseer during the show.