State of Mobile Driver’s Licenses in the U.S.

Chapters

• 0:25 — Introduction to Trinsic

• 2:02 — mDLs in the U.S.

• 13:20 — mDL Standards

• 19:13 — mDL Adoption

• 25:32 — mDLs with Trinsic

• 29:39 — AAMVA Annual International Conference (AIC)

• 32:43 — Demo Videos

• 36:57 — Predictions

• 38:00 — Relying Party Guidance

• 39:35 — Conclusion

• 41:10 — Q&A

Full Transcript

Transcript lightly edited for clarity.

Zack Jones: First of all, welcome everybody. Thanks for joining the session today on the state of mobile driver's licenses in the U.S. There's a lot going on here. We have a lot to cover. So as a quick introduction, I'm Zack Jones. I lead the product partnerships at Trinsic. For a little bit more context on what Trinsic does, Trinsic's digital ID aggregation platform. So we integrate with mobile driver's licenses, eIDs in Europe, bank IDs, reusable ID networks, and government digital ID wallets all around the world. So my job is essentially to figure out who are the identity providers and the wallet providers and partner with them to kind of surface their verification option through Trinsic's network. And then Trinsic goes out and sells to, you know, companies who need to verify their users and are looking to do that with a digital ID rather than, you know, a physical document upload every time, right?

Zack Jones: So this is a way to kind of augment your typical onboarding or verification process by allowing a user to present their mobile driver's license instead of taking a picture of their physical driver's license. So that's a quick intro to what we do and my role here. So kind of leading the product partnerships function, I've, you know, working, I work with all the ID providers that are currently integrated in our network, and then we're tracking another 200-plus digital ID networks around the world. So a big part of my job is just staying informed on kind of what's happening in the digital ID landscape globally, what things are changing, what new standards are launching, wallet applications are launching, and then, you know, helping our customers stay aware and informed and then keeping our product kind of ahead of the curve of what's coming up. So, since Trinsic is based in the U.S.

Zack Jones: and mobile driver's licenses are kind of, you know, one of the largest potential, like, digital ID movements happening here in a while, there is no national digital ID in the United States in the same way that there is in many other countries. So the mobile driver's license is a very exciting development within the digital ID space. While this is a fairly new kind of phenomenon or movement, right now 76% of Americans live in a state where a mobile driver's license is either already active or in development, right? So that means that either they could go download an application and get a mobile driver's license today, or, you know, there is some stage of progress, whether that means their state is, you know, months away from launching or a year or two away from launching a mobile driver's license application. So again, while this is fairly new, there's already a lot of momentum and progress happening in the U.S. And currently about 41% of Americans live in states where mDLs are active.

Zack Jones: So a lot of large population states like California, New York already have mobile driver's licenses live and available for end users. A little bit of the history of the mobile driver's license launches per year. This is a graphic that we created last year and we continuously update, so showing kind of what mobile IDs or mobile driver's licenses have launched over time. LA Wallet in Louisiana was the first to launch in 2018, with Arizona following in 2020. And then momentum has picked up since. So seven new states, or six states and Puerto Rico, launched in 2024. Our prediction, which we made at the end of last year, 12 months ago, was that we would see even more launches in 2025. So far we have Arkansas, Alaska, Montana, and North Dakota. We believe there will still be a few more to go live within the next few months to close out 2025, which could get us to close to 30 states. It's worth noting that there are a few mobile driver's license programs that are temporarily suspended and will be relaunching soon, we believe, in various states like Florida and Oklahoma.

Zack Jones: Shown a different way, the implementation status here of, like, what's going on. Again, there's about 41% have an active mobile driver's license. Another section are in development. There's another distinction where the mobile driver's license has been legislated or it's considered like a legal form of ID and it's in process at some point, but maybe not in development yet, and others are paused. So this is a map that AAMVA puts out related to the mobile driver's license implementations in the U.S. So part of this presentation are resources that Trinsic has accumulated, and another part is going to be, like, sharing helpful resources with you all from other industry bodies. So AAMVA is one of those industry bodies who is a huge, you know, supporter and proponent of the mobile driver's license ecosystem. AAMVA maintains the Digital Trust Service. So they have essentially given a darker color, a darker purple color, to the states that have entered their public keys in the Digital Trust Service.

Zack Jones: The lighter purple color means that the state currently has an interoperable mobile driver's license implementation. We'll talk a little bit more about what that means in a few slides. And then the dotted purple means that there's an interoperable implementation. in progress. And then you can see there's a few other colors about kind of other things in progress or started or being attempted, right? So this is AAMVA's map of the different jurisdictions and kind of who is live, who's interoperable, who has a public key in the Digital Trust Service. Right now, there are, I think, 17 different mobile driver's license wallets live across the U.S. So when you look at Apple, Google, and Samsung wallets being, you know, three of those, many states have state-specific wallets as well. So there's still a lot of kind of a lot of fragmentation. There's about, I think, 21 states live and 17 different wallets. We'll show this in a few other ways on a later slide as well, visually. Awesome. Great. Yeah, let me just highlight this question as well.

Zack Jones: Another recommendation here, mDL Connection is another amazing resource, highly recommended. So folks can kind of take that down as a resource as well to check out. There's a few good sites out there that are kind of tracking the adoption and implementation status of mDLs around the U.S. Awesome. Thanks for that comment. So the mobile driver's license, like the initial use case, because when you think about having a mobile driver's license credential in your wallet, the first question that most people ask is, what can I do with it, right? Like, who accepts the mobile ID? What can I do with it? And the big use case that kind of like launched a lot of states and is like kind of follows on when they announce a mobile ID, they're oftentimes announcing that an airport in that state is going to accept the digital ID as a form of identification in order to board a plane, right? So the TSA now maintains If you visit the link below, and we'll send out these resources after.

Zack Jones: The TSA maintains a list of participating states that have eligible digital IDs where you can use them, you know, to board a plane. And there's other maps that will show you which airports around the country, you know, support a digital ID to board a plane. If you've traveled recently, you've probably seen signs if you've been in certain airports that say that a digital ID is accepted. And, yeah, it's one of the key use cases. So a couple other graphics here just to kind of showcase, like, who supports what and kind of what's going on in the ecosystem here. This is a breakdown of which states support which wallets. So as you can see, certain states support a single wallet, right? Like Utah or Virginia or Alaska or Louisiana, or New York, for example, just have a single application where anybody who wants a mobile driver's license or a mobile ID would download that application.

Zack Jones: Other states like Arizona, Colorado, Georgia, Maryland, Iowa have a lot of optionality where a user could hold their mobile ID in Google Wallet, Apple Wallet, Samsung Wallet, or a state-specific mobile ID application. So in our latest calculation, there are 11 states that support Apple Wallet, and then Puerto Rico makes it kind of 12 jurisdictions. Google has nine states where you can get a mobile driver's license credential in your Google Wallet. But Google also has something a little bit different, which is called ID Pass, which is not a mobile driver's license, but it is also a mobile ID that is acceptable at TSA. And ID Pass is a derived passport credential. Apple has publicly stated that they will be doing this as well, though it's not live yet. But the Google ID Pass is theoretically available to anybody with a passport. So it's not based on if you live in a state like I do that doesn't have a mobile driver's license yet, you could get an ID Pass and have kind of a standards-compliant and accepted digital ID for boarding a plane.

Zack Jones: Without having to wait for your state's legislators to kind of legislate the mDL and pick a vendor and implement it. Samsung Wallet also supports seven states currently. All of these numbers are constantly going up. So North Dakota launched very recently, I think last week or maybe the week prior. So we are always having to update these graphics and update the counts and who supports what. IDEMIA is a large vendor in this space as well, and their approach has been to create state-specific apps. So you see in that column Arizona Mobile ID, Arkansas Mobile ID, you know, New York Mobile ID. So they're powered by the same vendor, kind of similar technology stack, but they're not, you know, it's not one IDEMIA wallet that supports seven states. It's kind of their technology that creates a state-specific instance of that application. And then there's six standalone wallet apps out there. So Alaska, California, MyColorado, LA Wallet, Utah, and the Virginia Mobile ID, all built by different vendors and all standalone applications with different levels of services in there.

Zack Jones: So another way to visualize this, this is a graphic directly from our e-book, which on the state of mobile driver's license adoption. We'll send that out as a follow-up to this. So, you know, you're welcome to take screenshots. We're going to post the recording, but also you'll get some more of this content kind of delivered to you via email afterwards. Awesome. Yeah. One question related to the ID pass. Does the source passport need to be an e-passport, or can a conventional passport be used to derive the Google ID? I believe that the passport does need to be like an e-passport with NFC enabled. So only that kind of secure transferring of the attributes and kind of hardware-based verification is, I think, considered like high enough assurance in order to create the derived ID pass credential. That's my current understanding. It's a good question. Awesome. So when people talk about mobile driver's licenses, they often talk about standards, and the main standard at play here is the ISO 18013 standard.

Zack Jones: So this is kind of a, you know, a standard that was created originally about six years ago and kind of has been updated, and other pieces have been added, annexes have been added, and other parts have been added to support new use cases and interaction models. The standard has a lot of You know, momentum and support here in the U.S., but there's also global momentum around this, and there are other countries that have standards-compliant mobile driver's license. Mobile driver's licenses is already issued, like Australia, Austria, Japan, and then others are going to be following on soon. Within the standard, the ISO 18013-5 was kind of the first, you know, publication here, which is meant to support in-person use cases or proximity use cases. So when you're presenting your mobile ID, your mobile driver's license at the airport to TSA, that is kind of, you know, think of that as like an in-person or proximity-based use case where you can present your mobile ID, you know, in person at a vendor. You need some specific hardware in order to read and, like, securely transfer that data.

Zack Jones: And so that is kind of, a lot of the wallets support this, or basically all of the wallets support this in-person or proximity use case. And this is what's been live in the airports for many years now and is increasingly now being supported for other types of use cases in person, like age verification for restricted goods at a stadium, for example. So you may have an automated, like, beer kiosk or something where you can present your mobile ID to prove that you're of age to be able to purchase an alcoholic beverage, and then you can check out, you know, with a credit card without having an attendant there necessarily to check your ID. Other, obviously other use cases in there. I think what's exciting right now, and this was in development for a long time, was the ISO 18013-7, or Part 7 standard. So this supports remote verification and online use cases. So this was published a year ago, still not implemented in most wallets. Well, the next slide will kind of show some of the differences and who's implemented what based on our understanding.

Zack Jones: And there are a few different interaction profiles supported within this part of the standard: REST API, OpenID for Verifiable Presentation, and the Digital Credentials API. So initially, kind of when the 18013-7 standard was published, people were very excited about remote verification, and there was a common kind of sentiment that, well, you're just going to support 18013-7, you'll be able to remotely verify any of the mDL wallets, right? Like that is kind of, you know, one school of thought, and I think over time that will prove to be true. But currently, things are still quite fragmented because different wallets have implemented different things or not implemented this yet. And because there are multiple different kind of interaction profiles or presentation mechanisms, if you support, you may support one of them, but the wallet may not support that one as well. So then you need to go support multiple things within the standard, which becomes more complicated. So we'll talk a little bit more about that in the next slide.

Zack Jones: So this is a graphic that we made based on our best understanding. Some of these things, again, these things are constantly changing. So even if this is made within the last month, things may be slightly different. But here is kind of what types of, you know, presentation mechanisms or standards are supported within the wallets. Basically everybody supports the 18013-5 standard in general, but within— The remote verification standard of DASH 7. Again, there's these three interaction profiles, and most of these are not supported. So Alaska launched recently and, like, notably supports the REST API version. And then, you know, Google and Apple have kind of made announcements and have APIs related to what's called the Digital Credentials API, which is, you know, very exciting and interesting. And then, but a number of wallets support kind of like a proprietary verification mechanism.

Zack Jones: So for a while, there's been the ability to have, like, a verify with Apple Wallet, verify with Google Wallet, verify with Samsung Wallet, and kind of remotely verify that way in more of a proprietary manner that, you know, is maybe there's some standards underneath the hood a little bit, but it's not that you've integrated one standard and you get to now verify all of those wallets necessarily. So similarly with kind of some of the IDEMIA wallets, California DMV and LA Wallet, there are ways to remotely verify it in kind of a proprietary manner at this point. Again, all things we believe will kind of will eventually converge to the standards. It's just a matter of time, right? So, yeah, the state of the ecosystem is still a bit fragmented. Okay. So mDL adoption is obviously a hot topic. Like, you know, how many people have a mobile driver's license? Like, how worthwhile is this to look at or implement, right? This is a very hard question to answer because the data is not readily available publicly, right?

Zack Jones: So certain states or jurisdictions will make an announcement, or it will be kind of mentioned offhandedly in an article. So there's every once in a while there'll be an article about Ohio, and it will just say there's been 400,000 mDLs issued in Ohio or something, right? California is the only state that we found that has kind of a public dashboard of the mobile driver's licensees that have been issued. Our kind of, this is another one of, this is more of our graphic, very similar to the AAMVA graphic about kind of who is live, although we're just looking at where there's an active mDL and not necessarily making distinctions between if they're in the digital trust service or if the implementation is interoperable yet or anything like that. So from kind of a high-level point of view, you know, over 40% of states have an active mDL, which is a pretty high adoption rate. And within those, a lot of them are fairly populous states like, you know, New York, Maryland, Virginia, California, Arizona, Colorado, all fairly populous states.

Zack Jones: Numerically, and this again is based on kind of the best data that we have available, which is not perfect or not great all the time. This is kind of our chart of like mDL adoption data. So a few disclaimers here. One, we believe this is definitely a low-end estimate because, again, a lot of this data isn't publicly available, and the source here might be, you know, could be over a year old at this point. Some states will report adoption data, again, like kind of privately to AAMVA or something like that, and in which case those numbers may be slightly more updated. Again, California is the only one that has like a public dashboard that we found that shows the number of unique people with an mDL. And then some states just don't have anything reported yet, right, because they're new or they've launched recently. One other disclaimer about this is that A couple, like Louisiana and Colorado have the highest kind of issuance rate of a mobile ID. Some percentage of those that are counted here are not necessarily compliant with the ISO 18013 standard.

Zack Jones: So because on the timeline graphic, you saw Louisiana launched before anybody else. They launched before the standard was formalized. They have, you know, a digital driving license. Some people will make a distinction between an mDL, a mobile driver's license, kind of has the connotation that it is a standards-compliant, you know, ID, versus like a digital driving license, which more so means it's a digital representation of a driving license. It might not follow the standard, and it might be kind of used as more of like a flash pass where you can kind of present your mobile ID to law enforcement or present it at a convenience store, but it might not, again, follow the same standards. I think what's also interesting about this is the states, Louisiana and Colorado, with high adoption, the applications They support more functionality than simply holding a digital driver's license in a wallet. You can do things like hold your hunting and fishing license, or apply for a new license, or kind of renew your car registration.

Zack Jones: So there are other benefits to having the application that have driven significant user adoption, right? So again, with the question of once you get a mobile driver's license, what do you do with it? I mean, this is kind of flipping that question a little bit on its head and says, hey, we have a state services application called My Colorado or LA Wallet, and one thing you can do is get a mobile ID in there. The other thing you can do is all this other stuff to interact with your local government in a more seamless and efficient way. And that's actually a model that's more, that we see more frequently in international markets, where when a mobile ID launches or a digital ID launches, the first use case is kind of state services-based. You're using it to log into a government portal, maybe pay your taxes, apply for things online, apply for a benefit or something like that. And then slowly, the mobile ID or the digital ID in the international market opens up to, like, regulated... use cases like banking and telcos and things like that.

Zack Jones: And then over time, they go into general private sector usage. So again, because the U.S. is a bunch of states that kind of have their own authority to, you know, release these programs and roll out applications that make sense for their jurisdiction, there isn't kind of a unified approach there yet. And this is kind of the state of the ecosystem. Let me just take a quick pause, maybe a few questions. We'll see if anybody... Yeah, was the 400K mDLs in Ohio a real update or hyperbole? That's a real update. That's corroborated by a GovTech article, I believe. In the e-book, we have all the sources linked and cited to all the most recent numbers, so that's a real one. And then we also see New York is over 275,000 currently. That's awesome. I don't remember which number we have there, but we will note that and update it. Thank you. Okay, so a couple more, a little bit more information kind of about, like, what Trinsic does in this space and how, kind of how, what our approach is and how we view it.

Zack Jones: So Trinsic is currently integrated with some of the mDL wallets and have a bunch more in progress. We focus specifically on the remote verification use cases, so kind of the in-person verification is a little bit out of our purview. We generally kind of our product surfaces in just in online scenarios, right? So that's the thing that we're interested in. When we often talk to companies that are considering, like, do we build this capability or do we in-house or do we buy it? So we have a lot of, like, considerations that we'll often talk people through. So, like we've shown earlier, there's a lot of variance kind of in the standards and the way that things are implemented currently and, like, the stages of implementation that currently exist within the market. So there isn't just, like, one thing you can adopt to inherit, you know, all the mDL wallets, which is maybe a little bit of a misconception. We definitely hear from a lot of people that think that that's the case, and unfortunately it isn't right now.

Zack Jones: Again, it may get there over time, but right now there's still a lot of fragmentation and variance in the market. Kind of key management's another thing to point out is that, again, even if you do, you know, support some wallets directly, you need to be pretty careful with kind of how you're verifying them, managing keys from all the different states to understand if what you're getting back is a trustworthy and signed output from the right authority. Different wallets output different data, so you have to, you know, normalize that across your data model and figure out who gives what and, you know, at what level of assurance it comes back. Generally, all the mobile driver's licenses are proofed at a high level, but then the point about additional validation or liveness or biometric matching often comes into play where, you know, could somebody have their brother's phone and prove their ID with that phone in order to onboard to, like, an age-restricted site or something like that, right?

Zack Jones: And then you need to make sure, you know, what measures are in place to make sure the person presenting that ID is the right person and that it isn't, you know, somebody else or a bad actor or something like that. Generally, a lot of those things are accounted for at the wallet level, but again, they vary in how they're implemented and, you know, some wallets may have... Really strong answers and processes for this, and others you may need to add, like an additional verification in order to meet, you know, the assurance level that you need. There's also a lot of non-technical considerations here, like you need to essentially work with the wallet providers and the identity providers in order to figure out, like, kind of what you're allowed to do with the data, essentially. So just, you know, it is not like a totally open and decentralized ecosystem where you just support a standard and suddenly there is data flowing into your systems.

Zack Jones: With kind of all of these, you need to be in contact at some level with, you know, authorities and wallet providers to get permissions and kind of get approved to be a verifier. And yeah, so anyways, a lot of considerations here. So, awesome. So yeah, core value prop of Trinsic here is that you can configure mobile driver's license acceptance, you know, in our dashboard alongside a bunch of other digital IDs around the world. So while adoption of mDLs is still growing in the U.S., there are a number of markets where digital IDs and mobile IDs are, like, almost ubiquitous already, and you can get a lot of those benefits in one place. So kind of to wrap up, we wanted to provide a quick overview of some of the learnings from the AAMVA Annual International Conference, which we went to a couple weeks ago in Phoenix. So AAMVA is the American Association of Motor Vehicle Administrators. So essentially all of the DMV operators in, like, kind of the U.S., the territory U.S., you know, continental U.S., the territories, and Canada, right?

Zack Jones: So there's 69 jurisdictions that are all represented here, and There's a lot that kind of. goes on related to DMV-related business, but there's also a lot of talk about mobile ID and mobile driver's licenses because it is kind of the next big thing in, you know, identity and driving license issuance. So a few of our reflections on the conference. So there is definitely a lot of industry momentum here. We got to see presentations from a lot of the major, all the major wallet providers like Google, Apple, Samsung, IDEMIA, Thales, et cetera. We're kind of showcasing new capabilities, talking about partnerships, mobile ID verification partnerships that were going on, and different use cases that they're kind of actively pursuing or working on. And we saw a bunch of demos, both like live demos, recorded demos, showcasing in-person use cases and online remote verification use cases. So I hope the dogs barking in the background, I hope people can't hear that.

Zack Jones: So within the presentations from the wallet providers, there were a number of kind of like logos shown of like large global brands that are basically planning to or announcing support for mobile driver's licenses. So places like Amazon, Turo, Chime, Uber were all kind of mentioned on slides from the wallet providers as being You know, early adopters in this space. So one of our kind of key drivers here that we think will happen is once users start to see the option to verify with a mobile ID, they will be a lot more inclined to go obtain a mobile ID because they know it'll be accepted to be used at Amazon or to be used at Uber. Okay. Awesome. All right, let me just take a quick pause, see if there's any questions. Okay. Okay. So Trinsic did showed a couple of demos at the, what was called like the Relying Party Showcase as part of the AAMVA conference. So we did a demo with Indeed showing how you could verify a job seeker with a mobile driver's license. This is the flow of the California DMV wallet. It's super fast. If you blink, you might miss it, right?

Zack Jones: The whole demo is only 15 seconds long. It's not sped up. That is actually like how quick the verification is. So essentially what you saw was that the user scans, you know, the user starts the journey on their desktop. They scan a QR code, which sends them into the California DMV wallet application, at which point they then consent, they kind of authenticate with the app and consent to sharing their data. So there's a Face ID, there's a consent screen. The user accepts that they're sharing that and their identity is verified. So that was one demo that we presented. We also were able to demo what the flow looks like with the digital credentials API using the Google Wallet, so I can show that here as well. So in this situation, the user is in the browser, and they get this, like, kind of pop-up modal asking them to, one, do they trust the site that they're on, that they're going to share data, and two, here's the consent screen. Are you sure you want to share the following fields with this website? And then the user clicks agree.

Zack Jones: They see kind of the privacy policies of the different provider, like the different players there, and then they, again, complete the verification flow. It's Google Digital Credentials API. So I just wanted to show these to give you an idea of the, like, the user experience at play here. The thing that's really appealing to all the relying parties and businesses that we talk to is that this is a very, like, fast and frictionless experience for a user. They don't need to find, you know, a physical document or a physical credential. They just need to click a couple buttons, authenticate on their wallet device or application on their device, and then complete a verification with a highly trusted and secure kind of sharing of credential attributes. Just one more demo to show the user experience here of Samsung Wallet. So the user selects that. They go open the Samsung Wallet app and Again, a lot of this will be familiar, but while these are all similar in nature, there's a lot of, like, quirks and nuances, right? So this is kind of the information request.

Zack Jones: Here's the party that's requesting your data. Here are the fields that they're requesting. The user then needs to kind of do either a biometric verification or enter their PIN in order to authenticate, and then they complete the share. Awesome. So a couple final reflections here to kind of wrap up this, the AAMVA International. Conference brings together a lot of people from around the world. So while it's kind of North America-focused, there's people coming from different countries everywhere. And it seems like there's a lot of kind of ecosystem alignment towards moving towards the standards, enabling relying party use cases in the private sector and the public sector, and that people are really expecting adoption to accelerate in the next, you know, 12 months or so. So adoption is still growing and use cases are just kind of rolling out right now, but we kind of think this will be a bit of a snowball effect where things are going to pick up momentum really quickly once a few of them get live.

Zack Jones: We originally made a prediction, I think when we first published the mDL e-book like a year, year and a half ago, that we could see 100 million mobile driver's licenses by the end of 2026. That was kind of our aggressive or optimistic prediction. I think we're tracking a little bit below that right now, but we still think that there's, you know, there's a chance we get to a significant growth rate, right? So again, because remote verification is still kind of like, we believe remote verification is the killer use case, but it's still a little bit early. Like Trinsic is trying to make it easier to adopt mobile driver's licenses without having to, you know, spend a ton of time building new integrations and maintaining connections to all these different wallets. We believe that once some of these key use cases get off the ground, we could see adoption really start to pick up quickly. So when we talk to relying parties or businesses that are looking to accept mobile driver's licenses, I think, you know, first it's important to recognize that the fragmentation is still there.

Zack Jones: So there is a need to kind of integrate individually with a number of different wallets and state applications. So it's, you know, fairly time-consuming and resource-intensive at the moment. One way to think about this, rather than thinking about like a national mDL strategy, is to test mDL acceptance in specific states that are early adopters and have reasonably high adoption rates. So thinking about California, New York, Arizona, Colorado, Louisiana, and other states where there are a significant number of users that already have a mobile driver's license and are, you know, somewhat familiar with the flow could be a good way to kind of start integrating this and at least conceptually understand like how it works and how it fits into existing onboarding flows. The other guidance is like a lot of the relying parties and businesses that we talk to are interested in accepting digital IDs generally, right? So mobile driver's licenses are just one form of digital ID.

Zack Jones: As adoption grows in the U.S., there are maybe other similar forms of digital ID that you could start accepting in the European geographies or in Asia or something like that. Awesome. So yeah, just to wrap up. There's a lot of great momentum happening in the space. Relying parties are interested. They're starting to integrate. They're starting to accept mobile driver's licenses as a way to streamline onboarding and reduce risk. I think there's, you know, we're going to see a lot of, like, pilots and activities and things happening in the next, like, six months or so. And then after that, I think we'll get kind of more and more production deployments that are kind of publicly notable, which will raise the awareness of, you know, that mobile driver's license is a thing and consumers want it. Because if you talk to somebody who lives in a state with a mobile ID and they're not really deep in the identity space already, they might not even know that it exists.

Zack Jones: Or maybe they've seen something about it and they don't really know what they can do with it, so they haven't bothered to download it or get set up or get onboarded yet, right? So we do believe this is kind of, you know, going to be a lot more mainstream over the next year or two. The wallet providers are kind of well positioned to deliver great user experience. And then once we see more relying party use cases come online, it'll be more and more clear to the consumer why they should prioritize, you know, getting their mobile ID or mobile driver's license. Awesome. So, yeah, Trinsic helps you verify users 10 times faster using digital ID they already have. This is a way to reduce fraud, cost less money in your onboarding flow. Always happy to talk more about that. And if there are, you know, we'll have time for questions now, and we'll also just make available some of the resources that we have, other content that we do. So afterwards you'll get an updated version of the mobile driver's license report.

Zack Jones: So a lot of the data you'll see in there with, like, sources cited and links to other information. We also talk more about global mDL adoption within that report as well. We have a broader digital ID adoption report, which talks about Kind of digital ID more broadly, government eID, you know, wallets, bank IDs, reusable IDs, not just the mobile driver's license. And then we also have our Opportunity Zones report, which kind of highlights key geographies around the world where we recommend people get started accepting digital IDs. And lastly, we have the Future of Identity podcast, which we've recently done some new episodes that we're going to be recording, that we've just recorded and will be put out soon. You'll hear our CEO Riley talk with people, identity, you know, identity people who have built ecosystems and wallets and kind of what they've learned. from, you know, launching digital IDs. So that is all for the planned content here. I will get into the questions and, yeah, thanks everybody for joining and listening in. Okay. Yeah, so this question was from a little while ago.

Zack Jones: How does this work across devices? Can a user hold the same mDL across two or more phones? I believe it depends on the geography or it depends on the state. In general, though, a user can hold the same mDL across two or more devices because you can have an mDL on, like, your Apple Watch, for example, or on your smartwatch. So if you're, you know, you might need to pay for something using Apple Pay on your watch, you could also present mobile ID on your watch. So in general, this is supported. I think maybe some states or platforms don't support it. In the California adoption dashboard, you'll see that there's, you know, over 2 million mDLs, like, issued and 1.2 or something million unique users, right? So they actually make the distinction between mDLs issued. This also makes it harder to count the adoption data because, you know, we're reporting the unique users with mDLs, but there's actually way more mDLs that have been issued because some of them are across multiple devices. Good question.

Zack Jones: Have you seen implementations incorporate mDL with agentic AI, where the agent utilizes mDL to automate ID presentation to access services? This is kind of the proof of concept that we did with Indeed and presented. I think I would say it's pretty early stages in terms of what, you know, it's not something that's live and in production necessarily, but this is kind of the demo that we built where, you know, you could have, you know, a job seeker has an agent kind of operating on their behalf, trying to find opportunities, but that job seeker is verified, you know, using their mDL to be not a bot, right? They're a real person behind the device. Awesome. Okay, what area of state government is overseeing the state's implementation? Generally, the Department of Motor Vehicles, the DMV is, again, this is kind of a quirk of the U.S. It's not similar or analogous to overseas where the department that licenses people to drive becomes like the de facto identity issuer.

Zack Jones: So it is a little bit odd, and I think it does at some level hinder adoption because it's so fragmented across every state and every DMV. And, you know, as staffing changes and legislation changes and budget changes, certain projects get, you know, postponed or delayed because it's kind of up to the state government and, like, the specific department within there. There's other offices of, like, technology and innovation that are oftentimes involved as well. And yeah. Awesome. Okay, appreciate it. Glad it was insightful. Would there ever be a use case of one wallet holding mDLs for several people or identities? That's a good question. I don't know. I mean, there are definitely use cases where one wallet could hold other credentials for other people. So at the AAMVA event showcase, one of the things that we saw across some of the European wallets that are being developed is people being able to hold things like car registration credentials alongside a driver's license and an ID document and like an insurance document or something like that.

Zack Jones: So there's definitely, definitely wallets support multiple different types of credentials. I generally think that like it's tied to the individual person, but one, you know, multiple people could have the same insurance card, right? Like multiple people in your family could have the same insurance card and potentially not as much for an mDL because you need to be of age in order to obtain one. But you could presume that eventually your wallet could hold something like certificates for your kids or something like that, and that's feasible. But yeah. Oh yeah, similar question here. Have you seen anybody printing birth certificates in a wallet? I believe this is happening somewhere. I don't—this is not quite my area of expertise. Again, I think it is a use case that like people are looking at and is being explored, but I don't know 100%. Good question though. Our 100 million uptake estimate was based on—we were projecting like actual registrations. So again, optimistic, kind of an aggressive estimate for sure.

Zack Jones: Currently, like right now, if everybody who lived in a state with an mDL got one today, just randomly, like we would hit that number. So it's already available to over 100 million people in the U.S., but, like, the actual adoption is a fraction of that right now. So, awesome. Great. I think that is all the questions here. So if people have other questions, please, you know, share them in the chat. We have a couple more minutes, but if not, we're happy to wrap up. I think, yeah, one of the things, yeah, we need an update session like this every quarter, no pressure. Yeah, we are trying to update our resources frequently. I mean, we update a lot of the graphics kind of on an ongoing basis. And if you follow me on LinkedIn, I tend to post about, like, when a new state launches or when we have, like, a new graphic about kind of the space here. And then the mDL ebook that we have available on the website, we just updated over the last few weeks. So that is, I think we originally published it a year ago. We updated it in April.

Zack Jones: We updated it again, you know, at the end of September, early October. So, yeah, try to keep things as up to date as possible, but follow on LinkedIn for updates. And then, you know, if you have questions, you can always ping me. So, awesome. Great. Well, thank you, everybody. Really appreciate everybody who joined here. We will send out a follow-up, you know, with more information and resources. And, yeah, talk to you soon. Thanks all.