Skip to content

Commit

Permalink
Clarify base64url instead of base64 (#124)
Browse files Browse the repository at this point in the history
* Clarify base64url instead of base64
* Fixed formatting
  • Loading branch information
stefan-kauhaus authored Jan 6, 2025
1 parent d935c3c commit a2a88d5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions payment-rfcs/ewc-rfc008-payment-data-confirmation.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,8 +66,8 @@ The following are the pre-requisites for this RFC:

## 4.1 Authorisation request

The authorisation request defined in EWC RFC 002 [3] is extended to support the new parameter <code>transaction_data</code></strong>. This enables a binding agreement between the user's identification/authentication and authorisation (see [Chapter 5.1 - Presentation Definition](#6-1-presentation-definition-6)) to complete confirmation of a payment transaction. It is defined as an array of strings, each of which is a base64 encoded JSON object containing a typed parameter set with details about the transaction that the Verifier requests the individuals to authorise.
The <strong><code>transaction_data</code></strong> parameter must contain a transaction data object (base64 encoded JSON object) that includes the following properties:
The authorisation request defined in EWC RFC 002 [3] is extended to support the new parameter <strong><code>transaction_data</code></strong>. This enables a binding agreement between the user's identification/authentication and authorisation (see [Chapter 5.1 - Presentation Definition](#6-1-presentation-definition-6)) to complete confirmation of a payment transaction. It is defined as an array of strings, each of which is a base64url encoded JSON object containing a typed parameter set with details about the transaction that the Verifier requests the individuals to authorise.
The <strong><code>transaction_data</code></strong> parameter must contain a transaction data object (base64url encoded JSON object) that includes the following properties:

<table>
<tr>
Expand Down Expand Up @@ -329,4 +329,4 @@ Below is a non-normative example of a key-binding JWT with transaction data:

9. W3C: Payment Request API, Editor’s Draft 09 September 2024. Available at: [https://w3c.github.io/payment-request/#paymentcurrencyamount-dictionary](https://w3c.github.io/payment-request/#paymentcurrencyamount-dictionary) (Last accessed: 18 Nov 2024)

10. EWC RFC 004: Individual Wallet Unit Attestation - v1.0. Available at: [https://github.com/EWC-consortium/eudi-wallet-rfcs/blob/main/ewc-rfc004-individual-wallet-attestation.md](https://github.com/EWC-consortium/eudi-wallet-rfcs/blob/main/ewc-rfc004-individual-wallet-attestation.md) (Last Accessed: 18 Nov, 2024)
10. EWC RFC 004: Individual Wallet Unit Attestation - v1.0. Available at: [https://github.com/EWC-consortium/eudi-wallet-rfcs/blob/main/ewc-rfc004-individual-wallet-attestation.md](https://github.com/EWC-consortium/eudi-wallet-rfcs/blob/main/ewc-rfc004-individual-wallet-attestation.md) (Last Accessed: 18 Nov, 2024)

0 comments on commit a2a88d5

Please sign in to comment.