What we support today. What we're committing to. What's on the roadmap.
Established tolling vendors publish certifications that took years to obtain. Quantum Mobility is new — we don't have those yet. What we do have is an architecture designed to meet these standards, and explicit commitments about what we will formally certify against, and when.
The three statuses below are honest:
Supported — the architecture natively supports this today, demonstrable in a pilot environment.
Committed — written into our engineering roadmap; committed to achieve during first production deployment.
Planned — on the longer-term roadmap; will be addressed as we scale into relevant markets.
The standards that enable multi-operator interoperability, cross-border tolling, and cross-system coordination.
The international reference architecture for electronic fee collection systems. Our architectural model maps directly to this standard.
The European framework for cross-border tolling interoperability. Our coordination model is compatible with the EETS provider-to-authority structure.
The DSRC-based transaction interface standard. Integration at the capture-system boundary respects this interface on the field-system side.
The European standard for exchange of toll data between service providers and toll chargers. Aligns with our Nexus-to-operator data model.
Industry-standard transit data schemas. Relevant for future Quantum Metro™ transit-extension deployments.
How we handle transaction and settlement data, and the controls we commit to.
Data minimization, purpose limitation, and subject-access processes aligned with GDPR principles. Personal data from account-linked transactions processed under agreed operator / authority boundaries.
Deployment-scoped data residency commitments: data stays within the operating jurisdiction agreed in the engagement contract. No cross-border data flows without explicit authorization.
Security, availability, and confidentiality controls audit. On the engineering roadmap for first production deployment.
Information security management system certification. Planned following SOC 2 and first production deployment.
Relevant for US deployments involving account-linked transactions with California residents. Supported alongside GDPR under our data-handling framework.
These are properties of the architecture itself — not optional features or paid add-ons.
Every transaction retains a tamper-evident history from capture through settlement. Write-once, verifiable by authorities, finance, and audit functions.
Pricing, policy, validation, and enforcement decisions stay with participating authorities. Quantum Nexus™ does not assume ownership of these.
Settlement outputs are produced without Quantum Mobility taking custody of revenue flows. Participating authorities and operators retain financial control end-to-end.
Shared audit rules and lineage across operators and agencies. Auditors see the same transaction history regardless of which operator's system originated the event.
If you're running RFP evaluation or internal procurement review, we're happy to walk through any of these commitments in detail — and respond to specific compliance questionnaires.