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

# Send Stored Card Details to a Hotel Property

> Tokenize a guest's card and let the hotel securely view or retrieve the card details, without the card data touching your systems.

This workflow covers tokenizing a card from any source and giving a hotel access to view the card details. Use this when you already have a token (or are tokenizing from a third-party source like an OTA or channel manager) and need to share it with a hotel. If you need to capture the card directly from the cardholder first, see [Collect a Guest's Card and Share with a Hotel](/use-cases/capture-and-relay-to-hotel) instead.

## Step 1: Tokenize the Card

Capture and tokenize the card using any of PCI Booking's methods:

* [Hosted Card Entry Form](/capture-cards/hosted-card-entry-form) - embed a card form in your website
* [Card By Link](/capture-cards/card-by-link) - send a secure capture link via email or SMS
* [Tokenization on Response](/capture-cards/tokenization-on-response) - tokenize card data from a third-party API response
* [Universal Tokenization](/capture-cards/universal-tokenization) - tokenize cards from any source format

The result is a card token (a URI pointing to the stored card details in PCI Booking).

## Step 2: Send the Card to the Hotel

How you deliver the card to the hotel depends on your integration approach:

### Option A: Card Display with OTP (Recommended)

Send the hotel contact a secure link. PCI Booking handles identity verification and card display. No portal setup or user accounts needed on the hotel's side.

1. Call the [Card Display OTP endpoint](/api-reference/process-cards/card-display-otp) with the card token, the hotel contact's email, phone number, and name.
2. PCI Booking sends an email with a secure link.
3. The hotel contact clicks the link and verifies their identity via SMS code.
4. Card details are displayed on PCI Booking's hosted page.

See [Card Display with OTP](/use-tokens/card-display-otp) for full details.

### Option B: Card Display (iframe in your portal)

If you operate your own portal where hotels can log in, display the card details in a secure iframe embedded in your system.

* Generate a [Card Display Form](/api-reference/process-cards/request-card-display-form) link for the token.
* Embed the iframe in your portal. The card details render inside PCI Booking's secure domain, so card data never touches your servers.

See [Card Display](/use-tokens/card-display) for setup details.

### Option C: Token Replacement

Send the card details directly to the hotel's API using [Token Replacement](/use-tokens/token-replacement-in-request).

* Build an API request to the hotel's system containing the card token.
* PCI Booking replaces the token with real card data in transit.
* The hotel receives the card details without you ever handling them.

## Related

* [Card Display with OTP](/use-tokens/card-display-otp). OTP-secured card display with no portal needed.
* [Third-Party Permissions](/manage-tokens/third-party-permissions). Control which properties and merchants can access your tokens.
* [CVV Retention Policy](/capture-cards/cvv-retention-policy). If the hotel needs to see the CVV, set a retention policy before they access the card.
* [Process OTA and Channel Manager Payments](/use-cases/third-party-to-gateway). Need to charge the card instead of sharing it? See this workflow.
* [Share a Token Between Merchants](/use-cases/share-token-between-merchants). Both companies on PCI Booking? Share the token directly without relaying card data.