How GOV.UK Verify works
GOV.UK Verify works with different organisations, known as identity providers (or certified companies), to prove users’ identities.
The identity providers have met government and industry standards to provide identity assurance services as part of GOV.UK Verify. They work with GOV.UK Verify to ensure users’ data is handled securely, helping your service to meet its data protection obligations.
The identity providers that currently work with GOV.UK Verify are Barclays, Digidentity, Experian, Post Office and SecureIdentity.
How users are verified during the signup journey
When signing in to your service for the first time, users will be asked to set up an account with one of the identity providers.
They’ll ask the user to provide evidence and answer questions about themselves. This will be checked against different records, such as their driving licence, passport, mobile phone contract or credit reference checks.
Proving users’ identities this way means the privacy of their data is protected to a high standard, because:
- their data is not stored in one place
- your service does not know which identity provider they’ve chosen
The user can use their account to:
- sign back in to your service at any time
- sign in to other government services that use GOV.UK Verify
What data GOV.UK Verify sends your service
After a user has proved their identity, your service will be sent some information about them, such as their:
- date of birth
- unique ID - this is created by the identity provider
You can use this information to match their identity to a record you have for them in an existing database. This means you can link the user to data that you already hold on them.
When a user views their driving licence information, the Driver and Vehicle Licensing Agency (DVLA) will match their details to a record in their database of people with driving licences.
By doing this they can be sure the service shows the right driving licence details for that person.
If you do not have an existing database, you can use the information provided by the identity providers to create a new database for matching identities or auditing purposes.
Read the technical documentation to find out more about the data your service gets and how to match it to existing records.