Web View Example Scenarios

Optional Web View step

Case: The user has the option to add an emergency contacts and send them their flight details through a web view before receiving their digital airplane boarding pass.

Scenario: During an interaction, before receiving a digital airplane boarding pass credential in the identity wallet, the user is offered an 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 - flight time, gate information, and seats - will be automatically sent to the provided emergency contacts. This step is optional, and skipping it will not affect receiving the boarding pass.

Mandatory Web View Step Without Parameters

Case: This scenario ensures that new students complete an essential orientation course before receiving their student ID, using a mandatory web view step without parameters.

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

The student must go through the orientation and click "Complete" at the end of the session. This step only verifies course completion. Once the web view confirms the orientation is completed, the student is redirected back to the app to receive their digital student ID credential.

Mandatory Use of Web View with Parameters (Single Completion)

Case: An insurance company requires users to verify their identity only once during their initial policy enrollment.

Scenario: To complete their first interaction, the user must go through mandatory web view steps.

In the "Get Proof of Auto Insurance" interaction, the user sees a button labeled "Verify Identity," which opens a web view where they can submit documents and verify their identity. The web view sends back parameters (e.g., verified identity details) to the app. Once this step is completed, the user will not need to verify their identity again for any future transactions within the same interaction.

We highly recommend using non-public self-attested credential definitions to prevent cross-service credential sharing.

Mandatory Web View with Parameters and "One Off"

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

Scenario: 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.

More information about the “One-off” option can be found in this Knowledge Base article:Credential Definition Page | One off .

We highly recommend using non-public self-attested credential definitions to prevent cross-service credential sharing.

Create a credential definition:

• Go to the schemas page and create a schema, naming and organizing it according to your requirements, then publish it.

• Important: “Public access“ checkbox should remain unchecked.

• Go to the “Credential Definitions“ tab of the “Schemas“ page and create self-attested credential definition based on that schema.

• If, you plan to use “Mandatory Web View step with Parameters and "One Off" scenario type,

  • check the “one-off“ checkbox.

The data from the web view step will be mapped to the corresponding attributes of the required self-attested credential definition included in the interaction.

More detailed information, about how to create credential schema and credential definition you can find on

• Credential Schemas Page

• Credential Definition Page

• SSI Interaction Page | Required and Issued Credentials section.