Fragmentation
Every wallet and scheme speaks its own protocol on its own update cycle. Building them one by one is a roadmap nobody wants.
The shift
A screenshot is not a digital ID.
Identity is moving into the wallet faster than most flows can keep up. That leaves two ways to lose: turn real credentials away, or wave fake ones through.
Impersonation
Screenshots and forged PDFs pose as real digital IDs. A picture of a wallet card, on its own, proves nothing.
Exclusion
Reject digital IDs outright and you add friction, lose conversions, and increasingly fall out of compliance with new mandates.
0+
countries adopting or rolling out digital ID systems
2B+
people already enrolled across 100+ national and regional programs
How it works
One layer. Every wallet.
A digital ID runs through the same battery as a physical one: detected, decrypted, and cryptographically proven to belong to a real, present person.
Selective disclosure
Share one fact. Prove all of it.
A wallet shares only the claim you ask for and keeps the rest sealed. And every share is cryptographically signed, so Incode can prove it is genuine.
On the phone
On Incode
Coverage
One integration, every credential
Wallets, government apps, chips, and PDFs: Incode reads them all and hands your flow one clean, standardized identity.
-
Device wallets
Accept mobile driver's licenses from Apple, Google, and Samsung Wallet, in native share sheets.
-
Government eID apps
Verify national eIDs like BankID, MitID, Singpass, DigiLocker, and the EU's EUDI Wallet.
-
PDF credentials
Handle PDF IDs like Brazil's CNH Digital and the Philippines' ePhilID, read, not just uploaded.
-
Selective disclosure
Share only the fields you need (age over 21, not a full date of birth) so users convert.
The payoff
Fewer steps. More customers.
Meeting users where their ID already lives removes the slowest step in onboarding.
A cryptographic credential needs no photo, no upload, and no retry, so 98% of users clear on the first try when a digital ID stands in for the plastic card.
0×
faster verification when a customer presents a digital ID instead of scanning a physical card
Global coverage
One map. Every scheme.
Tell Incode which credentials to accept. New wallets, national eIDs, and mDL schemes are added as governments launch them.
- Compliant by default Coverage tracks eIDAS 2 in Europe and AAMVA mDL guidelines in the U.S., so acceptance stays compliant as the rules change.
- New schemes fast As a government launches a wallet or mDL program, Incode adds support, so you don't build it credential by credential.
- Detected on sight The flow recognizes which digital ID a user holds and requests it automatically, with no extra taps.
30+
national wallets and IDs
160+
countries adopting digital ID
Canada
United States
Mexico
Colombia
Peru
Brazil
Chile
Argentina
United Kingdom
Spain
France
Germany
Italy
Denmark
Sweden
Nigeria
South Africa
India
Singapore
Philippines
Japan
Australia
Verified proof
Global banks, fintechs, and marketplaces trust Incode to verify who's who.
98%
of users verify on the first try.
8 of 10
top U.S. banks choose Incode
4 of 5
top LATAM banks run on Incode
30+
digital ID schemes verified
What is digital ID verification?
Digital ID verification confirms identity from a government-backed digital credential, a mobile driver's license, ePassport, or national eID app, by decrypting and validating its cryptographic signature against the issuer, instead of photographing a physical card.
Which digital IDs can Incode verify?
30+ government-backed schemes: mobile driver's licenses in Apple, Google, and Samsung Wallet; national eIDs such as BankID, MitID, Singpass, and DigiLocker; the EU's EUDI Wallet as it rolls out; ePassports; and PDF-based IDs like Brazil's CNH Digital and the Philippines' ePhilID.
What is ISO 18013-5?
ISO 18013-5 is the international standard for mobile driver's licenses, defining how an mDL is stored, encrypted, and shared in person, so a verifier can confirm the credential is authentic and untampered. Its companion, ISO 18013-7, extends the same trust to online and remote checks.
How is this different from scanning a physical ID?
A physical-ID flow captures and validates a document plus a selfie. Digital ID verification reads a cryptographically signed credential straight from a wallet or app: faster for the user, harder to forge, and increasingly mandated. Incode runs both in one flow, with automatic fallback.
What happens if a user doesn't have a digital ID?
The flow falls back automatically to document and biometric verification. Users without a supported credential complete the same journey through a different door, so no session is lost to a missing wallet.
What's next
Accept the IDs that already live on a phone.
See how one integration verifies 30+ digital ID schemes, with fallback built in.