Skip to main content
Transaction data

Validate transaction data

POST/v4/config/ows/issuer/transaction-data/validations

Checks that a holder approved a transaction (for example a payment) with a payment attestation that this issuer issued (an SCA attestation of EUDI TS12). Send the presentation of the attestation, as the wallet sent it to you, and the transaction data that the holder approved.

The issuer checks that it issued the presented credential (signature, jti, cnf), that the Key Binding JWT belongs to the presentation (sd_hash), and that the first value of transaction_data_hashes of the Key Binding JWT is the SHA-256 hash of the transaction data (OpenID4VP 1.0 Appendix B.3.3.1). When all checks pass, the answer has the stored record with isVerified: true and the credentialExchangeId of the issuance history of the attestation. A failed check gives HTTP 400.

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:presentation-definitions:create

Body

application/json

The presentation and the transaction data. Send the transaction data in transactionData or in transactionDataBase64, not both.

  • paymentWalletAttestationstringrequired

    The presentation of the payment attestation, as the wallet sent it: the SD-JWT VC that this issuer issued, with its disclosures and a Key Binding JWT that has transaction_data_hashes.

  • transactionDataHashesAlgenum<string>[]required

    The hash algorithm of transaction_data_hashes in the Key Binding JWT: exactly one value, sha-256.

    1 item.

    Available options:sha-256

  • transactionDataobject

    The transaction data as a JSON object. The issuer encodes it as the base64url of its RFC 8785 canonical JSON and hashes that string, so it matches only when the Authorization Request had the same encoding; else send transactionDataBase64. Send this member or transactionDataBase64, not both.

  • transactionDataBase64string

    The transaction data as the base64url-encoded string of the transaction_data of the OpenID4VP Authorization Request: a JSON object with type and credential_ids. Send this member or transactionData, not both.

Response

application/json

The transaction data passed the checks. The answer has the stored record.

  • transactionDataHistoryobject

    The stored transaction data record, with isVerified: true.