Platform · Consent-Gated Identity
GovPass .
Let citizens verify who they are, approve exactly what a service may receive, and complete high-value actions without handing raw biometric data to the app they are using.
A government-grade answer, not a copy of the citizen’s identity
GovPass gives a relying service the scoped, consented verification result it needs — never a face image, never a biometric template, and never an invisible blanket permission.
Consent that is specific
Name the relying app, the requested verification and the outcome before the citizen approves the request.
Biometrics stay inside the trusted flow
A bank, telco or benefits app receives a signed verification response — not the citizen’s biometric sample or stored template.
Signing is a separate, visible act
Step up for a named agreement, document or high-value action, then return an auditable signed outcome to the service.
A clear consent and verification path
The interface is only one moment in the journey. The platform coordinates the identity, policy, evidence and service systems around it so the result remains trusted after the user leaves the screen.
01
Request
A bank, telco, benefits agency or public service asks for a stated identity check or signed action.
02
Consent
The citizen sees who is asking, what will be checked and what the relying service will receive.
03
Verify
The citizen authenticates inside the trusted GovPass journey using the assurance required for that request.
04
Respond or sign
The service receives a scoped verification token or the signed outcome — with an audit record for the programme.
The citizen sees the request before the platform acts
GovPass makes consent, verification and signing visible in the journey. The screens below illustrate the same governed pattern across public services and regulated relying parties.
Citizen consent
The relying app names the identity action before redirecting to GovPass.
Itemised request
The trusted journey lists the facts being checked before authentication.
Scoped response
The service receives verified claims and a time-limited token, not biometrics.
Step-up signing
A separate face-authentication moment protects an important signature.
Signed outcome
The citizen sees the completed agreement and the service receives proof.
Product screen · itemised verification request
Make the trusted path visible to every participant.
The strongest national platforms make a complicated operating model feel simple at the point of use. Behind that simple moment sit the rules, integrations, recovery paths and evidence required to make the outcome defensible.
- Digital government and citizen-service access
- Banking and credit onboarding with trusted identity confirmation
- Telco activation and SIM lifecycle journeys
- Benefits, grants and eligibility verification
- Named-document approval and digital signing
What GovPass brings to the programme
Adopt a platform that can support the operating model around it, rather than a beautiful front end that leaves policy, integration, assurance and support to separate projects.
Relying-app integration
Use a governed redirect and response pattern so services can request identity outcomes without embedding biometric capture themselves.
Scoped verification claims
Release the minimum approved confirmation for the purpose — for example identity verified, resident status or eligibility — under the programme’s policy.
High-assurance digital signing
Bind a named document, consent and biometric step-up to a signed record that the citizen and relying service can retain.
Identity lifecycle and audit
Apply assurance, recovery, suspension, revocation and audit controls across the citizen credential and every service interaction.
Designed for public trust
Governance is a product capability.
GovPass is not just an identity app. The programme governs which services may ask, which claims may be released, what assurance applies, when a citizen must consent and how every decision is evidenced.
Frequently asked questions
What does a relying service receive from GovPass?
Does every request require the same level of assurance?
Can GovPass support banks, telcos and benefits agencies?
Related platforms
Plan the operating model with the platform
Build trust into every identity and service interaction.
Talk to Axon about architecture, integration, assurance, service design and a phased national rollout.