Skip Navigation

Timatic

Some airlines require multiple validations before a Passenger can correctly check in and/or board.

One of the validations can be done using Timatic database containing cross-border Passenger documentation requirements. Each Passenger in the reservation can be verified against this database to check recommendation if a Passenger can be checked-in/boarded basing on the provided details.

Digital Connect Check-In services support the following functionalities related to Timatic:

  • Informing POS that the Timatic verification is required and has not been triggered yet
  • Adding Timatic related documents and data
  • Verifying Passenger using Timatic database and returning the results of this validation
  • Overriding Timatic result (Agent-specific capability).

Digital Connect Check-In informs about the required Timatic Verification using mechanism of Eligibilities. The ADDITIONAL_VERIFICATION_REQUIRED code is returned as a part of the /dcci /passenger/details response and then POS should know that the Timatic verification should be triggered.

Timatic verification is a separate action available through Digital Connect Check-In services and should be performed when POS has collected all details from a Passenger. Using Digital Connect Check-In services there is a possibility to add Timatic specific data such as:

  • Timatic document type
  • Residency document
  • Stay type - which determines the reason for the travel
  • Return date - which determines when a Passenger leaves the particular country

Additionally, the Agent-oriented applications can use the 'Visa verified' flag which informs that an Agent already verified Visa details for the Passenger.

All the above details can be added using the /dcci/timatic/add service and when collected from a Passenger, the Timatic verification should be triggered by POS using the /dcci/timatic/verify service. The response depends on POS type and for self-service applications it contains the following results returned as eligibilities:

  • PASSENGER_DOES_NOT_HAVE_VISA
     

    This information means that Timatic validation status is either CONDITIONAL or NOT OK TO BOARD where we are able to determine that at least one of the status reasons is lack of VISA document. Because of this information VISA document can be added by a Passenger (if not added so far) and the Timatic status can be verified one more time.

  • SELF_SERVICE_CHECK_IN_NOT_AVAILABLE
     

    This information means that the Timatic status is either CONDITIONAL or NOT OK TO BOARD and the lack of VISA is not a problem. This Eligibility means that from self-service application perspective nothing can be done, and the Passenger should contact an Agent.

Note  If none of the above eligibilities occurs as a result of the /dcci/timatic/verify service, the Passenger can be checked-in by any channel (including self-service).

The Agent-oriented applications can retrieve more detailed information about the result of the Timatic verification operation. As an addition to eligibility information separate structure called timaticVerificationResults is returned. This section contains all pure details returned by the Timatic system. An Agent needs to go through the detailed response and decide whether a Passenger should be checked-in/boarded or not.

Whatever the Timatic verification result is, an Agent application still has a chance to override this result by using the /dcci/timatic/overrride service. After override action the Passenger is treated by Sabre systems in the same way as if Timatic result would be OK TO BOARD.