2026-10-20: Revenue inspection outcomes reporting – Littlepay

You can now get a complete record of fare inspection activity on your network: who inspected, when, where, and with what outcome. This helps you monitor inspection compliance and performance without adding any extra work for your inspectors.

This update covers the following related changes:

Revenue Inspection iOS app: every card inspection is now recorded automatically.
Littlepay data feed: a new Revenue inspection outcomes file.
Webhooks: a new inspection_activity event type on the inspection.received webhook.

About Littlepay Revenue Inspection

Littlepay Revenue Inspection helps you reduce fare evasion on your contactless network. Inspectors use the Littlepay Revenue Inspection app on an iPhone to scan a passenger’s contactless card or device. The app checks the card against Littlepay’s tap records and shows the inspector whether there is a valid tap.

If you are interested in using Revenue Inspection on your network, contact your Littlepay account manager.

Revenue Inspection iOS app: every card inspection is now recorded automatically

From iOS Revenue Inspection app version 1.3.0, the app records an inspection activity for every card check, whatever the result. This activity is what populates the new data feed file and webhook event described below.

This image shows a card validation result in the Revenue Inspection iOS app. Each validation is now recorded automatically as an inspection activity.

For more on using the Revenue Inspection app, see:

New data feed file: Revenue inspection outcomes

Inspection activity from the app is delivered in a new Revenue inspection outcomes file in your Littlepay data feed, alongside your other data feed files. Full field details are in Revenue inspection outcomes on Littlepay Docs.

The file contains one record for each inspection attempt, including:

Outcome: VALID_TAP, TAP_NOT_FOUND, BLOCKED or CARD_NOT_FOUND
When and where: inspection time in UTC and in the device’s local time, plus the device’s latitude and longitude if location was captured
Inspector and device: inspector login email, device ID, app version and inspection session ID
Card details, when Littlepay finds the card: vault ID, customer ID, card scheme, masked PAN, BIN, issuer country and form factor

You can use this data to:

Measure inspection activity by inspector, device, time of day or location.
Track fare compliance by comparing VALID_TAP outcomes with TAP_NOT_FOUND and BLOCKED outcomes.
Identify cards that were inspected but have never tapped on your network.

New webhook event type: `inspection_activity`

The same inspection activity data is also sent in real time through the inspection.received webhook. The inspection.received webhook now has three data_object types, identified by the type field:

backoffice_inspection_report — existing, unchanged
inspection_outcome — existing, unchanged
inspection_activity — new; published for every inspection recorded by the iOS Revenue Inspection app

The inspection_activity event carries the same information as the data feed file, including the outcome, inspection times, inspector, device, app version, session ID, location (if captured) and card details (when Littlepay finds the card). For an example event, see inspection.received webhook specification and its inspection_activity example.

Impacts and timeline of changes

These are new, additive changes. There are no breaking changes to your existing data feed files or to the existing inspection.received event types.

For operators using the Littlepay Revenue Inspection iOS app

Revenue Inspection iOS app: Littlepay will first share version 1.3.0 as a TestFlight build so you can preview it and report any issues. Littlepay will then make it available in Apple Business Manager (ABM) so you can deploy it to your inspection devices.
Data feed: the Revenue inspection outcomes file will contain a record for every inspection made with the app.
Webhooks: if you subscribe to inspection.received, you will start receiving the new inspection_activity event type, one for each inspection. If you do not subscribe to inspection.received, you remain unaffected.

For operators not using the Littlepay Revenue Inspection iOS app

Data feed: the Revenue inspection outcomes file will still appear in your data feed, but it will be empty. You do not need to take any action.
Revenue Inspection iOS app and webhooks: no changes to your operations.

Timeline

The data feed file and the inspection_activity webhook event are available now. They only include inspections made with iOS Revenue Inspection app version 1.3.0 or later, so you will start receiving this data once version 1.3.0 is deployed to your inspection devices through Apple Business Manager.

More information

For more information on this change, contact Littlepay support.