From 7dda22958092544a62bbc3358b3da5f84647581b Mon Sep 17 00:00:00 2001 From: John Henderson Date: Mon, 25 Sep 2023 14:23:44 +0100 Subject: [PATCH] docs(tutorials): exchange invitation details --- .../credential-exchange-multiple-credential-tutorial.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/apps/vc-api/docs/tutorials/credential-exchange-multiple-credential-tutorial.md b/apps/vc-api/docs/tutorials/credential-exchange-multiple-credential-tutorial.md index bd2087a4..a58df0d5 100644 --- a/apps/vc-api/docs/tutorials/credential-exchange-multiple-credential-tutorial.md +++ b/apps/vc-api/docs/tutorials/credential-exchange-multiple-credential-tutorial.md @@ -353,6 +353,14 @@ Copy this URL, including the domain, into the exchange definition below. #### 2.2 [Verifier] Provide an exchange invitation to the resident Having configured the exchange, the Verifier must then ask the resident to present the required credentials. +This invitation to a credential exchange can be done in mechanism such as a QR code or [CHAPI](https://chapi.io/). +The mechanism used is outside of the scope of VC API. + +The data structure below is an example of a data structure that could be package the exchange invitation. +Its structure is based on the [WACI-DIDComm Interoperability Profile](https://identity.foundation/waci-didcomm/#interoperability-profile). +The Verifier may construct any data structure, as long as it is accepted and understood by the recipient wallet. +Other data structures, such as a data structure described in the [CHAPI documentation](https://chapi.io/developers/wallets/native/#verifiable-credential-storage). +Constructing this data structure is outside of the scope of VC API. ```json {