16. 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).

Credential Presentation Table of Contents

• 16.1. Remote Flow
  • 16.1.1. Authorization Request
  • 16.1.2. Request URI Request
  • 16.1.3. Request URI Response
    • 16.1.3.1. Request URI Endpoint Errors
  • 16.1.4. Authorization Response
    • 16.1.4.1. Authorization Response Errors
  • 16.1.5. Relying Party Response
    • 16.1.5.1. Relying Party Response Errors
  • 16.1.6. Status Endpoint
    • 16.1.6.1. Status Endpoint Errors
  • 16.1.7. Redirect URI
    • 16.1.7.1. Redirect URI Errors
• 16.2. Proximity Flow
  • 16.2.1. Device Engagement
  • 16.2.2. mdoc Request
  • 16.2.3. mdoc Response
  • 16.2.4. Session Termination