Skip to content
ACCOMMODATION/
/
Regular travellers
Last updated

Regular travellers

Learn how to create accommodation orders where travellers pay directly at the property.

Pay at the property scenarios

In this scenario, the traveller pays the property directly during their stay. Depending on the property’s payment configuration, the traveller may also need to provide card details to guarantee the booking.

Traveller type
The flow
partnerTraveller pays directly at the property using one of the payment methods accepted by the property.✓ The traveller makes a booking and provides personal details.

✓ If required, the traveller also provides card details to secure the reservation.

✓ You send the booking details to Booking.com.

✓ The property handles the payment directly with the traveller.

Use case

A traveller uses your application to find a property, creates a booking, and chooses to pay directly at the property.

Follow the instructions below to build the payment object required in your /orders/create request.

1. Check the available payment options

→ Follow the Payments Quick guide to learn how to retrieve supported payment methods, timings, and schedules.

Type
Endpoint
usage
houseIconPay at the property/accommodations/detailsCheck which payment methods the property accepts for on-site payment.
/orders/previewDetermine whether a payment card is required to secure the booking and which card types are accepted.
  • If method_required = true the traveller must provide a card to secure the booking - Include the card details in the payment.card object of your /orders/create request.

2. Create the order

The following examples show common pay-at-the-property booking scenarios.

Each example demonstrates the payment object required in the /orders/create request.

  1. Create your /orders/create request
  2. Build the payment object based on the applicable scenario below.

Secure the booking with a card

The traveller pays at the property, but the property requires card details to guarantee the reservation.

The flow

  • The traveller provides card details to secure the booking.
  • You send the card details to Booking.com.
  • Booking.com securely forwards the booking guarantee information to the property.
  • The property charges the traveller directly during their stay.

drawing

The payment object in your /orders/create request should look like this:

{
  "payment": {
    "card": {
      "cardholder": "Test Name",
      "cvc": "123",
      "expiry_date": "2030-10",
      "number": "1234123412341234"
    },
    "method": "card",
    "timing": "pay_at_the_property"
  }
}

Field requirements:

  • payment.card.cardholder
  • payment.card.cvc
  • payment.card.expiry_date
  • payment.card.number

These fields must contain valid card details that can be used to secure the booking.

  • payment.timing - Must be "pay_at_the_property".
  • payment.method- Must be "card".

Use the /orders/preview response to determine which card types the property accepts in payment.methods.cards. See the Payments quick guide for more details.

For this scenario, do not include:

  • payment.airplus
  • payment.business_information
  • payment.include_receipt

Pay at the property without card

The traveller pays at the property and the property does not require card details to secure the booking.

This scenario is available when the property does not require a payment card either for prepayment or as a booking guarantee.

The flow

  • The traveller creates the booking without providing payment card details.
  • You send the booking details to Booking.com.
  • The property collects payment directly from the traveller during their stay.

direct pay

The payment object in your /orders/create request should look like this:

{
  "payment": {
    "timing": "pay_at_the_property"
  }
}

Field requirements:

  • payment.timing: Must be "pay_at_the_property".

For this scenario, do not include:

  • payment.card
  • payment.airplus
  • payment.business_information
  • payment.include_receipt

Because no online payment method is used,payment.method is not required.

Curious to know more?
Previous page
Next page