Transit ticketing — the deployment, not the slide.
Closed-loop fare collection, end to end. Cards in the rider’s pocket, SAMs in the validator, the depot sync at end of shift, and the issuer settling overnight. Same architecture for metro gates, BRT buses, ferries, light rail, and the kiosks that recharge them all.
What we ship
Card profiles
DESFire EV2 / EV3 personalisation profiles tuned to the operator’s fare logic. Brand artwork, photo IDs for staff cards, season-ticket files, stored-value files.
Validator firmware
Reader-side state machine that opens host SC to the SAM, runs the card auth flow, applies fare logic, signs the receipt, buffers for upload.
SAM personalisation line
Issuer-controlled key injection, audited, with split-knowledge custody. SAMs ship sealed and field-replaceable.
Depot edge
Local sync server for blacklist push, fare-table refresh, transaction-batch pull. Cellular failover where wired backhaul is intermittent.
Back-office connectors
Settlement file generation, audit reconciliation, blacklist authority API. Plays with whichever clearing house the operator already runs.
Operations tooling
Inspector handhelds, kiosk reload terminals, depot diagnostic tools. Same SAM trust chain everywhere.
Reference architecture
The complete architecture lives at /solutions/closed-loop-ticketing/. The Card↔Reader↔SAM trust chain is at /technologies/card-reader-sam-flow/. We do not duplicate that content here; this page is the buyer’s entry point.
Pilot a transit deployment.
Tell us your card volume, validator estate, target backhaul, and certification target. Pilots are usually 90 days; production rollouts 12-18 months from contract.