From 16a168140b08d05e9c41e9b45061dae0ddfdc4c7 Mon Sep 17 00:00:00 2001 From: Lal Chandran Date: Mon, 12 Feb 2024 14:21:59 +0100 Subject: [PATCH] Fix #7: Credential Offer credentials field is not matching the OID4VCI Draft 12 Signed-off-by: Lal Chandran --- ewc-rfc001-issue-verifiable-credential.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/ewc-rfc001-issue-verifiable-credential.md b/ewc-rfc001-issue-verifiable-credential.md index 3eca893..8df1fb5 100644 --- a/ewc-rfc001-issue-verifiable-credential.md +++ b/ewc-rfc001-issue-verifiable-credential.md @@ -113,7 +113,24 @@ Here, the `credential_offer_uri` query param contains the URL in which the crede ## 3.2 Credential offer response -Once the `credential_offer_uri` query param is resolved, the response for the authorised flow is as follows: +Once the `credential_offer_uri` query param is resolved, the response can be either of the following formats. + +```json +{ + "credential_issuer": "https://server.example.com", + "credentials": [ + "VerifiablePortableDocumentA1" + ], + "grants": { + "authorization_code": { + "issuer_state": "eyJhbGciOiJSU0Et...FYUaBy" + } + } +} +``` + +> [!NOTE] +> In order to support all EBSI conformant wallets, the following format for the response is also valid, but not **mandatory** to be supported: ```json {