1. Support Hub
  2. TripBuilder
  3. IBE - Internet Booking Engine

IBE with Marketplace Supply & Reservation Request

Get started with the TripBuilder consumer IBE in combination with marketplace supply and reservation request. This article walks you through the most important steps.

  1. Overview
  2. Details Explained
  3. Getting Started
    1. Checklist - Agreements & Terms
    2. Checklist - IBE Configuration


Nezasa's TripBuilder IBE with marketplace supply provides an all-in-one solution to sell personalized itineraries over your own website to consumers. Most customers opt for our default solution which comes with online payment. Read More

However, if you prefer to give consumers the planning tool without online payment, then that is possible too. We call this the TripBuilder IBE with a reservation request checkout

Booking Process with Reservation Request

The booking process in this case looks as follows:

Step 1 - Reservation Request

The consumer accesses your company's website with the embedded TripBuilder IBE, plans the trip, and goes into the checkout. The checkout will cover gathering the PAX details and then triggering a reservation request. The consumer as well as you will receive an email notification. From this point onwards, the consumer doesn't use anymore the TripBuilder IBE on your website.

Step 2 - Check Booking Request

As tour operator, you check the reservation request and perform the booking with your tour operator user in the TripBuilder. If the itinerary contains components from the Nezasa marketplace, you'll be asked to pay by credit card. This is your corporate credit card, not the consumer's credit card.

  1. Open the booking in Cockpit Customer Care 
  2. Verify if the itinerary is sound. At this point, you are still free to adjust the itinerary. No third-party supply has been booked yet.

Tip 1: in Customer Care, you can search by consumer name or by the itinerary ID which was mentioned in the email notification.

Tip 2: check out the Notes feature in the detail view of this itinerary. That's the place where internal remarks related to the booking can be stored.

Step 3 - Get Consumer Pre-Payment

Ask the consumer to pay. Because your IBE is without the online payment feature of TripBuilder, you'll need to get the payment from the consumer outside of TripBuilder: be it by invoice, cash if the consumer is in your office, or use another online payment solution (Stripe, Payrrex, Paypal, Twint, etc.).

Step 4 - Perform a B2B Booking

Perform the booking with your tour operator user in TripBuilder. If the itinerary contains components from the Nezasa marketplace, you'll be asked to pay by credit card. This is your corporate credit card, not the consumer's credit card.

  1. You should be logged in with your user
  2. Open the booking in TripBuilder (e.g., use the link for collaborators in the sidebar of Customer care)
    Bildschirmfoto 2020-11-09 um 16.45.02
  3. Go through the checkout and trigger the booking.

Step 5 - Inform the Consumer

All is done. Send the consumer now or later vouchers and travel documentation.

Getting Started

The onboarding process documented in form of checklists. The Nezasa support will guide you through the steps, of course. The process is similar to the one including the online payment, except that the additional terms and conditions can be skipped and are thus not listed on this page.

Checklist - Agreements & Terms

This three, contractual steps are required to get started.

Step 1

Product Plan

Subscribe to the product plan “Standard” or higher. 

Step 2

Order the Consumer IBE & Accept Service Terms

Please trigger the consumer IBE setup process with Nezasa support and accept the Nezasa service conditions for consumer bookings.

When doing so, please inform us that you opt-out of the online payment feature and would like to have the reservation request checkout configured.

Checklist - IBE Configuration

This checklist goes through configuration options available for your IBE.

Step 1

Base Setup by Nezasa

Get confirmation that Nezasa has enabled the consumer IBE for you.

Step 2

White-label Domain

By default, the IBE runs on a dedicated domain. While Nezasa provides such a subdomain (*.tripbuilder.app), it is highly recommended to use a subdomain of your primary domain because of the “third-party cookie policy” of modern browsers. 

Example: your main domain is “www.company.com” and you choose to use “ibe.company.com” for the consumer IBE of Nezasa.

Read more

Step 3

Embed IBE into Your Website

Set up a path and page on your website where the IBE will be integrated.

Read more

    Step 4

    Configure your IBE

    There are plenty of configuration options available. Here the most important ones:

    • Terms & Conditions
      Configure the IBE checkout such that the user has to accept the terms. This may also involve topics like EU-GDPR or EU-PRRL checks.

    • Cancellation Policy
      As a tour operator, you’ll enforce package cancellation policies which need to be defined and applied. You can either pack them into your terms & condition, or use the systems “cancellation policy” feature. 

    • Payment Terms
      Define what down payment you’ll ask from consumers.

      Remember: if a booking contains marketplace components, the system might apply a higher down payment. 

    • Markups
      Define for different product categories what markup you put on top of the net price. Read more

    Step 5


    It is essential to test all your settings and maybe even do a test booking. Here are some important remarks when it comes to testing:

    1. Test as "consumer"
      The final tests should take place in the same way as a real customer of yours would use the website. This is absolutely crucial! Doing the tests directly on TripBuilder portal while being logged in with your admin user might lead to different results as your user has special permissions which leads to more features being available or more information being shown.

    2. Test Booking
      Perform a real booking with an actual credit card. When doing so, do not use marketplace supply because it will trigger bookings in supplier systems. Use ad-hoc components instead and make sure the value of the itinerary is small. 
      Thanks to this booking test, you'll also be able to test the refund feature in the Payyo backend UI.