In any description of your business wherever it resides - your integration, related websites, marketing material, etc. - you must not claim or suggest that you are the supplier of any EAN property.
This includes suggestions of property exclusivity (e.g. "our unique collection of hotels") or price exclusivity (e.g. "the lowest prices on the web").
Your brand's association with EAN properties must clearly remain as a marketer of EAN properties, not a supplier.

You may not modify any price- or booking-related values that describe factual aspects of costs of stay, the property and its amenities. This also includes omitting or obscuring any part of such data.

Changes that do not affect the meaning of the contained language are acceptable, e.g. changing "swimming pool" to "pool," "wireless internet" to "WiFi."

Do not attempt to provide additional information than what is provided in the response. EAN cannot be held responsible for disputes resulting from inappropriate affiliate modifications or additions to API data.

Clearly display EAN's support number, or your own if you are not relying on EAN's customer support centers. You must also provide links to online customer service tools to allow customers to retrieve and review their own bookings.

Affiliates must follow PCI (Payment Card Industry) regulations when requesting, handling, and storing customer credit card data. A complete reference for these regulations is available at the official PCI Security Standards web site.

To assist with the PCI rules most critical to your integration, EAN provides a targeted guide for partners: https://rapid.ean.com/reference/credit-card-guide

By following the above guide, you will ensure that:

• CSV is required on all booking requests
• Card number truncation requirements met for display and storage
• SSL used on all booking-related pages
• Brand parity requirements met

Where EAN is Merchant of Record, evidence of PCI compliance, such as an an Attestation of Compliance (AOC), must be supplied.

EAN Affiliates must use the PCI Security Standards Council's Self-Assessment Questionnaire file "SAQ D - Merchants" to produce the proper AOC.

You can review the instructions and guidelines for SAQs and find the "SAQ D - Merchants" file on the official PCI Security Standards Document Library, or download the SAQ D - Merchants file directly as a PDF or Word document.

If you intend to consume the TripAdvisor content available in the EAN API, you must agree to comply with TripAdvisor’s guidelines to be authorized access.
This agreement must be provided via email to support@ean.com, or in writing, at the time of requesting approval to launch, or any time after going live. TripAdvisor hold the right to withhold/remove access to the TripAdvisor content, even after authorization is approved, at any time.

When a price breakdown is provided on the room availability page, the value returned for tax_and_service_fee must be displayed separately for all tax references. 

This display must include the exact text below, as it is legally required 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"

When sending or transmitting sensitive data, you must use SSL encryption. Sensitive data includes guest names, phone numbers or emails, payment card details, and booking/itinerary receipts and confirmation pages.

If the customer's browser does not employ a secure connection to send or receive this information, SSL is not properly incorporated .

The value returned for tax_and_service_fee must be displayed separately for all tax references and/or where a price breakdown is provided on your booking form(s).

The exact text below is legally required on your site for all Expedia Collect inventory when referring to any "taxes and fees" totals within a price breakdown. 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

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). Fees may not be included inside of existing fee breakdowns.
Affiliate booking or service fees may not be bundled into the price and must be broken out separately.

Example:
The example room below has a tax and service fee total of 27.09 euros. In the incorrect example, the partner service fee has been rolled into the EAN fee total. The correct example provides the partner service fee separately and clearly identifies its source.

When a mandatory_tax value returns, return this value separately in your charge breakdowns as an additional charge due at the hotel. These charges are collected directly by the hotel and are not part of standard tax recovery charges.

The email element within BillingContact must contain the customer's email address OR the mailbox your integration monitors for confirmation email handling. This ensures the destination of all EAN-generated emails is always known, which is required for cases of booking disputes or troubleshooting.

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.

If your integration permits child guests and the customer specified child guests for their room selection, you must clearly confirm the number of child guests and their ages on your booking pages for all Expedia Collect properties. This information is provided via the child_ages element.

When customers specify child guests, the API response may contain age restrictions and/or extra occupancy or crib charges that may affect the cost or eligibility of the booking. These items must be clearly messaged to customers before checkout.

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.

Non-refundable availabilities are indicated by refundable=<strong>false</strong>. This value always takes precedence over any differing policy data. Clearly state such rooms are 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.

Before allowing customers to confirm their purchase on your final booking page, you must provide the cancellation policy for the selected room or rooms and require customers to accept the policy.
Customers must not be allowed to book without agreeing to the room's specific cancellation policy.

Cancellation policies must always be obtained from live shopping responses via the cancel_penalties array.

It is acceptable to include this agreement as part of the customer's acceptance of your own terms & conditions, e.g. "By [selecting this checkbox/continuing with the booking/etc], you agree you have read and accepted our Terms and Conditions as well as the cancellation policy for your selected room."

The booking must include a viable contact number for the customer. Include this number in your booking request's phone field within the BillingContact object. Inform customers that this number will be used to contact them in the event a problem needs to be resolved with their reservation ahead of check-in time.

Example

Example

The emails/vouchers you send to customers must provide a charge breakdown.

The value returned for tax_and_service_fee 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"

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). Fees may not be included inside of existing fee breakdowns.
Affiliate booking or service fees may not be bundled into the price and must be broken out separately.

Example:
The example room below has a tax and service fee total of 27.09 euros. In the incorrect example, the partner service fee has been rolled into the EAN fee total. The correct example provides the partner service fee separately and clearly identifies its source.

If a mandatory_tax value returned earlier for the property to be booked, return this value separately in your pre-book price breakdown. These charges are collected directly by the hotel and are not part of standard tax recovery charges.

You must clearly identify the supplier of the hotel as either Travelscape LLC or Vacationspot, SL, according to the hotel's point of sale as follows:

• Vacationspot: Applicable for all French and Belgium Points of Sale (PoSa), e.g. French: Mytravel.fr or Belgium: Mytravel.be
• Travelscape: Applicable for all other PoSa.

You must send the Customer-Session-Id for each customer, beginning with their first property search, to ensure the content returned is consistent throughout API calls and your customers have a consistent experience from shopping to booking.

This value greatly eases EAN's internal debugging process for issues with partner requests, as it explicitly links together request paths for individual customers.

The customer's device IP address must be passed in all API calls to identify the point of sale.

This requirement ensures the correct POS is set within EAN's systems to provide customers with relevant content and the most suitable rates based on their location.

Passing static, dummy, or server IPs will cause price mismatch errors and incorrect content to return.