An Arkansas customer handing you a phone instead of a plastic card is now a normal moment at the counter, and it changes what “checking ID” actually means. A mobile driver’s license (mDL) carries the same identity data as the physical card, but that data only proves anything when a reader speaks to the credential and confirms the state issued it. Glancing at the screen tells you nothing you can trust, because a screen is the easiest thing in the world to fake.
That gap between looking and verifying is the whole story for Arkansas businesses that sell or grant access to age-restricted goods. Below, we walk through what a mobile driver’s license is, why a visual glance fails, how genuine mDL verification works, and what your staff and tooling need to handle now that both formats show up at the same door.
Current Information as of the latest Arkansas rollout
Arkansas driver’s licenses and state IDs became addable to Apple Wallet on May 27, 2026, building on the state’s existing Arkansas Mobile ID program. (Arkansas DFA)
Arkansas mobile IDs use the ISO 18013-5 standard: identity information stays encrypted on the device and is released only after the holder authorizes it with Face ID or Touch ID. (Arkansas DFA)
Because mobile IDs are not accepted everywhere yet, the state still tells residents to carry the physical license, so businesses will handle both formats for years to come. (Arkansas DFA)
Arkansas residents can now add their driver’s license or state ID to Apple Wallet, layered on top of the state’s existing Arkansas Mobile ID app. In plain terms this means that the same license that used to live in a physical wallet now also lives on a phone, and your customers are starting to present it that way.
An mDL is a state-issued digital version of a physical license, stored securely on the holder’s device and designed to be verified electronically rather than read by eye. It’s not a photo of a card. It’s a live, cryptographically protected credential that a proper reader can interrogate.
Key takeaways:
A mobile driver’s license is a digital identity credential built on the ISO 18013-5 international standard, which defines how a phone stores license data and how an authorized reader retrieves it. On an Arkansas mDL, the holder’s information stays encrypted on the device and is released only after they approve the request with Face ID or Touch ID.
Two features make the standard matter for verification:
The important point for an operator is that the security of an mDL doesn’t live in what appears on the screen. It lives in the encrypted exchange between the credential and a reader that can validate it.
A visual glance at a mobile ID proves nothing, because a screen shows only an image and an image is trivial to fake. A screenshot, a mocked-up wallet layout, or a lookalike app can all reproduce a convincing “digital license” that no amount of squinting will catch. There is no hologram to tilt, microprint to inspect, or laser-perforation to hold to the light. Only pixels.
Consider what your staff is being asked to judge when a phone appears:
With a plastic card, a trained eye and a scanner have physical anchors to work with. With a phone held across the counter, the eye has nothing real to grab. Any policy that amounts to “trust the screen” is a liability sitting in your staff’s hands, especially in age-restricted sales where serving a minor carries fines, license risk, and worse.
Key takeaways:
Genuine mDL verification replaces the human glance with a machine-to-machine exchange. Instead of reading the screen, an mDL-capable reader talks to the credential. It requests the data, then the holder authorizes release, and the reader confirms the issuing state’s cryptographic signature. Only then do you know the credential is real, unaltered, and actually issued by Arkansas.
Eyeballing a phone confirms that a phone displays an image; a compliant reader confirms that the state issued a valid credential.
The exchange does three things a glance can’t:
This is exactly why owned, purpose-built verification hardware and software outperform a repurposed phone app. Our Mobile ID (mDL) readiness capability is built to handle credentials the right way, and it sits inside the same ecosystem that reads physical licenses and runs fake-ID detection. For a broader look at the mechanics, our guide on how an ID scanner works covers the reading and validation process end to end.
For the foreseeable future, your door and your counter will see both formats. The state still advises residents to carry their physical Arkansas license because mobile IDs are not accepted everywhere, so an operator can’t pick one lane and ignore the other. Your staff and your tooling both have to handle plastic cards and phones with equal confidence.
That reality raises the bar in three practical ways:
The compliance stakes haven’t changed with the format. Serving or selling to a minor still triggers fines and puts your license at risk, and “the ID was on a phone” does not soften that. If anything, the digital era widens your exposure by adding a second format that is easier to fake visually and impossible to validate by eye.
For vertical-specific playbooks, see our guidance for bars and nightclubs, cannabis dispensaries, and liquor stores, each of which faces the both-formats problem at the counter. If you also want the physical-card context for the state, our overview of Arkansas’s new REAL ID driver’s license covers what the plastic version looks like today.
Key takeaways:
The digital-ID shift doesn’t make manual checking easier. It adds a second format that’s even easier to fake on a screen and impossible to validate with the human eye, which means the answer is better tooling. Preparing your Arkansas operation comes down to a few decisions:
We have spent 25+ years helping more than 20,000 businesses verify identity and age at the door and the counter, and we build hardware and software for exactly this kind of transition. As Arkansas customers start presenting phones, the safe move is to make sure your verification reads the credential.
See if your current setup can actually verify a mobile ID.Speak with an expert or explore our verification products to get ready before phones become the norm at your door.
Arkansas IDs are going digital, and that raises the standard for verification rather than relaxing it. A mobile driver’s license is a genuine, state-issued credential, but its security lives in the encrypted exchange between the credential and a compliant reader, not in the image on the glass. Because residents still carry physical cards, you will handle both formats at once, and both demand tooling that validates rather than displays. If your customers are starting to hand you phones, “trust the screen” is a compliance risk, and real verification means a reader that speaks the mDL standard and logs every check.
Yes, but not with a barcode scan or a glance. An Arkansas mDL is read through a cryptographic exchange defined by the ISO 18013-5 standard, where an mDL-capable reader requests the data and the holder authorizes its release with Face ID or Touch ID. A reader that only scans a 2D barcode or looks at the screen is not verifying the digital credential.
No. A screenshot is a static image with none of the underlying credential, so it cannot be cryptographically validated and should never be accepted as proof of identity or age. The security of a mobile ID depends on a live exchange with the real credential, which a screenshot cannot provide.
Yes. Because mobile IDs are not accepted everywhere yet, the state advises residents to continue carrying their physical Arkansas license. For businesses, that means planning to verify both physical cards and mobile IDs for the foreseeable future.
A phone screen shows only an image, with no physical security features to inspect and nothing to confirm the state actually issued the credential. Screenshots, spoofed wallet layouts, and copycat apps can all reproduce a convincing display. Genuine verification confirms the issuer’s digital signature, which only happens when a reader interrogates the credential rather than viewing it.
A verification tool that supports the mDL standard and can validate the credential cryptographically, alongside the ability to keep reading physical licenses. Since both formats will appear at the counter, the practical setup handles both and logs every check into an audit trail to support compliance.
Schedule a call to learn more
