Interoperability of ticket and payment systems project (Lippu)

Published 24.03.2017 | Updated 20.06.2018

In the first phase, the Act on Transport Services aims to enable one-stop solutions for single-ticket and travel-right purchases in road and rail transport. Transport service providers are required to provide open access to the sales interfaces of their ticket and payment systems. At the minimum, the sales interface must enable the purchase of a standard-rate single-journey ticket product, or the reservation of a single journey or transportation, if its exact price is not known at the start of the service, or the service is post-paid.

Initiated by the Ministry of Transport and Communications, the Interoperability of ticket and payment systems project is a joint project by FICORA, the Finnish Transport Agency, and the Finnish Transport Safety Agency. The aim of the project is to lay out the specifications of the technical sales interface solution and a code of conduct to facilitate the conclusion of contracts between operators. An open network has been set up for all operators in the field to make sure that everyone's views are heard. A pilot project with a handful of selected operators will provide crucial feedback on the interface specifications and the code of conduct.

For more information about the project, please contact Project Coordinator Timo Leppinen at timo.leppinen(at)

Lippu network

Project updates are published on the Lippu network mailing list and website and communicated in the Lippu network meetings. The network members include around 170 people from 80 different organisations. Lippu network meetings are organised approximately every two months. To join the network mailing list, please send an email to virpi.liehu(at)

Interface specifications

In cooperation with Solita, the Lippu project group has prepared technical interface specifications for single tickets, travel chain related incidents, accessibility, and ticket validity. The specifications enable one implementation of an interoperable interface. The service providers may, however, decide by mutual agreement to use some other type of interface.

For the further development of the specifications, service providers have been provided with access to electronic tools for communication and draft version management. Service providers can receive information and take part in interface specification as follows:

  • Developer discussions (Slack); for a Slack invite, please contact Olli Nylander, olli.nylander(at)
  • Distribution of specification documentation: GitHub

Code of Conduct

The aim of the Lippu project is to create opportunities for providing travel chains in accordance with the Act on Transport Services. The Code of Conduct facilitates service providers’ efforts to open their ticket and payment systems to other service providers. The Code of Conduct is prepared in a joint effort by the government agencies participating in the Lippu project and service providers. We have heard the views of the relevant parties in network meetings, Code of Conduct workshops and bilateral meetings.

Project report on contractual practices for travel chains defined in the Act on Transport Services [pdf, 1 MB]

Annex 1: Legal analysis prepared by Dittmar & Indrenius Attorneys Ltd. [pdf, 886 KB]

Annex 2: LIPPU-API: Security Considerations [pdf, 334 KB]

Annex 3: Analysis of needs to develop interoperable payment interfaces [pdf, 320 KB]

Annex 4: Travel chain data flows [pdf, 32 KB]


Pilot projects will be launched with a handful of selected service providers to test the interface specifications and the Code of Conduct in practice. In the pilots, the selected service providers test the interoperability of their ticket and payment systems by creating a sales interface on the basis of the Lippu interface specifications, and conclude a mutual agreement on ticket offering. Financial aid is granted on the condition that tickets are actually provided via the interface.

Other documents prepared in the Lippu project

Key words: Information security , Availability , Data protection , Functionality , Network , Open data , Ticket system , Travel chain , Travel status

LinkedIn Print