Setting Up
Aadhaar eSign Using Face Auth Setup Guide
11 min
introduction signzy provides aadhaar esign by employing the signer's facial features as biometrics to authenticate identity and finalize the signing process this involves utilizing the signer's face for verification during authentication the utilization of aadhaar esign with face authentication is exclusive to a native mobile application on a mobile device this functionality is not supported on desktops/laptops through web based workflows additionally, it will not operate on a mobile device when accessed via a web based workflow as of now, aadhaar esign with face authentication is compatible exclusively with android mobile devices ios, windows, or any other operating systems on mobile devices do not currently support this feature if you require assistance in setting up the service or have any questions, please contact our helpdesk at help\@signzy com or reach out to your designated customer success manager (csm) setup guide here is a step by step process to use aadhaar based esign using face auth step 1 utilize the " initiate contract api " to create the contract when employing the aadhaar esign using face auth functionality, ensure to include "signaturetype" "aadhaaresign faceauth" in the parameters step 2 upon generation of the contract through the api, the output will include the signer id step 3 invoke signzy's aadhaar esign sdk by utilizing this signer id signzy's aadhaar esign sdk integration steps e sign is a versatile and powerful software development kit designed specifically for android applications by seamlessly integrating esignsdk, developers can enhance their apps with the ability to facilitate electronic contract signings, ensuring both security and convenience to integrate the android archive( aar) file in any android application following steps need to be followed step 1 copy the esignsdk (env) release aar file to app/libs/ for testing in preproduction envrionment, use the esignsdk preproduction release aar for production envrionment, use the esignsdk production release aar links for both the files are provided below you can download them https //archbee doc uploads s3 amazonaws com/w0ydjmc6uxu0aj6spj9ot/n6hqkcu9vj1zyytehd0ce esignsdk preproduction release aar https //archbee doc uploads s3 amazonaws com/w0ydjmc6uxu0aj6spj9ot/ustic0okdqfp shsoxbq7 esignsdk production release aar you must install the face rd mobile application, provided by uidai, to capture facial data and perform face matching with uidai's records the face rd app for preproduction can be downloaded from https //drive google com/file/d/1pkkn1itnsntzwy1u8eaept7ip6lrpgup/view?usp=sharing https //drive google com/file/d/1rijb tkjhxyes9o5qjikh k6oksrrhf/view?usp=share link if you are having issues while downloading this file, please get in touch with your csm and they will provide you with the application the face rd app for production can be downloaded from google playstore https //play google com/store/apps/details?id=in gov uidai facerd\&hl=en in\&gl=us\&pli=1 https //play google com/store/apps/details?id=in gov uidai facerd\&hl=en in\&gl=us\&pli=1 step 2 in settings gradle add the following to support jitpack io dependencyresolutionmanagement { repositoriesmode set(repositoriesmode fail on project repos) repositories { //other deps maven{ url 'https //jitpack io' } } } step 3 import dependencies in app level build gradle add following dependencies implementation(files("libs/esignsdk (env) aar")) implementation "com github signzy\ esign sdk 1 0 0" implementation "androidx databinding\ viewbinding 8 2 1" implementation "com squareup retrofit2\ retrofit 2 9 0" implementation "com squareup retrofit2\ converter gson 2 9 0" implementation "com squareup okhttp3\ logging interceptor 4 5 0" implementation "com google code gson\ gson 2 10 1" implementation "com android volley\ volley 1 2 1" implementation "com scottyab\ rootbeer lib 0 1 0" step 4 invoke sdk to invoke sdk we need to call the startactivityforresult function using signzyesignactivity sdk needs to string params in input whose string constants are already there in signzyesignactivity signzy signer id it is the signer id which you get in inititate contract api signzy contract token it is the same token which you use while using the ots product val appstartintent = intent( this, signzyesignactivity class java ) putextra(signzyesignactivity signzy signer id, signerid) putextra(signzyesignactivity signzy contract token, token) startactivityforresult(appstartintent, signzyesignactivity signzy request code) step 5 watch for result on activity result can be setup string constants are available in signzyesignactivity as signzy result this will give you the file url of signed pdf signzy error message this will give the error message signzy error code this will give the error code override fun onactivityresult(requestcode int, resultcode int, data intent?) { super onactivityresult(requestcode, resultcode, data) if (requestcode == signzyesignactivity signzy request code) { if (resultcode == activity result ok) { 	 //this is the signed file url val file = data? getstringextra(signzyesignactivity signzy result) toast maketext(this,file,toast length long) show() } else { 	 // incase activity canceled {errmsg & errcode is available} val errmsg = data? getstringextra(signzyesignactivity signzy error message) val errcode = data? getstringextra(signzyesignactivity signzy error code) toast maketext(this,"$errcode $errmsg",toast length long) show() } } }