Fare Payments-as-a-Service

A Better Way of Running Ticketing Systems for Public Transport

Fare Payments-as-a-Service

In the past transport agencies designed and built their own bespoke ticketing systems. However, these systems were expensive to build, maintain and update – often taking years to go live, with significant build risk.

That’s why agencies and operators of all sizes are now opting for a Fare Payments-as-a-Service approach. By running their fare payments solution using a (SaaS multi-agency) shared platform brings significant benefits, including; significantly reduced costs, quick deployments and continuous updates.

Introducing Fare Payments-as-a-Service

A better way of delivering fare payment services to agencies and passengers.

The Problem: Design and Build Ticketing Systems

Transit agencies and transport operators have traditional purchased their own bespoke Automated Fare Collection (AFC) systems. These solutions are expensive to build, maintain and update and come with problems which are no longer necessary:

Expensive

Agencies and operators are overpaying unnecessarily for fare collection by buying bespoke technology.

Slow to Deploy

Fare collection deployments using bespoke technology can take years to go live.

No Updates

Bespoke system do not benefit from regular updates (unless a significant amount of money is spent).

Closed

Bespoke systems tend to be closed in nature and difficult to connect with new systems or enable MaaS (without expense).

The Solution: Fare Payments-as-a-Service

Fare Payments-as-a-Service offers a better way of providing fare payment services. Agencies can sign up to a multi-tenant fare payments platform which is already live. This enables agencies to deliver the latest innovations to riders extremely quickly and then grow capabilities as they get regularly released onto the platform, helping keep up with the pace of technology change and doing so far more cost-effectively than building and maintaining a bespoke fare collection system.

Cost-effective

Reduced capital, maintenance and update costs.

Speedy

Once functionality is added to the platform it’s super quick to deploy.

Regular Updates

New functionality is delivered regularly to everyone.

Open Integrations

An open API centric architecture means the platform can link to existing (or new) systems.

Future-Proof Roadmap

A roadmap of new features and capabilities removes the complexity of running ticketing services and allows agencies to keep up with the pace of technology change.

Mobility as a Service (MaaS) Enabled

Enabling MaaS for public transit is a key requirement as agencies look to attract more people to leave their cars at home.

Digital-First

Enabling concession, cash digitization and dematerialization with a digital-first approach, saving money and increasing convenience.

Account-Based Fare Payments

Fare Payments as a Service enables the delivery of tickets but also facilitate the latest account-based ticketing experiences, meaning riders no longer need to buy a ticket or understand fares to travel.