7.2. Digital Credential Presentation

This section describes how a Relying Party Instance requests to a Wallet Instance the presentation of the PID/EAAs.

In this section the following flows are described:

• Remote Flow, where the User presents a Digital Credential to a web Relying Party Instance according to OpenID4VP. In this scenario the user-agent and the Wallet Instance can be used in the same device (Same Device Flow), or in different devices (Cross Device Flow).

• Proximity Flow, where the User presents a Digital Credential to a mobile Relying Party Instance according to ISO18013-5. The User interacts with a Verifier using proximity connection technologies such as using QR Codes and Bluetooth Low Energy (BLE).

Note

In the case of using the batch Credential, the Wallet Instance SHOULD implement a Credential selection logic (e.g., based on the earliest expiring one) and MUST mark it as consumed. At the end of the flow it MUST decrease the number of available Credentials in the batch and using that it can control the time when it needs to obtain a new batch of Credentials.

Credential Presentation Table of Contents

• 7.2.1. Remote Flow
  • 7.2.1.1. Authorization Request
  • 7.2.1.2. Request URI Request
  • 7.2.1.3. Request URI Response
    • 7.2.1.3.1. Request URI Endpoint Errors
  • 7.2.1.4. Authorization Response
    • 7.2.1.4.1. Authorization Response Errors
  • 7.2.1.5. Relying Party Response
    • 7.2.1.5.1. Relying Party Response Errors
  • 7.2.1.6. Status Endpoint
    • 7.2.1.6.1. Status Endpoint Errors
  • 7.2.1.7. Redirect URI
    • 7.2.1.7.1. Redirect URI Errors
• 7.2.2. Proximity Flow
  • 7.2.2.1. Device Engagement
  • 7.2.2.2. mdoc Request
  • 7.2.2.3. mdoc Response
  • 7.2.2.4. Session Termination