Share Code Drivers Licence

[Asdrubal Dagreat]

Youcan only use this service if you have a Northern Ireland driving licence. If you have a licence from the Driver & Vehicle Licensing Agency (DVLA) in Great Britain go to: View or share your driving licence information - gov.uk

When the DMV collects personal information from you, state law (Civil Code section 1798.17) requires the DMV to notify you about the principal purpose(s) for which that information is to be used and any known or foreseeable disclosures which may be made of the information collected where the disclosure of such information to a governmental entity is either necessary for it to perform its duties or is required by law. For example, the DMV provides the notice on your Driver License/Identification (DL/ID) Card Application.

Vehicle Code Sections 1810 and 1810.2 allow government and commercial requesters who have been issued a requester code by the department to obtain DMV public record information for a governmental or legitimate business use without notifying you.

DMV uses a credit/debit card processing company to process credit/debit card transactions for services, and does not retain, share, store or use personal information for any other purpose except pursuant to a search warrant, subpoena, court order, or investigation of a crime. For making payments using our site, you must provide your name as printed on your credit/debit card, as well as your card type, card number, expiry date, security code, and zip code. DMV uses industry standard safeguards to protect the financial information we collect.

The DMV chatbot and live chat services use third-party vendors to provide machine translation. Machine translation is provided for purposes of information and convenience only. The DMV is unable to guarantee the accuracy of any translation provided by the third-party vendors and is therefore not liable for any inaccurate information or changes in the formatting of the content resulting from the use of the translation service.

The content currently in English is the official and accurate source for the program information and services DMV provides. Any discrepancies or differences created in the translation are not binding and have no legal effect for compliance or enforcement purposes. If any questions arise related to the information contained in the translated content, please refer to the English version.

The web pages currently in English on the DMV website are the official and accurate source for the program information and services the DMV provides. Any discrepancies or differences created in the translation are not binding and have no legal effect for compliance or enforcement purposes. If any questions arise related to the information contained in the translated website, please refer to the English version.

How does an mDL prevent fraud?

An mDL allows you to share data with the relying party (business, agency, or checkpoint) you choose to do business with. All the security and privacy checks happen automatically through digital signatures and certificate verification. Verifying the authenticity of a physical card, on the other hand, is dependent on the knowledge of the clerk or verifier, who must understand the security features on a physical card. Card security features vary from state to state and continually change.

Verifying the authenticity of an mDL is not dependent on the knowledge or training of the clerk. The Reader app does the work. The certificates used in an mDL transfer are signed by the State of Utah Driver License Division and give cryptographic proof that the data is valid. In turn, fake and altered IDs are rejected and cannot be authenticated.

How do I get an mDL?

With the program having transitioned to production, you can perform a self-setup and ID verification. Instructions are available here. The GET Mobile ID application will require you to scan your physical driver license, confirm your phone number, and take a live selfie inside the app. Please watch our social media for information about additional methods, including the ability to obtain your mDL during your visit to a DLD office.

What is the future of mDL?

The mDL is an optional extension of our physical credential. Just as we have worked for the last 3 years to get this project off the ground, each state will do something similar. That is just the first part of building an interoperable ecosystem. Then we have the relying parties who will have their own timeline of adoption. This timeline will be driven by the public and their adoption and desire to use an mDL. You can ask your favorite local businesses to use one of the many mDL Reader solutions on the market. The FAA states that there are 2.9 million domestic travelers daily. This would position TSA to be the largest relying party since they likely are one of the largest verifiers of our physical credentials already. This, by itself, could speed up the ecosystem and adoption rate of the mDL by states and citizens.

The second part of this answer is online or unattended verification. While the standards for this type of identity verification are still being written, the use cases expand exponentially. One example of this is opening a bank account online. While this is possible now, a bank gathers large amounts of data from you, asks for the upload of digital copies of documents, and runs several checks on a person to try to avoid fraudulent activity while using information from a multitude of 3rd parties. Digital verification of an mDL would significantly reduce a person from fraudulently being able to open or access an account. In short, the physical credential is not going away. The mDL is an optional extension of your hard card, just like putting your credit card on your phone. The future of mDL will open some avenues of use that we have not ever considered.

How does the app work?

The app, written by GET Group North America, can be downloaded from public app stores onto your mobile device. At the DLD office, someone will verify your identity and the system provisions your mDL directly into that app. At home, you may run a self-registration process.

How do I provision my mDL?

The at-home remote provisioning goes through the following steps. The license holder will: (1) download the app from the app store and then (2) confirm your mobile number and email and then (3) scan the 2D barcode on the back of the license and then (4) take a selfie and do a liveness detection. If the selfie matches the photo previously taken at a Driver License office and if the data on the back of the license matches the valid data in the Driver License database, then the license will be provisioned onto the phone.

The mDL data has been signed by Utah DLD when provisioned to your device. That digital signature makes it an official document that you control. The system uses the private keys on your device to encrypt each data element and ensure that only you can use it and share data. No other entity can access or read the mDL data without your consent.

A relying party (i.e., a business, restaurant, bank, etc.) will have a verifier app that contains a public key from all trusted issuers (such as Utah DLD.) The verifier receives encrypted data from you and authenticates that data with the correct public key. This ensures that the mDL data is authoritative (comes from the DLD), has not been altered, and was issued to you. If all the data elements you shared match, the credential is verified. If there has been any tampering or changes to the data, it will not be verified. The relying party can then approve your transaction.

You also have access to the transaction log of places you have shared your mDL data. This is also currently stored encrypted on the device and is never shared with any other entity, including any government entity.

Will the app track my location?

No. There are no location or tracking services associated with the mDL. On some devices, location service chips are used for Bluetooth and NFC communication, which is why you may have been promoted to consent to sharing location with the app itself (not any other entity.)

Will the app contain other government records?

No. Not only are no other government records stored in the app, but the app also does not link to or share data with any other government agency.

But could it contain other government records?

The DLD does not want and will not want to commingle any other data (fishing licenses, vaccine records, etc.) with the driver license database. So while the developer technically could do that, the scope for the app is so narrow to only include the mobile driver license data. And remember, adding your driver license to your phone is optional.

If the state government were to come up with a single digital platform for a person to manage all of their government documents, who would approve that decision?

Something like a digital government wallet would require significant debate, decision-making, and funding by the 104-member Utah Legislature. This mobile driver license project is not and will not be the platform for a digital government wallet.

Is the mobile license replacing the physical driver license?

This is not meant to replace the physical driver license. The mDL is available as an option for those who want it. Keep in mind that one of the common requests DLD receives related to the driver license is when can there be a secure mobile version of the license.

Who built the software?

The state contracted with GET North America to produce the app. GET does not have access to individual driver licenses, or directly to the Driver License Database. GET North America may also provide you with support for the application. The application privacy policy is posted here.

3a8082e126