B2B standalone launch requirements

GR3: Downstream agents must agree to our Agent Terms and Conditions for accessing our inventory.

Agents making a booking on behalf of a traveler must agree to our downstream agent agreement. A link to the downstream agent agreement should be provided for agents to review and accept prior to making a booking. Other versions are available on Expedia Partner Solutions.

BP5: Price display must include the total price and a breakdown of the taxes and fees.

A) Total price

The total price for the booking must be displayed to the traveler on the checkout page. The total price should match the API response, with no rounding or currency conversion permitted. The final breakdown must include room rates (total or per night), any additional nightly fees (except those in the property_fee field described below), all stay amounts and taxes, a chargeable total, and set out what is paid now and what is to be paid later at the property.

B) Tax breakdown

Price display must include the sum of tax_and_service_fee and property_fee as one line titled "Taxes and fees". The exact text below is legally required to be displayed when referring to any taxes and fees totals within the price breakdown. This can be displayed as a pop-up, plain text, modal, or other implementation. Property fee should not be displayed separately on the checkout page.

"The taxes are tax recovery charges paid to vendors (e.g. hotels); for details, please see our Terms of Use . Service fees are retained as compensation in servicing your booking and may include fees charged by vendors.” Translations can be found on Expedia Partner Solutions.

The value returned for tax_and_service_fee only includes taxes and fees mandated by a tax jurisdiction.

C) Partner service and booking charges

To the extent that Expedia Group grants a waiver to permit booking charges, partner service or booking charges must be clearly separated. If a partner-imposed service charge is added to the booking, it must be clear to the customer that the charge is levied by the partner, and not Expedia Group, for a separate service (i.e. not a further charge for the provision of accommodation). Charges may not be included inside of existing taxes and fees line items. Partner must not use the word 'fee' to describe any charge imposed by them. They could use 'affiliate booking charge' or 'affiliate service charge' instead.

CP1: Price display must include the total price as well as taxes and fees if a breakdown is provided.

A) Total price

The total price for the booking must be displayed to the traveler on the confirmation page. The total price should match the API response, with no rounding or currency conversion permitted. The final breakdown must include room rates (total or per night), any additional nightly fees (except those in the property_fee field described below), all stay amounts and taxes, a chargeable total, and set out what is paid now and what is paid later at the property.

B) Tax breakdown

Price display must include the sum of tax_and_service_fee and property_fee as one line titled "Taxes and fees". The exact text below is legally required to be displayed when referring to any taxes and fees totals within a price breakdown. This can be displayed as a pop-up, plain text, modal, or other implementation. Property fee should not be displayed separately on the checkout page.

“The taxes are tax recovery charges paid to vendors (e.g. hotels); for details, please see our Terms of Use . Service fees are retained as compensation in servicing your booking and may include fees charged by vendors.” Translations can be found on Expedia Partner Solutions.

The value returned for tax_and_service_fee only includes taxes and fees mandated by a tax jurisdiction.

C) Partner service and booking charges

To the extent that Expedia Group grants a waiver to permit booking charges, partner service or booking charges must be clearly separated. If a partner-imposed service charge is added to the booking, it must be clear to the customer that the charge is levied by the partner, and not Expedia Group for a separate service (i.e. not a further charge for the provision of accommodation). Charges may not be included inside of existing taxes and fees line items. Partner must not use the word 'fee' to describe any charge imposed by them. They could use 'affiliate booking charge' or 'affiliate service charge'.

ER6: Price Display must include the total price and breakdown of the taxes and fees.

A) Total price

The total price for the booking must be displayed to the traveler on the email receipt. The total price should match the API response, with no rounding or currency conversion permitted. The final breakdown must include room rates (total or per night), any additional nightly fees (except those in the property_fee field described below), all stay amounts and taxes, a chargeable total, and set out what is paid now and what is paid later at the property.

B) Tax breakdown

Price display must include the sum of tax_and_service_fee and property_fee as one line titled "Taxes and fees". The exact text below is legally required to be displayed when referring to any taxes and fees totals within a price breakdown. This can be displayed as a pop-up, plain text, modal, or other implementation. Property fee should not be displayed separately on the checkout page.

“The taxes are tax recovery charges paid to vendors (e.g. hotels); for details, please see our Terms of Use . Service fees are retained as compensation in servicing your booking and may include fees charged by vendors.” Translations can be found on Expedia Partner Solutions.

The value returned for tax_and_service_fee only includes taxes and fees mandated by a tax jurisdiction.

C) Partner service and booking charges

To the extent that Expedia Group grants a waiver to permit booking charges, partner service or booking charges must be clearly separated. If a partner-imposed service charge is added to the booking, it must be clear to the customer that the charge is levied by the partner, and not Expedia Group, for a separate service (i.e. not a further charge for the provision of accommodation). Charges may not be included inside of existing taxes and fees line items. Partner must not use the word 'fee' to describe any charge imposed by them. They could use 'affiliate booking charge' or 'affiliate service charge'.

GR1: Use of our names and logos

Use of our names and logos may only be used on traveler-facing or agent-facing sites with our explicit written approval in advance as an exception.

Example:

GR2: Links to the our terms and conditions URL to be displayed

Provide a link to our 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 & Conditions". You can find the English version and other versions on Expedia Partner Solutions.

Example:

GR4: Where we are the Merchant of Record (MoR): Proper use and display regarding credit card regulations

Where you obtain, use, transmit, store or process traveler's cardholder data, you must comply with the Payment Card Industry Data Security Standard as issued by the PCI Security Standards Council. A complete reference for these regulations is available at the official PCI Security Standards Council website.

GR5: Where are are the MoR or Property Collect: Evidence of PCI compliance supplied for applicable partners

Whether we are the Mor or the property is the 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 Council website.

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 object (see example below).

When travelers 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/2.4/properties/availability?checkin=2020-09-11
&checkout=2020-09-14
&currency=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=XXXX

Example 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 for each room

Shopping 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 travelers's bed choice(s).

When the bed_groups array returns multiple options, display the price_check links provided by the Shopping response for each bed type to allow selection by the traveler.

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 Shopping 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 Shopping 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 Content property definition. This information must be displayed on your availability page to ensure the traveler is aware of any potential fees at checkin or special access instructions.

The special check-in 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. 
<br />Extra-person charges may apply and vary depending on property policy. 
<br />Government-issued photo identification and a credit card may be required at 
check- in for incidental charges. 
<br />Special requests are subject to availability upon check-in and 
may incur additional charges. Special requests cannot be guaranteed. <ul>. ",
          "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": "<p>You'll be asked to pay the following charges at the property:</p> 
<ul><li>Deposit: USD 50 per day</li>
<li>Resort fee: USD 28.25 per accommodation, 
per night</li></ul> The resort fee includes:<ul
><li>Pool access</li><li>Fitness center access</li><li>Fitness/yoga classes</li>
<li>Airport shuttle</li><li>Phone calls</li><li>In-room safe</li><li>Self parking</li>
<li>Valet parking</li><li>Parking</li></ul> <p>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. </p>",
            "optional": "<p>The following fees and deposits are charged by the property at time of service,
 check-in, or check-out. </p> <ul> <li>Breakfast fee: between USD 6 and USD 25 per person
 (approximately)</li>  <li>Late check-out is available for a fee (subject to availability)</li>  
 <li>Rollaway bed fee: USD 20.0 per night</li>          
</ul> <p>The above list may not be comprehensive. Fees and deposits may not include tax
 and are subject to change. </p>"
        "policies": {
            "know_before_you_go": "<ul>  <li>Up to 2 children 12 years old and younger stay free when
 occupying the parent or guardian's room, using existing bedding. </li>
<li>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. </li> </ul>"

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, and 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 Content property definition. This information must be displayed to ensure the traveler is aware of any potential fees at check-in or special access instructions before they finalize their booking.

The special check-in 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 travelers to confirm their purchase on your final booking page, you must provide the cancellation policy or 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 Shopping 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.

Read more about how to construct cancellation policies.

Reference:

refundable=false

• A non-refundable amount will incur immediately once the booking is created. cancel_penalties and nonrefundable_date_ranges will provide more details.

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_penalties is empty or not returned.
• A penalty will incur when canceling during the time frame of cancel_penalties.
• 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.

Example API Response: Cancellation policy and non-refundable flag

"property_id": "11775754",
        "rooms": [
            {
                "id": "230434524",
                "room_name": "Traditional Room (Partner:Connect Test)",
                "rates": 
                        "id": "276321199",
                        "status": "available",
                        "available_rooms": 4999,
                         "refundable": true,
                         "cancel_penalties":  [
                            {
                                "start": "2020-09-10T18:00:00.000-07:00",
                                "end": "2020-09-11T18:00:00.000-07:00",
                                "amount": "76.00",
                                "currency": "USD"

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 by us or local government) and are not part of standard tax recovery charges, taxes, or fees included in the taxes and fees line.

Example API response: Fees array

"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 traveler 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 object.

BP8: We are the MoR or Property Collect: State when payment will be taken from the end traveler

If we are the 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 traveler could be charged by the property shortly after completing the booking.

BP9: Compliance with strong customer authentication (SCA) regulation

Regulatory agencies and card networks are introducing new requirements to strengthen security for online payments and protect consumers from fraud. Many of these regulations have included the requirement to use strong customer authentication (SCA) for online payments.

Learn more about strong customer authentication (SCA).

BP10: We are MoR – Payment processing location displayed on check-out pages

Where we are the MoR, the country where the payment will be processed must be displayed in a prominent place on the check-out 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 for payment options:

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:

If you will provide a hosted voucher within a mobile application, please continue to follow the requirements below.

ER1: Itinerary IDs displayed properly

CDS only

If your integration will provide our itinerary_id directly to the traveler, you must clearly display this number on your confirmation email.

If applicable, you must provide evidence that your agents have access to the our original itinerary IDs should they require assistance from our customer support.

A2A

Your agents should have access to their original itinerary IDs should they require assistance from our customer support.

ER2: Customer support to be clearly displayed, including links to online customer service tools

Clearly display your customer support channels within the booking flow or within the confirmation email e.g. telephone number or live chat. If our agents will be providing direct support to your travelers, display the our support number in your booking flow.

ER3: Bed type descriptions are present on each room

Confirm the traveler-requested bed type in your confirmation email/voucher and display messaging 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.

Display the values contained in the configuration array to describe the traveler's bed choice(s).

ER4: 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 traveler is aware of any potential fees at check-in or special access instructions.

The special check-in 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.

ER5: 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). These charges are collected directly by the property (not us or local government) and are not part of standard tax recovery charges.

TR1: Provide unique Affiliate Reference ID with each booking request

For every booking request you must use the affiliate_reference_id element with the intent of:

• Your own tracking.
• Preventing duplicate bookings/duplicate charges from multiple form submissions.
• Checking our systems for an itinerary if the reservation timed out or returned an empty result due to upstream timeouts.

{
  "affiliate_reference_id": "Launch_Requirement_TR1" ,
 "hold": false,
 "email": "TR4@Launch.Requirement",
 "phone": {
    "country_code": "Launch_Requirement_TR5b",
    "number": "Launch_Requirement_TR5b",
    "area_code": "Launch_Requirement_TR5b"
 },
"rooms": [
 {
    "given_name": "John_Launch_Requirement_TR5a",
    "family_name": "Doe_Launch_Requirement_TR5a,
    "smoking": false,
 },
 {
    "given_name": "David_Launch_Requirement_TR5a",
    "family_name": "Smith_Launch_Requirement_TR5a",
    "smoking": false,
 }
],

TR2: Provide the traveler country code with each request

• The traveler country_code must be passed in API requests for Shopping and Recommendations. The country code must match the point of sale being accessed by the traveler.
• This requirement ensures our systems provide travelers with relevant content and the most suitable rates based on the sales market.

Example API request:

https://api.ean.com/2.4/properties/availability?checkin=2020-09-11
&checkout=2020-09-14
&currency=USD&language=en-US&occupancy=2-3,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=XXXX

TR3: Billing information

TR3a) Payor name

For traveler, corporate, and virtual card:

• You must send the name of the cardholder whose card is being charged by us.

For Affiliate Collect/EAC Partners:

• Wherever possible, we strongly recommends that you send the name of the actual end payor for the booking.
• This information is required for regulatory/sanctions screening purposes.
• If it is not possible to provide the name of the actual end payor, provide the name of the company or legal entity paying us.

Note: If the POS is Russia, Ukraine, or Venezuela then true payor information is always required.

TR3b) Billing country

• Must represent the individual name passed in the billing contact/payor name field.

TR3c) Billing Zip

• Must represent the individual name passed in the billing contact/payor name field.

Note: For countries that do not maintain a Zip Code, this information does not need to be provided.

"payments": [
   {
       "type": "customer_card",
       "billing_contact": {
           "given_name": "Launch_Requirement_TR3a",
           "family_name": "Launch_Requirement_TR3a",
       "address": {
           "line_1": "555 1st St",
           "line_2": "10th Floor",
           "line_3": "Unit 12",
           "city": "Seattle",
           "state_province_code": "WA",
           "postal_code": "Launch_Requirement_TR3c",
           "country_code": "Launch_Requirement_TR3b"
       }
   },

TR4: Provide the traveler email address or monitored email mailbox

The email element of each itinerary must contain the traveler email address or the mailbox your integration monitors for confirmation email handling. This is required for cases of booking disputes or troubleshooting.

TR5: Provide accurate traveler information

TR5a) Traveler name

Bookings must always be submitted with the name of the actual travelers staying in each booked room. This means that in your booking request body the values for given_name and family_name within the rooms object must match the first and last name of the main guest checking in for each room.

TR5b) Traveler phone number

The booking must include a viable contact number for the traveler. Include this number in your booking request's phone field of each itinerary. We will not contact the traveler if the your agents provide direct support to your travelers.

TR6: Multi-room bookings

If multi-room bookings are supported, provide the API request and response logs for a test booking which shows each room has been booked and cancelled.

Each room that is booked will create a separate Confirmation ID, which allows the rooms to be cancelled separately. To cancel all rooms, complete a cancellation call for every confirmation ID within the itinerary.

We do not directly offer group bookings of more than 8 rooms through our API or template. Your account manager can advise you if you need to book more than 8 rooms.

TR7: Rapid error handling recommendations

Please confirm you have reviewed our error handling recommendations and implemented logic to handle them.