> 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-1.0.0-alpha.1.md). # Version 1.0.0-alpha.1 **Release Name**: Inji Verify v1.0.0-alpha.1 **Support**: Developer Release **Release Date**: 4th August, 2026 {% hint style="success" %} **Upgrade Notes**: Refer to '[Migrating from PEX to DCQL](/inji-verify/technical-overview/integration-guides/transition-from-pex-to-dcql.md)' guide to upgrade to DCQL and also refer to '[Removals & Replacements](#removals--replacements)' in this release. {% endhint %} {% hint style="success" %} **Notes**: * **Inji Verify v1.0.0-alpha.1** marks our formal adoption of the OpenID4VP 1.0 specification. This is an important milestone, and we want to provide clear guidance for all community members. * **Upgrading Guidance - Upgrading is optional but recommended** for teams ready to align with the finalized OpenID4VP 1.0 specification. Earlier 'Inji Verify' releases built on draft specifications remain fully functional, and can be continued without disruption, with the option to upgrade at a time that suits your roadmap. * **Legacy Support -** Note that this release **does not maintain full backward compatibility** with draft specification implementations. Limited support for Presentation Definition (PD) based sessions is retained on result-fetch endpoints only, allowing existing integrations to keep working through the transition. * APIs, credential formats, and endpoints that have been updated or replaced are detailed in [API Documentation](/inji-verify/api/api-changes.md). **Reviewing these sections before upgrading is strongly recommended.** {% endhint %} ### **Overview** We are excited to bring the release of **Inji Verify v1.0.0-alpha.1.** This release completes Inji Verify's move to DCQL (Digital Credentials Query Language) — the [OpenID4VP 1.0](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) way of describing what a verifier needs from a wallet — across the entire verification flow: authorization requests, VP token submission, validation, and results. The core change is the migration from Presentation Exchange (PEX) to [**DCQL** (Digital Credentials Query Language)](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#section-6). Presentation Exchange (`presentation_definition`) is no longer accepted for new requests; only previously completed PD-based verifications remain readable through the result-fetch endpoints. **Highlights** * **Stronger holder proof** — `require_cryptographic_holder_binding` lets verifiers demand cryptographic proof of holder possession for both SD-JWT VC and LDP\_VC presentations, replacing the older `acceptVPWithoutHolderProof` flag. * **Wider SD-JWT compatibility** — both `vc+sd-jwt` and `dc+sd-jwt` format identifiers are accepted, so wallets built against either the draft or final SD-JWT VC spec continue to verify. * **Replay protection** — KB-JWT `nonce` and `aud` claims are validated on every SD-JWT submission, so a captured presentation can't be resubmitted elsewhere. * **Tamper-resistant sessions** — VP request expiry and duplicate submissions are now enforced server-side, not left to the wallet to self-report. * **More accurate credential matching** — the Verify UI matches submitted credentials against DCQL `type_values`, keeping matches correct when multiple verifier configurations share a credential type. * **Spec-aligned protocol fields** — client ID scheme, `client_metadata` handling, and supported-formats fields are updated to match OpenID4VP 1.0. Full field-level detail: [API Changes](https://docs.inji.io/inji-verify/releases/pages/hhDN0MwzIPgWFzurfNZy#changes-which-came-with-inji-verify-1.0.0-alpha.1). {% hint style="info" %} **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. {% endhint %} ### **Repositories: Released/Dependent** **Inji Verify Repo** → 4 projects (all these projects are of same version) as below:
RepositoriesTags: Released/Dependent
vc-verifierv1.9.0
inji-verifyv1.0.0-alpha.1
### **Compatible modules** The following table outlines the tested and certified compatibility of Inji Verify v1.0.0-alpha.1 with other modules. | Module | Version | | ------------------ | ----------------------------------------------------------------- | | Pixel-Pass library | [0.8.0](https://docs.inji.io/inji-verify/releases/version-0.17.0) | | Inji Wallet | 1.0.0-alpha.1 (Release Coming Soon) | | Inji Web | 1.0.0-alpha.1 (Release Coming Soon) | ### **Bug Fixes** Below is the list of fixes as part of the **v1.0.0-alpha.1** release, refer [here](https://github.com/inji/inji-verify/issues?q=type%3ABug%20milestone%3A1.0.0-alpha.1) for the comprehensive list.
Bug IDDescription
#2086Verify library contributes global servlet context path when embedded in Certify.
#1919Upload valid claim 169 QR code shows invalid result intermittently.
#1920Scan QR Code feature returns invalid result for valid VC intermittently across multiple camera scenarios.
#2045Nonce validation gaps in VP request creation.
#2062Possible race condition in VP submission: status listener notified before transaction commits.
#1928Open INJI-Verify application Navigate to Verify Credentials Select Scan QR Code tab Disable internet connection (simulate offline mode) Click on Scan QR Code button Observe the behaviour after scan failure / retry.
### **User Stories**
Story IDDescription
#1721Changes in client_id did prefix as per OpenID4VP spec v1.0.
#1758Changes in client_metadata as per OpenID4VP spec v1.0.
#1765Handling client_metadata for Pre-registered client_id Scheme as per OpenID4VP spec v1.0.
#1768DCQL support in Authorization Request as per OpenID4VP spec v1.0
#1703Migrate OpenID4VP response handling from PEX to DCQL and implement vp_token validations.
#1935VP Token DCQL Query Satisfaction at Submission Stage.
#1957VP Result Processing & Validation (DCQL + Legacy Support).
#1961Inji Verify must support both vc+sd-jwt and dc+sd-jwt as credential format.
#1965Support require_cryptographic_holder_binding in DCQL during VP submission for LDP_VC.
#1988Support require_cryptographic_holder_binding in DCQL during VP submission for SD-JWT VC.
#1940Remove presentation_definition Table.
#2034Replace acceptVPWithoutHolderProof with DCQL require_cryptographic_holder_binding in Verify UI.
#1973Enforce VP Request Expiry and Prevent Duplicate VP Submission on Server Side.
#2049Verify UI: Match Submitted Credentials Using DCQL type_values Instead of Configuration type.
#2043Validate nonce and aud claims from Key Binding JWT (KB-JWT) for SD-JWT VP submissions.
### **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://github.com/inji/inji-verify/issues?q=type%3ABug%20-milestone%3A1.0.0-alpha.1%20-is%3Aclosed).
Issue IDDescription
#1845We 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.
#1844On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
#1852Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
#1789INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
#2178The latest Inji Verify release cannot support complete end-to-end testing of VP (Verifiable Presentation) flow and Data Share flow when integrated with Inji Web.
### **API Changes** Refer [here](/inji-verify/api/api-changes.md) for 'Changes to API' and 'New APIs'. ### Removals & Replacements The following are no longer supported in this release. See the [PEX to DCQL Migration Guide](/inji-verify/technical-overview/integration-guides/transition-from-pex-to-dcql.md) to update existing integrations.
RemovedReplaced ByWhat This Means
Presentation Exchange (presentation_definition, presentationDefinitionId)DCQL (dcql_query)New requests using PD are rejected; previously completed PD-based results remain readable via result-fetch endpoints only.
acceptVPWithoutHolderProofrequire_cryptographic_holder_bindingHolder-proof enforcement is now expressed inside the DCQL query itself.
presentation_submission— (DCQL-only)This field is no longer accepted; DCQL query IDs identify submissions instead.
Legacy request endpoints (/vp-request, /vp-session-request, /vp-request/{requestId}, /vp-submission/direct-post)/v2 counterpartsExisting integrations calling these paths must move to the /v2 endpoints.
### **Documentation** * [Feature documentation](https://docs.inji.io/inji-verify/overview/features) * [Integration Guide](https://docs.inji.io/inji-verify/technical-overview/integration-guides) * [API Documentation](https://mosip.stoplight.io/docs/inji-verify/67445477d332e-open-id-4-vp-verifier-api-inji-verify) * [Collab Guide](/inji-verify/functional-overview/releases-1/inji-verify-collab-guide.md) * [QA Report](/inji-verify/releases/version-1.0.0-alpha.1/test-report.md) --- # 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-1.0.0-alpha.1.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.