The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
Testing scope has been focused on the below features:
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers.
iPhone using Safari, Edge, Firefox and Chrome browsers.
MAC using Safari Edge, Firefox and Chrome browsers.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel using Chrome, edge, Firefox and Safari browsers.
Windows laptop with a front camera of 2 megapixel using Chrome, edge, and Firefox browsers.
Mobile Android phone Tablet with back camera 16 megapixel using browsers Chrome, Edge and Firefox browsers.
iPhone and iPad with 12 megapixels back camera Chrome, edge, Firefox and Safari browsers.
OVP functionality Verification with current INJI Verify version:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers, 0.17.0 INJI-mobile.
iPhone using Safari, Edge, Firefox and Chrome browsers, 0.17.0 INJI-mobile.
MAC using Safari Edge, Firefox and Chrome browsers.
Below are the results for Upload, Scan and OVP flow functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. Functional test was performed in combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: 7e1352eae4a0c9090bb15c4be234696d88ecf653
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: 1c3dd7f1144efdf7cab078315fc536af0ad6f960
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for more of the reports is .
Verified in low light to scan the QR code
Verified scan with blur, cracked, low quality QR codes was verified
584
511
66
0
10
10
0
0
27
27
0
0
Note : OVP flow supports 0.16.0 inji-mobile build only
Test Rate: 100%, With Pass Rate: 88%
Test Rate: 100% With Pass Rate: 100%
Test Rate: 100% With Pass Rate: 100%
Release Name: Inji Verify v0.13.0
Support: Developer Release
Release Date: 24th July, 2025
We are thrilled to announce the release of Inji Verify 0.13.0 that enhances Verifiable Credential (VC) verification capabilities and streamlines ease of integration with relying party applications.
1. Inji Verify SDK- Scan & Upload component: Inji Verify provides modular SDK components that empower verifier (relying party) applications to seamlessly integrate Verifiable Credential (VC) verification workflows—without relying on the full Inji Verify reference application.
Modular NPM Package: The Scan & Upload component is available as a standalone NPM module, promoting modularity and simplifying integration. Developers can incorporate it into their projects without depending on the full Inji Verify repository.
Comprehensive Integration Guide: A detailed is provided, explaining the setup and usage to ensure a smooth integration process. The steps are also available in the .
Framework Compatibility: Currently, this component is compatible exclusively with verifier applications built using React and TypeScript. Support for additional frameworks and languages is planned for upcoming releases.
Note: The Inji Verify UI is provided as a reference implementation to demonstrate how the SDK components can be orchestrated in a full-fledged verifier application. It is not required for adoption. Developers are encouraged to selectively embed only the components relevant to their business and technical needs.
Note: Inji Verify SDK- Scan / Upload component supports React version- 18.2.0
2. Server Setup for VC and VP Proof Verification in vc-verifier library
The vc-verifier library has been integrated into Inji Verify to enable server-side verification of both Verifiable Credentials (VCs) and Verifiable Presentations (VPs).
Originally designed for credential-level cryptographic and schema validation, the library has now been enhanced to support VP proof verification as per OpenID4VP specifications, ensuring end-to-end trust and compliance.
Key Capabilities:
VP Proof Verification for OpenID4VP flows
VC Proof Verification for OpenID4VCI flows
Support for key types: Ed25519VerificationKey2018, Ed25519VerificationKey2020, and RSAVerificationKey2018
Verification Methods: did:key and did:jwk
1. Support for JsonWebSignature2020 with Ed25519 algorithm type for VP verification : VC-Verifier library supports JsonWebSignature2020 with Ed25519 algorithm for Verifiable Presentation (VP) verification, so that we can process VPs secured with this cryptographic standard and ensure broader interoperability for presentation flows.
2. Configuration of DB Parameters: Database parameters like DB Name, DB Schema, and JDBC URL which were hardcoded earlier, are now dynamically configurable, so that deployments can be made more flexible, environment-specific, and manageable through configuration.
3. Integration of Swagger locally with the Inji Verify API service so that developers can easily access and test the API documentation without relying solely on the published Stoplight documentation.
4. Migration all the JSONB fields to TEXT in Inji Verify database so that we can improve database performance, as we are not utilizing JSON-based filtering and TEXT will better suit our use case.
OpenID4VP Draft 21 enhancement by streamlining the authorization response structure and eliminating unnecessary metadata.
Inji Verify Repositories: 4 projects (all these projects are of same version) as below:
inji-verify-service -
inji-verify-ui (ref implementation) -
SDK -
API-Test -
The following table outlines the tested and certified compatibility of Inji Verify 0.13.0 with other modules.
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
Below is the list of fixes as part of the 0.13.0 release:
Credential & Presentation Expiry Checks
Robust Error Reporting for failed verifications. This enhancement ensures the verifier backend meets security and interoperability standards while maintaining extensibility for evolving DID-based ecosystems.
Inji Verify
vc-verifier library
Inji Mobile Wallet
Inji Web Wallet
Pixel-Pass library
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.
Inji Verify SDK- Scan & Upload component.
Publish Scan & Upload component as a separate NPM module.
Implement Docker Compose setup for Inji Verify Service.
The online sharing VCs- OpenID4VP flow remains stuck in the loading state for both Upload and Scan methods.
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.
NPM warnings are preventing the Sonar analysis from being triggered./td>
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.
VP Proof Verification in VC- Verifier library.
Add support for JSON Web Signature 2020 using Ed25519 algorithm for Verifiable Presentation (VP) verification.
Add support for JSON Web Signature 2020 using Ed25519 algorithm for Verifiable Presentation (VP) verification.
Configure database parameters.
Integrate Swagger for API documentation in the Inji Verify backend.
Migrate all JSONB fields to TEXT data type.
OpenID4VP Draft 21: Update Authorization Response to remove unnecessary metadata.
Inji Verify remained unstable for a certain duration.
Multi-language support is not available (enhancement).
After uploading and verifying the QR code, the retrieved data should display the full name as the first field in the VC result area.
Unable to scan the Sunbird QR code on Mobile, Windows, or Mac devices.
On Windows, users do not receive an appropriate error message when uploading a file in an unsupported format.
Users occasionally face difficulty scanning valid Sunbird RC QR codes on mobile devices.
A 502 error is encountered after uploading a PDF file.
Tapping the 'Scan' button on iOS devices makes the scan screen unexpectedly scrollable.
The ‘Download’ button of verified VC is not properly aligned on the UI.
VC sorting functionality in the VP verification- Credential Selection panel is not working correctly.
API tests are failing following the VC Verifier integration.
UI tests are failing after integrating the Scan and Upload SDK.
VP Request QR code generation is failing.
Verification of Datashare VCs is slower than expected.
The API automation report indicates a failure in the 'GetVpTokenForRequest' method.
VC verification fails when the credential is downloaded from the Inji Web application.
VP verification is not compatible with Inji Mobile version 0.17.0 as the sprint build did not have the entire design in place to be compatible.