Your credentials. Your app.
Your wallet… or ours.
The ‘hold credentials’ layer of the Indicio Proven platform. Embed multi-format credential wallet capabilities directly into your existing Android or iOS mobile app with our Mobile SDK, or deploy our white-label wallet, Holdr+, for immediate use. Every major credential format. Every major protocol. All the code you need in one place.
Two ways to deploy
One wallet platform. Two integration paths.
Choose the path that fits your product and timeline. Both deliver the same multi-format, multi-protocol interoperability from a single codebase.
Add full wallet functionality directly into your existing mobile app so users never leave your brand experience. Your customers or users hold their keys and credentials on their own mobile devices with secure credential exchange happening natively inside your app.
- → Embed into existing iOS and Android apps
- → Support every credential format from one SDK
- → No forced redirects to third-party wallets
- → Kotlin, Swift, React Native, Flutter
- → Customers control their own data and keys
- → Built to evolve as standards change
Holdr+ is a complete, pre-built wallet application branded to your identity. Deploy a fully functional credential wallet without building from scratch. Ideal for fast time-to-market or when your end users need a standalone experience.
- → Ready to deploy with your branding
- → Full multi-format credential support
- → Works across any compliant issuing and verifying system
- → Built on open standards, not proprietary lock-in
- → Customizable workflows and UI
- → Unlimited wallet deployments
Under the hood
Format, protocol, and method support
One wallet platform that enables users to cross every major credential ecosystem.
With Indicio, multi-credential use is seamless. The Proven wallet takes care of the presentation requirements so users get fuss-free navigation across credential formats, jurisdictions, sectors.
- ISO 18013-5/7 mdoc/mDL
- SD-JWT VC
- W3C VC (JSON-LD)
- AnonCreds
- Open Badges 3.0
- DTC Type 1 & 2
- IATA One ID
- OpenID4VCI / OpenID4VP
- DIDComm V1.0
- BLE (Bluetooth Low Energy)
- NFC
- QR & barcode
- Wi-Fi Aware (roadmap)
- Digital Credentials API (roadmap)
- did:webvh
- did:key
- did:peer (v1, v2, v4)
- did:indy
- did:sov
- Biometric-protected storage
- PIN code access
- Selective disclosure
- Zero-knowledge proofs
- Pairwise identifiers
- Explicit consent for all sharing
- Secure on-device key storage
Built for
From one wallet, many use cases.
Passengers carry a reusable, verified digital identity through every touchpoint: airline check-in, bag drop, boarding gate, border crossing, hotel, car rental. No repeated document checks.
Learn more →Verify a customer once, issue a credential, and reuse that trusted identity across products, channels, and partners. Reduces onboarding friction and compliance costs.
Learn more →Issue verifiable employee and contractor credentials that work across systems, roles, and organizations. No manual re-provisioning, no shared passwords.
Learn more →Replace passwords and security questions with Verifiable Credentials. Customers authenticate and recover accounts instantly while stopping synthetic IDs and AI-driven fraud.
Learn more →Deliver personalized experiences and loyalty benefits using verified attributes customers consent to share. All without exposing personal data.
Learn more →User experience
Credential exchange that feels like a conversation.
The SDK wraps Verifiable Credential exchange in a conversational format
that feels natural and intuitive. Credential requests, presentations, and
approvals appear as contextual messages within a familiar chat-style interface.
Presentation requests appear as simple messages explaining what’s being asked, why, and by whom. Tap to approve or decline.
Both parties can verify each other before any data moves. The user sees who’s asking and confirms they're legitimate before sharing anything.
All communication travels over DIDComm secure channels — enterprise-to-wallet and wallet-to-wallet, fully encrypted.
The same conversational flow handles mdoc, SD-JWT, W3C VC, AnonCreds, and DTC credentials. The wallet software matches the right credential format to the request. The user never needs to know which format is being used.
Common questions
Indicio’s verifier platform can accept credentials presented from Apple, Google, EUDI, and any other standards-compliant wallet. The Indicio wallet itself can hold and present credentials to any compliant verifier. Interoperability is bidirectional. Users aren’t locked into one wallet ecosystem. Your verifiers aren’t limited to credentials from one issuer.
Credentials are stored on the holder’s device in a secure, biometric-protected wallet. Data is shared only through explicit user consent and, where required, with selective disclosure so a verifier receives only the precise information they need. Neither Indicio nor the issuer has access to the credential data after issuance.
No. Verification uses cryptographic proofs embedded in the credential. The verifier checks the signature to determine the issuer and confirms the issuer is in the trust registry. The signed data is cryptographically verfied to determine it hasn’t been tampered with. If it has, it will be immediately detectable. This all happens locally, instantly; there’s no callback to the issuer or a centralized database held by a third party, or Indicio.
The SDK ships with packages for Kotlin, Swift, React Native, and Flutter. This covers the major mobile development frameworks for both iOS and Android. Localization is supported in English, Spanish, French, German, Italian, Portuguese, Japanese, and Arabic out of the box, with additional languages available on request.
Yes. In-person credential presentation works over BLE and NFC without an internet connection. The cryptographic proof is self-contained in the credential so the verifier doesn’t need network access to confirm authenticity. This is critical for border crossings, remote locations, and any scenario where connectivity is unreliable.
Next step
See the wallet working with your use case.
Bring your app, your requirements, your credential formats. We’ll show you the SDK integration, walk through the white-label option, and demo credential exchange end to end.