Reusable Identity: The Push to Verify Once and Use Everywhere
Reusable identity promises to let people prove facts such as age, address or professional credentials without repeatedly handing over documents. The model could reduce fraud and friction, but it also raises hard questions about interoperability, privacy and who controls the wallet.
Identity verification is built around repetition. A person opens a bank account, rents a car, signs up for a marketplace or proves their age online, and each service may ask for the same passport, selfie and address evidence. Reusable identity aims to replace some of that duplication with a credential that has already been checked and can be presented again.
The idea is gaining practical momentum as governments deploy digital identity wallets, mobile driver's licenses expand in the United States, and standards groups align on ways to issue and verify digital credentials. But a system that works across borders, devices and industries remains far from assured.
From a one-time check to portable credentials
Reusable identity generally means that a verified attribute can be used with more than one relying party, the organization requesting proof. Rather than sending a fresh image of a passport to every website, a user might present a cryptographically signed credential stating that they are over 18, live at a given address, or hold a valid license.
Decentralized identity is a related, more specific model. It seeks to put credentials under the holder's control, usually in a digital wallet on a phone, rather than in a single platform's central account. The issuer, such as a government agency, university or bank, signs the credential. A verifier checks that signature and its current status without necessarily contacting the issuer for every transaction.
This does not mean identity becomes anonymous or entirely outside institutional control. Trusted issuers still establish the original facts, and verifiers still decide what evidence they require. It is better understood as a change in how proof is stored and exchanged.
The appeal: less data, less repeated friction
For users, the strongest promise is selective disclosure. A bar or online retailer checking age may need only confirmation that a customer is over a threshold, not a full name, date of birth or home address. That can reduce unnecessary data collection and the exposure created when document images are stored by many companies.
Businesses see a route to faster onboarding, lower document-review costs and potentially better fraud controls. A credential issued by a high-assurance source can be harder to alter than a static image. It may also help firms distinguish a genuine credential from a synthetic identity, in which fraudsters combine real and invented personal data.
- Users could reuse verified claims while disclosing only the information a transaction requires.
- Verifiers could receive machine-readable, tamper-evident evidence instead of manually reviewing document uploads.
- Issuers could update, suspend or revoke credentials when a license expires, a document is lost or a status changes.
- Cross-border services could rely on common technical formats rather than bespoke integrations.
Governments, standards bodies and platforms are shaping the market
The European Union is a major driver through the European Digital Identity Wallet framework under the updated eIDAS rules. Member states are working toward offering wallets that can hold public and private credentials, with use cases spanning government services, education, travel and regulated business. The framework also places obligations on certain large online platforms to accept the wallet when users choose to use it.
In the United States, adoption is more fragmented. State motor vehicle agencies are issuing or piloting mobile driver's licenses, while federal agencies, airlines and private businesses test digital credential acceptance. These efforts often draw on ISO standards for mobile driving licences. They are not, however, a single national identity system.
Technical foundations are being developed by the World Wide Web Consortium, the OpenID Foundation and the Internet Engineering Task Force, among others. Their work includes verifiable credentials and protocols for issuing and presenting them. Wallet providers, identity verification vendors, device makers, banks, universities and enterprise software companies are building services around those standards.
Privacy gains are possible, not automatic
A well-designed wallet can limit data sharing and reduce the number of document databases that attackers can target. Yet portability introduces its own risks. If a wallet or credential format allows the same identifier to be observed across many transactions, it can enable correlation, allowing organizations to link a person's activity across services.
The technical answer is often pairwise identifiers, one-time presentations and selective disclosure. Governance matters just as much. Verifiers need rules against requesting excessive attributes, issuers need clear limits on transaction logging, and users need meaningful choices. A wallet should not become a mandatory gateway for everyday life or a tool for routine tracking.
The central test is not whether a credential can be reused, but whether it can be reused without creating a new, highly visible record of where someone has been.
Adoption depends on trust and interoperability
The biggest barrier is the classic network problem. A credential is useful only when issuers, wallets and verifiers all accept compatible formats and trust one another's assurance levels. A university credential may be sufficient for an employer but not for a bank subject to anti-money-laundering obligations. Liability is also unresolved: participants need to know who bears losses when an issuer makes an error, a wallet is compromised or a verifier relies on a revoked credential.
Accessibility is another constraint. Not everyone has a modern smartphone, stable connectivity or the ability to manage recovery codes. Physical documents and assisted channels will remain necessary. Device loss, coercion and account recovery are especially sensitive in identity systems because a locked-out user can lose access to many services at once.
Reusable identity is therefore unlikely to eliminate conventional verification soon. More plausibly, it will first take hold in narrow, high-value journeys where the issuer is trusted and the proof needed is clear. Its long-term success will depend less on the wallet app than on interoperable standards, enforceable privacy rules and a user experience that is genuinely easier than uploading a document again.