> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/digital-credentials/wallets-presentation-and-verification.md). # Wallets, Presentation and Verification How a learner receives, stores, and presents a credential — and how a verifier checks it. ## What a Digital Wallet Is A digital wallet is an application used to receive, store, manage, and present digital credentials. The wallet does not create credentials — instead, it receives credentials from an issuer and stores them under the control of the holder. Within the GovStack ecosystem, wallets are an important part of digital identity and credential infrastructure because they allow individuals to control how and when their credentials are shared. Unlike registries, which act as authoritative sources of information, a wallet is controlled by the credential holder: the holder decides which credentials to keep, when to use them, and with whom they should be shared. ## How a Learner Receives a Credential After a credential has been issued, it must be delivered to the learner. Within this PoC, credential delivery is performed through the OID4VCI issuance flow: the learner receives access to the credential through a task that contains a QR code or issuance link that can be opened using a compatible wallet application. When the learner scans the QR code, the wallet establishes a secure issuance session with the issuer and requests the credential. Once the issuance process is completed, the credential is transferred to the learner's wallet and becomes available for future use — usable independently by the holder, while still remaining connected to the issuer and the trusted data from which it was generated. ## How Credentials Can Be Stored Credentials are typically stored in a digital wallet controlled by the holder. The wallet acts as a personal repository for digital credentials, allowing the learner to keep credentials issued by different organisations in one place. One of the key principles of the Verifiable Credentials ecosystem is **holder control**: the issuing organisation maintains the authoritative registry records, while the holder keeps portable credentials that can be presented when needed. ## Presenting a Credential to Another Party After receiving a credential, the holder may choose to present it to another party when proof of a qualification, achievement, or identity attribute is required. The verifier may be an educational institution, employer, government organisation, or another authorised party requesting proof of information. Presentation is usually performed through wallet-based interactions — credentials may be shared through presentation requests, QR codes, links, tokens, or other supported mechanisms, depending on the wallet implementation. ## How Verification of a Presented Credential May Work When a credential is presented, the verifier must determine whether it can be trusted. Verification typically involves checking whether the credential was issued by a trusted issuer, whether the digital signature is valid, whether the credential has been altered, and whether the credential satisfies the verifier's requirements. {% hint style="info" %} Because Verifiable Credentials contain cryptographic proof, verification can often be performed without directly contacting the issuer. However, some checks — such as credential status, expiry, suspension, or revocation — may require access to a trusted status service or another verification mechanism, depending on the implementation. {% endhint %} This allows the verifier to confirm the origin, integrity, and current validity of the credential before relying on its contents. ## Connecting to Existing Wallet Solutions: iGrant GovStack promotes the use of open standards to support interoperability between issuers, wallets, and verification solutions. Because Verifiable Credentials follow standardised formats and protocols, credentials issued by one system can be received and used by compatible wallet applications without custom integrations. {% hint style="success" %} The Learner Registry PoC uses **iGrant Wallet** as the learner-facing wallet application. Credential issuance is implemented using the OID4VCI protocol, and compatible wallets such as iGrant Wallet can receive credentials through this standard flow and store them for future use. {% endhint %} The wallet is used to receive credentials issued through the OID4VCI flow, store them under the learner's control, and support future credential presentation scenarios. This demonstrates how credentials issued from registry data can be managed independently from the issuing system while remaining interoperable with standards-based digital credential ecosystems. The wallet allows learners to: * receive credentials issued by the Learner Registry solution; * store credentials under their control; * manage multiple credentials in a single application; * present credentials when proof of qualifications or achievements is required. By using a standards-based wallet solution, the PoC demonstrates how credentials issued from registry data can remain portable beyond the issuing platform and participate in a broader interoperable digital credential ecosystem. {% hint style="warning" %} **Platform implementation vs. general pattern.** The PoC uses iGrant Wallet as its reference wallet implementation — this reflects the choice made for this PoC, not a requirement of the underlying architecture. Any compatible, standards-based wallet could interoperate with credentials issued this way. {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/digital-credentials/wallets-presentation-and-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.