New API for Adyen payment system

In this version, the Adyen API has been migrated from SOAP to REST technology, so it is a brand new, functionally transparent integration of Adyen that has been put in place.

Evolution of the Resaneo source

The integration of the Resaneo source has been increased as well as the reservation process in order to allow the management of train reservations. In particular, the following features have been added:

  • Added a cache for trains
  • Updated the API to include additional functionality
  • Added an autocomplete function for train search
  • Management of the booking agency code
  • Management of the type of transport (Air, Rail)
  • Management of station coding
  • Adaptation of the functionalities for reservations
  • Implementation of fare conditions for reservations
  • Adding the possibility to display a pictogram for luggage included or not
  • Implementation of a filtering system for train types
  • Added the possibility to see the seat/car number for reservations
  • Management of the margin
  • Evolution of the user interface design to adapt to Train products.

Void Management

This new functional evolution aims to automate the cancellation of fees for reservations that have been cancelled within 24 hours of issue, or for reservations that have not yet been issued.

It automates the implementation of common practices in the airline market where issue fees are not charged when the reservation is cancelled on the same day before midnight (often from the “point of sale”).

This automation will be implemented for reservations that meet specific void-ability conditions and the fee will not be automatically waived for reservations that do not meet these conditions.

A configuration will identify the types of fare lines that can be cancelled under these conditions. The time between the reservation and the cancellation request and the status of the reservation will be taken into account.

The interface will be enriched to display specific cancellation conditions to remind agents why certain fare lines can be cancelled.

Receptive platform, generation of the summary PDF

Within the framework of the receptive platform, we wish to exploit the data of a file stored in the BO in order to display them to a customer whose reservation was carried out on the receptive platform.
By a synchronization, we recover the file in our Back-Office database and the editorial information on the reserved products.

The PDF document will be generated automatically and will be available for the travel agent in the Back-Office interface. He will be able to retrieve it and send it by email to the customer for example.

The final PDF will be composed of 3 sections:

  • A cover page (with agent’s data, main picture of the tour)
  • The body of the pdf
  • An end of document (with text on legal notices, terms of sale, etc)

Regarding the availability in the BO, there will be a difference between a quote and a book:


For a quote

  • The document will be generated in the pdf of the preview “Detail of the file”.

For a book

  • The document will be generated in the “Travel document” section and can be consulted in this section.
  • It will be possible for the travel agent to complete with other documents and to use the emails in the “Travel document” section.

Integration of the SuperControl source

The SuperControl source for access to rental agency products in package mode has been integrated into Orchestra.

Related Activities & Services

The evolution allows to bring up the prices of the linked activities in mandatory mode in the dynamic package or hotel search, in order to include their prices in the prices displayed on the engine return.

For this, the link interface has been revised, the rights work in a similar way to the previous links.

Multilingual management for Pledg

Pledg split payment widgets are now compatible and multilingual with the languages of the booking process.