Session Outcome
Statuses, result fields and failure codes of EUDIPLO sessions, as returned by GET /api/session/{id}, sent in SSE events and in webhooks. How to receive them is described in Receive Results.
Statusesโ
| Status | Presentation session | Issuance session |
|---|---|---|
active | Request created; the wallet has not fetched it yet. | Offer created. |
fetched | The wallet fetched the request object. ISO 18013-7 and Digital Credentials API sessions skip this status. | The first credential of the session was issued. |
completed | The presentation was verified. | The wallet reported credential_accepted (Notifications). |
failed | Verification failed, or the wallet sent an error response (for example the user declined). | The wallet reported credential_failure or credential_deleted; see Issuance notifications. |
expired | expiresAt passed before the session finished. | The offer expired before it was redeemed (Credential Offers). |
Sessions only move forward: active โ fetched โ completed, failed or expired. The last three are terminal; a later offer redemption or presentation request is rejected with 400, and a late presentation response never overwrites the final status. A late issuance notification is accepted and recorded but leaves status and result alone.
Expiry is enforced when a wallet uses the session: a presentation request or response after expiresAt gets 400 ("The session has expired"). The status itself changes to expired when the session maintenance job runs, every SESSION_TIDY_UP_INTERVAL seconds (default 3600). Until then an overdue session still shows active or fetched.
Result fieldsโ
| Field | Content |
|---|---|
status | See above. |
credentials | Only when completed. OpenID4VP: [{ "id": "<query id>", "values": [ { <claims> } ] }], one values entry per presented credential. ISO 18013-7: [{ "id", "format": "mso_mdoc", "docType", "claims" }]. |
outcome | Structured result, see below. Set on completed and failed, for issuance once the wallet sent a notification. |
failureCode | Stable code of a classified failure, see failure codes. Absent or null otherwise. |
errorReason | Short, display-safe description of the failure. |
cancelReason | The reason given when the session was cancelled; null when none was given or the session was cancelled before 10.0. |
responseCode | One-time code of a completed OpenID4VP or ISO 18013-7 presentation; compare it with the response_code of a same-device redirect. Left out for callers that read the session only through sessions:read. |
consumedAt | When the presentation completed. |
expiresAt | When the request expires (presentation configuration lifeTime, default 300 seconds). |
transaction_data | The transaction data sent with the request. |
Outcomeโ
{
"result": "failed",
"source": "verifier",
"error": "trust_chain_not_trusted",
"message": "The credential issuer is not in the trusted list.",
"credentials": [
{
"id": "pid",
"format": "mso_mdoc",
"docType": "eu.europa.ec.eudi.pid.1",
"verified": false,
"error": "trust_chain_not_trusted",
"message": "The credential issuer is not in the trusted list."
}
]
}
| Field | Content |
|---|---|
result | success or failed. |
source | Who decided the result: wallet for a wallet error response or an OpenID4VCI notification, verifier when EUDIPLO verified the presentation. |
error | Failure code; same value as failureCode. Only for classified failures. |
message | Short, display-safe message; same value as errorReason. |
description | The wallet's own text: error_description of a wallet error response, or event_description of a credential_failure or credential_deleted notification. Wallet-controlled; show it as plain text only. |
credentials[] | Per credential query. On success every presented query with "verified": true; on a classified verification failure the credential that failed, with its error and message. |
credentials[].format, docType | Credential format and, for mDOC, the docType, when known. |
credentials[].trust | Success only, when an issuer was matched: the matched trust list entry (matchedIssuer: the entry's name, else the subject of its issuance certificate; issuanceThumbprint, matchMode, revocationThumbprint), or under OpenID Federation the issuer's entity ID with matchMode federation. For the first presented credential of each query. |
credentials[].warnings[] | Reserved for non-fatal conditions (code, message) observed while verifying the credential; currently never set. |
Branch on error; treat message as display text. Detailed diagnostics of a failure, such as certificate subjects or trust list URLs, are never part of the outcome; they go to the server log and the session log.
Failure codesโ
Credential verificationโ
The same codes are used for SD-JWT VC and mDOC, in OpenID4VP and ISO 18013-7 flows. An issuer listed only in a trust list discarded as outdated, or in a Trusted List that a list of trusted lists points to and that could not be loaded, counts as not listed (no_trust_chain_to_root or trust_chain_not_trusted); the server log line Discarded outdated trust list(s) ... or Discarded outdated or unavailable trust list(s) ... names the discarded lists, and so does the session log when it is enabled.
| Code | Message | Cause |
|---|---|---|
signature_invalid | The credential signature is invalid. | Issuer or device signature does not verify: tampered credential, wrong session transcript or key mismatch. |
no_trust_chain_to_root | The credential issuer does not chain to a trusted root. | No certificate path could be built from the credential's certificate: one past the size limits or a circular one (for an mDOC, when EUDIPLO's own check of the issuer's path finds it after the mDOC library's check passed); or, under OpenID Federation, no valid trust chain from the SD-JWT VC's issuer to a trust anchor, or no key kid in its metadata. |
trust_chain_not_trusted | The credential issuer is not in the trusted list. | The certificate path matches no PID, Pub-EAA or EAA issuance entry of the trust list, nor a granted qualified QEAA service of a Trusted List (Trusted Lists for QEAAs): the issuer is not listed, or, for example, it ends at the WalletSolution/Issuance certificate of an entity that is also listed with one of these issuance services (Trust lists). Also when the issuer's service is ignored for its ServiceStatus or a missing type (Service status and type). For an mDOC, also a status list or identifier list that is not signed under the signer the trust list requires. |
trust_list_unavailable | The trusted list could not be loaded, so the credential could not be validated. | A configured trust list could not be fetched, parsed or signature-checked, the configured lists hold more than 1,000 certificates together (Size limits), or every configured list is outdated: no valid NextUpdate or one that has passed, or no valid LoTESequenceNumber or TSLSequenceNumber or a lower one than a list accepted before. For a Trusted List, also when it is not signed by one of its signingCertificates, when none of the lists its list of trusted lists points to could be loaded and no other list of the etsi_tl entry is left, or when it points to more than 64 lists to follow (Trusted Lists for QEAAs); or, under OpenID Federation, the federation statements or the trust engine could not be reached. EUDIPLO fails closed. This is a verifier-side problem. |
certificate_expired | The credential issuer certificate is expired or not yet valid. | A certificate in the path is outside its validity period. For an mDOC, also a certificate from its status list or identifier list signer up to the certificate the trust list requires it to be signed under. |
x5c_missing | The credential is missing its issuer certificate chain. | The credential carries no x5c certificate chain. |
verification_error | The credential could not be verified. | Any other verification error, including a malformed x5c, an x5c or x5chain of more than 10 certificates (the credential's, or an mDOC status list's or identifier list's), an mDOC whose certificate path, or that of its status list or identifier list, exceeds the size limits, an SD-JWT VC without iss or kid under OpenID Federation, and an mDOC whose only trusted authority is an OpenID Federation. |
DCQL claim valuesโ
| Code | Message | Cause |
|---|---|---|
claim_value_mismatch | Disclosed claim values do not match the requested values for credential '<id>': <paths> | A disclosed claim is not one of the values of its claim query. With claim_sets, no set matched and at least one disclosed claim had another value. |
The message names the credential query and the claim paths, never the disclosed values. The outcome has no credentials entry for this code. A mismatch is reported before missing claims of the same credential.
Wallet error responsesโ
When the wallet answers with an OAuth error instead of a presentation, for example because the user declined, EUDIPLO records the wallet's code as failureCode (access_denied, invalid_request, vp_formats_not_supported, wallet_unavailable, ...). errorReason and outcome.message read Wallet error: <error>: <error_description>; outcome.source is wallet and outcome.description holds the wallet's error_description on its own. The wallet gets HTTP 200, as OpenID4VP 1.0 ยง8.2 requires, with a redirect_uri carrying error and error_description if a redirect is configured. EUDIPLO accepts the error both as form parameters and inside an encrypted direct_post.jwt response.
Issuance notificationsโ
When a wallet sends an OpenID4VCI notification, EUDIPLO records its result on the issuance session, with outcome.source set to wallet; for credential_failure and credential_deleted, the notification's event_description becomes outcome.description:
| Event | Status | failureCode | errorReason and outcome.message |
|---|---|---|---|
credential_accepted | completed | none | none |
credential_deleted | failed | credential_deleted | The wallet user rejected the credential |
credential_failure | failed | credential_failure | The wallet could not store the credential |
Only the first event finishes the session: it moves a fetched session to completed or failed and writes the fields above. A wallet that received several credentials in one session can notify for each, and may notify again; those later events are stored on their entry in notifications and sent to the webhook, but status, outcome, failureCode and errorReason keep the first event's result. Before 10.0 the latest event decided.
Other failuresโ
Some failures have no code; failureCode and outcome.error are absent and errorReason describes the problem. Examples:
Missing required credentials: ...orMissing required claims for credential '...': ...: the response does not satisfy the DCQL query.Presentation validation failed: ...: for example a transaction data hash mismatch, an invalid key binding, an SD-JWT VC status list that does not verify (Status List JWT verification failed: ..., also for anx5cof more than 10 certificates or a path past the size limits), or several presentations for a query withoutmultiple.HPKE decryption failed: an ISO 18013-7 response that cannot be decrypted.
What the wallet or browser receivesโ
An OpenID4VP response that fails verification is answered with 400 and an error body with statusCode, timestamp and path but no message; the session status says why. With a configured redirect the body also contains redirect_uri with error=invalid_request and the message as error_description. An encrypted OpenID4VP response that cannot be decrypted, uses encryption the request did not advertise (Keys and algorithms), or whose nbf or exp is out of range, is answered with 400 and a message starting Could not decrypt the authorization response, without redirect_uri; the session keeps its status, so the wallet can send the response again. An ISO 18013-7 response that fails verification is answered with 400 and the code:
{
"statusCode": 400,
"timestamp": "2026-10-03T10:01:12.000Z",
"path": "/presentations/3f0c1d9e-4c1b-4f63-9a59-2f4f0b6a2c11/iso-18013-7",
"error": "trust_chain_not_trusted",
"message": "The credential issuer is not in the trusted list."
}
Session logsโ
GET /api/session/{id}/logs returns the log entries stored for a session (timestamp, level (info, warn or error), stage, message, detail). Entries are only stored when LOG_SESSION_STORE is errors (warnings and errors), all or verbose (also request and response bodies); the default off stores nothing. See Environment Variables.