> ## 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.

# Collect a Card and Process a Payment

> Securely collect card details from a cardholder and charge through any connected payment gateway. PCI Booking handles the card data so your servers never touch it.

This workflow covers collecting card details directly from the cardholder and charging the card through a payment gateway using PCI Booking. Your servers never handle raw card data, keeping you out of PCI scope while you process payments through any supported gateway.

## Card capture and payment processing options

| Capture Method                                                                          | Charge Method                                                                                                          |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| [Hosted Card Entry Form](/capture-cards/hosted-card-entry-form) - embed in your website | [Universal Payment Gateway](/use-tokens/universal-payment-gateway) - send to gateway via PCI Booking **(recommended)** |
| [Card By Link](/capture-cards/card-by-link) - send a capture link via email/SMS         | [Token Replacement](/use-tokens/token-replacement-in-request) - inject card data into your own gateway API call        |

You can mix and match any capture method with any charge method. The example below uses Card By Link and Universal Payment Gateway.

## Step 1: Set Up Your Payment Gateway

Before processing charges, set up an account with a supported payment gateway.

1. Find a supported gateway on the [PCI Booking website](https://pcibooking.net/universal-payment-gateway/).
2. Set up an account with that gateway (or use existing credentials).
3. Store your gateway credentials in PCI Booking via the [Gateway Credentials](/account-setup/gateway-credentials) setup.

## Step 2: Customize the Card Capture Experience

Brand the capture experience to match your business:

* [Custom Translations](/account-setup/custom-translations) - localize form labels and messages
* [Stylesheets](/account-setup/stylesheets) - apply custom CSS to the card form
* [Card By Link Templates](/account-setup/card-by-link-templates) - customize the Card By Link email, SMS, and landing page

## Step 3: Collect the Card

Using Card By Link as an example:

1. Send a [Card By Link request](/api-reference/tokenize-cards/cotp-send-card-form) to PCI Booking with the cardholder's email or phone number. Include optional details like amount, currency, and reference number.
2. PCI Booking sends a secure link to the cardholder via email or SMS.
3. The cardholder clicks the link and enters their card details on a mobile-friendly, PCI Booking-hosted page.
4. If configured, a [3D Secure prompt](/account-setup/3ds-merchant-setup) is displayed.
5. PCI Booking validates, tokenizes the card, and sends a [callback](/api-reference/tokenize-cards/cotp-callback) to your system with the token.

## Step 4: Charge the Card

Send a [Process Transaction](/api-reference/process-cards/process-transaction) request with:

* Card token (from the callback)
* Amount and currency
* Gateway name
* Gateway credentials

PCI Booking injects the real card data and forwards the charge to the gateway. You receive the gateway's response directly.

## Related

* [Universal Payment Gateway](/use-tokens/universal-payment-gateway). Full guide on charging cards through supported gateways.
* [Authorize and Capture](/use-tokens/authorize-capture). Two-step auth + capture flow instead of direct charge.
* [Refunds and Voids](/use-tokens/refunds-voids). Reverse or refund a processed transaction.
* [Charge and Save for Future Payments](/use-cases/capture-charge-and-store). Need to save the card for future charges? See the full lifecycle guide.
* [Process OTA and Channel Manager Payments](/use-cases/third-party-to-gateway). Receiving cards from a third party instead? See this workflow.
