Web view example scenarios

Case: Optional Web View step

Scenario: The user has the option to send their flight details to emergency contacts and add an emergency contact through a web view before receiving their airplane ticket.

During an interaction to receive a digital airplane ticket credential in the identity wallet, the user is presented with the optional action:

"Send Flight Details to Emergency Contacts": The user can click on an optional button labeled "Send Flight Details to Emergency Contacts." This opens a web view where the user can input one or more emergency contact details (e.g., name, email, phone number). Once submitted, the flight details, such as flight time, gate information, and seat number, will be automatically sent to the provided emergency contacts. This step is optional, and skipping it will not affect receiving the ticket.

Case: Mandatory Web View Step Without Parameters

This scenario below ensures that new students complete an essential orientation course before gaining access to their student ID, using a mandatory web view step without parameters.

Scenario: Before a new student can receive their digital student ID, the university want them to complete a mandatory web view step for an orientation course. On the interaction screen in the app, the user sees a button labeled "Complete Orientation Course." Clicking this button opens a web view displaying the course, which includes videos, reading materials, and guidelines for academic life, student services, and campus safety.

The student must go through the orientation course and click "Complete" at the end of the session.

This step only verifies course completion. Once the web view confirms that the orientation course has been completed, the user is returned to the app and can proceed to receive their digital student ID credential.

Case: Mandatory Use of Web View with Parameters (Single Completion)

Scenario: A financial institution requires users to verify their identity only once during their first transaction.

When completing their first transaction, the user is redirected to a web view step for identity verification. They see a button labeled "Verify Identity," which opens a web view to submit documents and verify their identity. The web view sends back parameters (e.g., verified identity details) to the app. Once this step is complete, the user will not need to verify their identity again for future transactions within the same interaction.

Case: Mandatory Web View with Parameters and "One Off"

Scenario: A fitness studio requires users to fill out a health questionnaire every time they renew or update their membership.

When renewing or updating their fitness studio membership, users are required to complete a mandatory web view step to fill out a health questionnaire. The app displays a button labeled "Complete Health Questionnaire." When the user clicks the button, a web view opens where they are prompted to answer questions about their current health condition (e.g., recent injuries, medical history, fitness goals).

The answers provided in the questionnaire (e.g., injury status, medical conditions) are temporarily saved as parameters for the duration of the interaction. With the "One Off" option, the health information is not stored beyond this interaction. This means that each time the user renews or updates their membership in the future, they will be required to fill out the health questionnaire again.

After completing the questionnaire, the user is redirected back to the app, where they can finalize their membership renewal or update. They will then receive a digital confirmation credential for their membership.