Error codes
This page lists the HTTP error responses that the Truvity EUDIW Connector returns to wallets when processing presentation responses.
Wallet-facing error responses
When the connector encounters an error while processing a wallet request, it returns a JSON response with an error field and the corresponding HTTP status code.
| Error code | HTTP status | Description |
|---|---|---|
invalid_request | 400 | Validation errors during request parsing or format validation |
invalid_request | 403 | Cryptographic validation failures (signatures, key binding, nonce) or trust chain validation failures |
access_denied | 403 | The wallet rejected the presentation request (for example, user declined consent) |
server_error | 500 | Infrastructure errors (database, key management) |
temporarily_unavailable | 503 | Transient errors (downstream service timeouts) |
The invalid_request error code maps to two HTTP statuses because it covers two distinct failure categories defined by OID4VP. Use the HTTP status code to distinguish them: 400 indicates a malformed or missing request parameter, while 403 indicates a cryptographic or trust validation failure.
Error description field
Error responses may include an optional error_description field with a human-readable explanation of the error. This field provides additional context for debugging but is not guaranteed to be present in every response.
Further reading
- Callback events—Presented Credentials Event statuses and payload fields
- Connector architecture—how the connector processes requests and delivers results
- Handle verification errors—implement error handling and retry logic