📄️ Introduction
The verifier service exposes API to create proof requests that can be consumed by the Client Application to request for user data in a more secure manner by enhancing user consent and privacy using Bhutan NDI Wallet. The proof request can be customized by the Client Application based on business requirements by using the attributes from the available Schemas.
📄️ Proof Request
The Client Application can use Verifier Service to create a Proof Request as per the business requirement and use QR Code or Deep Link for using Bhutan NDI Wallet. A generic Proof Request flow can be found here.
📄️ Proof Request using NDI Biometric Authentication
The client application can use NDI-based biometric authentication for proof request, making it ideal for high-risk transactions. It verifies a user by checking unique biometric data from RGOB and performing a liveness check with Bhutan NDI, ensuring top-level security.
📄️ Get Proof Request
The Client Application can get the Proof Request details which contain the attributes that can be further used in other API calls.
📄️ Proof Request using Relationship
The Client Application can use this API if it has Relationship DID of a user which can be used for sending the Proof Request directly to the Bhutan NDI Wallet without the need of QR code scan.
📄️ Proof Request for Image VC
Bhutan NDI has an image as a verifiable credential (VC) in the self-attested section. Like any other VC, it can be shared as a proof request and provide clients with a visual means of identification and authentication. Additionally, before the image is added to your wallet as a VC, it is validated against the wallet’s owner to ensure authenticity.
📄️ Proof Constraints with Issuer DID
The issuer DID in proof constraints lets multiple issuers reuse the same schema while allowing verifiers to require that proofs come from a specific issuer.
📄️ NDI OTP Authentication
The client application can use an in-app OTP to generate an OTP request by sending the OTP directly to the user's wallet.