CA DMV is currently using OpenCred for the following use cases today (with CA DMV also acting as a Relying Party):

1. Disability Placard Enrollment
   • Individual goes to CA DMV website to start the enrollment process.
   • The current process of using a physical form, or filling out an online form, is replaced by an easier auto-fill process when using the CA DMV App.
   • A new option, with the individual’s consent, uses the CA DMV App to upload the digital driver’s license and automatically fill out the enrollment form for a Disability Placard.
   • The helps individuals with physical accessibility needs that create challenges when filling out paper forms and eliminates errors when filling out form fields or uploading pictures.
2. Secure Login for DMV Services
   • Individual goes to CA DMV website to start a process that requires them to log into their CA DMV website account.
   • The current process requires them to use a username and password, which can be forgotten or stolen.
   • A new option, with the individual’s consent, uses the CA DMV App to log in using a much more secure mechanism than using a username and password.
   • This helps provide more security around the individual’s account and how they manage their CA DMV related activities.

The mDL provides a secure, verifiable identification for residents. This can be used as a tool by state agencies and commercial entities (banks, financial institutions, others), that issue licenses, permits, and benefits to (1) reduce fraudulent claims, (2) improve the online user experience, and (3) reduce costs associated with verifying legacy forms of identification.

A few examples: State benefits, Access to secure locations, eKYC use case for various Banking and financial institutions applications processes (opening an account, loan, etc.) which can be enabled in a few days using the open source OpenCred software.

1. API Integration: Organizations can integrate OpenCred into their systems through an Application Programming Interface (API). This allows them to automatically request and verify credentials as part of their digital processes. They can also check the status of these requests to see if the credentials have been presented correctly.
2. OIDC Login Flow: Alternatively, organizations can use a more straightforward method similar to logging in with social media accounts. This “Login” flow uses OpenID Connect (OIDC), a secure sign-in protocol, to request and receive credential presentations. It’s user-friendly and doesn’t require the holder to share unnecessary personal information.

In both cases, OpenCred ensures that the exchange of credentials is secure, verifiable, and respects the privacy of the individuals sharing their information.

• Docker-based deployment to popular on-premise, hybrid, and cloud environments such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure. 
• Horizontal scaling to support tens of millions of verifications per day. 
• Customizable colors, brand images, and page text. 
• Support for the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers. 
• Support for workflows as an OpenID Connect Identity Provider or using an HTTP API for non-OpenID systems. 
• Open digital wallet selection support through the Credential Handler API (CHAPI) 
• Presentation protocol support for Verifiable Credential Exchanges API (VC API) and OpenID for Verifiable Presentation (OID4VP). 
• Native/local verifier support that is not dependent on any external services. 
• Remote/external verifier support using either the Verifiable Credential Verification API (VC API) or Microsoft Entra 
• Storage of historical DID Documents to enable local auditing