Given the user is on the Relying Party service page

When the user initiates the wallet verification flow

Then a presentation request flow is initiated

Given a presentation request flow has been initiated

When the Desktop browser invokes the Digital Credentials API

Then the user is prompted to grant permission

Given the browser displays a permission prompt

When the user grants permission

Then the Relying Party generates a valid presentation request

Given a valid presentation request has been created

When the browser processes the request

Then a QR code is displayed to the user

Given a QR code is displayed on the Desktop browser

When the user scans the QR code with the mobile device camera

Then the presentation request is transferred to the mobile device

Given the mobile device has received a presentation request

When no installed Wallet Unit contains suitable attestations

Then the user is notified and the process is terminated

Given the mobile device has received a presentation request

When the system identifies one or more suitable attestations

Then the user sees an extension of the Wallet open automatically

Given the extension of the Wallet is open

When the presentation request screen is shown

Then the requesting Relying Party and the requested attestations and related attributes are displayed

Given the presentation request screen is displayed in the Wallet

When the user consents to share attributes and enters a valid six-digit PIN

Then the attestation is presented successfully

Given the Wallet requests PIN authentication

When the user enters an incorrect six-digit PIN

Then an authentication error is displayed

Given the attestation has been presented from the mobile Wallet

When the Relying Party validates the attestation successfully

Then a verification confirmation is displayed in the Desktop browser

Given the attestation has been presented from the mobile Wallet

When the Relying Party fails to validate the attestation

Then an error message is displayed and retry is allowed