National Order Database (NOD)

📢 Notice: SFTP Service Shutdown

We would like to inform you that the SFTP solution we are hosting at Entur is planned to be replaced by a new REST API, which is integrated into the IOS application. For details on how to use the REST API, please contact the NOD Ticketing Team.

We plan to shut down the SFTP server during September 2025.

About this document

The purpose of this document is to provide an overview of the functionality that the National Order Database platform enables (hereafter called NOD). The document also provides a review of the general functionality of NOD. The document also serves as a general guide to relevant parts of Handbook V821.

About National Order Database

NOD was developed by Interoperabilitetstjenester A / S on behalf of the Norwegian Public Roads Administration, with the intention of simplifying electronic ticketing and interoperability between various public transport operators. Some of the benefits of NOD:

  • The security solution is on the server side. This means that "insecure" clients such as mobile phones or home PCs can be used as vending machines for collecting tickets.

  • The business logic is on the server side. This means that the business rules can be changed without the clients having to be updated.

  • Distribution is separated from the sales channel. This allows anyone in principle to sell tickets.

  • The solution is always online. This means that sold tickets are immediately available nationally.

  • The platform is modular. Operators can develop their own "plugins" with their own business rules, also for non-interoperable products.

NOD is an implementation of the technical specifications found in Handbook V821.22 for Online distribution of sold tickets. This implementation is a platform that can be used by PTOs as a "cloud-based" service in the "Software as a Service" category. NOD has two primary interfaces: one back system for PTOs and one internet interface for NOD Clients. NOD model