A privacy-first identity wallet that lets you prove who you are without giving everything away.

ZAKAPI Personal Identity Wallet – Your Digital ID, Your Control

Overview

A dashboard that shows the user’s primary Verifiable Identity Credential, such as a government-issued digital ID or a KYC-completed credential. This can include name, photo, and date of birth, similar to a digital ID card, but the wallet lets the user share only the specific attributes a service requests. The wallet supports multiple identities, such as personal, work, or pseudonymous profiles, via decentralized identifiers (DIDs).

Credential manager

Users can receive and store a variety of credentials: government IDs, driver’s licenses, proofs of address, university diplomas, professional certifications, health or vaccine certificates, membership cards, and more. Each credential is digitally signed by the issuer and encrypted for the user. The wallet categorizes these credentials and shows their status, including valid, expired, or revoked.

Share proofs with selective disclosure

The wallet has a built-in Share Proof function. Whenever a service requests verification, it presents a clear consent prompt. For example: "Acme Bank is requesting: proof that you are over 18 and that your KYC is verified. Do you want to allow this?" The user can review exactly what will be proven and what will not be shared, such as "Your exact birthdate will not be shared." With one tap, they approve and the wallet uses the relevant credentials to generate a fresh non-interactive zero-knowledge proof for that specific request. Where needed, these proofs are bound to SQL-style checks over issuer databases that have been committed in advance, giving verifiers assurance that the right query was run on the right data without exposing any records.

Services catalog

A dedicated section lists integrated services and use cases, for example:

• Login with Zakapi - manage which websites and apps you have logged into with Zakapi, and revoke access if needed.
• Age verification - quickly generate proofs such as "over 18" or "over 21" in person or online.
• KYC verification - reuse your verified identity to onboard new financial, telecom, or government services.
• SIM registration - prove identity to mobile operators for SIM or eSIM activation.
• Travel credentials - store and present digital passports or travel-related credentials.
• Government services - connect national ID or e-government accounts for seamless public service login.
• Health and consent - manage health-related credentials and consents you might share with providers.
• Education credentials - store diplomas, certificates, and training records for easy sharing with employers.

Secure document vault

A secure vault stores sensitive personal documents in encrypted form, accessible only to the user. Credentials can reference these documents via cryptographic fingerprints, so a verifier can trust that a document was checked at issuance without ever seeing the file itself.

Recent activity log

The wallet maintains a log, visible only to the user, of all activity. For example: "KYC verification used for Bank of XYZ", "Age verification (18 plus) for Marketplace ABC", "Credential BSc in Computer Science received from Acme University". Each entry shows what was proven and to which service, helping users understand and control how their identity is used.

Security and privacy features

The wallet is non-custodial: users hold their own keys. It is secured by device biometrics or PIN and uses hardware-backed security where available. Credentials are issued to DIDs that resolve to keys on the device or are encrypted to the user’s keys, so no one, including Zakapi, can read them without user consent. Backup and recovery options, such as encrypted cloud backup or social recovery, help users avoid lockout if they lose a device.

The wallet can also operate offline in many scenarios. For example, users can present credentials via QR or NFC for airport checks or venue access, with verifiers checking signatures and proof validity without an online round trip to the original issuer.

User consent and control

The wallet puts users in full control. It does not auto-share information without a clear user action, except where the user has explicitly configured a low-risk auto-present rule. Before any proof is shared, the wallet displays what is being requested, who is asking, and which credential will be used. Users can decline at any time. If a credential is no longer trusted or needed, users can remove it or mark it inactive.

How it works in practice

Suppose a user named Alice has her government eID credential and a bank-issued KYC credential in her Zakapi Wallet. She visits an online marketplace that requires age verification to access certain listings. She clicks "Verify age with Zakapi". Her Zakapi mobile app shows: "MarketCo is requesting proof that your age is at least 21. Your date of birth will not be revealed."

Alice taps approve. The wallet uses her government ID credential, which contains her birth date, to construct a zero-knowledge proof that her age is above 21 without exposing the date itself. If the marketplace needs additional checks such as "not on internal fraud list" or "KYC completed in the last 12 months", those are handled by SQL-style queries executed by the bank over its own database, with the results folded into the same proof using committed data and non-interactive verification.

MarketCo receives the proof, validates it with Zakapi’s verification library and the issuer’s public keys, and gets a simple yes or no decision. Alice proceeds without sharing any raw documents.