Jump to:
- User registration
- Login
- User session
- Card scan
- Card details
- Tap details
- Revenue inspection outcome
- Sandbox testing
User registration
How do I register an inspector to use the inspection app?
Inspectors are added through the Control Portal under Settings by a Control Portal administrator.
Instructional video: Create a new inspector user via Control Portal
What happens after an inspector is registered?
The inspector receives an email containing a password reset link. They must reset their password before logging into the app.
Login
How do I set up two-factor authentication (2FA)?
To set up two-factor authentication, follow the steps shown in this video:
Log in for the first time and set up 2FA (using Apple Password native tool)
Troubleshoot login errors
The following are some common login errors, and actions to resolve them.
Error: “Login failed: User/email not configured properly or used with multiple participants.”
The inspector account is linked to more than one participant or merchant.
Each inspector must belong to one participant only.
Error: “Failed to unlock token: [error]”
A device error occurred while initialising Apple Tap to Pay.
If you encounter this error, report it via the app Settings → Report Feedback.
Error: “Sorry we encountered an error logging in.”
An Auth0 sign-in error occurred.
If you encounter this error, report it via the app Settings → Report Feedback.
User session
How long does a session last?
An Auth0 session last one hour. Afterwards, the user will need to re-authenticate using Face ID.
When will Face ID be required again?
Face ID is required every hour (session refresh).
When is Auth0 login required again?
After one week of inactivity, the user must re-authenticate with the authenticator passcode.
Do users need to log in again when switching apps?
No, users are not required to log in to the iOS Revenue Inspection app after switching between apps.
Card scan
How do I inspect a card?
Tap Validate to start, then follow the instructions on the app.
For a demo, see Scan a card for a successful outcome.
How long does Apple Tap to Pay take to prepare to scan a card?
When Apple Tap to Pay is launched for the first time from the app, it may take up to 90 seconds to initialise before a card can be scanned. After the initial setup, subsequent uses are typically much faster.
A similar initialisation delay may occur if the app is reinstalled.
Troubleshoot card scan errors
Error: “Contactless Card Not Found”
The card has not been used on your transit network.
Error: “Error reading card, please try again.”
Apple Tap to Pay encountered a read error.
If you encounter this error, report it via the app Settings → Report Feedback.
Card details
Card details displayed in the app (numbered + descriptions)
| # | Field | Description |
|---|---|---|
| 1 | Last 4 Digits of Card | Identifies the scanned card while masking sensitive card data. |
| 2 | Expiry Date | The month/year the card expires. |
| 3 | Last Tap Time | The most recent tap recorded on the network. |
| 4 | Card Status | Indicates whether the card has a valid tap, is blocked, or has no tap found. |
| 5 | Deny List Status | Shows whether the card is blocked due to insufficient funds or issuer decline. |
What do the card statuses mean?
| # | Status | Meaning |
|---|---|---|
| 1 | Valid Tap | The card was tapped within the last 24 hours. |
| 2 | Blocked | The card is on the deny list; travel not permitted. |
| 3 | Tap Not Found | No taps logged on the transit network recently. |
What does the deny list status mean?
The grey section shows messages such as:
“Card added to the deny list on [Date/Time]”
This means the card was blocked due to insufficient funds or issuer decline.
Travel is restricted until the balance is cleared.
Tap details
Tap details displayed in the app (numbered + descriptions)
| # | Field | Description |
|---|---|---|
| 1 | Tap Date/Time (Local) | The exact timestamp of each tap (latest first). |
| 2 | Travel Mode | Indicates transport mode: bus, rail, parking, etc. |
| 3 | Tap Status | Shows if the device technically accepted or rejected the tap. |
| 4 | Transaction Type (TAP / TAP ON / TAP OFF) | Identifies if the user entered, exited, or simply tapped. |
| 5 | Station ID | Internal identifier of the station. |
| 6 | Station Title | Public-facing name of the station. |
| 7 | Device ID | Identifier of the device that recorded the tap. |
| 8 | Tap Outcome | Shows whether the gate or device allowed or denied travel. |
How far back can taps be viewed in the app?
The app displays card taps that occurred within the last 24 hours from the current date and time.
Report inspection outcome
What does “Report an Outcome” do?
Report an Outcome sends inspection results to the Back Office for compliance and operational reporting.
Fields included when reporting an outcome (numbered + descriptions)
| # | Field | Description |
|---|---|---|
| 1 | Card Details | Last four digits of the scanned card. |
| 2 | Inspection Time | Timestamp when the outcome is submitted. |
| 3 | Vehicle ID | The vehicle associated with the last tap (if available). |
| 4 | Outcome | Valid, invalid, or inconclusive classification of the inspection. |
| 4.1 | Outcome: Valid | The card has valid travel rights or a valid tap. |
| 4.2 | Outcome: Invalid | The card has no valid tap, is blocked, or has no travel rights. |
| 4.3 | Outcome: Inconclusive | The card could not be read or verified (device issues, unreadable card, etc.). |
| 5 | Action | Indicates whether a Fine was issued or None. |
| 6 | Notes | Additional comments added by the inspector. |
Where can I see previously reported outcomes?
You can see previously reported outcomes under the History tab.
Why can’t I find a previous outcome?
The inspection outcome history is not retained under the following scenarios:
- The app was reinstalled.
- A different inspector logged in.
Troubleshoot outcome reporting
Error: “The outcome couldn’t be sent, please try again.”
There was an issue submitting the report.
If you encounter this error, report it via the app Settings → Report Feedback.
Sandbox testing
How do I install the Revenue Inspection app via TestFlight?
You need an invitation to download and install the Littlepay Revenue Inspection app.
Before you begin
Check that the following are set up:
- Your device is running iOS 14.0 or later.
- You device has TestFlight installed. You can download TestFlight from the App Store.
Once an invitation is sent, you will receive an email as follows:
- On your device, open the email invitation and tap View in TestFlight.
-
This action launches the Littlepay Revenue Inspection Dev app on TestFlight:
-
- On Revenue Inspection Dev app, tap Accept, then Install.
-
This action takes you through the Revenue Inspection Dev app onboarding:
-
Installation complete
You can now test the Revenue Inspection app on your device.
How do I test scanning a card via Apple Tap to Pay using the Apple Sandbox environment?
You need to have an Apple Sandbox test account.
To get a Sandbox test account, do the following:
- Request for the Littlepay Apple Tap to Pay developer team to add or create your email address as a Sandbox test account. You cannot use an existing Apple Account for sandbox testing.
- On your iOS device, sign in using the sandbox test account set up by Littlepay.
- This step may take a few minutes while the device is configured for the sandbox environment.
- Once signed in with the sandbox test account, launch the Revenue Inspection app through TestFlight. Then, log in using your Revenue Inspection app credentials provided by Littlepay.
How do I scan a test card and view test tap results in the sandbox environment?
You need an EMV test card for the device to scan, and for an associated tap to already exist on the Littlepay Control Portal QA environment. If you do not have access to the Littlepay Control Portal QA environment, contact Littlepay support.
An EMV test card can be one that is provided by Apple, or any EMV-supported test card; that is, test cards used for EMV Level 3 certification.
Set up a tap in the Control Portal QA environment
In order for the Revenue Inspection app to return a tap history from an EMV test card, a tap must exist on the Control Portal.
To set up a tap, do the following:
-
On the Control Portal QA, click Tap Simulator on the left pane:
The Tap Simulator displays a form whose fields reflect the Device Create a Transaction request payload.
- Fill the required fields, as well as optional fields if you wish to, to simulate a tap.
- Make sure that the card PAN and Card Expiry match those on the EMV test card that you wish to test against the Revenue Inspection app. Otherwise, a tap history will not appear on the app.
-
Click either of the following to submit the tap details:
- Tap to simulate a single-fare tap
- Tap On and then Tap Off to simulate a variable-fare journey
The resulting tap history will reflect as a transaction payload response under Results.
Scan the EMV test card
Using the Revenue Inspection Dev app on your iOS device, scan the EMV test card.
The app will return the tap history for the card. Note the app only returns the tap history for the last 24 hours.
Comments
Please sign in to leave a comment.