---
title: "W3C VC via OID4VP"
description: "Present a W3C Verifiable Credential from an Enterprise wallet service using OID4VP 1.0 with DCQL (Wallet2 Service)."
stack: "Enterprise Stack (commercial) — version 1.1.1"
stack_version: "1.1.1"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-presenting/w3c-vc
generated: 2026-10-01
---
# Presenting W3C VC Credentials via OID4VP 1.0

This guide shows how to present a [W3C Verifiable Credential](https://docs.walt.id/concepts/digital-credentials/verifiable-credentials-w3c.md) stored in an Enterprise wallet to a verifier using the **Wallet2 Service**. You hand the wallet a presentation request — for example one created with [Verifier2](https://docs.walt.id/enterprise-stack/services/verifier2-service/overview.md) — and it matches, signs, and submits in a single call.

**Note:**

This page follows the **single-call full flow**. To preview matches, show a consent screen, or present credentials that aren't stored in the wallet, see [Isolated Flow](https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-presenting/isolated-flow.md).

## Prerequisites

- A **wallet service** with a linked KMS, DID Store, and Credential Store — see [Setup](https://docs.walt.id/enterprise-stack/services/wallet2-service/setup.md).
- The wallet holds a **W3C VC** — see [Receiving W3C VC Credentials](https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-receiving/w3c-vc.md).
- A **presentation request** from a verifier (an `openid4vp://` URL).

---

## Present the Credential

This single call resolves the request, DCQL-matches credentials from the wallet's stores, signs the presentation with the wallet's key, and submits it to the verifier.

**Option: CURL**

Endpoint: `POST /v2/{target}/wallet-service-api/credentials/present`

**Example Request**

```bash
curl -X POST \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v2/{org}.{tenant}.{wallet-id}/wallet-service-api/credentials/present' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '{
  "requestUrl": "openid4vp://authorize?client_id=did:jwk:eyJrdHkiOiJPS1AiLCJjcnYiOiJFZDI1NTE5In0&request_uri=https://verifier.example.org/request/abc123"
}'
```

**Path Parameters**

- `orgID` _String_ — Organization host alias.
- `target` _resourceIdentifier_ — The wallet's resource path, e.g. `waltid.tenant1.wallet`.

**Body Parameters — `Wallet2PresentCredentialRequest`**

- `requestUrl` _String_ — The OID4VP authorization request URL from the verifier.
- `keyReference` (optional) _String_ — Full resource path of the key to sign the presentation with. Defaults to the first key in the wallet's linked KMS (or the service's configured static key if the KMS has none).
- `key` (optional) _Object_ — Inline serialized key (`{ "type": "jwk", "jwk": { … } }`). Takes precedence over `keyReference`.
- `did` (optional) _String_ — DID to present as. Defaults to the first DID in the wallet's linked DID Store (or the configured static DID).
- `didReference` (optional) _String_ — Full resource path of a DID in a linked DID Store (`{org}.{tenant}.{didstore}.{did-id}`). An alternative to `did` — when provided, the wallet resolves the DID from the store by this reference. Returns an error if the referenced DID does not exist.
- `runPolicies` (optional) _Boolean_ — When `true`, applies configured holder policies before presenting and blocks if a policy denies it. Omitted or `false` skips policy enforcement.

**Example Response — `WalletPresentResult`**

```json
{
  "transmission_success": true,
  "verifier_response": {
    "status": "received",
    "message": "Presentation received and is being processed."
  }
}
```

- `transmission_success` _Boolean_ — Whether the wallet successfully transmitted the presentation to the verifier's response endpoint.
- `verifier_response` _Object_ — The raw response returned by the verifier. For a `direct_post` verifier (e.g. Verifier2) this is `{ "status": "received", "message": "…" }`; some verifiers instead return a `redirect_uri`.
- `redirect_to` _String_ (optional) — Present only when the verifier returns a redirect URL to send the user to; absent for `direct_post`.
- `get_url` / `form_post_html` _String_ (optional) — Populated instead of `redirect_to` for the redirect (`get_url`) or `form_post` (`form_post_html`) response modes.

**Response Codes**

- `200` — Presentation built and submitted.
- `400` — The presentation request could not be resolved (e.g. an unfetchable `request_uri`).

**Note:**

  When the request resolves but **no stored credential satisfies the DCQL query**, the call still returns **`200`** with `"transmission_success": false` and the verifier's DCQL-fulfillment error inside `verifier_response` — it does **not** return `400`.

- `401` — Invalid authentication.

🎉 You've presented a W3C VC to the verifier.

---

## Doing It Step by Step

The full-flow call above matches, signs, and submits in one request. To preview which credentials match before presenting, show a consent screen, or present credentials supplied inline, drive the isolated endpoints yourself:

`preview` → `build-vp-token` → `send-response` (or `reject`)

Advanced resolve/match steps remain available for custom matching. Each step and the isolated inline variants are documented in [Isolated Flow](https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-presenting/isolated-flow.md). You can also use the full-flow `credentials/present` endpoint when you do not need to inspect or approve intermediate results.

---

## Next Steps

- **Present other credential types** — [SD-JWT VC](https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-presenting/sd-jwt-vc.md) or [mDL](https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-presenting/mdl.md).
- **Receive more credentials** — [Credential Receiving](https://docs.walt.id/enterprise-stack/services/wallet2-service/credential-receiving/overview.md).
- **Manage stored credentials** — [list and retrieve](https://docs.walt.id/enterprise-stack/services/wallet2-service/management.md) credentials in the wallet.