Example Bottle ShopSan Francisco delivery
Botanical spirits
Botanical gin
750 ml · 43% ABV
Small-batch dry gin
$46.00Add to cart
Add Digital ID to your verification flow
Give users a faster way to prove who they are using an mDL from their digital wallet. Stile handles the credential exchange and returns a signed result your product can act on. Get higher confidence identity checks, collect less personal data, and avoid complex integrations.
Checkout
Example Bottle Shop adds botanical gin and tonic water to a $54 order. Only the gin requires an age check. Checkout asks the shopper to verify with Stile before payment.
Wallet
An illustrative California Wallet prompts the shopper to present a mobile ID to Example Bottle Shop. The shopper confirms with a hold gesture. The final frame highlights age-over-21 evidence and California credential context, then shows a Sent to Bottle Shop receipt.
Decision
Stile returns a low-risk assessment, an advisory Allow recommendation, and signed evidence. Example Bottle Shop's policy makes the final transaction decision and selects Approve.
How to verify an mDL
Add mDL verification to your website or app. Your customer shares from a compatible wallet; your server receives the result.
Start a verification
Enable mDL in your Stile workflow. Create a session from your server and associate it with the customer, account, or transaction in your application.
Your customer shares
Your customer opens a compatible wallet, reviews the requested information, and approves sharing. Supported desktop flows let them continue on their phone.
Stile checks the response
Stile handles the OpenID4VP exchange and checks device authentication against the verification session.
Use the result
Verify the webhook signature and match the result to your session. Process each event once, then apply your own rules for access, approval, or review.
The customer experience
Let customers share from their wallet
Customers with a supported mDL can share the requested information without photographing their physical license.
Skip the document upload
Customers open their wallet, review the request, and approve sharing. They do not need to photograph the front and back of their physical license.
Benefits
- No document upload
- No license positioning
- No glare or blur
- No text extraction from photos
Share selected attributes
An mDL can support sharing selected attributes instead of an image of the whole license. What is requested and shared depends on the wallet and configured verification flow.
Benefits
- Selected attributes
- Visible request
- Customer approval
Connect the check to your application
Stile processes the wallet response and sends a signed verification event to your server. Match it to the customer or transaction that started the session.
Benefits
- Signed webhook
- Session reference
- Your application’s decision
Remove the photo capture step
Glare, blur, and poor lighting can make a physical license difficult to photograph. An mDL flow receives data from the wallet instead of extracting it from a document image.
Benefits
- No document glare
- No blurry ID images
- No document-photo retries
Review before sharing
The customer reviews the requested information in their wallet before approving the exchange. Data handling also depends on the wallet, verification flow, and your application’s practices.
Benefits
- Visible request
- Customer approval
- Selected information
mDL API
Get results on your server
Stile sends your server a signed webhook with the verification status, session ID, and your transaction reference. Use those fields to connect the mDL result to the right customer, account, or order.
The webhook does not include raw captured ID evidence. Verify its signature and match it to the original session before your application decides whether to continue, decline, or request review.
Read the quickstart Explore the event schemaExample mDL webhook · abridgedjson
US mDL adoption
Check availability for your customers
Mobile driver’s licenses are issued state by state. The map highlights issuing states, so you can assess whether customers in your target markets may have an mDL.
A state issuing mobile licenses does not mean every wallet works with your integration. Check the wallet, device, browser, and Stile workflow you plan to offer.
Apple Wallet
Google WalletCheck wallet support before you launch
Start with the states and devices your customers use. Confirm that their wallets can complete your Stile flow, and offer another method when mDL is unavailable.
Apple Wallet ID verification
Review Apple’s participating jurisdictions and device requirements. Apple Wallet is not currently available as a standalone Stile workflow method, so confirm a supported integration route before planning your launch.
Google and state wallets
Check Google Wallet’s ID availability or the issuing state’s wallet guidance. Then test the wallet and device combinations you expect customers to use with Stile.
Customers without a supported mDL
Configure an alternative, such as document capture, so customers without a compatible wallet can complete verification. Review Stile’s verification methods when choosing that path.
In-person and online mDL verification
Compare the hardware used for in-person checks with the online flow you can add to your website or app.
In person: an mDL reader
At a store or service desk, a compatible mDL reader or scanner connects to the customer’s nearby phone. The customer reviews the request in their wallet and approves sharing information from their license.
Online: Stile’s hosted flow
Your server starts a verification session. The customer approves sharing from a compatible wallet, and Stile returns the outcome through a signed webhook. Supported desktop flows let the customer continue on their phone.
Compliance and security
Proof with privacy
Ask only what the decision requires. Stile returns a clear result without sharing raw ID data.
Customer sees
9:41
Example Bottle ShopSecure checkout
1Botanical gin750 ml · Qty 1
$46.00Deliver to100 Market Street✓
PaymentVisa ending 4242✓
Confirm you’re 21 or older
Required before this order can be completed.
The retailer receives the age result, not the ID.
Buyer sharesOver 21
Full ID stays privateNo name, birth date, address, or ID image
You decideContinue checkout
Use Cases
Add an identity check before the next step
Use mDL verification before onboarding someone, restoring account access, or completing a handoff. Your application decides whether the result meets the requirements for that action.
Vendor onboarding
Request an identity check from the person joining your vendor onboarding process.
BenefitsUse the result alongside your business and authorization checks.
Account recovery
Ask the person requesting access to complete an identity check.
BenefitsUse the result alongside your account ownership and recovery checks.
Research enrollment
Ask a prospective participant to complete an identity check before enrollment.
BenefitsApply your study’s eligibility rules separately.
Rental vehicle pickup
Request an identity check before pickup, then use the result in your reservation and handoff process.
BenefitsYour rental system decides whether to release the vehicle.
Before you integrate
Plan for the customers and checks you need
Can customers continue without an mDL?
Yes, if you configure another verification method. Offer document capture or another supported path for customers whose wallet or credential cannot complete the mDL flow.
Does a verified result approve the customer automatically?
No. Stile returns the verification outcome. Your application applies its own rules for access, eligibility, or approval.
Will I still need liveness or face match?
That depends on your use case and policy. Some workflows need an additional check that the person is live or matches a reference photo; configure those checks separately when required.
FAQ
FAQs
Wallet, issuer, and schema support change frequently. See the documentation for current coverage and event details.
What is a mobile driver’s license (mDL)?
An mDL is a government-issued digital driver’s license held in a compatible mobile wallet. It lets a customer share identity information from the wallet without scanning a physical card.
Can a user start on desktop and finish on a phone?
Yes. On desktop, Stile can hand the request to a supported mobile wallet, typically with a QR code, so the user reviews and shares from their phone.
What does my backend receive?
Your backend receives a signed verification event with the session outcome and the identifiers needed to match it to the correct user or transaction. Review the event schema and webhook signature guide before acting on the result.
What data does Stile process, return, delete, and retain?
Stile does not send raw captured evidence or collected personal data in the webhook. Retention varies by data type, workflow, and applicable policy: captured document evidence is purged after a final decision, while verification outcomes and sensitive hashed anchors may persist. See Data Retention & Privacy for details.
Does an mDL replace document capture, liveness, or face match?
An mDL can replace photographing a physical license in a supported verification flow. It does not automatically replace liveness or face match. Configure additional checks when your use case and policy require them.
Which mobile wallets and jurisdictions are supported today?
Stile is US-first. Wallet availability varies by issuer, state, device, and configured workflow. See the verification methods guide for current method availability and device requirements.
How do I add Digital ID to my workflow?
Create a workflow, start a verification session from your server, add the hosted Stile widget, and act only on the signed webhook result. The quickstart walks through the full integration.
Plan your mDL integration
Tell us where you need to verify customers. We’ll walk through wallet compatibility, the online verification flow, and an alternative for customers without an mDL.