API Travelfusion

From docs.websky.tech
Revision as of 09:50, 29 January 2021 by I shaletin (talk | contribs) (→‎Related settings to get started in Websky)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Travelfusion is one of the leading content aggregators for OTA, providing direct access to the resources of numerous air, rail and hotel suppliers. In addition to its direct functions, GDS has its own payment tool for mutual settlements (TF.Pay), as well as ready-to-use services (both for B2B and B2C models) for effective business management. It specializes mainly in low-cost suppliers.

The company was founded in 2000. Travelfusion is headquartered in London, UK, and has offices in Shanghai, China. Resource: about 220 airlines and rail carriers. A full list of supported suppliers is available on Travelfusion's official website: [1] Distribution: predominantly Europe.

The process of connecting to Travelfusion at Websky

  1. In the Websky system, you can currently implement a connection to Travelfusion only to work with the "Air tickets" component. To do this, the agency needs to contact the Travelfusion sales department and sign a contract. You should also specify in the letter that the agency is going to work with Travelfusion through Websky.
  2. After signing the contract, the account manager sends the agent a file with requisites (username and password) to connect (Travelfusion Welcome Pack) and a checklist form to fill out.
  3. The agency provides the details to Websky tech support through a ticket in the project tracker. The tech support staff helps fill out the questionnaire, and the agent sends it to Travelfusion.
  4. After Travelfusion officially confirms and authorizes you to get started, the tech support team starts and configures the Websky requisite package for the agent.

Related settings to get started in Websky

After completing the requisites configuration, the agent also needs to make the following settings:

  1. Enter the necessary rules for the companies to be billed through the Travelfusion Connector into the pricing file. Commission values are not transmitted to the provider when they are discharged, so you can specify zero commission for all such airlines and assign your agency fees if necessary. (See Pricing (air tickets))
  2. Add an itinerary receipt template for the supplier Travelfusion (see Itinerary receipt).
  3. Check that all fields are filled in under Avia Settings → Agency Profile in the Nemo Connect settings.
  4. If you wish, you can implement the output of additional information text in a pop-up window (next to the checkbox agreeing to the booking rules and the public offer on the order page in the same block). You can enter the text in the settings section "Site management" → "Domains and protocols" → "Additional transport rules". To display a pseudo-reference to the popup with this text you need to change the value of the language variable new-passinfo-footer__agreementText (see Localization) by adding html code:

Example

I have read and agree to <a href="/booking__policy" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'Booking Rules'}">booking rules</a>, <a href="/booking__additional_flight_rules" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'title you need'}">rules for ancillary services</a>, <a href="[%-faresurl-%]" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title: 'Rate Terms'}">the fare rules</a> and <a href="/booking__policypd" class="new-ui-pseudoLink js-thickbox__frame__href" data-popup="{title:'Rights of the subject of personal data'}">the rights of the subject of personal data</a>. I agree and confirm the consent of third parties, specified by me in the booking, to the processing of personal data, including their transfer to third parties providing or servicing the transportation, as well as the cross-border transfer of personal data.

Ordering process in Websky

After selecting a Travelfusion flight and filling in passenger information on the booking page in Websky, the customer clicks the "Book" button. In this case the booking is not created in the airline. The booking object is created only in the Travelfusion system itself, but no seats are actually reserved, and passenger data is not transmitted to the airline. After successful payment, Websky launches a ticketing request (at this point the airline is already creating a booking). But even after successful processing of the request, the order page will initially display the "Tickets are being processed" inscription, since in the response to the statement request the provider initially does not send ticket numbers, since the airline booking is not confirmed immediately. Websky then automatically updates the order (at a frequency of once every 7 minutes), and during the update already receives the ticket number from the supplier. The itinerary receipt will be automatically sent to the customer's email.
The text of the Tickets are being issued message can be changed in the localization, via the ticketed_without_tickets language variable.

Features of Travelfusion

  • Travelfusion requires an agent's personal account on the side in order to debit the creation of bookings with the airline.
  • Due to Travelfusion's focus on low-cost suppliers, airline bookings are only created when they are ticketed in Websky. When booking in Websky, a pseudo-booking is created on the Travelfusion side, nothing is created on the airline side and no seats are blocked.

Attention! Because of this, before the ticketing in Websky, there is no guarantee that the booking will be successfully made. In the case of a situation where a booking is made, payment passed, and there is no ticketing after launch, the only way to perform ticketing for the reservation is to reissue the entire booking, starting with a search.

Also, due to Travelfusion's focus on low-cost suppliers, there may not be a ticket after ticketing in Websky, often Travelfusion has a booking code in the airline system with which passengers need to go to the airline site for ticketing. Once a booking is made in the airline's system, Travelfusion does not synchronize it; accordingly, Websky does not receive information about flight changes, flight changes need to be tracked by the passenger.

  • Due to the specifics of Travelfusion receiving data from the airlines, at different stages of the purchase (search, updating and booking in Websky) price of the flight and booking can be different - usually due to rounding errors in calculating the total amount on the side of Travelfusion and Websky.
  • It is obligatory to enter the client's contact information, as passengers might have problems with the check-in for the flight if they do not have this information. Information important for the agent will be sent to these contact details.
  • Websky returns problem statuses received from Travelfusion. In case of problem statuses, the agent should follow the instructions and contact Travelfusion technical support.
  • Travelfusion has a protection against duplicate bookings, in such cases an error is returned. If an error occurs, no new booking will be created in Websky.
  • Due to the frequent updating of requirements for agents to connect to Travelfusion, the connection process can be lengthy.

Features of working with Travelfusion in Websky

  1. Currently, Websky allows you to work with Travelfusion only with TF Prepay Method: the agency opens a personal account in Travelfusion for a certain amount, and when the customer makes a booking on the site, the price of the flight is deducted from the agent's balance to the Travelfusion account. Then Travelfusion independently transfers the funds to the account of the airline. Attention! Payment directly to the airline is not possible at this time with the customer's card.
  2. Attention! Currently Websky does not implement:
    • search by nearest dates (planned in the future);
    • search by nearest airports (planned in the future);
    • sales of optional services (baggage, meals and seat selection);
    • search by complex route (ST) - not supported by Travelfusion;
    • supplementing and modifying bookings (passport and visa information, loyalty card) - not supported by Travelfusion;
    • cancellation of unissued bookings and updating of issued bookings - not supported by Travelfusion;
    • voiding, exchanging and refunding bookings (not supported by Travelfusion). The customer must contact the airline directly for this.
  3. All fares are treated as non-refundable.
  4. Airlines send their own confirmation letter (i.e. their itinerary receipt) to the customer's e-mail address that was provided at the time of booking. This itinerary receipt will show the net price of the flight, i.e. the customer will see the price without agency extra charges.
  5. If the flight/schedule is changed after the booking is issued, the changed data is not displayed in Travelfusion, i.e. synchronization after the booking is not possible, and this data will only be available at the airline directly.
  6. The default booking page for a low-cost flight displays Attention! This flight is provided by a low-cost airline. Meals are not available on board! The text of this message can be changed in the localization, by the no_meal_for_LowCost language variable. You can completely hide the output of this message by using css styles.
  7. Currently it is enough to specify the deposit currency in the requisites to the GDS, in the package it is optional.
  8. The base price of flights from Travelfusion when searching can come in any currency - it depends on the airline, and there can be prices in different currencies (fare in euros, and fares in dollars, for example) for the same flight in the supplier's response. Websky then requests the Travelfusion exchange rates from their system and converts the entire cost of the flight according to that rate into the currency of the requisition. Translation of prices on the agent site into other currencies will be according to the rates set in the agency currency directory (System Settings → Currencies and rates → Directory of currencies and rates, see Currency. Currencies).
  9. Travelfusion can send negative tax values (i.e. discount rates) or no taxes at all, or the taxes can be already included in the fare.
  10. Supplier side booking time limit is 15 minutes and can't be longer.
  11. Travelfusion does not allow booking a separate seat for an infant. Warnings about this are displayed on the results page and on the booking page in the form of the caption: Booking a separate seat for an infant is not allowed by the carrier. You can change the warning text on the results page by setting the flightsGroup__flightWarnings__insBookingNotAllowedBySupplier variable translation in the localization settings, on the booking page - ins_booking_not_allowed_by_supplier.
  12. As required by Travelfusion, you must be sure to set up routing according to their schedule. See Search request filters (Air tickets)
  13. Along with the address information from Avia Settings → Agency Profile in the Nemo Connect settings, the name of the agency in Nemo Connect is passed to Travelfusion as the company name. To change the name of the company transferred to Travelfusion, you must change the name of the agency in the Nemo Connect settings. To do this, you need to create a request to the technical support team: helpdesk.nemo.travel.
  14. One of the requirements of Travelfusion is to have the PointOfSale parameter in StartRouting and ProcessTerms requests to the provider. PointOfSale is for certification and correct operation. The value of this parameter is changed in the Nemo Connect settings in the Avia Settings → Agency Profile → Agency Country Code field.
  15. The ProcessTerms request uses fields:
    • Company name - in the XML field Company
    • Office - in XML field Flat
    • House - in XML field BuildingNumber
    • Street - in XML field Street
    • City - in XML field City
    • Region - in XML field Province
    • Postal code - in XML field Postcode
    • Country - in XML field CountryCode

You can change the values of these parameters in the settings of the Websky adminitration panel in Account Management → Agents and Users → Company Profiles.


Possible errors and their causes

  • Your branch cannot perform booking through the TF.Payment Service - means that the Travelfusion account is not activated.
  • Supplier does not support payments through the TF.Payment Service - the airline does not support the TF.Pay payment method. Disabling the issuance of flights of this airline is possible on the side of Travelfusion, by contacting their technical support.
  • Temporary supplier error - problems on the side of the supplier. It is recommended to repeat the action later. If the error continues to occur frequently, you should contact Travelfusion Technical Support.
  • The supplier is too busy - similarly, temporary problems on the supplier side due to a high load on the Travelfusion system.
  • Internal server error - an internal error on the Travelfusion servers.
  • RequestValidationError - agency profile (address and contact information) is not filled in the Nemo Connect admin panel.
  • Title missing - the Automatically add passenger's title setting is not enabled in the Travelfusion package booking requisites in the Nemo Connect administration panel.
  • Address postal code is required for this journey - no address information has been entered in Avia Settings → Agency Profile in the Nemo Connect settings.

Contact Information

See also

Retrieved from "https://docs.websky.tech/index.php?title=API_Travelfusion&oldid=303"