> For the complete documentation index, see [llms.txt](https://docs.blerify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blerify.com/id-wallet/get-started.md). # Get Started with the Blerify Wallet The Blerify Wallet is a mobile app where you receive, store, and present digital credentials. This page explains what the wallet is, what you can do with it, and how to receive your first credential. *** ## What is the Blerify Wallet The Blerify Wallet is an identity wallet that stores W3C Verifiable Credentials and ISO 18013 mDocs on your device. Credentials are encrypted at rest and unlockable only with your biometric (fingerprint or face) or PIN. When an organization asks you to present a credential — at an online service, at a kiosk, inside an app — the wallet shows you exactly which fields they're requesting. You approve or decline. Nothing leaves your device without your consent. Credentials are stored locally. Blerify does not hold a copy of your credentials in a cloud database. *** ## Install the wallet The Blerify Wallet is available on: * **iOS** — App Store * **Android** — Google Play Download and install it before following the steps below. *** ## Receive a credential Credentials are delivered to your wallet by an issuer — a government agency, employer, university, or other organization that has issued you a digital credential. You receive a credential in one of three ways: ### Option A — Scan a QR code The issuer shows you a QR code (on screen, on paper, or in an email). Open the Blerify Wallet, tap **Scan**, and point your camera at the QR code. The wallet downloads the credential, validates its signature, and asks you to confirm that you want to add it. Tap **Accept**. The credential is stored on your device. ### Option B — Tap a deeplink The issuer sends you a link — via email, SMS, or their own app. Tap the link on your phone. If the Blerify Wallet is installed, the OS routes it directly to the wallet. The wallet shows you the credential and asks you to confirm. Tap **Accept**. The credential is stored on your device. ### Option C — Push notification If the issuer has your wallet account linked, you may receive a push notification. Tap the notification. The wallet opens on the credential confirmation screen. Tap **Accept**. The credential is stored on your device. *** ## Present a credential When a service or organization asks you to present a credential, the process is the same regardless of whether they're a website, kiosk, or mobile app. 1. The verifier shows you a QR code or button. 2. You open the Blerify Wallet (or, on a mobile page, tap the button to open it directly). 3. The wallet shows a consent screen: the verifier's name, what they're asking for, and which fields from your credential will be shared. 4. You approve with your biometric or PIN. 5. The wallet sends the cryptographic proof to the verifier. The verifier's system receives the result. Your screen shows a confirmation. The verifier only receives the fields you approved. Your full credential is never transmitted. *** ## What the wallet holds The wallet can store both W3C Verifiable Credentials and ISO 18013 mDocs. You can have multiple credentials of the same type — for example, multiple employee credentials from different organizations, or both a national ID and a professional license. Credentials are grouped in the wallet's main screen. Tap any credential to see its fields, its issuer, its validity period, and its status (active, expired, revoked). *** ## Authenticate with your wallet Beyond presenting credentials to verifiers, the wallet supports logging in to services by presenting a credential directly. Instead of a username and password, you prove your identity by presenting a verifiable credential — an ISO mDL or a W3C Verifiable Credential — which the service verifies cryptographically. The service issues you a bounded, revocable session in return. The credential is bound to a single-use challenge issued by the service, so nothing is replayable. If your session expires, the wallet can refresh it silently; if the refresh token itself expires or is revoked, you present your credential again to start a new session. This login flow is used internally by the wallet app to authenticate with the Blerify platform. If you're building a service that accepts this kind of credential-based login, see the developer documentation at . *** ## Revoked or expired credentials If an issuer revokes a credential, the wallet flags it on the next background sync. The credential stays visible in your wallet with a `REVOKED` badge — you won't be able to present it to verifiers, and any attempt will fail verification. Contact the issuer to understand why it was revoked and whether a replacement can be issued. An expired credential is similar — it stays in your wallet for reference but won't pass verification. Issuers typically notify you before expiry if a renewal process is available. *** ## Privacy and data * Your credentials are stored on your device, not on Blerify servers. * Blerify does not track when or how often you present your credentials. * The issuer is not notified when you present a credential. * Uninstalling the wallet removes the credentials from your device. They cannot be recovered from Blerify. Contact the issuer to re-issue them. *** ## Next steps [**Issuance: Issue a W3C Credential**](/introduction-to-issuance/build/issue-a-w3c-credential.md) — if you're building a service that delivers credentials to wallets, this is where to start. See also: [Verification: Get Started](/introduction-to-verification/build/get-started.md) — how verifiers request and validate credential presentations from the wallet. --- # 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.blerify.com/id-wallet/get-started.md?ask=&goal= ``` `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.