> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/releases/version-0.14.0.md). # Version 0.14.0 **Release Name**: Inji Verify v0.14.0 **Support**: Developer Release **Release Date**: 30th September, 2025 ### Overview We are excited to announce the release of **Inji Verify v0.14.0**, which brings significant enhancements to OpenID4VP - Same Device flow support, SDK modularization and improvements in verification result handling. ### New Features **1. OpenID4VP Same-Device flow via deeplink:** Inji Verify now supports the OpenID4VP Same Device Flow, allowing verifier and wallet to operate on the same mobile device. * Verifier sends an Authorization Request with `presentation_definition` via deep link. * Wallet authenticates the user, collects consent, and returns a `vp_token` via redirect (`response_mode=direct_post`). * Inji Verify parses the vp\_token, validates credentials, and displays results with statuses: Valid, Valid but Expired, Invalid. * Multiple VCs displayed in card format, expandable details, color-coded statuses, and JSON download option. * This feature provides a seamless, app-like experience on same mobile device without requiring a second device. **2. Inji Verify SDK- OpenID4VP- VP verification component** where same device flow (point 1) functionality is incorporated * **Modular NPM Package:** : Released as a standalone TypeScript component for seamless integration into verifier/relying party apps. * **Easy Integration:** Comes with a step-by-step [integration guide](https://github.com/mosip/documentation/blob/inji/docs/technical-overview/integration-guides/openid4vp-vp-verification-integration-guide.md) and [README](https://github.com/mosip/inji-verify/blob/release-0.13.x/inji-verify-sdk/Readme.md).​ * **Compatibility:** Supported for React + TypeScript verifier apps (React 18.2.0); broader framework/language support planned in future releases. **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. ### Additional Enhancements: **1. OpenID4VP – QR Codes via `request_uri`:** Inji Verify now supports QR codes that reference the Authorization Request via `request_uri` instead of embedding it directly. * Wallets resolve the request by performing an HTTP GET to the hosted request object. * This reduces QR code size, improves security (request hosted on trusted verifier servers), and alignment with OpenID4VP best practices. **2. DID-based client\_id:** Aligned with OpenID4VP Draft 23, Inji Verify now supports DID-based `client_id` values, replacing the deprecated `client_id_scheme`. This improves interoperability and trust through decentralized identifiers. **3. VP verification results display:** * Verification results now display **all originally requested credentials**, including any newly shared after a missing credential prompt. * Status clearly shown (Valid, Invalid, Valid but Expired) with completion confirmation once all checks are done. ### Repositories: Released/Dependent | Repositories | Tags: Released/Dependent | | ------------ | ------------------------------------------------------------ | | Inji Verify | [v0.14.0](https://github.com/mosip/inji-verify/tree/v0.14.0) | ### Projects: Released Inji Verify Repositories: 4 projects (all these projects are of same version) as below: 1. Inji Verify Service - [0.14.0 Inji Verify service](https://github.com/mosip/inji-verify/tree/release-0.14.x/verify-service) 2. Inji Verify UI (ref implementation) - 3. SDK - 4. API-Test - ### Compatible modules The following table outlines the tested and certified compatibility of Inji Verify 0.14.0 with other modules.
ModuleVersion
Inji Mobile Wallet0.18.0
Inji Web Wallet0.13.0
Pixel-Pass libraryv0.6.0
vc-verifier libraryv1.4.0
### 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.](https://mosip.atlassian.net/issues/?jql=project%20%3D%20%22INJIVER%22%20AND%20status%20not%20in%20%28Closed%2C%20Canceled%29%20AND%20type%20%3D%20Bug%20ORDER%20BY%20created%20DESC)
Jira IDDescription
INJIVER-1061In OpenID4VP (Cross device) component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
INJIVER-1131The 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.
INJIVER-1062We 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.
INJIVER-1063On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
INJIVER-625Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
INJIVER-1194INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
INJIVER-1220User friendly error message is not displayed for expired session scenario.
INJIVER-1069The MOSIP UIN VCs generated via reg-client are currently not verifiable through INJI Verify.
INJIVER-979Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
### User Stories
Jira IDDescription
INJIVER-526OpenID4VP Same-Device flow via deeplink, allowing verifier and wallet to operate on the same mobile device.
INJIVER-1127Integrate OpenID4VP- VP verification component (same device flow) in Inji Verify SDK.
INJIVER-1140OpenID4VP Draft 23- Implement DID based client id scheme.
INJIVER-1213OpenID4VP: Authorisation Request via request_uri for did based client id.
INJIVER-1235Removal of wallet selection panel in OpenID4VP Same device flow (mobile).
INJIVER-1100Display VC result of all credentials originally requested after missing credentials have been shared from mobile wallet successfully.
### Bug Fixes Below is the list of fixes as part of the 0.14.0 release:
Jira IDDescription
INJIVER-1278Data share VC verification is failing.
INJIVER-1264Timeout error occurs in /vp-request/{request_id}/status() for Same Device Flow on Android after successful VP submission.
INJIVER-1262VP verification in Cross-Device Flow causes the iOS Inji Mobile app to crash.
INJIVER-1261VP verification in Same-Device Flow causes the iOS Inji Mobile app to crash.
INJIVER-1230SDK README on the NPM site is not updated.
INJIVER-1221Same Device Flow is not fully developed.
INJIVER-1217After scanning a QR code, clicking on 'Verify Another QR Code' sometimes causes the camera to freeze with a black screen.
INJIVER-1201The Verifiable Credential Selection Panel is not set as the default option.
INJIVER-1198UI Automation README is outdated and not aligned with recent changes.
INJIVER-1191Add provision to send transactionID for VC submission from the Relying Party.
INJIVER-1186The Verifiable Credential Panel contains duplicate element IDs.
INJIVER-1181NPM warning prevents Sonar analysis from being triggered.
INJIVER-1163Security testing identified a camera access issue in Inji Verify.
INJIVER-1139Overlapping text appears at the bottom of the screen during the ‘Initiate VP Request’ process.
INJIVER-1090Unable to verify two scenarios in the OVP flow.
INJIVER-1067Language selection is not applied consistently across the entire screen.
INJIVER-939Button label and layout are misaligned.
### Documentation * [Feature documentation](https://docs.inji.io/inji-verify/overview/features) * [Integration Guide](https://docs.inji.io/inji-verify/technical-overview/integration-guides/openid4vp-vp-verification-integration-guide) * [API Documentation](https://mosip.stoplight.io/docs/inji-verify) * [Collab Guide](https://docs.inji.io/inji-verify/functional-overview/releases-1/inji-verify-collab-guide) * [QA Report](https://docs.inji.io/inji-verify/releases/version-0.14.0) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.inji.io/inji-verify/releases/version-0.14.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.