> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pcibooking.net/llms.txt
> Use this file to discover all available pages before exploring further.

# For Payment Service Providers

> Learn how PSPs integrate with PCI Booking's API, Payments Library, Apple Pay and Google Pay support, gateway credentials management, and data blocks.

# For Payment Service Providers

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

<CardGroup cols={2}>
  <Card title="API Overview" icon="code" href="/api-reference/overview">
    Explore the full PCI Booking REST API for tokenization, token management, and payment processing.
  </Card>

  <Card title="Quickstart Guide" icon="rocket" href="/start-here/quickstart">
    Set up authentication and make your first API call.
  </Card>

  <Card title="Payments Library" icon="wallet" href="/payments-library/overview">
    Integrate the client-side SDK to accept credit cards, Apple Pay, Google Pay, PayPal, and more.
  </Card>

  <Card title="Gateway Credentials" icon="key" href="/account-setup/gateway-credentials">
    Store and manage payment gateway credentials for processing transactions.
  </Card>

  <Card title="Apple Pay Setup" icon="apple" href="/account-setup/applepay-setup">
    Configure Apple Pay for use with the Payments Library.
  </Card>

  <Card title="Google Pay Setup" icon="google" href="/account-setup/googlepay-setup">
    Configure Google Pay for use with the Payments Library.
  </Card>

  <Card title="Data Blocks" icon="database" href="/additional-functions/data-blocks">
    Store and retrieve arbitrary sensitive data using tokenized data blocks.
  </Card>

  <Card title="Testing and Going Live" icon="flask-vial" href="/getting-started/testing-and-going-live">
    Use the sandbox environment to validate your integration before production.
  </Card>
</CardGroup>

## 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](/capture-cards/tokenization-on-response) and [Tokenization on Request](/capture-cards/tokenization-on-request).
* **Token replacement**: Inject real card data into outgoing requests to downstream providers. See [Token Replacement](/use-tokens/token-replacement-in-request).
* **Payments Library credentials**: Store PSP credentials for Apple Pay, Google Pay, PayPal, and other methods. See [Payments Library Credentials](/account-setup/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](/additional-functions/data-blocks).

## API Reference

For detailed endpoint documentation including request/response schemas, authentication, and error codes, see the [API Reference](/api-reference/overview).