Scan the passport chip
Scan the passport chip to get the information from the passport.
When to use this pattern
This pattern is for services where members of the public scan their passport.
You may find that your particular use case or user needs means you need to adjust the guidance based on your research.
You should make it clear which passport the user needs to scan, because a person may have several.
How it works
Users can only scan the chip in their passport, if they are using a device with a near field communication (NFC) chip. Phones that can make contactless payments have an NFC chip.
For external users, this normally means they need to be using a mobile phone app.
To scan the chip, you need the information in the machine-readable zone (MRZ) of the passport. Users should take or upload a photo.
Scanning the chip in a passport has the highest level of trust. It also collects the largest amount of data, the chip contains:
- the data in the machine-readable zone (MRZ)
- at least one or more facial biometric encoding
- zero or more finger biometric encodings
However not all passports have chips, so you’ll need to ask the user whether their passport has a chip or not. You might already know from the context that the passport must have a chip, for example it’s a UK passport from after 2006. To determine whether the passport has a chip, ask the user if the chip symbol is on the front cover (it may be a different colour).
Some users with some passports may not be able to tell that their passport has a chip. You should provide an alternative method, such as manual entry.
You should explain why they need to scan their passport, and provide some helpful tips:
- close your passport
- remove any phone cases
- remove any passport cases
- put the top of your phone halfway down your passport
- your phone is touching your passport
Provide visual guidance to assist users who find it hard to read English.
You should investigate if there is a limit to the number of times that the chip can be scanned. This should be clearly communicated to the user at the beginning of the process.
You should provide pictures, sounds and vibrations as feedback to users while scanning the chip.
If the chip scan fails then show the helpful tips again, before asking the user to try again.
Consider what users can do if they hit a barrier:
- if they don’t have a compatible phone, can they go to a physical location to get their passport scanned, or should they try another method
- if the scanning of the chip completely fails, what do they do next
Once a chip is successfully scanned, there are background checks on the data. You should consider what happens if these fail.
Date of birth century
The date of birth stored on the chip only has 2 digits for the year. You may need to ask users for the century to confirm whether the year is 1920 or 2020, if it’s not obvious from context.
Names
The names stored on the chip may be truncated. The names are identical to those in the machine-readable zone. They may appear different to in the visual display of the passport, it may be:
- truncated to 39 characters
- transliterated into the 26 character Latin alphabet
- diacritics are removed
You should present the important information back to the user. You should not allow them to change the answers. You should provide guidance on what to do if the information is incorrect.
Accessibility
Consider that users may need more than one method for capturing the information. What do they do if they hit a barrier?
Some users with some passports may not be able to tell that their passport has a chip. You should provide an alternative method, such as manual entry.
Research
Scanning the chip is used by:
Help us improve this pattern
This pattern needs improving. We need evidence about:
- scanning passport chips in internal systems
- asking for information from other identity documents, such as national identity cards, UK residence card, biometric residence card, biometric residence permit
- whether to label nationality as country of nationality when showing users the information scanned in the chip
To contribute, add your thoughts and research findings to our GitHub discussion, or follow our contribute guidance.