The following launch requirements apply to all affiliates with a business-to-consumer (B2C) integration model where end customers interact with your integration directly. See our B2B launch requirements for template/platform integrations for use with partner programs or other business-to-business scenarios.

Use the following checklist during your development to ensure all required items for displaying EAN inventory are present.

You are required to include all items as it pertains to your integration and your agreement to the EAN Affiliate contract. Refusal to fulfill any required items or requests by EAN to make corrections to your site will result in a denial of API access.


Launch Requirements for B2C/Consumer-Facing Content

1. Presentation
1.1 Room type descriptions are present on each room
1.2 Room rate disclaimer is present on the room availabilities page
1.3 Check-in instructions displayed
1.4 Links to online customer service tools prominently displayed
1.5 Expedia Collect availabilities state booking is prepaid in full
1.6 Disclaimer included wherever EAN photos are displayed
1.7 Where affiliate allows children to be included in bookings, proper messaging and input of child ages is implemented
1.8 Affiliate customer support and telesales number clearly displayed
1.9 Itinerary IDs and confirmation numbers displayed properly
1.10 No use of Expedia or EAN names or logos
1.11 Affiliate-controlled confirmation emails must provide itinerary and confirmation IDs and state hotel supplier
1.12 No changes to API information are made by the Affiliate
1.13 Mobile deals displayed

2. Policies
2.1 Non-refundable policies are clearly visible
2.2 Proper use and display regarding credit card regulations
2.3 Cancellation policy for the selected room for booking includes a validating booking form checkbox
2.4 General hotel policies are being displayed from the hotel info result for Expedia Collect inventory only
2.5 Site links to the EAN booking Terms & Conditions URL
2.6 Affiliate confirms that affiliate address information is provided accurately to EAN

3. Taxes and Fees
3.1 Clear breakdown of charges is provided
3.2 Taxes and Fees are clearly stated as a separate line item
3.3 Total price charged is clearly displayed on both the booking and confirmation pages
3.4 Sales tax, city tax and hotel occupancy tax values are reported separately
3.5 Affiliate service or booking fees must be clearly separated

4. Security
4.1 SSL encryption is present for sensitive data
4.2 Evidence of PCI compliance supplied for applicable partners
4.3 Affiliate privacy policy covers sharing customer data with EAN for the purpose of processing the booking

5. Technical
5.1 Logic has been implemented to prevent duplicate bookings
5.2 Logic has been implemented to handle pending and error states
5.3 Affiliate is providing name of actual traveller in the booking
5.4 Affiliate is providing customer IP address with each booking request
5.5 Affiliate is providing customer email address with each booking request
5.6 Affiliate is providing session ID with each booking request
5.7 Affiliate is providing customer's user agent string with each request
5.8 Affiliate is providing unique Affiliate Confirmation ID with each booking request
5.9 Affiliate is proving their internal reference with the booking
5.10 Affiliate is determining valid payment types before booking
5.11 Logic implemented to prevent display of mobile deals to non-mobile users

1. Presentation

1.1 Room type descriptions are present on each room

For room selections, display each room's rateDescription or roomTypeDescription value from the availability response. Include bed type descriptions when returned.

<rateDescription>Deluxe Room, 1 King Bed, Corner</rateDescription>
<roomTypeDescription>Deluxe Room, 1 King Bed, Corner</roomTypeDescription>
<supplierType>E</supplierType>
<propertyId>25290</propertyId>
<BedTypes size="1">
<BedType id="14">
<description>1 king</description>
</BedType>
</BedTypes
example 1.1

example 1.1


 

1.2 Room rate disclaimer is present on the room availabilities page

You must display the room rate disclaimer below on all room availability pages. This text is not returned in the API.

The room rates listed are for double occupancy per room unless otherwise stated and exclude tax recovery charges and service fees.
 

1.3 Check-in instructions displayed

example 1.3

example 1.3

The contents of checkInInstructions must be displayed for each room when returned in the room availability or reservation response. These instructions may include critical information such as fees that can be incurred at check-in, or after-hours access instructions.

 

1.4 Links to online customer service tools prominently displayed

You must provide customers with easy access to self-service tools for common tasks such as itinerary retrieval and cancellation. You may build your own tools if desired. Single header links leading to self-service areas are acceptable.

example 1.4

 

1.5 Expedia Collect availabilities state booking is prepaid in full

Booking pages for Expedia Collect availabilities must state that the credit card provided will be charged immediately for the full amount of the reservation.

Confirmation pages for Expedia Collect bookings must state that payment was made for the full amount of the reservation.

EXAMPLE 1.5 – booking page

EXAMPLE 1.5 – confirmation page

 

1.6 Disclaimer included wherever EAN photos are displayed

The disclaimer below must be included on any page containing EAN-sourced property photos.

“It is the responsibility of the hotel chain and/or the individual property to ensure the accuracy of the photos displayed. {Affiliate site/brand name} is not responsible for any inaccuracies in the photos.”
 

1.7 Where affiliate allows children to be included in bookings, proper messaging and input of child ages is implemented

numberOfChildren and childAges are required elements for Expedia Collect properties when children will occupy the room.

If your integration permits children to be included on a shopping request or booking, the customer must be able to specify the number of children and their ages. Customers must be messaged for any age restrictions and/or any extra occupancy/rollaway bed/crib charges required.

example 1.7

Each hotel configures what age range they classify as a child. Typically individuals aged 17 or younger are considered children, but can vary by property. Some properties do not allow guests under age 18.

 

1.8 Affiliate customer support and telesales number clearly displayed

Clearly display EAN's support numbers or your own if you handle your own customer support. Do not bury numbers in footers, secondary support pages, etc. or otherwise prevent easy access to phone support.

 

1.9 Itinerary IDs and confirmation numbers displayed properly

Capture the itineraryId and confirmationNumbers values from the booking response and display them at the top of your booking confirmation pages and retrieved itineraries.

example 1.9

 

1.10 No use of Expedia or EAN names or logos

None of the Expedia or EAN names or logos (including Travelnow) may be used on affiliate sites for any purpose. Any exceptions must be approved by legal and relevant groups within Expedia, with approval attached to the affiliate launch record.

 

1.11 Affiliate-controlled confirmation emails must provide itinerary and confirmation IDs and state hotel supplier

If you opt out of EAN's automated customer confirmation emails, the emails you send to customers must provide the original EANitineraryId and confirmationNumbers for the booking. Emails must also clearly state the hotel is provided by Travelscape LLC or Vacationspot SL.

 

1.12 No changes to API information are made by the Affiliate.

Any information provided by EAN's API must be used as-is. No changes are allowed except by explicit written permission from EAN.

 

1.13 Mobile deals displayed

Mobile deals must be displayed to mobile users when returned by the API (promoType=Mobile). Request access by providing your CID(s) to EAN Support.


2. Policies

2.1 Non-refundable policies are clearly visible

When the nonRefundable element returns true, clearly state the room is non-refundable on room selection pages and reiterate the non-refundable policy on your final booking page. These reservations are not refunded by the property under any circumstances.

While non-refundable policies are typically echoed in the cancellationPolicy as well as roomDescription and rateTypeDescription elements, you may not rely on these values alone to identify these availabilities. You must ensure your integration actively checks the nonRefundable element for these policies and messages customers appropriately in addition to any data provided by the property.

example 2.1

 

2.2 Proper use and display regarding credit card regulations

Affiliates must follow PCI (Payment Card Industry) regulations when requesting, handling, and storing customer credit card data. Review these details carefully to insure your site follows all PCI regulations. These regulations dicate how users are provided with a choice of accepted credit cards, which part of the user's card number can be displayed, and how the credit card information can be submitted or verified.

Fines are imposed by credit card companies to offending sites that can run into tens of thousands of dollars. When using the API to collect and send user credit card information, all rules must be followed exactly as outlined to prevent your site from incurring fines from these payment processors.

 

2.3 Cancellation policy for the selected room for booking includes a validating booking form checkbox

Before allowing customers to confirm their purchase on your final booking page, you must provide cancellation policy for the selected room with a validating checkbox required to proceed. Customers must not be allowed to book without agreeing to the room's specific cancellation policy.

Never hard-code any policy information or text. Always obtain cancellation policy info directly for each room.

example 2.3

 

2.4 General hotel policies are displayed from the hotel info result for Expedia Collect inventory only

You may obtain general hotel policies using the options parameter for the room availability request, or directly from the hotel information request. Display the contents of the hotelPolicy element from the HotelDetails node on room selection pages, individual room pages, and hotel overview pages.

 

2.5 Site links to the EAN booking Terms & Conditions URL

Your site must link to EAN's Terms & Conditions using the following URL (substitute your own CID):

http://travel.ian.com/index.jsp?pageName=userAgreement&locale=en_US&cid=#####

This includes the contracting policy acknowledging Travelscape LLC and/or Vacationspot, SL as the supplier.

 

2.6 Affiliate confirms that affiliate address information is provided accurately to EAN

You must provide accurate address information on your affiliate profile at ean.com. Verify the information provided both under Account > Profile and Account > Tax Forms on your ean.com profile.


3. Taxes and Fees

3.1 Clear breakdown of charges is provided

Break down or list any surcharges that are included in the Surcharges array. When salesTax and hotelOccupancyTax are returned, add these two values together and display as one line item.

Display fees returned by the HotelFees array separately, as they are collected by the property itself at checkin or checkout.

Include a breakdown of the total price, taxes and fees, and nightly room rates of the Expedia Collect reservation in these locations:

  • Booking page
  • Confirmation page
  • Additional confirmation emails sent to customer (if handling own emails)

Follow the example booking page breakdowns provided in this section.

  • Include either each individual per-night rate for the dates selected OR a total of all night rates (shown in image to right) without taxes

Your final breakdown should include a clear itemization of charges that displays values representing a subtotal of nightly rates (individual per-night rate shown below), a total of surcharge amounts and a chargeable total:

Room and Rate/Night: Queen Three 

10 Nov 10 $159.00 
11 Nov 11 $119.00
12 Nov 12 $119.00 
13 Nov 13 $119.00 
(excluding tax recovery charges and service fees) 

Extra person fees: $52.00

Total Tax Recovery Charges and Service Fees: $88.18 

Total Charges at time of booking : $656.18 (USD)
(includes tax recovery charges and service fees)
example 3.1

example 3.1

 

3.2 Taxes and Fees are clearly stated as a separate line item

The value returned for TaxAndServiceFee must be displayed separately for all tax references and/or where a price breakdown is given, such as room availability, booking form and confirmation results for Expedia Collect properties.

The exact text below is legally required on your site for all Expedia Collect inventory when referring to any "taxes and fees" totals. Base your display on the point of supply of the hotel, not the customer's location.

  • Europe: "Tax Recovery Charges"
  • All Other Regions: "Tax Recovery Charges and Service Fees"
example 3.2 – europe

example 3.2 – europe

 

3.3 Total price charged is clearly displayed on both the booking and confirmation pages

example 3.3 – booking page

example 3.3 – booking page

 
example 3.3 – confirmation page

example 3.3 – confirmation page


 

3.4 Sales tax, city tax and hotel occupancy tax values are reported separately

When tax values other than TaxAndServiceFee or ExtraPersonFee are returned by the Surcharge array, and/or when the HotelFees array returns additional fees, you must display these values separately in your charge breakdown. Certain jurisdictions such as the state of New York require the separate display of these values by law.

 

3.5 Affiliate service or booking fees must be clearly separated

If you will charge your own booking or service fee, it must be clear to the customer that the fee is levied by you, the affiliate, and not EAN for a separate service (i.e. not a further charge for the provision of accommodation).
Affiliate booking or service fees may not be bundled into the price and must be broken out separately.


4. Security

4.1 SSL encryption is present for sensitive data

SSL encryption is required on all booking forms, booking confirmation pages, itinerary request forms, itinerary response pages, cancellation request forms and cancellation response pages.

 

4.2 Evidence of PCI compliance supplied for applicable partners

For API partners with an estimated annual gross booking volume of $10m and where EAN is merchant of record, evidence of PCI compliance, such as an an attestation of compliance, must be supplied.

 

4.3 Affiliate privacy policy covers sharing customer data with EAN for the purpose of processing the booking


5. Technical

5.1 Logic has been implemented to prevent duplicate bookings

See the Prevent Duplicate Bookings page and usage of affiliateConfirmationId to help your implementation meet this requirement.

 

5.2 Logic has been implemented to handle pending and error states

See the Pending Supplier Process page and our error handling section at large to help your implementation meet this requirement.

 

5.3 Affiliate is providing name of actual traveller in the booking

The values for firstName and lastName within each Room object must match the first and last name of the guest checking in for the reservation.

 

5.4 Affiliate is providing customer IP address with each booking request.

Use the customerIpAddress common request element to provide this data. IP address must be captured from the customer – do not substitute static values or your own IP address.

 

5.5 Affiliate is providing customer email address with each booking request

The email element within ReservationInfo must contain the customer's email address.

 

5.6 Affiliate is providing session ID with each booking request

Use the customerSessionId common element to provide this data.

 

5.7 Affiliate is providing customer's user agent string with each request

The customer's user agent string must be passed in all API requests. This data is required in order to receive access to mobile deals.

Use the customerUserAgent common request element to provide this data.

 

5.8 Affiliate is providing unique Affiliate Confirmation ID with each booking request.

Use the affiliateConfirmationId element in the reservation request to provide this data.

 

5.9 Affiliate is providing their internal reference with the booking

Use the affiliateConfirmationId element in the reservation request to provide this data.

 

5.10 Affiliate is determining valid payment types before booking

Use the payment types request to obtain this data and allow accepted payment cards on your booking form appropriately.

 

5.11 Logic has been implemented to prevent display of mobile deals to non-mobile users

The affiliate must ensure mobile deals are not displayed to customers using non-mobile device types. Failure to provide device-appropriate rates will result in removal of mobile deals access.