Rail & public transit · Fare Systems · Payments Security · Station Operations
Rotate fare-system keys across gates, validators, and mobile wallets
Can new keys become active across every channel without rejecting riders or extending old trust indefinitely?
Operational pain
Offline validators, concession devices, account-based systems, bank interfaces, and mobile credentials update at different rates.
Trigger
Payment-scheme change, key expiry, new fare medium, or suspected compromise.
QNSI contribution
Connect the decision to a controlled security path
Track key generations, device cohorts, activation windows, algorithms, issuers, and last-seen validation in QNSI.
Decision artifact
A fare-key cutover plan with overlap limits, station readiness, offline acceptance, fraud monitoring, and retirement proof.
What still requires validation
The authority tests payment compliance, passenger impact, revenue protection, offline behavior, settlement, and rollback.
External problem context
Primary sources
These sources establish the external requirement or risk context. They do not endorse HEOSSI or prove that QNSI completed this scenario.
Evidence boundary
What this page does—and does not—prove
This is a product evaluation pattern, not a customer case study, certification, legal opinion, regulator endorsement, or claim that a production deployment completed the described work.