The following launch requirements apply to all affiliates with a business-to-business (B2B) integration model where internal agents, members of an affiliate program, etc. interact with the software instead of end customers. See our B2C launch requirements for integrations that cater directly to end customers.

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 – B2B Closed User Base/Agent Platform

1. Presentation
1.1 No price change functionality within platform
1.2 Users alerted that package rates must be booked with a flight
1.3 Affiliate to confirm following information is communicated to the end customer via email or other tangible form:
1.3.1 Links to online customer service tools (must also be prominently displayed within platform)
1.3.2 Expedia Collect bookings confirmed as prepaid
1.3.3 EAN's itinerary IDs and confirmation numbers
1.3.4 Hotel supplier notice
1.3.5 Where EAN is MOR, the relevant soft descriptor
1.4 Where Affiliate allows children to be included in bookings proper messaging and input of child ages is implemented
1.5 No changes to the API information are made by the Affiliate and no ability within platform to make changes

2. Policies
2.1 Following information must (i) be included in platform; and (ii) Affiliate to confirm is communicated to the end customer via email or other tangible form:
2.1.1 Non-refundable policies
2.1.2 Cancellation policy for the selected room
2.1.3 General hotel policies
2.1.4 Site links to the EAN booking Terms & Conditions URL
2.1.5 Downstream affiliate must agree to EAN’s Terms of Use for accessing EAN inventory
2.2 Affiliate confirms that affiliate address information is provided accurately to EAN

3. Taxes and Fees
3.1. Following must (i) be included in platform; and (ii) Affiliate to confirm is communicated to the end customer via email or other tangible form:
3.1.1 Clear breakdown of charges is provided
3.1.2 Sales tax, city tax and hotel occupancy tax values are reported separately
3.2 Affiliate service or booking fees must be clearly separated

4. Security
4.1 Evidence of PCI compliance supplied if required
4.2 Affiliate’s privacy policy covers the sharing of customer data with EAN/third parties 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 booking 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

1. Presentation

1.1 No price change functionality within platform

The platform may not allow users to amend or modify rates provided by EAN (no functions that allow agents to adjust the price or add hidden service fees).

 

1.2 Users alerted that package rates must be booked with a flight

Wording must be included to alert users that package rates must be booked with a flight. Ideally, include a checkbox to show acceptance of this rule and a place for including the flight or PNR number.

 

1.3 Affiliate to confirm following information is communicated to the end customer via email or other tangible form:

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.3.1 Links to online customer service tools (must also be prominently displayed within platform)

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.

1.3.2 Expedia Collect bookings confirmed as prepaid

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

 

1.3.3 EAN's itinerary IDs and confirmation numbers

The itineraryId and confirmationNumbers values from the booking response must be provided directly to the end customer.

 

1.3.4 Hotel supplier notice

End customer emails or other tangible communications must clearly state the hotel is provided by Travelscape LLC or Vacationspot SL.

 

1.3.5 Where EAN is MOR, the relevant soft descriptor

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

numberOfChildren and childAges are required elements 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.

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.5 Affiliate makes no changes to API information and platform has no ability to make changes

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


2. Policies

2.1 Following information must (i) be included in platform; and (ii) Affiliate to confirm is communicated to the end customer via email or other tangible form:

2.1.1 Non-refundable policies

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 organic API data 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.1.2 Cancellation policy for the selected room

Use the text provided by the cancellationPolicy response element.

 

2.1.3 General hotel policies

You may obtain general hotel policies using the options parameter for the room availability request, or directly from the hotel information request.

 

2.1.4 Site links to the EAN booking Terms & Conditions URL

MUST be communicated to the end customer via email or other form. 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.1.5 Downstream agents must agree to EAN’s Terms of Use for accessing EAN inventory

Before they are permitted to access EAN's inventory using your platform, downstream agents must be required to agree to EAN's Terms of Use. This agreement is typically provided within the agent interface to allow agent-side users of your platform to easily review and accept the terms. Contact your account manager or support for the appropriate specific document to provide.

 

2.2 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 Following information must (i) be included in platform; and (ii) Affiliate to confirm is communicated to the end customer via email or other tangible form:

3.1.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 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
example 3.1

example 3.1

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) 
 

3.1.2 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.2 Affiliate service or booking fees must be clearly separated

example 3.2

example 3.2

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 Evidence of PCI compliance supplied if required

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

 

4.2 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 booking request

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.