The code for every sign-in
Conductors
Each conductor number is tied to a vehicle. Sign in on the Conductor app and the phone is on that vehicle straight away — no approval step on this test server. Signing in on another phone moves the vehicle to it.
| Phone number | Vehicle | Route | Owner | Phone |
|---|
Passengers
Each already holds a card with money on it. Sign in on the Passenger app and the card is there.
| Phone number | Card | Balance |
|---|
Owners, operator, agent, staff
| Role | Phone number | What they can do |
|---|
Free passenger cards
Each one is already sold and holds UGX 2,000. In the Passenger app choose Link a card and scan it here or type its number; it is yours from then on and drops off this page. Top it up in the app and confirm the payment in the dev console.
Where to go
Dashboards →Owners, operators and staff. Fares, vehicles, card batches, payouts, audit. Android apps →Install Conductor, Passenger and Agent on a phone. Test cards to scan →QR codes for every outcome: paid, too little, blocked, unsold, never issued. Dev console →Every message the system sent, and the mock Mobile Money queue. USSD simulator →What a feature phone sees on the short code.Back office
A first run through
- Install the three apps on a phone from the downloads page.
- Open the Conductor app, sign in as +256700000020. The phone then waits to be approved.
- Open the dashboards as the owner +256700000010, go to Vehicles → UBE 001A → Conductor phones, and approve it.
- Open the Passenger app on any unused test number and link one of the free cards above (or buy one in the Agent app as +256700000030).
- Top the card up in the app and confirm the payment in the dev console.
- Scan the card with the Conductor app. Try it again within five minutes: it asks whether someone else is travelling on the same card.
- Turn on airplane mode and keep scanning — everything still works and syncs when the network returns.
- Watch the fares appear on the dashboard within about ten seconds of the phone syncing.
While testing these shortcuts are on: one known sign-in code for everyone, a known staff second factor,
and no real SMS. All three are switched off by settings that refuse to start outside a test environment.