> 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/authentication/1kosmos-mobile-application/application-capabilities/digital-wallet.md).

# Digital Wallet

***

### Capabilities in this category

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td>Identity wallet</td></tr><tr><td>Verifiable credentials</td></tr><tr><td>Selective disclosure</td></tr></tbody></table>

***

### Identity wallet

A user-controlled digital wallet that stores all identity assets on-device.

**What it does** — Provides encrypted, on-device storage for identity documents, biometric assets, account credentials, and verifiable credentials. Each wallet is created with a unique decentralized identifier (DID) and a public-private key pair generated in the device's secure enclave.

**When to use it** — Foundational capability — every user has a wallet. Used implicitly by every other capability that stores identity data.

**Key details**

* Public-private key cryptography (FIDO2-compatible)
* Private key stored in device secure enclave
* Decentralized identifier (DID) per wallet
* Encrypted at rest with device-bound keys
* Recoverable via 12-word mnemonic

***

### Verifiable credentials

Issue, store, and present W3C-compliant verifiable credentials.

**What it does** — Acts as a verifiable credential holder and provider. Trusted issuers (employers, institutions, agencies) sign credentials and deliver them to the user's wallet. Users can present credentials to relying parties, who verify authenticity cryptographically without contacting 1Kosmos.

**When to use it** — Decentralized identity ecosystems, professional certification, employment verification, age verification, membership credentials, and any flow requiring tamper-proof identity assertions.

**Key details**

* W3C Verifiable Credentials data model
* Cryptographically signed by issuers
* Selective disclosure supported (share only required attributes)
* Verification possible without contacting 1Kosmos
* Tamper-evident through digital signature

***

### Selective disclosure

Share only the specific attributes a relying party needs.

**What it does** — When presenting a credential, users can disclose only the attributes required for the request — for example, proving "over 21" without revealing date of birth, or proving employment without revealing employer or salary.

**When to use it** — Privacy-respecting verification flows, age verification, eligibility checks, and compliance-driven minimum data exposure scenarios.

**Key details**

* Built into the verifiable credential presentation flow
* Cryptographic guarantees on disclosed and undisclosed fields
* Consent prompt shown before any disclosure
* No data leaves the device without explicit user approval

{% hint style="success" %}
**Privacy by design.** Users share only the attributes a verifier needs — and 1Kosmos never sees what is shared, when, or with whom.
{% endhint %}

### Wallet architecture

The wallet uses three layers of protection:

| Layer        | Mechanism                          | Purpose                                     |
| ------------ | ---------------------------------- | ------------------------------------------- |
| Storage      | Device secure enclave + encryption | Prevents tampering and unauthorized access  |
| Cryptography | Public-private key pair (FIDO2)    | Ensures only the user can sign and present  |
| Recovery     | 12-word mnemonic phrase            | Allows wallet to be restored on new devices |


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/authentication/1kosmos-mobile-application/application-capabilities/digital-wallet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.