Open Payments&Ticketing Reference Architecture (OPRA)

The Open Payments & Ticketing Reference Architecture (OPRA) project aims to take away one of the biggest hurdles in the open Mobility ECO System: Payments and Ticketing.

We need to align with private and public partners to overcome this in the field of Payments and Ticketing. We need to focus on the outputs of MaaS: urban development & planning, environmental impact and User-oriented solutions.

How can we pay for MaaS?

In many areas, public transit options may only cover a small portion of riders’ desired journeys, with further alternative means needed (walking, taxi, bike share) to reach their final destination. These gaps force customers to pre-plan journeys extensively, with the constant risk of disruption and delay. This is the space that Mobility as a Service (MaaS) must fill. The current payment and ticket solutions are the following (as pointed out in our whitepaper):

  • Closed-loop prepayment
  • Open-loop pay-As-You-Go
  • Subscription
  • Post-payment

The ideal MaaS solution will offer everyone, irrespective of socioeconomic status, the fastest, cheapest, most fluid and most information-rich experience for almost every conceivable journey. To reach this ideal, we need to solve

  • Interoperability
  • Disputes
  • Privacy & Security


The scope will include the payments ecosystem germane to the public and private mobility ecosystem. It will address all aspects of payments, from cash, bank transfers, card purchases, international and national schemes, and crypto. It will review and discuss the interactions and specific needs of each identified methodology for payment and create a common lexicon that explains the interactions, pros/cons, periods of applicability, and usage within the MaaS ecosystem.

The scope will also include all aspects of ticketing and media with the MaaS ecosystem, including account-to-account interactions, and address the specific interactions outlined for the payment open reference architecture.

This output will derive a minimum interoperability model to facilitate discussion between parties. The outputs will include, but are not limited to:

  • A data lexicon and terminology
  • A definition and explanation of the various elements of payments and ticketing
  • A logical flow and construct for the payments and ticketing ecosystem
  • Harmonise data models
  • Create a reference architecture

Join this project

Related Projects

Mobility Knowledge Loop

Building Mobility Awareness

Building Interoperability