OID4VCI: how credentials are issued
OpenID for Verifiable Credential Issuance (OID4VCI) standardises how a wallet or an agent fetches a credential from an issuer — with a token, a nonce and proof of possession. It is the issuance path of the EUDI and E-ID world.
The flow
The issuer publishes its metadata; the recipient obtains an access token, requests a nonce and proves possession of its key when fetching the credential. The credential is bound to exactly that key.
At Mandact
The endpoints /api/v1/oid4vci/token, /nonce and /credential issue mandates as SD-JWT VC; the metadata is at /.well-known/openid-credential-issuer. The nonce endpoint is public by specification and rate-limited.
What it brings
An agent receives its mandate through the same path by which wallets will receive their IDs — no special format, no proprietary retrieval.
Status
Endpoints implemented (token, nonce, credential).