Roadmap 2026

Here we present the Inji-Stack product roadmap for 2026 and our strategic horizon forward. This roadmap outlines the planned features, progress, and release details for Inji Stack.

The annual product cycle for the Inji Stack begins in January and concludes in December.

For detailed module-wise roadmaps, please refer to the respective sections; Inji Wallet (Mobile, Web), Inji Certify and Inji Verify.

Inji Wallet

• Inji Mobile

• Inji Web

Inji Mobile

Vision

Building a trust-first digital wallet experience simplified sharing, enhanced protection, and frictionless verification for every user, everywhere.

Inji Mobile Wallet’s 2026 vision is to evolve into a fully interoperable, standards-aligned verifiable credential wallet that is secure, user-centric, and future-ready. The roadmap focuses on strengthening foundational capabilities—OpenID4VP & VCI final spec compliance, advanced cryptographic support (ECC R1, BBS+), unified key management, profile creation, and end-to-end revocation across all major VC formats (SD-JWT, JWT, mDoc). These upgrades ensure the wallet remains globally interoperable while meeting the needs of governments, implementers, and ecosystems adopting Inji.

We aim to deliver a highly reliable and scalable wallet that supports cross-platform verification, richer offline and BLE capabilities, multi-format rendering (SVG, PDF), and enhanced privacy models.

We will be able to introduce strategic features such as Shamir’s Secret Sharing for key recovery, BLE enhancements for iOS↔iOS, mDoc revocation, and a dedicated iOS verification library later during the year. Longer-term (2027+) innovation tracks explore multi-user credentials, one-time/bulk credential patterns, consent management, DIDComm, anonymous credentials, and multi-tech-stack portability—setting the foundation for Inji as a universal, secure, and inclusive digital credential wallet for global public infrastructure.

Priority 🗓️	Features 🛠️	Details 📝	Status 📊	Release 📌
P0	Presentation During Issuance.	2178	🟠 In-Progress
P0	Claim 169 QR Code Support.	2179	🔵 Planned
P1	Wallet Login & Common Key Management.	2119	🔵 Planned
P1	Create Profile - Profiling with Single VC.	TBA	🔵 Planned
P1	Support for ECC R1.	TBA	🔵 Planned
P1	Credential Refresh Support.	TBA	🔵 Planned
P1	DC API Support.	TBA	🔵 Planned
P1	Upgrade to OpenIDVCI final version 1.0	TBA	🔵 Planned
P1	Upgrade to OpenIDVP final version 1.0	TBA	🔵 Planned
P1	W3C Data Model 2.0-based SD-JWT & JWT VC Support.	TBA	🔵 Planned
P1	IETF based SD-JWT & JWT SVG Rendering.	TBA	🔵 Planned
P1	Delegated Access Support from Issuer.	TBA	🔵 Planned
P1	Shamir’s secret open standard Implementation.	TBA	🔵 Planned
P1	Revocation of mDoc/mDL VC Format.	TBA	🔵 Planned

Inji Web

Vision

The vision for the Inji Web roadmap is to build a secure, interoperable, and user-friendly web wallet that fully supports the next generation of global verifiable credential standards. By introducing capabilities such as W3C Data Model 2.0, SD-JWT, mDoc/mDL, revocation, credential refresh, profile management, delegated access, and offline/USSD-based sharing, Inji Web aims to offer citizens and organizations a trusted platform to receive, manage, and present credentials across diverse digital ecosystems. With enhanced privacy features like BBS+ and seamless integration with identity providers and verifier services, Inji Web will evolve into a comprehensive, inclusive, and scalable wallet experience suitable for national-level deployments and cross-sector use cases.

Priority 🗓️	Features 🛠️	Details📝	Status 📊	Release 📌
P1	W3C Data Model 2.0 & SVG Render Method.	TBA	🟠 In-Progress
P1	Revocation of Data Model 2.0 VC.	TBA	🔵 Planned
P1	Claim 169 QR Code Support.	TBA	🔵 Planned
P1	SD-JWT via OpenIDVP Flow.	TBA	🔵 Planned
P1	Pre-Auth Code Flow.	TBA	🔵 Planned
P2	Recovery of Web Wallet.	TBA	🔵 Planned
P1	Create Profile - Profiling with Single VC (Profile Management Multi-profile).	TBA	🔵 Planned
P1	Presentation During Issuance.	TBA	🔵 Planned
P1	mDoc/mDL VC Support.	TBA	🔵 Planned
P2	Credential refresh.	TBA	🔵 Planned
P2	Enhancement to Inji Web Login: Support other ID provider login like eSignet.	TBA	🔵 Planned
P2	Delegated Access Support from Issuer.	TBA
P2	USSD Support - Offline VC sharing via a feature phone USSD Wallet.	TBA	🔵 Planned
P2	BBS + Support: Improve user privacy 1 secret, and a domain-specific public key	TBA	🔵 Planned
P2	W3C Data Model 2.0 SD-JWT & JWT VC Support.	TBA	🔵 Planned
P3	Enhancement to Inji Web Login: Audit Mechanism with Inji web login.	TBA	🔵 Planned

Inji Certify

Vision

In 2026, Inji Certify will be a globally trusted, standards-aligned digital credential issuance platform enabling secure, interoperable, and scalable verifiable credentials across ecosystems. By supporting universal credential formats, OpenID4VCI v1.0, advanced cryptography, and a robust multi-issuer architecture, Certify will simplify adoption for large-scale government and enterprise deployments. Alongside delivering policy-ready issuance, revocation, and trust framework integrations, the platform will prioritize clearing technical debt and strengthening security, maintainability, and operational reliability—ensuring Certify remains a future-ready, developer-friendly backbone for privacy-preserving digital credentials worldwide.

Priority 🗓️	Feature 🛠️	Details 📝	Status 📊	Release 📌
P1	Presentation During Issuance with JSON LD VC Format.	TBA	🟠 In Progress
P1	VC Issuance with mDoc/mso VC format.	TBA	🟠 In Progress
P1	Pre Auth Code Issuance for JSON-LD Format.	TBA	🟠 In Progress
P1	Embedding Multiple QR code in VC.	TBA	🟠 In Progress
P1	Multiple issuer.	TBA	🔵 Planned
P1	Adoption of OpenIDVCI v1.0.	TBA	🔵 Planned
P1	Support VC Format.	TBA	🔵 Planned
P2	Trust registry and verifiable data registry/ Support for dedi protocol.	TBA	🔵 Planned
P1	SVG Rendering - support for multiple templates rendering.	TBA	🔵 Planned
P1	Support for adoption of external key manager system to Certify.	TBA	🔵 Planned
P2	Trust registry and verifiable data registry/ Support for keri protocol.	TBA	🔵 Planned
P1	Multi-lingual support for credential data (Enhancement).	TBA	🔵 Planned
P1	Credential Refreshing.	TBA	🔵 Planned
P1	Support for wallet attestation client auth.	TBA	🔵 Planned
P1	Revocation of Credentials.	TBA	🔵 Planned
P1	Presentation during Issuance.	TBA	🔵 Planned
P1	Pre-Auth Code.	TBA	🔵 Planned
P1	Support for VC Issuance in PDF format.	TBA	🔵 Planned
P2	VC issuance with mutiple VC formats.	TBA	🔵 Planned
P2	Multiple QR Codes embedded in VC.	TBA	🔵 Planned
P2	BBS Support.	TBA	🔵 Planned
P2	Multi-proof support for single credentials. Inji Certify all have to be enhanced with multi-proof - ED, EC & BBS+.	TBA	🔵 Planned
P2	VC Generation: Create Credentials from the Request Payload.	TBA	🔵 Planned
P3	Subject Holder relationship VC.	TBA	🔵 Planned
P4	VC multiple status List support.	TBA	🔵 Planned
	GA Release.	TBA	🔵 Planned
P4	Plug-ins for commonly used databases and data exchange.	TBA	🔵 Planned
P4	Allow bulk generation of onetime credentials.	TBA	🔵 Planned
P4	Support for PDF Template and rendering (Credential Issuance).	TBA	🔵 Planned
P4	Support for WebVH (Verified History).	TBA	🔵 Planned

Inji Verify

Vision

By 2026, Inji Verify aims to become a universal, multilingual, and highly interoperable verification platform supporting all major credential formats including W3C JSON/JWT VCs, IETF JWT/SD-JWT, mDoc/mDL, MOSIP UIN VCs, and advanced revocation with multiple status lists backed by decentralized trust through KERI, DEDI, and global trust registries. It plans to deliver rich, branded verification outputs through SVG and PDF templatising, multi-language rendering, and support for multiple QR formats.

Verification experiences aims to be seamless across online, offline, and proximity-based scenarios with OpenID4VP and OpenIDVP same-device flows, BLE presentations, offline SDKs, and server-side ECC-R1 verification.

Inji Verify plans to expand platform reach through native Android/iOS apps and broad framework-compatible SDKs, making it a secure, accessible, future-ready, and developer-friendly global standard for credential verification.

Priority 🗓️	Feature 🛠️	Details 📝	Status 📊	Release 📌
P1	Ability to verify Claim 169 QR Code.	1365	🔵 Planned
P1	OpenID4VP - Same device flows alongside Web wallets.	1437	🔵 Planned
P1	OpenIDVP: Same Device Flow (via DC API).	1016	🔵 Planned
P1	Support Server Side VC Verification: ECC- R1.	1017	🔵 Planned
P1	Ability to verify JSON (W3C) VC.	1018	🔵 Planned
P1	Upgrade to OpenIDVP final version 1.0.	1019	🔵 Planned
P1	W3C Data Model 2.0-based JWT VC.	1020	🔵 Planned
P1	Multi language for SVG Template rendering.	1021	🔵 Planned
P2	Offline Verification SDK.	1022	🔵 Planned
P2	BLE based verifiable presentation.	1023	🔵 Planned
P2	Multi-Lingual Support.	1024	🔵 Planned
P2	BBS+ Support.	1025	🔵 Planned
P2	VC Label translation with well known.	1026	🔵 Planned
P3	Inji Verify SDK Support apart from React applications for Wider Framework Compatibility.	1027	🔵 Planned
P3	Ability to verify mDoc and mDL.	1028	🔵 Planned
P3	Support for philisys QR code.	1029	🔵 Planned
P3	Revocation for SD-JWT and JWT.	1030	🔵 Planned
P3	Trust registry and verifiable data registry/ Support for: keri protocol dedi protocol	1031	🔵 Planned
P4	IETF JWT VC Support.	1032	🔵 Planned
P4	Native App for Inji Verify - Android device.	1033	🔵 Planned
P4	Native App for Inji Verify - iOS device	1034	🔵 Planned
P4	Revocation for mDoc/ mDL.	1035	🔵 Planned
P4	Multiple QR Codes embedded in VC in a single PDF.	1036	🔵 Planned
P4	SVG Rendering for IETF based SD-JWT & JWT.	1037	🔵 Planned
P4	PDF Template Support.	1038	🔵 Planned
P4	VC multiple status List support.	1039	🔵 Planned
P4	Support for WebVH (Verified History).	1040	🔵 Planned

---

Acronyms and Legends:

TBA: 'Github Issues Link - To Be Added'