diff --git a/content/data/digilocker/quickstart.mdx b/content/data/digilocker/quickstart.mdx index 7b0186f6..6549f79a 100644 --- a/content/data/digilocker/quickstart.mdx +++ b/content/data/digilocker/quickstart.mdx @@ -64,9 +64,40 @@ You have to provide a `redirectUrl` in the request, which has to be a valid publ It will also be used by Setu to send back relevant information about a request. By default Setu includes the `success` flag of the user consent and DigiLocker request `id`. -- For a failed user consent, we will send back—`?success={false}&id={Digilocker_request.id}&errCode={code}&errMessage={message}` -- For a successful signature—`?success={true}&id={Digilocker_request.id}` +It also includes a scope parameter, which provides the information about the documents the user has consented to during their UI journey. The possible values are `ADHAR` for Aadhar, `PANCR` for PAN and `DRVLC` for Driver's License. +
+ + + + + + + + + + + + + + + + + + + + + + + +
Consent state Redirect URL
Failed user consent <redirectUrl>?success={False}&id={Digilocker_request.id}&errCode={code}&errMessage={message}
User Consent to Aadhaar + <redirectUrl>?success={True}&id=Digilocker_request.id&scope=ADHAR +
User consent to all three documents + <redirectUrl>?success={True}&id=Digilocker_request.id&scope=ADHAR%2BPANCR%2BDRVLC +
User journey completed without selecting any document + <redirectUrl>?success={True}&id=Digilocker_request.id&scope= +
+
You can also add custom query params such as session id from your end. You would append this to the provided URL, like so—