Corporate partners

Learn how to define the required payment data when you create your order, so your business travellers can pay at the property with an authorisation form (VCC or AirPlus)

Is this for me?

This use case is for Corporate partners who are authorised to pay at property on behalf of their employees with the supported payment methods.

	Traveller type	Payment method
	The traveller is a company employee and makes a booking for a business trip.	✓ Virtual credit cards (VCC) authorised by property (also known by "Payment instructions") ✓ AirPlus (when authorised) ✓ Virtual Credit Card (VCC) + MOTO

The following sections show, for each payment method and scenario:

The data that the /orders/preview response must contain.
How to define the payment object in your /orders/create request to use your payment option.

Follow these instructions and recommendations to create the payment data needed for your request.

1. Check payment timing and available methods

→ Refer to the Quick guide for examples of orders/preview responses and initial instructions on how to use the payment endpoints. So you can check the available payments options, including timings, schedules and methods.

2. Create your request

The following examples show different possibilities that your application could support when using the selected payment method.

Each example shows the payment structure that you must provide in your /orders/create request.

Go to your /orders/create request
Specify the needed information in the payment object, following the examples provided.

Pay at property

With a VCC and authorisation form

This option is only available if you are able to generate or obtain your own Virtual credit cards.

Pre-requisites

Checklist
☑	Your partner agreement authorises you to use Virtual credit card.
☑	You have a Virtual credit card provider/ Payment service provider (PSP).
☑	Demand API version must be updated to version 2.9 to use Virtual credit cards + Payment timings.

The flow

You forward a Virtual credit card (VCC) + details of what charges are allowed, to Booking.com.
Booking.com sends an authorisation form with this information to the property, so that it can charge the card appropriately when the business traveller stays.

drawing

→ Call /orders/preview to see the final details of the accommodation and products including when and how the payment can be made.

Refer to the Quick guide for examples of orders/preview responses and initial instructions on how to use the payment endpoints. So you can check the available payments options, including timings, schedules and methods.

The response must contain the general_policies.payment.pay_at_the_property field, with this data:

 "accommodation": {
           ...
           "general_policies": {
               "payment": {
                   ...
                   "pay_at_the_property": {
                       "method_required": true,
                       "dates": [
                           {
                               "at": "2023-12-18",
                               "price": {
                                   "accommodation_currency": 0.00
                                   "booker_currency": 0.00
                               }
                           },
                           {
                               "at": "2024-01-10",
                               "price": {
                                   "accommodation_currency": 205.78,
                                   "booker_currency": 205.78
                               }
                           }
                       ],
                       "methods": {
                           ...
                           "cards": [1,2,3,4,...]
                       }
                   }
               }
            },
           ...

This response shows that, for the selected property and product, with your authorised payment features:

You can only use the pay_at_the_property option to pay for the booking.
The method_required must be true

Dates: Contain two payment schedule items, showing how and when the total price of the booking must be paid:

Schedule	`at`	`price`
First item	The booking date (that is, the current date).	Is always 0 for the pay_at_property timing (as the payment will be made at checkin date)
Second item	The checkin date for the booking.	The amount that the property must charge to your provided VCC at checkin. This is the total price of the booking including extra charges (if any) in this case 205.78.

The pay_at_the_property.methods.cards: Contains the IDs of payment cards that can be used to pay for or secure a booking (in this case, 1,2,3 and 4).
- You must be able to generate/obtain a VCC for one of these cards.
Use the common/payments/cards endpoint to know which cards are identified with these numbers.

Pay with AirPlus

Our Demand API is integrated with AirPlus, which is a VCC external provider, so those Corporate partners who cannot or do not want to generate VCC themselves, they can use AirPlus instead for their business travellers.

By using AirPlus as your virtual credit card provider, you can pay for business travel bookings by using a 12-digit AirPlus number instead of full details of a virtual credit card, allowing for an efficient and secure booking process.
You just need to call the reservation creation order endpoint announcing the intention to use this integration, and passing your own AirPlus identifier.

Note

This option is only available if you are an AirPlus customer and have a 12-digit AirPlus number. If you are using an AirPlus VCC directly (not via the integration), see cards method instead.

→ Call /orders/preview to see the final details of the accommodation and products including when and how the payment can be made.

You can see all payment-related details in the general_policies.payment.pay_at_the_property field provided in the response. Example:

     "accommodation": {
         ...
         "general_policies": {
             "payment": {
                 ...
                 "pay_at_the_property": {
                     "method_required": true,
                     "dates": [
                         {
                             "at": "2023-12-18",
                             "price": {
                                 "accommodation_currency": 0.00
                                 "booker_currency": 0.00
                             }
                         },
                         {
                             "at": "2024-01-10",
                             "price": {
                                 "accommodation_currency": 205.78,
                                 "booker_currency": 205.78
                             }
                         }
                     ],
                     "methods": {
                         "airplus": true,
                         ...
                     }

This response shows that, for the selected property and product, with your authorised payment features:

You can only use the pay_at_the_property option to pay for the booking.
The method_required must be true

Dates: Contain two payment schedule items, showing how and when the total price of the booking must be paid:

Schedule	`at`	`price`
First item	The booking date (that is, the current date).	Is always 0 for the pay_at_property timing (as the payment will be made at checkin date)
Second item	The checkin date for the booking.	The amount that the property must charge to the AirPlus VCC at checkin. This is the total price of the booking including extra charges (if any) in this case 205.78.

The pay_at_the_property.methods.airplus: Must be true.

Online payments: Credit Card + MOTO

The Mail/telephone order (MOTO) is an Online payment method that we offer to Corporate partners so they can book prepaid rates by classifying their offline bookings as MOTO transactions in our Demand API.

Pre-requisites

Checklist
☑	You have a fraud risk prevention provider.
☑	Demand API version must be updated to minimum version 2.10.

Note

You can only use this option if your partner agreement with Booking.com allows it.

The flow

The traveller decides to order reservation via MOTO.
You flag the transaction as a MOTO via our API along with traveller`s credit card information.
Booking.com charges the traveller credit card and pays the property.

Create your order request

→ Call /orders/create and specify the following information in the payment.card.authentication field:

business_information: Must contain the necessary business related information for billing, and for the authorisation form that will be sent to the property. This is mandatory for this sort of payments.
Card.authentication: Define the appropriate authentication method for the card that is being used to secure the booking.
- In this case is Credit Card with MOTO (SCA exempted) hence you dont need to include a SCA token.
- sca_exemption: Must be "moto".
cardholder, cvc, expiry_date, number: Must contain the details of a valid payment card that can be used to secure the booking (as per the list returned in methods.cards in the /orders/preview response).
method: Must be "card".
timing: Must be "pay_online_now".

For this case do not use the riskified or 3d_secure fields.

For example:

 "payment": {
     "card": {
         "authentication": {
             "sca_exemption": "moto",
         },
         "cardholder": "xxxx",
         "cvc": 123,
         "expiry_date": "2030-10",
         "number": "1234123412341234"
     },
     ...