Version 0.17.0
Coming Soon!
Release Name: Inji Verify v0.17.0
Support: Developer Release
Release Date: March 2026
Overview
We are excited to announce the release of Inji Verify v0.17.0. This version introduces enhancements in API design for /vc-verification endpoint and the /vp-result/{txnId} endpoint and verification support for Claim 169 QR code.
New Features:
API Redesign:
We have redesigned the Inji Verify /vc-verification endpoint so that it provides more than just the final status (SUCCESS / INVALID / EXPIRED / REVOKED). The response now includes additional details that allow the relying party application to determine the next steps.
Similarly, the /vp-result/{txnId} endpoint is updated to return richer information for each credential, rather than only the final status, enabling the relying party to make informed decisions.
Claim 169 QR Code Verification: Standardized Compact Credential Encoding: Inji Verify now supports verification of Claim 169-encoded QR credentials—an IANA-registered MOSIP standard (1.1.0) for compact, cryptographically-signed identity QR codes. This standardized encoding enables efficient credential delivery and verification across diverse deployment scenarios. What This Enables:
QR Code Verification: Scan or upload Claim 169 QR codes through camera scanning (versions 1–v27) or document upload (versions 1–v32).
CBOR Decoding & Signature Validation: Automatically decode CBOR-encoded QR payloads and validate Ed25519 cryptographic signatures to authenticate credential authenticity.
Selective Attribute Verification: Handle credentials containing multiple QR codes, each encoding different identity attributes (demographic data, biometrics) for granular verification workflows.
Flexible Deployment: Support for scenarios where compact QR-based credential presentation is required.
Technical Implementation: Integration with PixelPass library (v0.7.0) for CBOR decoding, enhanced /vc-verification endpoint for detailed validation diagnostics.
Note: The Inji Verify UI is a reference implementation to demonstrate orchestration. Developers can selectively embed SDK components in the verifier applications as per their needs.
Repositories: Released/Dependent
Inji Verify
v0.17.0
Projects: Released
Inji Verify Repo → 4 projects (all these projects are of same version) as below:
i) inji-verify-service - <Insert Link Here>
ii) inji-verify-ui (ref implementation) - <Insert Link Here>
iii) SDK - <Insert Link Here>
iv) API-Test - <Insert Link Here>
Compatible modules:
The following table outlines the tested and certified compatibility of Inji Verify 0.10.0 with other modules.
Bug Fixes
Below is the list of fixes as part of the 0.17.0 release, for the complete list refer here.
User Stories:
As a Verifier, I should be able to Upload and Scan to Verify the VCs with claims mapped to Claim 169 (for single QR code)
The /vc-verification and /vp-result/{txnId} endpoints have been enhanced to return detailed verification information in addition to the final status. These richer responses enable relying party applications to understand verification outcomes better and make informed decisions on next steps.
Known Issues
Below is a list of some key known issues. For a detailed overview and the complete list of issues related to Inji Verify, please click here.
In OpenID4VP (Cross device)component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
The OpenID4VP (Cross device) component in Inji Verify currently validates a presentation as successful even when a wrong Verifiable Credential (VC) is submitted. As a temporary workaround, implement credential type validation on the Relaying Party (RP) side, by verifying that the received VC matches the expected type defined in the original presentation_definition.
We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
Documentation
QA Report
Last updated
Was this helpful?