End User Guide

User Manual

The Verification SDK is a backend utility designed to handle document verification processes. It is integrated into backend services like the Beneficiary Backend and Provider Backend, and therefore, it does not offer any direct, user-facing flows or interfaces.

Instead, it works behind the scenes, ensuring that any verifiable credentials (VCs) submitted through applications are validated as per the defined verification processes before being imported or processed further.

Integration Examples

Although users do not interact with the Verification SDK directly, it plays a critical role in backend processes at two key points within the application ecosystem:

Integration Point	Description
Beneficiary	VC verification during VC import — When a beneficiary scans a VC QR code to import credentials into their profile, the verification of the document is handled by the Verification SDK behind the scenes.
Provider	VC verification for VCs received in Benefit Application form — When benefit applications containing VCs are submitted, the Verification SDK verifies these documents before they proceed for approval or rejection by the provider.

These integrations ensure that all documents being stored or reviewed in the system have passed necessary verification checks, maintaining data integrity and trust in the platform.

User Flows and Screenshots

Uses of Verification SDK in Beneficiary

Beneficiary Provider - VC verification during VC import

When beneficiaries scan the VC QR code in the beneficiary app to import VC into the profile before applying for any benefits, document verification happens behind the scenes.

The Beneficiary backend’s /user_docs API uses the Verification SDK API to verify the document before importing it.

Error from verification SDK is used to show an error message in the Beneficiary app while document importing if document verification fails due to any reasons.

Uses of Verification SDK in Provider

When providers see the individual application in the provider app there providers can verify the document before Approving / Rejecting the application.

In the provider, verification of documents happens using verify-vcs API of provider backend which uses Verification SDK API to verify the documents.

Verification Status of Documents is Pending initially

When the verification of documents is triggered by the "Verify all documents" action, it calls the /verification/verify-vcs API of the provider backend, which internally uses the verification SDK API to verify the documents.