![](https://help.apple.com/assets/6537FB06A074DBB5E802EA07/6537FB31280588A5490B6E1D/en_AU/52d714626638d3391623c853be0c593b.png)
IDs in Apple Wallet
On iPhone 8 or later using iOS 15.4 or later, and Apple Watch Series 4 or later using watchOS 8.4 or later, users can add their state ID or driver’s licence to Apple Wallet and tap their iPhone or Apple Watch to seamlessly and securely present it at participating locations.
Note: This feature is available only in participating US states.
IDs in Apple Wallet use security features built into the hardware and software of the user’s device to help protect their identity and help keep their personal information secure.
Adding a driver’s licence or state ID to Apple Wallet
On iPhone, users can simply tap the Add (+) button at the top of the screen in Apple Wallet to begin adding their licence or ID. If users have an Apple Watch paired at the time of set-up, they are prompted to also add their driver’s licence or ID to their Apple Wallet on Apple Watch.
Users are first asked to use their iPhone to scan the front and back of their physical driver’s licence or state ID card. The iPhone evaluates the quality and type of images to help ensure that the images provided are acceptable by the state issuing authority. These identity card images are encrypted to the state issuing authority’s key on the device and then sent to the state issuing authority.
Next, the user is asked to complete a series of facial and head movements. These movements are evaluated by the user’s device and by Apple to help reduce the risk of someone using a photograph, video or mask to try to add someone else’s ID to Apple Wallet. Results from the analysis of these movements are then sent to the state issuing authority, but not the video of the movements themselves.
To help ensure that the person adding the identity card to Apple Wallet is the same person the identity card belongs to, users are asked to take a selfie. Before the user’s photo is submitted to the state issuing authority, Apple servers and the user’s device compare the photo with the likeness of the person who performed the series of facial and head movements and help ensure that the photo being submitted is of a live person with the same likeness as that on the ID. Once the comparison is made, the photo is encrypted on device and then sent to the state issuing authority to be compared against their image on file for their ID.
Last, users are asked to perform a Face ID or Touch ID authentication. The user’s device ties this single matched Face ID or Touch ID biometric to the state ID to help ensure that only the person who added the ID to this iPhone can present it; other enrolled biometric information can’t be used to authorise presentation of the ID. This occurs strictly on device and isn’t sent to the state issuing authority.
The state issuing authority will receive information necessary to set up the digital ID. This includes images of the front and back of the user’s ID, data read from the PDF417 barcode as well as the selfie the user took as part of the ID verification process. The issuing state also receives a single-digit value, used to help prevent fraud, that’s based on the user’s device use patterns, settings data and information about their personal Apple ID. It’s then ultimately the issuing state’s decision to approve or deny the ID being added to Apple Wallet.
After the state issuing authority authorises adding the state ID or driver’s licence to Apple Wallet, a key pair is generated in the Secure Element by iPhone that anchors the user’s ID to that specific device. If adding to Apple Watch, a key pair is generated in the Secure Element by Apple Watch.
After the ID is on iPhone, the information reflected on the user’s ID in Apple Wallet is stored in an encrypted format protected by the Secure Enclave.
Using a driver’s licence or state ID in Apple Wallet with an identity reader
To use their ID in Apple Wallet, users need to authenticate with the Face ID or Touch ID device associated with the ID in Apple Wallet before iPhone presents the information to the identity reader.
To use their ID in Apple Wallet on Apple Watch, users need to unlock their iPhone using the associated Face ID appearance or Touch ID fingerprint each time they put on their Apple Watch. Then, they can use their ID in Apple Wallet without authenticating until they take their Apple Watch off again. This capability leverages foundational Auto Unlock capabilities detailed in System security for watchOS.
When users hold their iPhone or Apple Watch near the identity reader, or when sharing their ID within an app, users see a prompt on device displaying which specific information is being requested, by whom, and if they intend on storing it. After authorising with the associated Face ID or Touch ID, the requested identity information is released from the device.
Important: Users don’t need to unlock, show or hand over their device to present their ID.
If users have an accessibility feature like Voice Control, Switch Control or AssistiveTouch instead of having Face ID or Touch ID enabled, they can use their passcode to access and present their information.
Transmission of identity data to the identity reader follows the ISO/IEC 18013-5 standard, which provides for multiple security mechanisms available that are able to detect, deter and mitigate security risks. These consist of identity data integrity and antiforgery, device binding, informed consent and user data confidentiality over radio links.
Using a driver’s licence or state ID in Apple Wallet with iOS apps
Users can also share their driver’s licence or state ID information in Apple Wallet with iOS apps. When a user shares their ID with an app, Wallet will fetch and validate an encryption certificate that is registered with the app developer.
This certificate will be used to encrypt the information that the user has agreed to share. The information is encrypted by Wallet using HPKE and is never made available to Apple. Wallet periodically queries Apple servers to verify that the ID is still valid. If no check has been performed recently, one may occur when the user shares their ID with an app.