Read transaction data
GET/v2/config/digital-wallet/openid/sdjwt/transaction-data/:transactionDataId
Reads one transaction data record by its transactionDataId.
The digital wallet of the organisation must be deployed. If it is not, the server answers with HTTP 400.
Request
Path Parameters
Unique identifier of a transaction data record associated with a credential exchange.
Header Parameters
Optional. Unique identifier of the sandbox organisation to use for this request. When you send this header, the service runs the operation in the context of the named sandbox organisation, that is, against the wallet of that sandbox organisation and not against the main wallet of the organisation. Leave the header out to use the main wallet.
The service reads this header only when you authenticate with a bearer access token. When you authenticate with an API key, the service takes the sandbox organisation from the API key and ignores this header. To run an API-key call in a sandbox organisation, bind the key to the sandbox organisation with PUT /v2/config/admin/apikey/{apiKeyId}/sandbox-org instead.
X-SubwalletId is the deprecated name of this header. The service continues to accept it, but X-SandboxOrgId wins if you send both headers.
The sandbox organisation must exist, must belong to your organisation and must be deployed. An unknown identifier, an identifier of a sandbox organisation that is not deployed, and an identifier that belongs to a different organisation all make the call fail with HTTP 400.
Responses
- 200
- 400
- 401
- 500
The server returns the requested transaction data record.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
transactionDataHistory objectrequired
The transaction data record.
Internal record identifier of the transaction data record. It is not the same value as transactionDataId. Always use transactionDataId to address the record.
Unique identifier that the server gives to the transaction data record. Use this identifier in the path of the read endpoint.
Identifier of the credential issuance history record that this transaction data belongs to. The value is an empty string when the record belongs to no credential issuance.
Identifier of the OpenID4VC deployment that validated the transaction data.
Base64url encoded transaction data strings that the issuer verified against the key binding JWT. The value is null when the issuer verified no string.
Payment Authenticator Verifiable Presentation token that the holder sent.
transactionData object
Transaction data payload in plain JSON, for example the payee and the amount of a payment. The value is null when the request gave the payload as transactionDataBase64.
Transaction data payload in plain JSON, for example the payee and the amount of a payment. The value is null when the request gave the payload as transactionDataBase64.
true when the issuer verified the transaction data hashes against the key binding JWT.
vpTokenDecoded object
Decoded payload of the Verifiable Presentation token that the holder sent. The value is null when the issuer could not decode the token.
Decoded payload of the Verifiable Presentation token that the holder sent. The value is null when the issuer could not decode the token.
Unix timestamp, in seconds, of the moment that the server created this record.
Unix timestamp, in seconds, of the moment that the server last changed this record.
{
"transactionDataHistory": {
"id": "string",
"transactionDataId": "string",
"credentialExchangeId": "string",
"openIdOrganisationId": "string",
"transactionDataBase64s": [
"string"
],
"paymentWalletAttestation": "string",
"transactionData": {},
"transactionDataVerified": true,
"vpTokenDecoded": {},
"createdAt": 0,
"updatedAt": 0
}
}
The organisation is unknown, the OpenID wallet is not deployed, or no transaction data record matches transactionDataId.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Unauthorized
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Internal server error
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}