> For the complete documentation index, see [llms.txt](https://docs.meeco.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meeco.me/openapi-docs/svx-api/svx-wallet-issuer-and-verifier.md).

# SVX Wallet: Issuer and Verifier

The SVX Wallet part of the API is focused on issuer and verifier workflows.

**Issuance**

Wallet endpoints support Credential Issuer metadata publication, credential configuration metadata, schema and template management, and credential offer creation for OpenID4VCI flows. Schema and template resources define credential structure, display metadata, supported format details, and validity policy used during issuance.

Issuance can be initiated through credential offers (issuer-initiated) or through wallet-initiated flow using issuer metadata discovery and `scope` resolution against `credential_configurations_supported`. The API includes the Credential Issuer endpoints and the Authorization Server endpoints required for authorization code flow deployments.

Credential offers support pre-authorized code and authorization code grants where configured, including issuance states and identifiers used to correlate subsequent token and credential requests. Offer, nonce, and authorization artifacts are exposed through dedicated endpoints used by wallets during proof-of-possession and credential retrieval steps.

Issuance lifecycle endpoints allow clients to create, list, fetch, and delete offer and issuance state resources, enabling complete operational handling of OpenID4VCI issuance sessions from metadata discovery through credential delivery.

**Verification**

Wallet endpoints support verifier request creation, presentation template management, and authorization request publication for OpenID4VP flows. Presentation templates define what a verifier requests from the wallet, including DCQL-based query structures or DIF Presentation Exchange (`presentation_definition`), response handling mode, and verifier redirect behavior.

Verification requests are initiated as OpenID4VP authorization requests and can be represented directly or via `request_uri`. The API includes endpoints to publish and retrieve verifier request JWTs, collect authorization responses submitted by wallets, and persist request/response state for later inspection.

Presentation submissions support `direct_post` and `direct_post.jwt` response modes, including encrypted JWT responses where required by verifier policy. When configured, verifier redirect URIs are returned to continue front-channel UX flows after successful submission.

Request and response lifecycle endpoints allow clients to create, list, fetch, and delete verification requests and their associated responses, enabling complete operational handling of OpenID4VP verification sessions.