From 79514e1bc9917cb90f3cbca1816b06a4269528c9 Mon Sep 17 00:00:00 2001
From: Kristina <52878547+Sakurann@users.noreply.github.com>
Date: Sat, 7 Dec 2024 07:44:03 +0100
Subject: [PATCH] moving transaction data to a section that describes both
 sd-jwt and mdocs

---
 openid4vc-high-assurance-interoperability-profile-1_0.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/openid4vc-high-assurance-interoperability-profile-1_0.md b/openid4vc-high-assurance-interoperability-profile-1_0.md
index 0f1762a..fdc1ccc 100644
--- a/openid4vc-high-assurance-interoperability-profile-1_0.md
+++ b/openid4vc-high-assurance-interoperability-profile-1_0.md
@@ -232,6 +232,7 @@ The requirements for the Wallet and the Verifier, unless specified otherwise:
   * The Wallet MUST support both signed and unsigned requests defined in Annex A.3.1 and A.3.2 of [@!OIDF.OID4VP]. The Verifier MUST support signed requests, unsigned requests, or both.
 * Wallet Invocation is done via the W3C Digital Credentials API or an equivalent platform API. Custom URL schemes MUST NOT be used.
 * Response Mode MUST be `dc_api.jwt`. The response MUST be encrypted.
+* Specific requirements for the response encryption are tbd.
 * The DCQL query and response as defined in Section 6 of [@!OIDF.OID4VP] MUST be used. Presentation Exchange as defined in Sections 5.4 and 5.5 of [@!OIDF.OID4VP] MUST NOT be used. Below is the list of features in the DCQL query and response that MUST be supported:
   * tbd