One platform that sells and checks tickets, runs NFC cards and ride passes, takes mobile money and card payments, and gives operators and the government a live view of sales.
- Sector
- Government transportation, public transport
- Scope
- Three web panels, a field app on tap-to-pay POS devices and one backend API
- Stack
- Next.js, Flutter, NestJS, PostgreSQL, AWS
Anonymised case study. Government transportation.
Fares were collected in cash and tickets were paper, so revenue was hard to count, every party kept its own records, and a copied or reused ticket was easy. Passengers pay with many mobile money operators, and crews work on moving vehicles with unreliable connections and shared devices. The programme needed one system every party trusts: every fare paid for, every ticket verifiable, every sale visible.
- Users
- Administrators, transport companies, resellers and field agents
- Payments
- Mobile money, bank and card through one gateway
- Languages
- English and French across the API and notifications
- Delivery
- June to November 2026
From the sale to the live dashboard. Select a step to see the rule behind it.
6 steps, in order
step 1 of 6
Sell a fare
An agent sells a ticket for a whole route or between any two stops, one way or return, for one or several passengers. The price is always calculated on the server from the fare. The app never sends a price.
- Where
- Agent app or reseller panel
- Where
- Flutter agent app on tap-to-pay POS devices
- Rule
- Prices are set on the server
- Payment succeedsThe ticket, card or pass is created
- Payment fails or expiresNothing is issued, a held card is released
- First scanThe ticket becomes used
- Second scanRefused, a ticket cannot be reused
- Admin panelNext.jsPlatform administratorsManage companies and plans, routes and stops, bus and card categories, agents, passengers, app versions and branding, and watch platform-wide sales and payment health.
- Company panelNext.jsTransport company administratorsAdopt routes, set fares, register buses, build crews, manage agents, resellers and card stock, and follow tickets, payments and subscriptions.
- Reseller panelNext.jsCard resellersReceive card stock, sell cards and tickets, and track their own sales.
- Agent appFlutter, on tap-to-pay POS devicesDrivers, collectors and validatorsSell tickets, cards and ride passes, take payment, scan and verify tickets, tap cards to use rides, and see their own day's sales.
- Backend APINestJS, PostgreSQL, AWSAll of the aboveOne set of rules for pricing, payment, access and audit.
Every call is identified, checked and signed before the backend acts on it.
4 steps, in order
step 1 of 4
Sign in
A user signs in with Cognito and receives a token. Roles come through groups.
- Where
- Amazon Cognito
- Where
- Amazon Cognito
Payments that answer slowly or not at all
The payment stays pending and the app polls for the result. A repeated request with the same key returns the first answer.
Two agents selling the same card at once
The card is reserved for the pending payment and released if it fails or expires.
A way to issue tickets without paying
Found during development and closed. Every sale now goes through the payment flow.
One tap on a card using two rides
A two-minute guard, a per-tap id, and a short window to give a ride back.
Many roles, one codebase
Role and company checks applied the same way on every endpoint, with tests for each role.
Sales spread across three kinds of products
One combined agent dashboard and one date-range rule across tickets, cards and passes.
- Tickets that cannot be faked or reusedA unique code and QR code per ticket, scanned once and then refused.
- Payments through operators people already useMobile money, bank and card options through one gateway. The list of methods is served by the API, so one can be switched on or off without a new app release.
- NFC transport cardsCompanies create card batches, set prices by category and move stock to resellers. A card is held for the buyer while a payment is pending, so two people can never sell the same card.
- Ride passesA pass on a card for a route and stop pair, a number of rides and a date range. A second tap within two minutes is refused, and a mistaken ride can be given back within ten minutes.
- Fleet and route operationsRoutes with ordered stops, distances from Google Directions, fares per stop pair and bus category, and crews that pair a bus with a driver, a collector and a validator.
- Live dashboardsSeparate views for the platform, each company, each reseller and each agent, with the payment method and distance travelled for each ticket.
- Notifications and auditIn-app and push notifications for sales, payments, stock and account events, and an activity log of who did what and when.
- Platform controlsSubscription plans for companies, platform branding, public app settings and forced-update control for the mobile app.
Pay first, then issue
No unpaid tickets, cards or passes. Revenue equals sales.
Prices set on the server
The app cannot be edited to undercharge.
Idempotent payments
A double tap or a lost connection never charges twice or issues two tickets.
A locked-down backend
The application server accepts calls only from the gateway layer, never directly from the internet.
Strict role and company scoping
A company sees only its own routes, agents and sales. An agent sees only what they sold.
Everything traceable
Every sale links to a payment, an agent, a crew and a vehicle.
Records are never hard-deleted
History stays intact for audits and disputes.
English and French
Messages, labels and notifications in the user's language.
Digitising a public service?
We build platforms where every transaction is paid for, verifiable and visible, on foundations a public authority can trust.