Workflow

Sequence Diagram

Visit https://www.plantuml.com/plantuml/uml and import the following file to edit the above sequence diagram as UML

@startuml
participant User
participant InjiVerify
participant DeviceCamera
participant PixelPass
participant VerificationSDK
participant Issuer

User -> InjiVerify: Scan Request
InjiVerify -> DeviceCamera: Scan Request
DeviceCamera --> User: Camera permissions
User -> DeviceCamera: Granted Camera Permissions
User -[#red]-> DeviceCamera: <color:red>Deny Camera Permissions
DeviceCamera -> InjiVerify: QR Read Data
InjiVerify -> PixelPass: Unzip and Decode QR Data
PixelPass --> InjiVerify: Decoded Data
PixelPass -[#red]-> InjiVerify: <color:red>Invalid Data
InjiVerify -[#red]-> User: <color:red>Error Display
InjiVerify -> VerificationSDK: Verify Data
VerificationSDK --> InjiVerify: Verified status
InjiVerify -> Issuer: Get Display properties
Issuer --> InjiVerify: Display Properties
InjiVerify --> User: Credential DIsplayed
|||
|||
|||
|||
|||
User -> InjiVerify: Upload File with QR
InjiVerify -> PixelPass: Unzip and Decode QR Data
PixelPass --> InjiVerify: Decoded Data
PixelPass -[#red]-> InjiVerify: <color:red>Invalid Data
InjiVerify -[#red]-> User: <color:red>Error Display
InjiVerify -> VerificationSDK: Verify Data
VerificationSDK --> InjiVerify: Verified status
InjiVerify -> Issuer: Get Display properties
Issuer --> InjiVerify: Display Properties
InjiVerify --> User: Credential DIsplayed

@enduml

Understanding the workflow:

Scan flow:

• The user sends a scan request to the Inji verify portal.

• Inji verify portal sends a scan request to the Device camera.

• The user will be prompted to ask for Device camera permissions.

• The user grants camera permissions.

  • The user scans the QR code using the device camera, and the QR data is returned to the Inji Verify portal.

  • Inji Verify passes the QR data to the Pixel Pass SDK.

  • The Pixel Pass SDK returns the decoded data to Inji Verify.

    • Inji Verify then passes the decoded data to the Verification SDK for verification.

    • The status is returned to the Inji Verify portal from the Verification SDK.

    • Inji Verify retrieves the display properties of the credential from the issuer’s well-known configuration.

    • Finally, Inji Verify displays the credential details using the fetched display properties.

  • The pixel-pass library fails to decode the data

    • Inji verify goes back to the home screen and displays the QR code format not supported error

• The user denies the camera permissions and the Camera permissions denied screen appears on the Inji verify portal

Upload QR flow:

• The user uploads a file with a QR Code.

• Inji Verify passes the QR data to the Pixel Pass SDK.

• The Pixel Pass SDK returns the decoded data to Inji Verify.

  • Inji Verify then passes the decoded data to the Verification SDK for verification.

  • The status is returned to the Inji Verify portal from the Verification SDK.

  • Inji Verify retrieves the display properties of the credential from the issuer’s well-known configuration.

  • Finally, Inji Verify displays the credential details using the fetched display properties.

• However, if Pixel Pass fails to decode the data:

  • Inji Verify navigates back to the home screen and displays the "QR code format not supported" error.

Note: To understand the Inji Verify components in detail please refer to the topic Components under Technical Overview section.