Description (User Story)

For this case we consider the mobile verifier.  Note that this may turn out to be an anti-pattern that is disallowed by the spec.

Note that this could also be called peer-to-peer trust validation or self-sovereign did-comm wallet (ie wallet<=>wallet) connection use case.

Narrative

The following is an actual use case for a Louisiana Driver's license Verify You. (click there to see their web page.  Following is quote from that page.)

VerifyYou™ is a unique feature that allows one LA Wallet user to validate another LA Wallet license holder. By scanning a custom generated QR code, a “Verifier” can validate the license validity, coarse age, full name and/or driver’s license number of another LA Wallet user. Meanwhile, the “Presenter” maintains full possession of his or her phone and controls which information is temporarily presented. Only the information the "Presenter" allows to be communicated is visible to the "Verifier." The received information is securely presented and not stored.

Specific Use Case

One specific use case is a delivery person that requires age verification.  The same app that the holder uses for verifying their age can be used to verify another's age.

...

Data Provided

Data Retained

The received information is securely presented and not stored. (according to the web site.)

Diagram

Steps

Primary Use Case

...