Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »





Backoffice


From the IBE backoffice, the airline administrator will be able to control and set the configuration parameters of the operation for the web search engine. Modifications made and stored from the backoffice will be reflected in the purchase process immediately.

The access for backoffice will be granted from KIU helpdesk or by account executive for the airline.

The available languages for Backoffice are Spanish and English. It will be defined according to the default language of the browser.

The internet booking engine is available on these operating systems using the following web browser versions.

MAC

  • Safari 10.1
  • Chrome 49

Windows

  • Chrome 49
  • Internet Explorer 11
  • Mozilla 44

IOS Iphone/Ipad

  • Safari 10
  • Chrome 65

Android

  • Chrome 4.4 o superior
  • "Internet" 7 



Search Flights


Default Type of Journey

In this section you can choose the default type of journey to show on the Flight Search page. The options are:

  • One way
  • Round trip

Flight Search Display Logic

This section allows to change the name and code display that the passenger uses in the Flight Search screen. If there is no configuration the information for origins and destination is taken from KIU RES bases on INNOVATA updates.

Display options might be combined with the following indicators, always considering this sintaxis

<city name> <(airport code)>, <airport name> <(airport code)>, <country name> <(country code)>
  • City Name
  • City Code
  • Airport Name
  • Airport Code
  • Country Name
  • Country Code

Passengers Management

Throughout this section you can select the types of passenger that will be able to book and buy. Adult passenger is the default, Child and infant are optional.

Destination Settings

Minimum booking time

In this section you will be able to configure the allowed minimum time to book a flight before the depature.

Origin and Destination

In this section you will have to configure all the routes that are offered trough the IBE. They will be completed with the following criteria:

Indicating the IATA code for the airport or city of departure and arrival
You can designate wether the route is going to be available to use in that moment or load it up for future activation
You can indicate wether that route will accept direct flight or connection flight by checking the box “direct flight only”
Indicate what will be the frequency for the flight, which days of the week will be available to book a flight and in that order the calendar will be able to show only the days that the flight is offered
Bear in mind that if a city has more than one airport, you must add the code of the city to be able to search by city.

You can allow to search by airport name, but in that case you need to add the routes by airport too. For example, for the segment Buenos Aires – New York this will be some alternatives:


BUE - NYC will search from any airport in Buenos Aires to any New York airport, the result shows passengers all the flights that exist between the airports in those cities.

EZE - JFK will search from Ezeiza airport in Buenos Aires to John F Kennedy International airport in New York, the result only shows flights operating from those airports.

EZE - EWR will search from Ezeiza airport in Buenos Aires to Newark International airport in New York, the result only shows flights operating from those airports.

BUE - LGA will search from any airport in Buenos Aires to La Guardia airport in New York, the result shows passengers all flights that exist from any airport in Buenos Aires to the specific airport in New York


Frecuency


This configuration allows to choose which days of the week the route will be displayed on the calendar of the search flight screen.

First Available Date and Last Available Date

This configuration indicates the beginning and the end of operation for the route, the dates will be displayed on the calendar of the search flight screen All loaded routes and their configurations will be registered in the “List of Origins and Destinations” lists. You can edit the data by clicking on  or delete by clicking on  In addition, the icon indicates if the route is enabled. In case of clicking, confirmation will be requested to disable the route.

Texts for Flight Search Display

This sections allows editing the texts for each indicator, in other word the airline can choose the names and codes to be displayed

If no configuration is made the information for origins and destination is taken from KIU RES bases on INNOVATA updates.

The configurations can be deleted by clicking on the  icon or edited by clicking on the  icon.

Country Settings

In this section you can create registers to configure different sales options on IBE so that the airline can unify on the Search Flight screen all the options available for the passengers. In order to create the registers the following data must be completed


Indicator
Description
Validation
DescriptionText display on the combo of the Flight Search Screen25 alphanumeric characters
ISO Country CodeISO country code where the sale is made2 alphabetic characters
Currency CodeISO currency code in which the sale is made3 alphabetic characters
Currency NameText display to indicate currency (not implemented)25 alphanumeric characters
Device ID

Device ID from KIU RES where the booking will be made. Please remind to send an email to webservices@kiusys.com to authorise the use of the chosen device ID.

10 alphanumeric characters
User IDUser ID from KIU RES that books the reservation.NEW USER ID from the HB* command line should be used here9 alphanumeric characters
DefaultFlag that display the register as available for the passenger on the Flight Search screen.
Display on Flight SearchFlag that display the register as available for the passenger on the Flight Search screen.

All registers and their configurations will be shown on the Country Settings List. You can edit the data by clicking on  or delete by clicking on . In addition, the icon  indicates if theregister is displayed to the passenger. The icon  marks the register as default.


Consideration

  • The first created register will replace the configuration in which the airline was creates, the first configuration is always considered as default.
  • The register set as default can't be erased
  • The register set as default will be the first shown on the options combo on the Flight Search screen
  • Only the non-default register/s might be edited; if you wish to edit the default register, you should mark another one and the proceed to the change. 
  • Form of payment should be created in KIU RES for every used country and currency. 
  • ITR configuration must exist in KIU RES for every country used on the settings otherwise the generic configuration must exsit in order to display the .pdf for the issued e-ticket.

Country Settings Frontend Label 

In this section a title/label is set for the combo shown to the passengers, if no label is added no reference will be display on the flight Search screen. The text must be configured both in Spanish and English, entering the text in each tab (ES for Spanish and EN for English), 30 alphanumeric characters are supported for this configuration.

|

Search Results


Kiu_AirShopping 

This method is managed exclusively with Family Fares, the fare basis are assembled in specific categories previously configured in KIU RES (FFAM/* command line). Based on these categories, the method will present the results of availability and price combined allowing the application of all existing fare rules and fare types (One Way, Round Trip, Through Fares).

Round Trip fares for round trip itineraries are shown using the following logic: departure options will display the half price of the most economic fare available, return options will display the remaining fare.

If a Family Fare does not exist for a route or flight the airline can choose how the situation is displayed on the results grid. It might be left blank or use a free text configured in the backoffice, see configuration

Family Fares

  • KIU RES Family Fare Key: you will have to enter a key that associates the information loaded in KIU RES with the different names for the Families on KIBE. If you wish to use different names for the Families between KIU RES and KIBE you can do it in this section too. (only used with KIU_Airshopping)
  • Family Fares: is the name of the fare group and the one that the passenger will see in the search results of flights and prices.
  • Rate conditions: these are the fare conditions that include the fare group. The conditions must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). The fare conditions will be visible to the passenger when the course is passed over the fare group's cell.

Once the data is loaded, they are reflected in the Price Groups table where you can edit the data by clicking on  or delete it by clicking on 

Not Available Family Fare 

Only available for Kiu_AirShopping

If a Family Fare is not available on a responde of a search you may choose what the passenger will see on the page.

  • Blank: the cell for that Family Fare will be left blank
  • Free Text: a 20 alphanumeric character text can be added to display on the cell.

Terms and Conditions

Information text

In this section, the text displayed in the “Terms and Conditions”  link is configured in a new window. The text must be configured both in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). In order for the acceptance of Terms and Conditions to be mandatory, the option YES or NO must be selected.

Sold Out Fares 

In this section, you can configure how you want to show the passenger that a fare is sold out. The possible options are:

• Do not show the amount of the fare, the passenger will only see the legend Sold Out.

• Show the fare amount and  Sold Out e legend.

• Show the amount but with the price crossed out  and  Sold Out legend.

Information text

In this section, you configure the message or information text to be displayed in the search results screen in the lower part before the summary of the amounts of fares of your selection.

Pricing simulator in Search Response screen (KIU_AirPrice method)

This configuration simulates a quotation before moving onto the purchase. If the selected fares are not combinable, and error message will be displayed to the passengaer and they will be forced to select new fares. The error message displayed is the following

Your preferred fare/s can't be combined. Please select a new combination




Passengers Information


Passengers Information


Other Contacts

Emergency contact

This option allows to include in the information form that the passenger completes an emergency contact. The contact will be included on the booking as Emergency Contact, the contact city will be the one that belongs to the first segment.

Destination contact

This option allows to include  in the information form that the passenger completes a contact at destination. The contact will be included on the booking as Contact at Destination. The contact city will be the one that belongs to the destination city of the consecutive segment taking into consideration any difference above 24 hours.

Form of Identification

In this section, the types of documents that you want to give the passenger as an option are configured. You can also configure with what name you want to show the document in the form that the passenger sees when completing the data. The name must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). These are the documents that complete the FOID (Form of Identification) field in the passenger's booking.

Special Service Requirement


SSR DOCx

In this section, you will be able to configure those routes that request SSR DOCX information, meaning that the information that will be requested in the forms will also include documentation in addition to the usual personal information. The routes will be configured by origin and destination but it could also be configured by all origins and all destinations, in order to avoid input the information per route. You can only configured those that are in the IBE, the ones that are configured on BOOKING CONFIGURATION

Bear in mind that if there is no travel documentation, in every cases, the passengers date of birth will be entered as an SSR DOB (DATE OF BIRTH)

You can select which types of SSRs DOCx to use, for example SSR DOCS for traveling documents, SSR DOCO for visa information, SSR DOCA for addresses, destinations or residency information. In addition you can configure that all de DOCS should be requested

Once you added the routes, they will be documented on the “created configurations” board, where they can be edited by clicking in the icon and deleted by simply clicking the icon

Documents DOCS Settings

In this section you will learn to configure the types of documents that you wish to accept for the SSR DOCS. You can also configure which Names will be showed on the form that the passenger completes.  The name must be configured both in English (EN) and Spanish (ES)

Frequent Flyer 

In this section the frequent flyers program/s will be activated so that the passengers can enter their information. If configured the airline IATA code and Frequent Flyer Program Name should be entered. The settings will be displayed on the Airlines Added table where they can be edited by clicking in the icon and deleted by simply clicking the icon 

Reservation summary


Taxes

In this section, you must configure the names  you want to show the taxes charged to the passenger. In case they are not configured, the passenger will see the IATA codes corresponding to each tax

The code and the description of the tax or rate must be detailed. The name must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English).

Once the tax and / or rate descriptions have been entered, they are documented in the table Existing Tax Codes from where they can be deleted by clicking on the icon  or edited by clicking on the icon

Fees

In this section, you must configure the names you want to show the fees charged to the passenger. In case they are not configured, the passenger will see the same codes as KIUU RES hace (TX*FEE/* table)

The code and the description of the fee must be detailed. The name must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English).

Once the fee descriptions have been entered, they are documented in the table Fees from where they can be deleted by clicking on the icon  or edited by clicking on the icon


Purchase


Message for Booking Confirmation

For those airlines that do not use payment gateways or validators the backoffice offers the option to insert a text to display to the passenger that have finish the purchase flow. The text must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). This option is only showed for those airlines without a payment gateway linked with IBE, If no message is configured, the following default message will be displayed

EN: The reservation has been confirmed, to be able to process the payment, contact the airline.
ES: La reserva ha sido confirmada, para poder procesar el pago comuníquese con la aerolínea.


Message for Successful Transaction

A message to be displayed to the passenger must be configured for the successful payment transaction confirmation. The message must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). If no message is configured, the following default message will be displayed

 

EN: Successful transaction! Payment accepted. Thank you for choosing to fly with us.
ES: ¡Transacción Exitosa! Pago aceptado. Gracias por elegirnos.

Message for Issuing Failure

This message wil be shown to the passengers when the e-ticket issue fails, this configuration applies only when whe the issuing method fails but not the payment validation.The text must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). If no message is configured, the following default message will be displayed

EN: We are sorry, there was an error while issuing your e-ticket. Please contact the airline.
ES: Lo sentimos, hubo un error en el proceso de emisión de su/s ticket/s electronico/s. Por favor comuniquese con la aerolinea.


Message for Declined Transaction

The message to be displayed to the passenger must be configured when the purchase is not completed before the time limit of the reservation indicating that it expired. The message must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). If no message is configured, the following default message will be displayed


EN: Transaction rejected. Not debit was made to your account.
ES: Transacción rechazada. No se ha realizado ningún débito a su cuenta.


Message for Expired Booking

A message to be displayed to the passenger must be configured when the purchase is not completed before the time limit of the reservation indicating that it expired. The message must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English). If no message is configured, the following default message will be displayed

EN: Transaction rejected. We are sorry, your booking has expired. Please start again.
ES: Transacción cancelada.¡Lo sentimos! Su reserva expiró, por favor inténtelo nuevamente.

VAT Information

Business name

In this section, the inclusion of the company name in the process of issuing the passenger eticket will be configured. You can configure the mandatory use of the company name to include it in all issues. It is also necessary to configure the name of the company to be used to display on the screen displayed by the passenger, the text must be configured in Spanish and English, entering the text in each tab (ES for Spanish and EN for English).

In the passenger's eticket, the Company name Information will be reflected in the endorsement field.

VAT Identification Key

In the passenger's ticket, the VAT information will be reflected in the VAT field with the chosen VAT number and with the validated information as configured in the backoffice.

VAT Remark

A comment might be added when Business Name and/or VAT Number Information is asked on Extras.


Security and Technical Specs


The current architecture for the KIBE Platform is build with 3 independents security layers.
The first layer, the one that is exposed from the client side, we use Cloudflare services, on which we have a WAF (Web Application Firewall) implementation. This works for several tasks:
  • Hiding the location of our servers
  • Protect the integrity of the app from known xploits that may affect the availability of the service, compromise the security or generate big consumption of resources.
  • Mitigate DDoS and DoS attacks.
  • For exhaustive analysis over the type of incoming traffic, deleting automatics behaviors. 

On the second layer, we are protected with AWS Firewall Manager. This allow us to apply access restrictions (ACLs) to the servers. The reverse proxy provided by Cloudflare, is the only direct point of access.
And for the third layer we have keep updated our equipment with LTS versions and automatic updates policies that are based on CVS newsletters for which we have monthly test for external and internal vulnerabilities. This guarantees the strength and reliability for our applications.

Finally, on application level, we configured security modules in all our web engines, i.e., one of them is the Nginx ModSecurity.

Documentation and datasheets for our toolse:


  • No labels