The JWT should encode a JSON object with the following params. NOTE: The JWT should be created using our API to automatically include some other required parameters.
The REST api of the verifier where to deliver the credential data.
*Currently added later automatically and hardcoded, but will be required in the future.
The "aud" (audience) claim identifies the recipients that the JWT is intended for (currently hardcoded as
The "sub" (subject) of the jwt. Should be
*Currently added automatically (randomly generated) when creating a jwt, but will be required in the future, maybe with a different name.
A unique identifier for the JWT within the context of the verifying party. Used by the verifying party to match a response with the corresponding request.
The type of credential that is requested, as defined in the ssi service. This maps to the specific credential types of the different supported wallets.