| Table of Contents |
|---|
Introduction
The Ticketing and Payment Standard BoB (Biljett- och Betalstandard) was developed by Samtrafiken in cooperation with Samtrafiken’s owners. The goal was to create an open module based architecture and create possibilities for interoperability between different ticketing systems and sales clients. Another goal was to move towards a more uniform way for managing machine-readable mobile tickets. The standard also makes it possible to combine several tickets into one. This would enable a traveller to present a travel document containing multiple tickets from different transport companies.
...
Let’s go through some practical examples to make this less theoretical.
Search a ticket
In this case the customer uses an app to search a ticket for the planned journey. The Sales Channel sends a request to the Price and Product in a Ticketing System and asks for suggestions. The Ticketing System finds two tickets that matches the journey in question. Sends over a manifest containing the information about the tickets. The app indicates those tickets that are possible to purchase based on the filtering options selected by the traveller from the Sales Channel app.
...
Buy ticket
The customer chooses one of the tickets that are offered and payment is made via the connection of the Sales Channel with the Payment Service Provider. An order is then sent to the Ticket Engine where the ticket information with its safety content is generated and returned to the app. This generates an Aztec code that contains the ticket information. A transaction is now created in the database linked to the Ticket Engine.
...
Validate ticket
The Aztec code that is shown in the App is displayed to a reader that translates the information in the code into a format that can be interpreted by the Validation Service. The ticket information that is obtained is then compared with the current time, place, etc. in order to check whether or not the ticket is valid, which is indicated to the customer. Information on the valid or invalid ticket is transferred to the transaction database in the Ticket Engine. Analysis tools can now collect information in order to create statistics, settlements, reports, etc.
...