How does an Open Transport API support the aims of MaaS?

Mobility-As-A-Service (“MaaS”) is the concept that users of transport or transit services migrate away from personally owned means of transportation and adopt an on-demand & pay-per-use service instead. This shift in behaviour (and potentially billing) means a user can then choose their preferred trip based on: cost, time, environmental factors, convenience or a combination of these.

But how does the creation of an Open API for transport account interoperability forward the aims of Mobility-As-A-Service?

  1. A clearer view of online transport accounts
    The aggregation of accounts via single interoperable standard API would give consumers the ability to quickly, simply and efficiently consolidate all their accounts into one place. E.g. to use one chosen online travel account for viewing information about all other modes (e.g. bus tickets, rail carnets, etc.).
    There is even the potential opportunity to allow new services into the market, in the same way that Money Dashboard ( uses Open Banking technology to give consumers a ‘unified view of their finances’ and is called an Account Information Service Provider (AISP).
  2. Removing barriers to MaaS adoption
    It is anticipated that by creating an easier way for consumers of travel services to access multiple accounts online, that they are more likely adopt it and use it. Therefore by removing the need to sign-up or remember new account details for every different MaaS provider, a key barrier to the use of multiple mobility service is removed.
  3. Reducing the cost of innovation
    Providing anything from scratch is usually quite hard, whereas copying or adopting what already exists is easier. IT Departments or their suppliers don’t have to spend time and money coming up with a new way to integrate with another travel account.
    Plus the benefit of an Open Standard is that, should it need changing or enhancing, this can be fed back into the standard too.

%d bloggers like this: