oid4vci-deferred-notification

Implement OID4VCI deferred credential retrieval and notification endpoints with transaction IDs.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill oid4vci-deferred-notification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oid4vci-deferred-notification
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/oid4vci-deferred-notification
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill oid4vci-deferred-notification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of handling credentials that are not issued immediately and allows for notifications about their status, improving the user experience and issuer workflow.

Core Features & Use Cases

  • Deferred Issuance: Manages the retrieval of credentials when immediate issuance isn't possible using transaction_id.
  • Notification System: Enables wallets to inform issuers about credential acceptance, failure, or deletion events.
  • Use Case: A user requests a digital ID. The issuer can't generate it instantly but provides a transaction_id. The user's wallet later polls a deferred endpoint using this ID to retrieve the credential once ready, and then notifies the issuer that it was successfully stored.

Quick Start

Use the oid4vci-deferred-notification skill to handle a deferred credential request with transaction ID '8xLOxBtZp8'.

Frequently Asked Questions about oid4vci-deferred-notification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle deferred credential issuance in OID4VCI when a verifiable credential isn't immediately available?

Deferred credential issuance in OID4VCI uses a transaction_id to retrieve verifiable credentials later. The issuer provides this ID when immediate generation isn't possible, allowing wallets to poll a deferred credential endpoint until the credential is ready for retrieval.

What is a deferred credential endpoint and how does it manage transaction IDs?

A deferred credential endpoint manages transaction IDs for delayed verifiable credential retrieval in OID4VCI. It allows wallets to securely poll the endpoint using the transaction_id to fetch the credential once the issuer has finished generating it.

How do I notify an issuer about verifiable credential acceptance or deletion events in OID4VCI?

To notify an issuer about verifiable credential acceptance or deletion in OID4VCI, use the notification system endpoints. These allow wallets to inform issuers about credential acceptance, failure, or deletion events after the credential is successfully stored or removed.

Can I use OID4VCI deferred issuance endpoints with encrypted requests over TLS?

Yes, OID4VCI deferred issuance endpoints support encrypted requests and responses over TLS. This secure communication channel handles deferred credential retrieval and notification events according to the OpenID for Verifiable Credential Issuance specifications.

When do I need to implement deferred credential retrieval for verifiable credentials?

You need deferred credential retrieval when a verifiable credential cannot be issued instantly. The issuer provides a transaction_id, and the user's wallet later polls the deferred endpoint to retrieve the credential once ready, then sends a notification confirming successful storage.