Design how your service sends users to GOV.UK Verify
GOV.UK Verify will be part of your service’s user journey, so you need to consider where and how you will send users to that part of the journey
See all the steps involved in the GOV.UK Verify user journey for a:
Where to put GOV.UK Verify in your user journey
Your service should send users to GOV.UK Verify at the point you need to check their identity. For most services, this will be at the start of the journey, but some services may allow users to enter some information first, for example to confirm their eligibility.
Using GOV.UK Verify at the start of the service
Use GOV.UK Verify at the start of your service when:
- your service contains sensitive data that should only be visible to a verified user
- you want the user’s name, date of birth and address (entered during the verification process) to be passed to the service without the user needing to submit it a second time
- you want users to be able to save their progress and return later
- you want to filter out users who are unable to verify their identity with GOV.UK Verify so they can be directed to another way of using your service
Using GOV.UK Verify later in the service
Some services put GOV.UK Verify later in their user journey. This means users can complete as much of your service as possible before they need to verify their identity.
Use GOV.UK Verify later in the service when:
- you want to check users’ eligibility to use a service before checking their identity
- your service has other ways for users to verify their identity, such as face-to-face in a government office – they can complete parts of the service online before finishing the later stages somewhere else
How to send users to GOV.UK Verify from your service
Usually, your service should send your users to the GOV.UK Verify sign-in page. This page will tell users that they can use your service with either:
- GOV.UK Verify
- a digital identity from another European country
If your service lets users sign in another way
Use the multiple sign-in page pattern if users can sign in to your service using something other than GOV.UK Verify or a digital identity from another European country. For example, users can sign into some HM Revenue & Customs services with Government Gateway as well.
You can use the create an account pattern to show new users how to create accounts for the different ways they can access your service.
If a user cannot be verified
GOV.UK Verify will show any users who cannot be verified the other ways they can use your service, for example by phone or by post.