RPO

The problem

A revenue protection officer has about two minutes with a passenger. In that time a fixed penalty notice has to be identified, issued, paid or recorded, and made auditable — on a moving train, often with no signal, and in a way that stands up if it is later challenged.

Paper does the first part and fails the rest. Systems designed for an office fail the first part. RPO was built for the gangway.

The product

RPO equips Revenue Protection Officers to issue Fixed Payment Notices (FPNs) in under two minutes — on a train, at a station, offline or online. Fully automated, fully synchronised, fully auditable.

Each additional FPN issued per day is recovered annual revenue. Already live and proven with Irish Rail.

Architecture

platform

Android · offline-first

devices

NFC + contactless · Bluetooth printers

sync

offline issuance · server on reconnect

admin

real-time RPO monitoring dashboard

integration

open API · 3rd-party connectors

payment

integrated gateway · on-device

Frequently asked questions

What is a fixed penalty notice?

The notice a revenue protection officer issues to a passenger travelling without a valid ticket, recording the fare due and the penalty, and serving as the auditable record of the inspection.

How long does issuing one take?

Under two minutes in production, which is the figure measured with Irish Rail.

Does it work with no signal?

Yes — issuance is offline-first on the device and synchronises to the server on reconnect, because a train in a tunnel is the normal case, not the exception.

What hardware does it run on?

Android devices, with NFC and contactless payment and Bluetooth printers.

Can passengers pay on the spot?

Yes, through an integrated payment gateway on the device.

Is it in production anywhere?

Yes, live and proven with Irish Rail.