Test Cases - Trusted Getaways

Following information should be displayed to the users in the Trusted Getaways booking flow. Some of it is mandatory; the rest is optional but suggested for clarity. These test cases are in place to minimise post-booking escalations caused by missing or wrong information.

Pre-Booking Flow:

  1. Package title, nights and days, star category and route (e.g. "3N Hanoi → 2N Danang → 2N Ho Chi Minh City" for fdljkya) - Mandatory
  2. Departures - travel dates, price per adult and seats left; sold-out or closed departures not bookable - Mandatory
  3. Prices by traveller type - adult, single adult, child with bed, child without bed, infant - Mandatory
  4. Age bands and room rules in the travellers picker (minimum adults, maximum per room) - Mandatory
  5. Day-wise itinerary - date of each day, transfers with place names, sightseeing with type (Shared / Private / Ticket only), hotel stays (fdljkya) - Mandatory
  6. Flights - airline, flight number, times, duration, baggage, "+1d" for next-day arrival, internal flights placed on the right day and in the right order (fdljkya) - Mandatory
  7. Upgrades and add-ons, each with its price per traveller type - Mandatory (when the package has them):
    ◦ Hotel upgrade (fdljkkv, fdljkya)
    ◦ Sightseeing add-on (fdljkkv)
    ◦ Transfer add-on (fdljkya)
    ◦ Start-from-another-city flight add-on (fdljkkv)
  8. Inclusions and exclusions - Mandatory
  9. Payment policy and cancellation policy - Mandatory
  10. Price breakdown and trip total on the review page - Mandatory
  11. Price change pop-up (Book returns 409) - Mandatory
  12. Lead traveller name, contact number and email address - Mandatory
  13. Market price struck through - Optional
  14. Package images and sightseeing images - Optional
  15. Seats-left badge - Optional

Post-Booking Flow:

  1. Provisional booking code (booking_code from the Book API) - Mandatory
  2. Status "Booking received · seats held" until the final code arrives; never shown as confirmed before that - Mandatory
  3. Final booking code once the Booking Status Webhook sends FINAL_BOOKING_CODE_ASSIGNED - Mandatory
  4. Your booking reference (buyer_booking_reference) - Mandatory
  5. Trip summary - package title and listing code (e.g. fdljkkv), travel dates, rooms and travellers, chosen upgrades and add-ons - Mandatory
  6. Booking amount - Mandatory
  7. Note that the traveller's documents will be collected before the booking is confirmed - Mandatory

Pricing Rules to Verify:

Every total is checked by the Book API. If your total differs, Book returns 409 with TravClan's expected_amount, so a mismatch shows up as a failed booking. Full rules: Pricing and Occupancy Rule and Add-ons and Upgrades.

RuleWhat to check
Child-to-adult promotionIn a room with 1 adult + 1 child, charge the lower of: single adult price + child price, or 2 × adult price (the child is charged as an adult).
Upgrade follows the roomThe hotel upgrade is charged the same way as the room. If the child is charged as an adult for the room, use the adult upgrade price for that child too.
Sightseeing, transfer and flight add-onsCharged per traveller: adult price × adults, child price × children (with and without bed), infant price × infants.
SeatsAdults and children take a seat; infants do not.

Worked example (5N Singapore Getaway, sandbox prices at the time of writing: adult ₹40,000, single adult ₹55,000, child with bed ₹30,000, One Farrer upgrade ₹500 per adult, ₹200 per child with bed):

RoomOption AOption BCharged
Room 1: 2 adults——₹80,000
Room 2: 1 adult + 1 child with bed₹55,000 + ₹30,000 = ₹85,0002 × ₹40,000 = ₹80,000₹80,000 (B)
One Farrer upgrade, both rooms—Room 2 follows B: 2 × ₹5004 × ₹500 = ₹2,000
Trip total₹1,62,000

Charging the child's upgrade at the child rate (₹500 + ₹200 in room 2) gives ₹1,61,700, which Book refuses.


Bookings in SANDBOX

Use these two sandbox packages. Pick any departure that is open for booking with enough seats at the time of testing; prices and dates may change, so always compare your total with the Book API.

PackageCodeCovers
5N Singapore Getaway | Ex-DELfdljkkvHotel upgrade, sightseeing add-on, start-from-another-city flight add-on
7N Vietnam Getaway with Day Cruise | Ex-DELfdljkyaHotel upgrade, transfer add-on, next-day arrival flight, multiple internal flights
PackageRooms and travellersUpgrades / add-onsWhat to verify
1fdljkkv1 room: 2 adultsNoneTotal = 2 × adult price; seats held with a provisional code
2fdljkkvRoom I: 1 adult + 1 child with bedNoneMinimum price: lower of single adult + child with bed, or 2 × adult price
3fdljkkvRoom I: 2 adults · Room II: 1 adult + 1 child with bedHotel upgradeChild-to-adult promotion in Room II; upgrade charged the same way as the room (see worked example)
4fdljkkv1 room: 2 adults + 1 child with bedSightseeing add-onAdd-on shown on its day with adult, child and infant prices; charged per traveller
5fdljkkv1 room: 2 adultsStart from another cityOption shown on the Day 1 flight; charged per traveller; sent in flight_origin_addon_codes
6fdljkya1 room: 2 adults + 1 infantHotel upgrade + transfer add-onBoth priced per traveller type , infant included; sent in hotel_upgrades and transfer_addon_codes
7fdljkyaRoom I: 1 adult + 1 child without bedTransfer add-onMinimum price with a child without bed; add-on charged at the child price
10Booking from case 3 (see Booking Status Webhook test below)—TravClan sends FINAL_BOOKING_CODE_ASSIGNED; your status page replaces "seats held" with the final booking code

Room add-ons on hotels (for example "Single sofa cum bed") are not accepted by the Book API. Do not show them as bookable and do not send them in Book.


Booking Status Webhook test

The sandbox does not confirm bookings on its own, so ask the TravClan team to confirm one of your sandbox bookings. This tests the full journey from "seats held" to "confirmed" on your site.

StepWhoWhat happensWhat to verify
1YouMake a sandbox booking (for example case 3)Book returns a provisional booking_code; your status page shows "Booking received · seats held" with your buyer_booking_reference, and does not show the booking as confirmed
2YouShare your webhook URL and the buyer_booking_reference and booking_code of that booking with the TravClan team-
3TravClanConfirms the booking in sandbox and sends FINAL_BOOKING_CODE_ASSIGNED to your webhookYour webhook answers 200
4YouOpen the booking status page againThe page shows the final booking code from the webhook, and the booking is marked Confirmed
5TravClanSends the same callback againNothing changes on your side; your webhook still answers 200


Bookings in PRODUCTION

IMPORTANT

❗ Please alert the TravClan team before testing in production, so that the test is not processed as an actual booking.

Room CountOccupancy Pattern
112 Adults
22Room I - 2 Adults
Room II - 1 Adult + 1 Child with bed + 1 Infant

Did this page help you?