Roadmap 2025

Here we present the product roadmap for the entire Inji Stack for the calendar year 2025. The annual product cycle for the Inji Stack begins in January and concludes in December.

For detailed module-wise roadmaps, please refer to the following:

• Inj Wallet

  • Inji Mobile

  • Inji Web

• Inji Certify

• Inji Verify

Prioritization: Through this roadmap the startegic or adaptive prioritization, if there is, has been indicated as below:

• Add [ ^➕ ]: Added new.

• Strategic priortization [ ^↑ ] : Brought ahead in schedule.

• Adaptive reschedule [ ^↓ ]: Is moved to approaching quarters.

Inji Wallet

Vision

In 2025, Inji Wallet will continue to ensure compatibility with diverse ecosystems by supporting multiple credential formats, such as mDoc/mDL, SD-JWT, and JWT. The wallet will also incorporate privacy-preserving mechanisms such as BBS+, selective disclosure, and one-time credentials, empowering users to retain full control over their personal information. Additionally, the wallet will enable multi-user credential sharing, addressing family-based use-cases such as ration cards and property deeds, further enhancing its versatility and real-world applicability.

The wallet’s roadmap includes critical features like OpenIDVP enhancements for cross-device and same-device flows, Shamir’s secret sharing for secure key recovery, ECC K1 and R1 key support. By enabling the seamless integration of features like credential offer endpoints and pre-authorized code flows (OpenID4VCI), Inji Wallet will cater to real-world use cases with ease.

The mobile and web interfaces of Inji Wallet will support high-performance operations, maintaining accessibility even in low-connectivity environments. With robust user login and profile management features, along with integration of play integrity on Android, the wallet will ensure a scalable, secure, and privacy-focused user experience.

By 2025, Inji Wallet aims to be a reliable, standards-compliant digital wallet, empowering users to manage their credentials while fostering trusted data exchange and seamless interoperability within the verifiable credentials ecosystem.

Inji Mobile

Quarter🗓️	Feature 🛠️	Details 📊	Status 📝	Release 📌	Notes 📖
Q1	iOS Keystore: RSA, ECC R1/K1, Ed25519 Key Generation Support	ECC_Key_Support	🟢 Completed	v0.15.0
Q1	OpenIDVP : Cross-Device Flow	OpenID4VP	🟢 Completed	v0.15.0
Q1	Support of mDL/mDoc Credentials	mDoc/mDL_Wallet-Support	🟢 Completed	v0.15.0
Q2	Cross-Device Enhancements for Credential Sharing ( OpenIDVP :Verifier Metadata Management)	Cross-device-flow_Enhancements	🟢 Completed	v0.16.0	Moved to: Q2
Q2➕	VC Verifier SDK (Kotlin): ECC K1 Verification Support	ECC_Key_Support	🟢 Complete	v0.17.0	Added to Q2
Q2➕	Sharing of mDL/mDoc via OpenIDVP	mDoc/mDL_Wallet-Support	🟢 Complete	v0.17.0	Added to Q2
Q2➕	Complaint to Draft 23 of OpenIDVP Spec	Draft23_OpenIDVP	🟢 Complete	v0.17.0	Added to Q2
Q2➕	WLA login through deep link in iOS	Deeplink_login	🟢 Complete	v0.17.0	Added to Q2
Q2↑	Same Device Flow: Multiple credential requests during the presentation (OpenIDVP)	OpenIDVP_SameDevice_Flow	🟢 Complete	v0.17.0	Moved to Q2 to Q3
Q3	OpenID4VCI Support for credential offer endpoint and pre-authorised code flow	OpenIDVCIEnhancement	🟢 Complete	v0.18.0
Q3↓	Support for SD-JWT Credentials Format	SD_JWT	🟠 In-Progress	v0.19.0	Moved to Q3 from Q2
Q4↓	W3C Data Model 2.0 & SVG Render Method	WalletRendering & svgTemplate	🟠 In-Progress	v0.20.0	Moved to Q4 from Q2
Q4➕	Selective Disclosure via OpenIDVP	SD_JWT	🔵 Planned	v0.20.0	Added to Q4
Q4	Support for JWT Credentials Format	JWT_VC_Support	🟠 In-Progress	v0.21.0
Q4+	Presentation During Issuance	presentation_during_issuance	🔵 Planned	v0.21.0	Added to Q4
Q4↓	Credential Revocation	Credential_Revocation	🔵 Planned	v0.21.0	Moved to Q4 from Q3
Q4	Support for Advanced Cryptographic Keys (ECC R1)	ECC_Key_Support	🔵 Planned	v0.21.0
2026↓	Wallet Login with Unified Key Management	Holder Login	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Profile Creation Using a Single Credential	User_profile	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Secure Key Recovery with Shamir’s Secret Sharing	Sharmir's-OpenStandard_Implem	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Advanced Privacy Features with BBS+	BBS+	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Android App Security with Play Integrity	App integrity	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Multi-User Family Credentials	Multi-user_Credentials	🔵 Planned	NA	Q4 Moved to 2026
2026↓	One-Time Use Credentials for Privacy	One-time_Credentials	🔵 Planned	NA	Q4 Moved to 2026
2026↓	Secure Wallet Setup with Key Binding (SIOP)	SIOP	🔵 Planned	NA	Q1 Moved to 2026

Inji Web

Quarter 🗓️	Feature 🛠️	Details 📊	Status 📝	Release 📌	Notes 📖
Q1	Enabling VC Validity for Verification		🟢 Complete	v0.11.0
Q1	Enable RSA256 Signature Suites for Guest Login(without login)		🟢 Complete	v0.11.0
Q2	Enabling customisation of PDF Template		🟢 Complete	v0.12.0
Q3+	User Login with IDP	User Login	🟢 Complete	v0.13.0	Added to Q3
Q3+	Enable RSA256 Signature Suites for Login Flow		🟢 Complete	v0.13.0
Q3↓	Enable Ed25519 2018 and 2020 Signature Suites for Login Flow	ED25519_Key-Support	🟢 Complete	v0.13.0
Q3↓	Enable ECC K1 Signature Suites for Login Flow	ECC_Key_Support(Web)	🟢 Complete	v0.13.0
Q4↓	SD-JWT Credential Support	SD JWT VC	🟠 In-Progress	v0.14.0	Moved to Q4 from Q3
Q4+	Enable Ed25519 2018 and 2020 Signature Suites for Guest Login (Without Login)		🟠 In-Progress	v0.14.0	Added to Q4
Q4+	Enable ECC K1 Signature Suites for Guest Login (Without Login)		🟠 In-Progress	v0.14.0	Added to Q4
Q4+	OpenIDVP Support for SD-JWT	SD JWT VC	🔵 Planned	v0.15.0	Added to Q4
Q4	Support for Advanced Cryptographic Keys (ECC R1)	SIOP_Key_Binding	🔵 Planned	v0.15.0
Q4↓	Credential Revocation	VC Revocation	🔵 Planned	v0.15.0	Moved to Q4 from Q3
Q4↓	W3C Data Model 2.0 & SVG Render Method	VCRendering	🔵 Planned	v0.15.0	Moved to Q4 from Q1
2026↓	Secure Key Recovery Using Shamir’s Secret Sharing	Sharmir's-OpenStandard_Implem	🔵 Planned	NA	Q2 Moved to 2026
2026↓	Support for mDoc/mDL Credentials	VC Formats	🔵 Planned	NA	Q2 Moved to 2026
2026↓	CBOR Credential Format Support	CBOR_VC_Support	🔵 Planned	NA	Q2 Moved to 2026
2026↓	OpenID4VCI Support for credential offer endpoint and pre-authorised code flow	OpenID4VCI Enhancements	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Advanced Privacy with BBS+ Support	BBS+_Support	🔵 Planned	NA	Q3 Moved to 2026
2026↓	One-Time-Use Credentials for Privacy	One-time_Credentials	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Multi-User Family Credentials	Multi-user_Credentials	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Support for JWT Credentials	ECC_Key_Support(Web)	🔵 Planned	NA	Q3 Moved to 2026
2026↓	Unified Key Management for Web & Mobile	Key_Management_Wallet	🔵 Planned	NA	Q1 Moved to 2026

Inji Certify

Vision

The goal of Inji Certify for the rear 2025 is to provide a comprehensive and user-centric platform for issuing, managing, and verifying credentials, tailored to meet the diverse needs of individuals, organizations, and issuers. With support for multiple credential formats (e.g., SD-JWT, mDoc/mDL), advanced cryptographic standards (ECC, BBS), and privacy-preserving mechanisms, the platform ensures secure and flexible credential handling.

By enabling features like multi-issuer onboarding, deferred issuance, subject-holder relationship management, and one-click authorization during issuance, Inji Certify addresses real-world scenarios such as sharing family credentials, automating bulk credential generation, and simplifying issuer interactions. The integration of offline capabilities (e.g., printable QR-embedded credentials) and scalable architecture ensures accessibility, even in low-connectivity environments, while maintaining performance benchmarks of up to 1 million credentials per day.

Inji Certify’s vision is to foster trust and interoperability in the digital identity ecosystem, empowering users with control over their credentials while providing issuers with a reliable and standards-compliant platform.

Quarter 🗓️	Feature 🛠️	Details 📊	Status 📝	Release 📌	Notes 📖
Q1	Local deployment using docker compose	Local_Deplyment	🟢 Completed	0.10.1
Q1	Support for VC data model 2.0	Data_Model_2.0	🟢 Completed	0.10.1
Q1	Implementation of Data Provider Plugin	Data_Provider_plugin	🟢 Completed	0.10.1
Q1	ED25519 (2018 & 2020) VC Signing	ED25519_Key_Support	🟢 Completed	0.10.1
Q2	Support for ECC K1	ECC_K1_Key_Support	🟢 Completed	0.11.0	Moved to Q2 from Q1
Q2+	Support for ED25519 (2018 & 2020)	ED25519_Key_Support	🟢 Completed	0.11.0	Added to Q1
Q2+	OAuth Support with external authentication	OAuth_Support	🟢 Completed	0.11.0	Added to Q1
Q3↓	Add New Credential Type to Issuer	Add_New_VC	🟢 Completed	0.12.0	Moved to Q3 from Q2
Q3↓	Support for ECC R1	ECC_R1_Key_Support	🟢 Completed	0.12.0	Moved to Q3 from Q1
Q3+	Support for Data Integrity	Data_Integrity	🟢 Completed	0.12.0	Added to Q3
Q3↓	Credential Revocation Mechanism	revocation_mechanism	🟠 In-Progress	0.12.0 & 0.13.0	Moved to Q3 from Q1
Q3↓	Credential Formats Support for - SD JWT	SDJWT_VC_Format_Support	🟠 In-Progress	0.12.0 & 0.13.0	Moved to Q3 from Q1
Q3↓	Credential Formats Support for -mDoc	mDoc_Format_Support	🟠 In-Progress	0.13.0	Moved to Q3 from Q2
Q3↓	Pre-authorized Code Flow	pre-authorized-code-flow	🔵 Planned	0.14.0	Moved to Q2 from Q1
Q3↓	Presentation during issuance of Credential	presentation_during_issuance	🔵 Planned	0.14.0	Moved to Q3 from Q2
Q3+	Claim 169 Support with QR Code Generation	QRCode_Generation	🔵 Planned	0.14.0	Added to Q3
Q3↓	Anon Credential	anon_cred	🔵 Planned	TBD	Moved to Q3 from Q2
Q3	VC Generation: Create Credentials from the Request Payload	W3C_VC_Issaunce_API	🔵 Planned	TBD
Q3	Multi-issuers: Onboarding of multiple issuers	multi-issuers	🔵 Planned	TBD
Q3	Subject Holder relationship for VC	subject_holder_relationship	🔵 Planned	TBD
Q3	Allow bulk generation of onetime credentials	bulk_batch_issuance	🔵 Planned	TBD
Q4	Deferred Credential Endpoint	deferred_credential	🔵 Planned	TBD
Q4	Multi-User Credentials	multi_user_cred	🔵 Planned	TBD
Q4	Issue a physical credential (PDF / Printable)	presentation-based-plugin	🔵 Planned	TBD

Inji Verify

Vision

Our vision for 2025 is to position Inji Verify as the go-to tool for seamless and secure credential verification. We aim to deliver easily configurable UI components for third-party verifier portals, tailored to meet the diverse needs of organizations across the globe. With support for multiple credential formats (SD-JWT, mDoc/mDL, W3C) and advanced cryptographic standards (ECC), Inji Verify ensures flexible and secure credential handling.

Inji Verify fosters trust and interoperability in the digital identity ecosystem. By introducing features like multi-proof capabilities, QR Based Verifiable Presentation in Same Device, SVG Rendering post VC verification, able to identify revoked credentials during verification, able to support credential correction, verification of documents with multiple QR codes, BLE Based verifiable presentation - Inji Verify will redefine user experience and reliability. With a focus on performance , enhanced design for an intuitive look and feel, and adherence to global standards (Data Model 1.1/2.0), the GA release will set new benchmarks for stability, usability, and excellence in digital verification.

Quarter 🗓️	Feature 🛠️	Details 📊	Status 📝	Release 📌
Q1	OpenIDVP: Cross Device Flow (QR code based Verifiable Presentation)	OpenIDVP_CrossDeviceFlow	🟢 Completed	0.11.0, 0.11.1, 0.12.3
Q1	Upgrades in OpenID4VP - Draft 21 specification	Draft21_OpenIDVP_adoption	🟢 Completed	0.11.0
Q1	Inji Verify SDK: OpenID4VP- VP Verification component (cross device flow) and publish as an NPM module	InjiVerify_SDK	🟢 Completed	0.12.3
Q1	Migration of Inji Verify backend from H2 in memory DB to PostgreSQL DB	InjiVerify_Backend_Migration	🟢 Completed	0.12.3
Q2	Inji Verify SDK: Scan/ Upload Component and publish as an NPM module	InjiVerify_SDK	🟢 Completed	0.13.0
Q2	Server Setup for VC and VP Proof Verification in vc-verifier library	VC_VP_Proof_Verification	🟢 Completed	0.13.0
Q3	OpenIDVP Same Device Flow (via deeplink): Integrate to Inji Verify SDK	OpenIDVP_Same_Device_Flow	🟠 In-Progress	0.14.0
Q3	OpenID4VP Draft 23: Implement DID-based client_id Scheme	OpenIDVP_Draft23_Adoption	🟠 In-Progress	0.14.0
Q3	OpenID4VP: Authorization Request via request_uri for did client id	OpenIDVP_Auth_Request	🟠 In-Progress	0.14.0
Q3	OpenIDVP: Same Device Flow (via DC API)	OpenIDVP_Same_Device_Flow	🟠 In-Progress	0.14.0
Q3	SD JWT (IETF) VC and VP support	SD-JWT_Support	🔵 Planned	0.15.0
Q4	Support Server Side VC Verification: ECC- K1 and R1	ECC-K1_R1_Support	🔵 Planned	0.16.0
Q4	Inji Verify SDK Support apart from React applications for Wider Framework Compatibility	InjiVerify_SDK	🔵 Planned	TBD
Q4	Claim 169 QR Code	Claim_169_QRCode	🔵 Planned	TBD
Q4	Verify SD- JWT (W3C) VC	SD_JWT_Support	🔵 Planned	TBD
Q4	Revoked Credentials	Credential_Revocation	🔵 Planned	TBD
Q4	Verify mDoc and mDL	mDoc_mDL_Support	🔵 Planned	TBD
2026	OpenID4VP - Cross device and same device flows alongside Web wallets		🔵 Planned	NA
2026	Templatizing post-VC verification (SVG Rendering)	SVG_Rendering	🔵 Planned	NA
2026	Support for Country QR code - CWT Format	Country_QR_Code	🔵 Planned	NA
2026	Multi-language Support for VC during verification	Multi_Language_Support	🔵 Planned	NA
2026	Verify document(pdf) with multiple QR Codes	Multiple_QR_Verification	🔵 Planned	NA
2026	Support for multi proof: Single credential should support multiple proofs	Offline_SDK_Verification	🔵 Planned	NA
2026	GA Release	InjiVerify_LTS_B1	🔵 Planned	NA
2026	Credential Correction	Credential_Correction	🔵 Planned	NA
2026	Offline Verification SDK	Offline_Verification_SDK	🔵 Planned	NA
2026	BLE based verifiable presentation	InjiVerify_BLE_Verification	🔵 Planned	NA