Sharing booking context with properties

Providing a seamless experience for corporate partners and clients

Overview

Rapid API offers options to help properties better serve travelers by sharing additional booking context in lodging bookings. They are particularly useful for, but not limited to, business travelers.

These options help properties:

• Recognize corporate and TMC relationships
• Understand when virtual credit cards are used and how they should be handled

The main features are:

• Partner and client identification: share information with properties about the booking source (e.g. TMC and corporate clients).
• Virtual credit card instructions: share clear guidance on how a virtual credit card should be used for a property collect booking.

These are particularly useful when used in combination with:

• Travel purpose
• Hotel loyalty points
• Invoicing

Partner and client identification

Purpose

Partner and client identification lets you include information in the Booking request so the property can see:

• Which partner handled the booking (for example, a specific travel management company) and/or
• Which corporate client employs the traveler

This context gives properties enhanced visibility on the source of a booking, enabling them to:

• Recognize the Rapid partner a traveler booked through
• Recognize repeat or high‑value corporate guests
• Provide a more tailored travel experience
• Maintain continuity of treatment for frequent corporate travelers

API parameters

You can send this information using the following fields in the Booking request:

• supplier_transparency (object)
• consent_to_share (boolean, required if you want data shared with suppliers)

You may pass either partner or client name, or both.

Key rules:

• consent_to_share is mandatory for Rapid API to pass the data to suppliers
• If consent_to_share is not true, Rapid API will not share the partner/client information, even if supplier_transparency is populated

Example partner and client identification

{
  ...
  "supplier_transparency": {
    "point_of_sale_display_to_share": "PLS Partner Name",
    "company_name_to_share": "Corporate Client Name",
    "consent_to_share": true
  }
}

Field details

Virtual credit card instructions

Context

Corporate programs often pay for business travel using a mix of:

• Traveler personal credit cards
• Corporate payment cards
• Virtual credit cards (VCCs)

However, some properties lack clear guidelines on:

• How to recognize and process virtual credit card
• Which charges are authorized on a virtual credit card
• When the card can be charged (validity period)

This can lead to confusion at check‑in and/or check‑out and negative experiences for business travelers.

Purpose

Virtual credit card instructions provide properties with structured guidance on:

• Whether a virtual credit card is being used for a property collect booking
• Which expenses are covered (room, taxes, specified incidentals, etc.)
• Any charge limits and validity dates
• How to reach a card contact if something goes wrong

API Parameters

These instructions are added within the Booking request using:

• payments array:
  • type identifies a virtual credit card when virtual_card is used
• additional_handling object (within a payment entry) provides detailed payment handling instructions, such as:
  • authorized_expenses
  • specified_incidental_expenses
  • total_charges_allowed
  • is_cvc_required
  • authorizing_company
  • card_contact
  • payment_allowable_period_start
  • payment_allowable_period_end

The additional_handling object is optional, but recommended.

Example virtual credit card with additional handling

{
  ...
  "payments": [
    {
      "type": "virtual_card",
      "number": "4111111111111111",
      "security_code": "123",
      "expiration_month": "08",
      "expiration_year": "2025",
      "billing_contact": {
        "given_name": "John",
        "family_name": "Smith",
        "address": {
          "line_1": "555 1st St",
          "line_2": "10th Floor",
          "line_3": "Unit 12",
          "city": "Seattle",
          "state_province_code": "WA",
          "postal_code": "98121",
          "country_code": "US"
        }
      },
      "additional_handling": {
        "authorized_expenses": "total_plus_incidentals",
        "specified_incidental_expenses": [
          "breakfast",
          "internet"
        ],
        "total_charges_allowed": {
          "value": "875.00",
          "currency": "USD"
        },
        "is_cvc_required": true,
        "authorizing_company": "Conferma",
        "card_contact": {
          "email": "chucktesta@mydomain.com",
          "phone": {
            "country_code": "1",
            "area_code": "555",
            "number": "5555555"
          }
        },
        "payment_allowable_period_start": "2024-01-01",
        "payment_allowable_period_end": "2025-08-01"
      }
    }
  ]
}

### Key additional handling fields

| Field | Details |
| ----- | ----- |
| `authorized_expenses` | High‑level rule indicating what the virtual credit card can be used for, e.g.<br><br>• `room_only`<br>• `room_and_tax`<br>• `total_plus_incidentals` |
| `specified_incidental_expenses` | A list of specific incidentals that are allowed (for example breakfast or internet) |
| `total_charges_allowed` | An explicit upper limit on charges<br><br> • value: maximum amount<br>• currency: currency code (e.g. USD) |
| `is_cvc_required` | Indicates whether the CVC must be present for property to charge the card |
| `authorizing_company` | Name of the company that issued or manages the virtual credit card (for example a virtual credit card provider or corporate entity) |
| `card_contact` | Contact details in case the property experiences any issues charging the card:<br><br>• `email`<br>•`phone.country_code, phone.area_code, phone.number` |
| `payment_allowable_period_start / payment_allowable_period_end` | The date range during which the card is valid for charges (often aligned with stay dates plus a small buffer). |