Version 0.16.0
Release Name: Inji Verify v0.16.0
Support: Developer Release
Release Date: 19th December, 2026
Overview
We are excited to announce the release of Inji Verify v0.16.0. This version introduces the revocation feature, multi-lingual support, SVG Rendering, and MOSIP UIN VC Verification.
New Features
Revocation: Inji Verify now supports real-time revocation checks using the W3C BitString Status List 2021 mechanism. During verification, the system reads the credentialStatus field, fetches the issuer’s Status List Credential, validates its proof, and determines whether the credential is valid, revoked, suspended, or invalid. The verification result is displayed clearly while preserving the VC’s original layout. This enhancement ensures secure, privacy-preserving, standards-compliant verification without exposing user data.
Multi-Lingual Support: Inji Verify now supports viewing credential data and verification results in multiple languages. The system auto-detects the browser language (defaulting to English) and displays all VC claims, metadata, and validation outcomes accordingly. Users can switch languages without affecting verification results or credential layout, ensuring clarity and consistency across regions.
SVG Rendering: Inji Verify now supports rendering Verifiable Credentials using SVG templates, ensuring the credential’s original design, layout, fonts, and branding remain intact. Verification results (Valid/Invalid/Expired) are overlaid seamlessly without altering the visual integrity. The system also supports uploading QR codes in SVG and other compatible formats, with improved error handling, consistent UI, and accessibility compliance.
MOSIP UIN VC Verification: Inji Verify now fully supports the verification of MOSIP-issued UIN Verifiable Credentials, enabling seamless, secure, and standards-based validation of identity information. The system automatically decodes the UIN VC, validates its cryptographic proof, checks its revocation status, and displays a clear verification outcome—while preserving the credential’s original visual design. This enhancement ensures verifiers can confidently authenticate MOSIP UIN credentials across services, improving interoperability, trust, and user experience within the MOSIP ecosystem.
Tips:
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
Projects: Released
Inji Verify Repo → 4 projects (all these projects are of same version) as below:
ii) inji-verify-ui (ref implementation)
iii) SDK
iv) API-Test
v) UI-Test
Compatible modules
The following table outlines the tested and certified compatibility of Inji Verify 0.16.0 with other modules.
Bug Fixes
Below is the list of fixes as part of the 0.16.0 release, For the list of the total bugs which got fixed, refer here.
Request verifiable credential button is not aligned in arabic language RTL
Premature Expiry and Page Reload When Verifying VCs Sequentially
Incorrect Error Message Displayed on VC Verification
Mis-alignment in "download" and "open in flow" button
Secuirty testing: inji-verify(0.16.0) - docker vulnerabilities as per Snyk report
Language dropdown values are missing locators to locate them
Unable to verify a newly created vc in qa-inji1 environment
For farmer VC we are seeing N/A in Inji Verify UI
Getting error when we try to upload a TAN VC
Cross device flow is failing in specific set of device
Same device flow is failing in specific set of device
Old MOSIP data share VC verification is failing
Fix the "reliability bugs" in sonar for "verify-ui" in "develop" branch
Security testing: Inji-verify :Using user-controlled data in methods such as innerHTML, outerHTML
Security testing: Inji-verify: Using setAccessible(true) issue
Security testing: inji-verify :Using dynamic expressions to access object properties
Security testing: update vulnerable libraries in api-test/pom.xml & ui-test/pom.xml as per Snyk report
Security Testing (0.14.0 / 0.16.0): License Compliance Issue
Support SD-JWT verification submitted via "/vc-submission" in the "/vp-result/{transactionId}"
In mobile view we dont have copyrights-content present in upload screen
Error message for expired scan scenario is not proper
Scan and Upload component's loading bar is not aligned in middle
injiweb: no.of field values in VC document and scanned documnet are not the same
The MOSIP UIN VC's created from reg-client are not verifiable from INJI-verify
User Stories
Jira ID
Description
For same-device verification, some devices may experience browser background throttling after the wallet POST, leading to long-polling /status timeouts and resulting Verifier UI errors. To address this, the /vp-submission/direct-post endpoint now includes a redirect_uri in its response body, enabling OpenID4VP Web Online Sharing to provide a more reliable fallback flow.
Inji Verify supports full verification of MOSIP UIN VCs, including proof validation and revocation checks, for trusted identity authentication.
Inji Verify now displays VC data and verification results in multiple languages with automatic detection and seamless language switching.
Inji Verify now renders VCs using SVG templates to preserve original design while overlaying verification results without altering visual integrity.
Inji Verify now performs real-time revocation checks using W3C Status List 2021, ensuring secure and privacy-preserving validation of credential status.
Inji Verify now supports SD-JWT credential submissions via /vc-submission, automatically generating a transactionId when one is not provided and storing the credential for processing. Verifiers can then retrieve the full VC and its verification status through /vp-result/{transactionId}, enabling seamless end-to-end SD-JWT verification.
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.
User friendly error message is not displayed for expired session scenario
INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
The MOSIP UIN VCs generated via reg-client are currently not verifiable through INJI Verify.
Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
Documentation
Last updated
Was this helpful?