HOTELS

The evidence must be submitted as a PDF file with screenshots clearly labeled with their corresponding item numbers. Links to your website are not valid for this process. Reports can be submitted in the same PDF or as attachments. If any of these requests do not apply, please report them and document them.

📘

Bookings for certification should be done in SandBox Environment

1. The complete set of booking and cancellation logs, along with the corresponding vouchers, shall be provided for the following test bookings executed in our Sandbox environment. These artifacts will be used to validate correct request execution and data accuracy. All test bookings may be cancelled shortly after confirmation; all related logs and vouchers must be included.

   The following reservations must be created for testing purposes: – 1 room with 1 adult – 1 room with 2 adults and 1 minor (7 years old) – 2 rooms with 2 adults each – 2 rooms: one with 1 adult and 1 minor (3 years old), and the other with 2 adults and 1 minor (1 year old)

2. It is mandatory to verify the minor's age is set in the search field (ages ranging 0-17 yo).

3. We recommend searching up to 100 hotel id per request.

4. Make sure that customer's name and surname include the following characters only: may contain: a-z, A-Z and "ÁÉÍÓÚáéíóúäëïöüÄËÏÖÜÕŨÑãõũñÂÊÎÔÛâêîôûÇçḈḉḐḑȨȩḜḝĢģḨḩĶķĻļŅņŖŗŞşŢţçüéàßø" (ISO-8859-1)

5. Verify that the hotel name,room type, bedding and meal plan are displayed in the search results.

6. Verify that the filter “charge_at_destination” is displayed in the booking flow (mandatory as required by California’s AB 537).

7. Make sure that the cancellation policies are displayed. Include the details of how they are calculated.

8. Indicates which payment type was developed: depositpayment and/or agencycreditpayment. Reservation and cancellation logs must be provided for each implemented payment method. If only credit card (cc) payment is implemented, no additional logs are required.

9. Indicate if the static content shown is from HotelDO or how it is constructed.

10. Make sure your platform allows including passenger names per room.

11. Ensure that at least one passenger name is provided per room, and clearly define how booking errors are displayed on your side, including the relationship between error codes and the corresponding HotelDO ID.

12. Validate the correct use of the "IsBindingRate" tag for Binding Rates; if "IsBindingRate = true," the "AgencyPublic" value must be applied as the minimum selling rate (“Total” value will always remain the net rate). To validate this item, you must also provide files as evidence.

13. Perform the complete confirmation flow of a reservation (search, prebook, payment, book, cancel, change, etc.).

    1. During the prebook stage, ensure comprehensive logging by utilizing the "include" parameter to capture both hints and exchange_policies data. These elements can be requested within the same API call to optimize performance and provide complete visibility into the booking process and policy information.

14. Verify that the confirmation receipt or voucher displays the following:

    1. Date of the reservation.
    2. Hotel DO confirmation number.
    3. Service confirmation details:
       1. Room;
       2. Meals;
       3. Occupancy;
       4. Guest name;
       5. Check-in and check-out dates;
       6. Main guest name;
       7. Cancellation policy;
       8. Fees to pay at Destination
       9. Notices;

15. After-sale services can be validated using the v3/reservations endpoint, which provides the information required to review and verify reservation data when necessary. Partners should ensure that the PNR returned in the v3/reservations response is properly captured and stored, as it is used in subsequent after-sale operations.

    1. Voucher: Determine whether you will utilize your own voucher system or HotelDO's voucher service. Regardless of the chosen approach, all voucher details must be transmitted to the end customer. When using HotelDO's system, the voucher can be accessed through the "download_voucher_url" field provided in the Status response.
    2. Cancellation: Support both manual and automated cancellation processes. It's important to note that cancellation operations affect all participants included in the reservation - partial or individual participant cancellations are not supported by the system.