> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/ial2-verification/identity-wallet-based-verification.md). # Identity Wallet-Based Verification Identity wallets allow you to store identity documents, and social security details, all in one place on your smartphone or on the web. They allow you to reuse previously verified identities. *** ### Identity Wallets on the Smartphone Every time you download and install the 1Kosmos app, a new identity wallet is created for you using public key cryptography. A decentralized identifier along with the key pair constitute your identity wallet. PII information about the user is stored within the wallet and requires the user's private key and biometrics to read data from the wallet. The private key is securely stored in the Secure Enclave of the device, and the public key is stored by relying parties. When data from the wallet needs to be presented to a relying party, the holder must present biometrics and consent to share data. When approved, the private key is presented as a credential to unlock the wallet and share data. The private key never leaves the device, minimizing it from compromise. ### Identity Wallets for the Web For enterprises looking to onboard their customers purely from a web-based journey, 1Kosmos supports web wallets that are implicitly created during sign-up. A decentralized identifier along with the public key and private key constitute your identity wallet. Web wallets are protected by password-based or passwordless MFA methods. In addition, wallets require a user-provided PIN to unlock the wallet. ### Replacing Passwords with Public Key Cryptography Public key cryptography reduces the threat from potential database breaches. Initiating 1Kosmos mobile generates a public-private key pair on the user's authenticator (a physical device). The user's public key is stored by requesting websites / relying parties, but this alone is useless to an attacker. An attacker cannot derive the user's private key from the data stored on the server, which is required to complete authentication. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.1kosmos.com/identity-verification/ial2-verification/identity-wallet-based-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.