B2C standalone launch requirements
These launch requirements apply to all Expedia Group partners with a business-to-consumer (B2C) integration model where end customers interact with your integration directly.
Overview
These requirements have been categorized into two sections:
- B2C SA requirements: These are specific to this booking flow. Please read through these requirements carefully as these may differ from any other rate types/booking flows you have integrated previously.
- Common requirements: These requirements are common across all booking flows. Please ensure to meet all these requirements across all flows.
Checklist
You can find a checklist to help support your development or to provide feedback on the requirements here. If you are going to provide screenshots for your site review please add the screenshots and corresponding logs in the checklist as this will help us to complete your review.
B2C standalone requirements
Common requirements
The below launch requirements apply to all Expedia Group partners across all booking flows. Additional requirements specific to each rate type, including a detailed description of price display, are provided in individual rate requirement lists.
GR1: No use of Expedia Group or Expedia Group names and logos.
Use of Expedia Group names and logos may only be used on customer- or agent-facing sites with explicit written approval in advance from Expedia Group as an exception.
Example:
GR2: Links to the Expedia Group Terms and Conditions URL to be displayed.
Provide a link to the Expedia Group Terms and Conditions within your site's own terms and conditions text or directly link to the terms from your booking page. These terms detail the policies that govern the booking. Place the following link in an easy-to-find location, using the link wording 'Supplier Terms and Conditions'.
The English version can be found here.
Other versions are listed here.
Example:
GR4: Expedia Group MoR - Proper use and display regarding credit card regulations.
Where you obtain, use, transmit, store, or process end customers' cardholder data, you shall comply with the PCI DSS as issued by the PCI Security Standards Council. A complete reference for these regulations is available at the official PCI Security Standards site.
GR5: Expedia Group MoR or Property Collect - Evidence of PCI compliance supplied for applicable partners.
Where Expedia Group or the property is MoR an Attestation of Compliance (AOC) must be supplied as evidence of PCI compliance. You can find advice regarding PCI compliance on the official PCI Security Standards site.
SP1: Where affiliate allows children to be included in bookings, proper messaging and input of child ages is implemented.
If your integration permits child travelers, you must offer the ability to specify the age of each child traveler at the time of check-in. This information is provided via the occupancy element (see code sample below).
When customers specify child travelers, the API response may contain age restrictions and/or extra occupancy or crib charges that may affect the cost or eligibility of the booking.
Each hotel configures what age range they classify as a child. Typically, individuals aged 17 or younger are considered children. Some properties do not allow guests under age 18.
Example API request:
https://api.ean.com/v3/properties/availability?checkin=2020-09-11
&checkout=2020-09-14
¤cy=USD&language=en-US& occupancy=2-9,4 &property_id=XXXX
&country_code=XX&sales_channel=XXXX
&sales_environment=XXXX&filter=XXXX&rate_plan_count=XXXX
&rate_option=XXXX&billing_terms=XXXX&payment_terms=XXXX
&partner_point_of_sale=XXXX&platform_name=XXXXExample API response:
"occupancies": {
"2-9,4" : {
"nightly": [
[Example user interface: 1 Room with 2 adults and 2 children aged 9 and 4
AP1: Bed type descriptions are present on each room.
Shop responses may return the bed_groups array with a single value or multiple options. Display the values contained in the configuration array to describe the customer's bed choice(s).
When the bed_groups array returns with multiple options, display the price_check links provided by the Shop response for each bed type to allow selection by the customer.
Messaging must be displayed to the traveler that choices between multiple bed types for the same room are requests only and may not be honored at the hotel if availability does not permit.
Room names are returned within the Shop response's rooms array as room_name.
Example API response:
"property_id": "11775754",
"rooms": \[
{
"id": "230434524",
"room_name": "Superior double room" ,
"rates": [
{
...
"bed_groups": {
"133243": {
"id": "133243",
"description": "Double bed" ,
"links": {...},
"configuration": [...]
},
"133242": {
"id": "133242",
"description": "2 single beds" ,
"links": {...},
"configuration": \[...]
}
},Example user interface:
AP2: Non-refundable flag is clearly visible.
Non-refundable availabilities are indicated by refundable=false in the Shop availability response. When refundable=false is returned in an availability response, clearly label the applicable rooms. This value always takes precedence over any differing policy data. These reservations are not refunded by the property under any circumstances.
Example API response:
"property_id": "XXXX",
"rooms":
"id": "XXXX",
"room_name": "Fairmont King",
"rates":
"id": "XXXX",
"status": "available",
"available_rooms": 4999,
"refundable": false ,
"deposit_required": false,
"merchant_of_record": "expedia",Example user interface:
AP3: Display check-in and special check-in instructions.
The contents of the checkin, checkout, fees, and policies objects must be displayed for each room as returned in the property content definition. This information must be displayed on your availability page to ensure the customer is aware of any potential fees at check-in or special access instructions.
The special_instructions field may include information critical for check-in that is not included in the checkin object's instructions field, such as a requirement to notify the property of expected arrival time, check-in at a different location from the guest building, or an alert to expect special check-in instructions from the property via email.
Make sure to display both the instructions and special_instructions to the traveler within the same area.
Example API response:
"11775754": {
"property_id": "11775754",
"checkin": {
"begin_time": "16:00 PM",
"end_time": "4:00 AM",
"instructions": "Minimum age to check in is 18 years old.
Extra-person charges may apply and vary depending on property policy.
Government-issued photo identification and a credit card may be required at
check-in for incidental charges.
Special requests are subject to availability upon check-in and
may incur additional charges. Special requests cannot be guaranteed.",
"special_instructions": "Front desk staff will greet guests on arrival. For more details,
please contact the property using the information on the booking confirmation.",
"min_age": 18
"checkout": {
"time": "11:00 AM"
"fees": {
"mandatory": "You'll be asked to pay the following charges at the property:
Deposit: USD 50 per day
Resort fee: USD 28.25 per accommodation, per night The resort fee includes: Pool access, Fitness center access, Fitness/yoga classes, Airport shuttle, Phone calls, In-room safe, Self parking, Valet parking, Parking. We have included all charges provided to us by the property.
However, charges can vary, for example, based on length of stay or the room you book.",
"optional": "The following fees and deposits are charged by the property at time of service,
check-in, or check-out. Breakfast fee: between USD 6 and USD 25 per person
(approximately), Late check-out is available for a fee (subject to availability)Rollaway bed fee: USD 20.0 per night.
The above list may not be comprehensive. Fees and deposits may not include tax and are subject to change."
"policies": {
"know_before_you_go": "Up to 2 children 12 years old and younger stay free when
occupying the parent or guardian's room, using existing bedding.
The property has connecting/adjoining rooms, which are subject to availability
and can be requested by contacting the property using the number on the booking
confirmation."Example user interface:
BP1: SSL encryption is present for personal data.
When sending or transmitting personal data, you must use SSL encryption to secure connections between client browsers/applications and your site, as well as the network communications with dependent systems. Personal data includes guest names, phone numbers or emails, payment card details, booking/itinerary receipts, and confirmation pages. Stop or redirect the connection when it is not secured.
BP2: Display check-in and special check-in instructions.
The contents of the checkin, checkout, fees, and policies objects must be displayed for each room as returned in the property content definition. This information must be displayed to ensure the customer is aware of any potential fees at check-in or special access instructions before they finalize their booking.
The special_instructions field may include information critical for check-in that is not included in the checkin object's instructions field, such as a requirement to notify the property of expected arrival time, check-in at a different location from the guest building, or an alert to expect special check-in instructions from the property via email.
Make sure to display both the instructions and special_instructions to the traveler within the same area.
BP3: Cancellation policy and non-refundable tag clearly displayed.
Before allowing customers to confirm their purchase on your final booking page, you must provide the cancellation policy/non-refundable tag for the selected room or rooms. The cancellation policy for each rate is provided within the cancel_penalties object in the Rapid Shop Availability API.
For refundable rates, the response includes an array of cancellation policy details. The details include the start date and end date of the specified penalty as well as the penalty type and value, and any exception booking dates that apply. The penalty types include a fixed amount, number of nights, and percentage of total cost.
| Response | Meaning |
|---|---|
refundable=true | This rate is fully refundable. |
refundable=true + cancel_penalties | • This rate is refundable during the cancellation timeframe. • The earliest cancel_penalties.[].start is the free cancellation deadline, if it is a future timeline.• The rate is 100% non-refundable after the latest cancel_penalties.[].end |
refundable=false | • This rate is non-refundable. • No cancel penalty window is returned. |
refundable=false + cancel_penalties | • The rate can be partially refundable. • cancel_penalties should be shown in conjunction with nonrefundable_date_ranges which will show the stay dates of this range are non-refundable once the booking is created. |
Further information on how to construct cancellation policies can be found here.
Reference:
refundable=false:- A non-refundable amount will incur immediately once the booking is created.
cancel_penaltiesandnonrefundable_date_rangeswill provide more details.
- A non-refundable amount will incur immediately once the booking is created.
nonrefundable_date_ranges:- The stay dates of this range are non-refundable once the booking is created.
cancel_penalties:- Applicable to the stay dates that are not involved in
nonrefundable_date_ranges. - The rate is 100% non-refundable when
cancel_penaltiesis empty or not returned. - A penalty will incur when canceling during the time frame of
cancel_penalties. - The earliest
cancel_penalties.[].startis the free cancellation deadline, if it is a future timeline the rate is 100% non-refundable after the latestcancel_penalties.[].end.
- Applicable to the stay dates that are not involved in
Example API responses:
Fully refundable:
"property_id": "XXXX",
"rooms": [
{
"id": "XXXX",
"room_name": "Traditional Room",
"rates":
"id": "XXXX",
"status": "available",
"available_rooms": 4999,
"refundable": true,
"cancel_penalties": [
{
"start": "2021-05-27T18:00:00.000-07:00",
"end": "2021-05-28T18:00:00.000-07:00",
"amount": "76.00",
"currency": "USD"Non-refundable:
"property_id": "XXXX",
"rooms":
"id": "XXXX",
"room_name": "Traditional Room",
"rates":
"id": "XXXX",
"status": "available",
"available_rooms": 4999,
"refundable": false ,
"deposit_required": false,
"merchant_of_record": "expedia",Partially refundable:
"property_id": "XXXX",
"rooms": [
{
"id": "XXXX",
"room_name": "Traditional Room",
"rates":
"id": "XXXXXXXX",
"status": "available",
"available_rooms": 4999,
"refundable": false,
"cancel_penalties": [
{
"start": "2023-09-03T13:59:00.000+02:00",
"end": "2023-09-04T13:59:00.000+02:00",
"nights": "1",
"currency": "USD"
}
],
"nonrefundable_date_ranges": [
{
"start": "2023-09-08",
"end": "2023-09-13"
}
],Example user interface:
BP4: Display charges due at the property separately within the price breakdown.
When charges are returned in the fees array, display each value separately as a charge due at the property (check-in or check-out). Present the traveler the local currency and request currency. These charges are collected directly by the property (not Expedia Group or local governments) and are not part of standard tax recovery charges, taxes, or fees included in the taxes and fees line.
Example API response:
"fees" : {
"resort_fee": {
"request_currency": {
"value": "74.97",
"currency": "USD"
},
"billable_currency": {
"value": "74.97",
"currency": "USD"
},
"scope": "per_accommodation",
"frequency": "per_night"
}
},Example user interface:
BP7: If applicable, child ages must be reiterated.
If your integration permits child travelers and the customer specified child travelers for their room selection, you must clearly confirm the number of child travelers and their ages on your booking pages. This information is provided via the child_ages element.
BP8: Expedia Group MoR or Property Collect: State when payment will be taken from the end traveler.
If Expedia Group MoR, state that the credit card provided will be charged immediately for the full amount of the reservation.
If Property Collect, state that the credit card provided will be charged by the property at check-in or check-out. If the property is serving a non-refundable post-pay rate, instead indicate that the customer could be charged by the property shortly after completing the booking.
BP9: Compliance with European Economic Area Regulations: Payment Services Directive 2 (PSD2).
PSD2 compliance is required for any partner that intends to transact with customers in the European Economic Area (EEA). Learn more here.
Expedia Group MoR or Property Collect.
If Expedia Group is the MoR, or Property Collect is used with European customers, the booking path must include the adoption of Rapid’s APIs for two-factor authentication.
Affiliate MoR - General.
Partners must follow the Strong Customer Authentication (SCA) requirements of the PSD2 regulations when transactions with customers are within the scope of the regulations. The complete text of the directive is available at the European Commission. Further information about the compliant standards that can be adopted is available in EMVCo’s “3D Secure Protocol and Core Functions Specification”.
Affiliate MoR - Corporate card or virtual card.
Partners paying Expedia Group with a partner-owned card, issued in a country within the EEA, must follow the requirements of PSD2 regulations. To mitigate the need for PSD2 2FA a partner could use a card that is compliant for B2B payments and is exempt from 2FA (two-factor authentication).
Compliant options include:
- Single-use virtual cards.
- Multi-use corporate card that is registered to the company (not a person). Special profile configuration required.
Example API request:
https://api.ean.com<Price Check link from previous availability request>Example API response:
{
"status": "available",
"occupancy_pricing": {... },
"links": {
"payment_session": {
"method": "POST",
"href": "/v3/payment-sessions?token=XXXX"
}
}
}BP10: Expedia Group MoR – Payment processing location displayed on checkout pages
Where Expedia Group is MoR, the country where the payment will be processed must be displayed in a prominent place on the checkout page. The phrase "This payment will be processed in" must be inserted before the country name.
Use the Payment Options function of the Shopping API to retrieve this information.
Example API request:
https://api.ean.com<payment-options link from previous availability request>Example API response:
"credit_card": {
"name": "Credit Card",
"card_options": [
{
"name": "MasterCard",
"processing_country": "US"
},
{
"name": "Visa",
"processing_country": "US"
}
]
}Example user interface:
