> ## 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 Online Travel Agencies

> Learn how OTAs use PCI Booking to capture traveler card data, relay tokens to hotels, charge via payment gateways, and stay PCI DSS compliant.

# For Online Travel Agencies

PCI Booking helps Online Travel Agencies (OTAs) handle payment card data without the burden of PCI DSS certification. Whether you need to capture cards from travelers, relay card details to hotels, or charge cards through your payment gateway, PCI Booking acts as a secure middleman so sensitive data never touches your servers.

With PCI Booking, your OTA can tokenize cards at the point of booking, store them securely, and use tokens to process payments or forward card data to accommodation providers. This keeps you fully compliant with PCI DSS and PSD2/SCA requirements while maintaining a seamless booking experience for your customers.

## Where to Start

<CardGroup cols={2}>
  <Card title="How PCI Booking Works" icon="diagram-project" href="/concepts/how-pci-booking-works">
    Understand the tokenization flow and how PCI Booking fits into your booking pipeline.
  </Card>

  <Card title="Quickstart Guide" icon="rocket" href="/start-here/quickstart">
    Get up and running with your first integration in minutes.
  </Card>

  <Card title="Capture Cards from Travelers" icon="credit-card" href="/capture-cards/overview">
    Embed a secure card entry form in your checkout flow to tokenize card data.
  </Card>

  <Card title="Card By Link" icon="link" href="/capture-cards/card-by-link">
    Send a secure link via email or SMS so travelers can enter card details for phone bookings.
  </Card>

  <Card title="Relay Tokens to Hotels" icon="hotel" href="/use-tokens/token-replacement-in-request">
    Forward tokenized card data to hotels and suppliers using token replacement.
  </Card>

  <Card title="Charge via Payment Gateway" icon="money-check-dollar" href="/use-tokens/charge">
    Process charges through 100+ supported payment gateways using stored tokens.
  </Card>

  <Card title="PSD2/SCA Compliance" icon="shield-check" href="/use-cases/comply-with-psd2">
    Implement Strong Customer Authentication to meet PSD2 requirements.
  </Card>

  <Card title="Common Use Cases" icon="route" href="/use-cases/how-do-i">
    Browse step-by-step workflows for OTA scenarios like capture-and-relay and capture-and-charge.
  </Card>
</CardGroup>

## Typical OTA Workflows

* **Capture and relay to hotel**: Tokenize the traveler's card at booking, then use token replacement to send the card data to the hotel's system. See [Capture and Relay to Hotel](/use-cases/capture-and-relay-to-hotel).
* **Capture and charge**: Tokenize the card and process a charge through your payment gateway in a single flow. See [Capture and Charge](/use-cases/capture-and-charge).
* **Phone bookings**: Use Card By Link to send a secure card capture form to travelers who book by phone. See [Card By Link](/capture-cards/card-by-link).

## Testing Your Integration

Before going live, use PCI Booking's sandbox environment to validate your integration end to end. See [Testing and Going Live](/getting-started/testing-and-going-live).