A digital identity wallet is an app the user holds that stores verifiable credentials and shares proofs on demand, so they present a confirmed attribute instead of raw documents. Its promise is cutting repeat KYC and reducing how much personal data gets exposed, but a slick wallet screen proves nothing on its own.
What is a digital identity wallet, in plain English?
A digital identity wallet is an app on the user's phone that holds verifiable credentials, which are cryptographically signed claims from a trusted issuer, like a government or a bank. When a service asks who they are, the user shares a proof rather than a photo of a document: the wallet presents a signed statement that they are over 18, or that their name and address were confirmed, without handing over the underlying files.
The appeal for a risk team is real. Reusable, issuer-signed credentials can cut the pain of repeating full KYC at every new service, and selective disclosure means the customer shares only the attribute you actually need, not their entire document. National wallet schemes and open standards are pushing this from a pilot idea toward everyday use.
The catch is what a wallet does not prove. A polished wallet screen shows a credential; it does not show that the issuer is trusted, that the credential is still current, or that the person tapping the phone is its rightful holder. In fraud terms, holding a credential is not the same as being the person it describes.
How a wallet presentation flows
- Issue — Credential is granted. A trusted issuer verifies the user once and drops a signed credential into their wallet.
- Request — Service asks for a proof. Your onboarding flow requests a specific attribute, like age or a confirmed address.
- Present — Wallet shares the proof. The user consents and the wallet returns a signed proof, ideally disclosing only what was asked.
- Verify — You check it is real. You validate the issuer signature, confirm it is not revoked, and bind it to a live holder.
- Lower risk — Trusted issuer, fresh, live holder. Signature valid, credential current, and a liveness check ties the phone to the real person.
- Higher risk — Cloned or coerced wallet. A valid credential presented by someone who is not its owner, with no holder check to catch it.
Who is involved?
Who | Their role |
The issuer | Verifies the user once and signs the credential, such as a government agency or a bank. |
The holder | The user who stores credentials in the wallet and chooses what to present. |
The verifier | Your service, which requests a proof and must check the signature, freshness, and holder. |
The fraudster | Tries to clone a wallet, coerce a holder, or present a valid credential they do not own. |
What it looks like in practice
In practice
A new customer opens your app and, instead of scanning a passport, taps a national identity wallet to share a proof of name and date of birth. The credential is signed by a government issuer and validates cleanly, so onboarding is nearly instant.
Weeks later, a fraud case shows the same credential presented from a different device with no liveness step. The wallet had been restored onto a second phone from a stolen backup. The credential was genuine, but nothing tied it to the real holder, so the proof passed while the person behind it did not.
Why it matters to operators
Wallets can lift good customers through onboarding fast and shrink the personal data you store, which is a genuine win for both conversion and privacy. The risk is that the smooth experience invites teams to treat the wallet screen as the answer instead of the beginning of a check.
Two things separate a strong wallet integration from a weak one: verifying the issuer and revocation status rather than trusting the look of the app, and adding a holder-binding step so a valid credential cannot be presented by the wrong person. Without a liveness or holder check, a cloned or coerced wallet defeats the whole model.
What to watch in the data
- Unverified issuer. A credential is only as trustworthy as who signed it; an unknown or untrusted issuer is not a pass.
- Stale or revoked. Always check the credential is current and has not been revoked, not just that the signature parses.
- No holder binding. A valid credential with no liveness or holder check means you never confirmed the presenter owns it.
- New device restore. The same wallet credential appearing on a fresh device can mean a restored backup in the wrong hands.
- Coercion signals. Rushed presentations, prompting from off-screen, or reluctance during a live step can point to a coerced holder.
Quick questions
How is a wallet different from uploading a document?
With a document, you receive the raw file and verify it yourself. With a wallet, you receive a signed proof from an issuer who already verified the user, so you check the signature and status instead of inspecting the document.
Does a valid credential prove the person is real?
No. It proves the issuer once verified someone and that the credential has not been tampered with. It does not prove the person presenting it is the rightful holder, which is why a liveness or holder check still matters.
What is selective disclosure?
It lets the wallet share only the attribute you ask for, such as over 18, without revealing the whole document. It reduces data exposure, but you still need to trust the issuer and confirm the holder.
Can a wallet be cloned or stolen?
Yes. Backups can be restored onto another device and holders can be coerced into presenting a proof. The credential stays valid, so the defense is binding it to a live, willing holder at presentation.
Should I stop doing document checks if a wallet is used?
Not blindly. For low risk, a strong wallet proof can replace a document, but for higher risk actions add a live holder check. Match the assurance to the risk rather than trusting the wallet screen alone.
Go deeper
- NIST Digital Identity Guidelines (SP 800-63) ↗ — The US standard for identity proofing and authentication assurance levels.
- FATF ↗ — The global standard-setter for AML, counter-terrorist-financing, and counter-proliferation. Recommendations, guidance, and jurisdiction lists.