ITKIT
Identity and government services · 01 / 20
OneID
National digital identity and trust
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
One identity. Every service.
1
People repeat in-person identity checks for every service.
2
Each ministry runs its own login and password store.
3
Paper signatures slow approvals and cannot be verified remotely.
Queues · Paper copies · Stamps · One identity
ITKIT · OneID · Prototype screens, synthetic data
The problem
Our answer
Prove it once. Sign anywhere. Share less.
Prove who you are once, sign with legal effect, and share only what a service needs. OneID is the authentication and trust layer; the civil registry stays authoritative for who a person is.
How it works · 1 of 6
Checked against the civil registry. No copy kept.
With OneID, you prove it once, from your phone, against the registry’s own evidence.
ITKIT · OneID · Prototype screens, synthetic data
How it works
How it works · 2 of 6
No passwords. Nothing to phish.
A passkey replaces every password, and it only works on the real site.
ITKIT · OneID · Prototype screens, synthetic data
How it works
How it works · 3 of 6
Share only what is needed.
Services see only what you approve. Your national number stays private.
ITKIT · OneID · Prototype screens, synthetic data
How it works
How it works · 4 of 6
Signatures with legal effect.
Sign applications with legal effect. Keys stay in the national HSM.
ITKIT · OneID · Prototype screens, synthetic data
How it works
How it works · 5 of 6
When evidence disagrees, a person decides.
The system never guesses. A named adjudicator decides, and the citizen can ask for an independent review.
ITKIT · OneID · Prototype screens, synthetic data
How it works
How it works · 6 of 6
No one left behind.
No smartphone? Service centres enrol you in person, with the same strong checks.
ITKIT · OneID · Prototype screens, synthetic data
How it works
What it includes
22 screens and workflows in the prototype
Verify yourself: card scan and liveness
Citizens during remote activation
Create your passkey
Citizens finishing activation, or adding a device
Sign-in request and consent
Citizens signing in to a government or approved private service
Sign a document
Citizens and business owners signing applications
Share a credential by QR
Citizens proving something in person, for example age at a cinema
Activity, consent and data rights
Citizens reviewing how their identity was used
Adjudication case
Identity adjudicators
Assisted enrollment
Proofing agents and trusted referees at citizen service centres
ITKIT · OneID · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in OneID |
|---|---|
| NIST SP 800-63A-4 | Remote identity proofing: resolution, validation and verification |
| NIST SP 800-63A-4 §3.11 and ISO/IEC 30107-3:2023 | Presentation attack detection, injection attacks and forged media |
| NIST SP 800-63B-4 | Phishing-resistant authentication |
| NIST SP 800-63C-4 | Pairwise identifiers, data minimisation and runtime consent |
| OpenID Connect Core 1.0 (ISO/IEC 26131:2024) | Federated sign-in for relying parties |
| W3C Verifiable Credentials Data Model v2.0 and Bitstring Status List v1.0 (Recommendations, May 2025) | Credential issuer, validity and revocation status |
| RFC 5280 and RFC 6960 | Certificate revocation, CRL and OCSP |
| World Bank ID4D Principles on Identification (2021 update) | Inclusion and grievance redress |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · OneID · Prototype screens, synthetic data
Built to standards
Connects to
What OneID works with
OneRegistry (identity evidence)
OneService (single sign-on)
OneHealth (patient login)
Bank and enterprise relying parties
ITKIT · OneID · Prototype screens, synthetic data
Connects to
Safeguards
What OneID will never do
Not a population registry.
Not passport production.
No biometric surveillance.
No resale of identity data.
ITKIT · OneID · Prototype screens, synthetic data
Safeguards
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
OneID at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
Durations are typical ranges, fixed per contract
ITKIT · OneID · Prototype screens, synthetic data
Delivery
Next step
Ask ITKIT for a OneID pilot plan with synthetic data.
OneID by ITKIT. Ask us for a pilot plan with synthetic data.
1 · Demo
A guided session on the OneID prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you