Given a presentation request is received from an RP presenting its registration certificate
When the consent screen is displayed
Then the screen shows the RP's user friendly trade name and the trade name of the specific service
Given the RP uses an intermediary for the presentation request
When the consent screen is displayed
Then the Wallet does not inform the user of the intermediary's trade name or its service trade name
Given the RP uses an intermediary for the presentation request
When the transaction is completed
Then the intermediary trade name is recorded in the Wallet transaction log
Given an issuance request is received from a PID Provider or Attestation Provider presenting its access certificate
When the issuance approval screen is displayed
Then the screen shows the provider's identity as included in the subject information of the access certificate
| Number of Scenarios | 4 | Total Duration | 1m 10s |
| Total Number of Test Cases | 4 | Fastest Test | 16s |
| Number of Manual Test Cases | 4 | Slowest Test | 17s |
| Tests Started | Aug 28, 2026 08:32:56 | Average Execution Time | 17s |
| Tests Finished | Aug 28, 2026 08:34:06 | Total Execution Time | 1m 10s |
| ## | Scenario | Context | Steps | Result |
|---|---|---|---|---|
| Retrieval and display of the interacting party's identity from the Access Certificate | Consent screen displays the RP's trade name and service trade name | 3 | ||
| Retrieval and display of the interacting party's identity from the Access Certificate | Intermediary's trade name is not disclosed to the user during the transaction | 3 | ||
| Retrieval and display of the interacting party's identity from the Access Certificate | Intermediary's trade name is recorded in the transaction log | 3 | ||
| Retrieval and display of the interacting party's identity from the Access Certificate | Issuance approval screen displays the identity of the Provider | 3 |