oid4vci-credential-offer

Implement OID4VCI credential offer flows with grant types and token requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the implementation of credential offer flows, specifically for issuer-initiated issuance, by detailing the necessary parameters and grant types.

Core Features & Use Cases

  • Credential Offer Handling: Understand and implement the credential_offer parameter and credential_offer_uri.
  • Grant Type Support: Covers authorization_code and pre-authorized_code grant types.
  • Use Case: A wallet needs to process a credential offer received from an issuer. This skill guides the wallet through constructing the correct token request to obtain the credential.

Quick Start

Use the oid4vci-credential-offer skill to understand the pre-authorized_code grant type for token requests.

Frequently Asked Questions about oid4vci-credential-offer

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

FAQPage Schema
How do I implement an OID4VCI credential offer flow for issuer-initiated issuance?

To implement an OID4VCI credential offer flow, you use the `credential_offer` parameter or `credential_offer_uri` to initiate issuance, then process the offer to construct the correct token request for obtaining the verifiable credential.

What is the difference between authorization_code and pre-authorized_code grant types in OID4VCI?

The `authorization_code` grant type requires standard user authentication, while the `pre-authorized_code` grant type allows the issuer to pre-authorize the wallet to receive credentials, streamlining the token endpoint request process without additional user interaction.

How does a wallet process a credential_offer_uri to request a token endpoint in OpenID Connect for Verifiable Credential Issuance?

A wallet retrieves the offer details from the `credential_offer_uri`, determines the applicable grant type, and constructs a token endpoint request according to RFC6749 specifications to obtain the access token needed for credential retrieval.

How do I handle error responses for pre-authorized_code grant type token requests in OID4VCI?

Error handling for `pre-authorized_code` token requests follows RFC6749 specifications, requiring the wallet to parse token endpoint error responses and manage exceptions when the credential offer or authorization fails.

When should I use the credential_offer parameter instead of a credential_offer_uri in verifiable credential issuance?

Use the inline `credential_offer` parameter for smaller payloads passed directly, and use `credential_offer_uri` when the offer payload is large or needs to be fetched separately by the wallet to avoid exceeding URL length limits.