Skip to main content
PCI Booking provides payment service providers (PSPs) with a robust API for tokenization, card data management, and payment processing. Whether you are building a gateway integration, adding digital wallet support (Apple Pay, Google Pay, PayPal), or storing sensitive data on behalf of merchants, PCI Booking’s PCI DSS Level 1 certified infrastructure handles the compliance burden. The Payments Library offers a client-side SDK for accepting multiple payment methods through a single integration. Data blocks let you store arbitrary sensitive data (not just card numbers) in a tokenized, compliant manner.

​
Where to Start

API Overview

Explore the full PCI Booking REST API for tokenization, token management, and payment processing.

Quickstart Guide

Set up authentication and make your first API call.

Payments Library

Integrate the client-side SDK to accept credit cards, Apple Pay, Google Pay, PayPal, and more.

Gateway Credentials

Store and manage payment gateway credentials for processing transactions.

Apple Pay Setup

Configure Apple Pay for use with the Payments Library.

Google Pay Setup

Configure Google Pay for use with the Payments Library.

Data Blocks

Store and retrieve arbitrary sensitive data using tokenized data blocks.

Testing and Going Live

Use the sandbox environment to validate your integration before production.

​
Key Integration Points

  • Server-side tokenization: Tokenize card data on incoming or outgoing API calls without changing your existing message format. See Tokenization on Response and Tokenization on Request.
  • Token replacement: Inject real card data into outgoing requests to downstream providers. See Token Replacement.
  • Payments Library credentials: Store PSP credentials for Apple Pay, Google Pay, PayPal, and other methods. See Payments Library Credentials.
  • Data blocks: Tokenize and store any sensitive data (passports, IDs, PII) with the same compliance guarantees as card data. See Data Blocks.

​
API Reference

For detailed endpoint documentation including request/response schemas, authentication, and error codes, see the API Reference.