clarify usage of sdjwt vc

payment-rfcs/ewc-rfc008-payment-data-confirmation.md

@@ -38,7 +38,7 @@ Published under a Creative Commons Attribution 4.0 International License
 
 This specification defines how a Relying Party (RP) can interact with an EUDI wallet to receive verifiable confirmation that a user has agreed to specific details of an (intended) payment transaction. The RP could be the user’s bank (two-party model) or an intermediary like a merchant or a Payment Initiation Service Provider (three-party model). In the latter case, the way how the intermediary relays the data to the user’s bank is out of the scope of this specification but would typically happen through industry-specific protocols such as e.g. EMV 3-D Secure [1] or the Berlin Group’s suite of open banking APIs [2].
 
-This specification builds upon using the OpenID4VP protocol defined in EWC RFC 002 [3]. It also leverages the <strong><code>transaction_data</code></strong> feature recently introduced to OpenID4VP [4] to add a dynamic element to the presentation. Lastly, this specification uses the Payment Wallet Attestation (PWA) specified in EWC RFC 007 [5] as the credential referencing the wallet's key to confirm the payment transaction details. The credential format used in this document is SD-JWT, but others may also be supported.
+This specification builds upon using the OpenID4VP protocol defined in EWC RFC 002 [3]. It also leverages the <strong><code>transaction_data</code></strong> feature recently introduced to OpenID4VP [4] to add a dynamic element to the presentation. Lastly, this specification uses the Payment Wallet Attestation (PWA) specified in EWC RFC 007 [5] as the credential referencing the wallet's key to confirm the payment transaction details. The credential format used in this document is SD-JWT VC, but others may also be supported.
 
 This specification further details concepts developed and documented by the EWC Payment Task Force in their “Payment Authentication (SCA) using EU DI Wallets – Implementation Guide” [6].