Contract SDK

when we select the contract screen type, the onboarding merchant while going through the onboarding process needs to sign the contract then and there, only then the journey is completed but in contract sdk, merchants can fill out all the details, submit the supporting documents, and complete the onboarding journey but can sign the contract later on through their email within a valid time the merchant can also sign the contract on the fly/during the journey if the journey doesn't have any sub merchant added to it, and/or if the 'allow adding signers?' toggle is disabled if this toggle is enabled, then the merchant cannot sign the contract on the fly, but later through email options to customize contract sdk signature type currently the only option to validate the contract is e sign contract executer name name of the person who will prepare the contract contract name name of the contract that is prepared upload contract template upload a pre built contract here it can be in doc or html format sign on specific pages? merchants can be asked to sign on some specific pages signing options signing options can be chosen amongst indian and global the indian signing option is in compliance with the regulations of india and the global options can be used across all the other journeys which is globally accepted indian four signing options are available aadhaar esign, esign, i accept and i accept with email aadhar esign this option helps to sign the contract using the data of the aadhaar of the signer the signer has to enter the aadhaar number and the contract will be considered signed on entering the correct otp sent to the linked mobile number enable name match enabling this toggle verifies the name match between the signer and the data fetched from nsdl or emudra basis a threshold value the client can decide this ensures that only the authorized individual can sign the contract using their own aadhaar details name match threshold a threshold value decided by the client(bank/nbfc) can be entered here the esign will pass only when the name match score is more than the entered threshold value the possible threshold values can be between 0 01 to 1 00 the entered value should be in two decimal places esign enabling this toggle helps to sign the contract digitally using various methods any one of the below options has to be selected if the esign method of signing is chosen upload signature the merchant can upload the image of their signature font signature this feature lets the merchant choose their name in different font styles for their signature draw signature this option enables the merchant to draw their signature for the contract hide valid consent in esign when the merchant digitally signs the contract, a consent declaration appears, confirming their acceptance of the digital signature as their proxy checking the box will hide this consent hide resuse consent in esign when the merchant digitally signs the contract, a consent declaration appears, confirming their acceptance to reuse their esign for further purposes if required checking the box will hide this consent i accept this method of signing involves accepting the contract by just clicking on the 'i accept' checkbox at the end of the contract i accept with email this method of signing involves accepting the contract by just clicking on the 'i accept' checkbox at the end of the contract that is sent to the merchant on their email various toggles are present allow adding signers? allows to add more signers to the contract restrict editing signers? restricts the addition of more signers restrict removing signers? restricts the removal of the added signers additional verification required enabling this toggle adds additional verification to the contract id video this makes video verification an additional verification for the contract mobile otp this sends an otp to the mobile number provided by the merchant email otp this sends an otp to the mobile number provided by the merchant prefill signers the signers can be prefilled the name and email of the signer can be hardcoded by giving a hardcoded value or can be prefilled by selecting the pages and variables from where it can be prefilled if 'id video' is chosen as the criteria for addition verification then another configuration is added in prefill signers, i e , face match id, where the pages and variables from which face match id will be prefilled can be selected the signature position can also be customized by enabling the 'signature customisations' toggle the page number(s) where the signature has to be added is entered the position of the signature for the page(s) can be configured by providing the x and y coordinates(maximum value 250) for the page the height and width(maximum value 250) of the signature can also be configured note this customisation is valid only for a single signer also, it is valid only for a dynamic number of signers 6\ custom signature position the position and size of the main merchant's signature can be chosen according to requirements this can be done by selecting its position on the x and y coordinate and, also putting the value for its height and width when this toggle is enabled these options appear 7\ estamping an electronic stamp can also be put on the contract if required estamp is a part of the esign module when the contract is e signed, a pdf is generated an estamp is then inserted on the first page of this pdf once the estamp is inserted, the reference id of the stamp is embedded on the side of all the pages of the contract when the toggle for estamp is enabled the below fields have to be filled out global upload signature this option helps to sign the contract by simply uploading a file containing the signature font signature the applicant gets multiple options of font styles in which their name is written to sign the contract draw signature this is the option with the help of which the applicant can draw the signature on the screen in real time hide valid consent in esign? this hides the consent box during esign hide reuse consent in esign? when an applicant signs a contract a checkbox askes them if their consent can be reused in case of any other onboarding, this option hides that checkbox for reuse of consent various toggles are present allow adding signers? allows to add more signers to the contract restrict editing signers? restricts the addition of more signers restrict removing signers restricts the removal of the added signers additional verification required enabling this toggle adds additional verification to the contract id video this makes video verification an additional verification for the contract mobile otp this sends an otp to the mobile number provided by the merchant email otp this sends an otp to the mobile number provided by the merchant prefill signers the signers can be prefilled the name and email of the signer can be hardcoded by giving a hardcoded value or can be prefilled by selecting the pages and variables from where it can be prefilled if 'id video' is chosen as the criteria for addition verification then another configuration is added in prefill signers, i e , face match id, where the pages and variables from which face match id will be prefilled can be selected 7\ custom signature position the position and size of the signature can be chosen according to requirements this can be done by selecting its position on the x and y coordinate and, also putting the value for its height and width when this toggle is enabled these options appear 8\ estamping an electronic stamp can also be put on the contract if required estamp is a part of the esign module when the contract is e signed, a pdf is generated an estamp is then inserted on the first page of this pdf once the estamp is inserted, the reference id of the stamp is embedded on the side of all the pages of the contract when the toggle for estamp is enabled the below fields have to be filled out sequential signing if a contract has multiple signers, then each signer gets a mail to sign the contract they can sign it one by one sequentially another signer can sign the contract only when the previous signer has finished signing parallel signing in this case, if there are multiple signers, all of them get the mail for signing the contract at once any one of them can sign the contract without following a sequence, but if one signer is in the process of signing the contract then another cannot simultaneously validity time(in seconds) the time for which the contract is valid for signing by the merchant can be configured here in epoch time (default is 14 days, i e , 1209600) contract reminder frequency(in seconds) signers who have not yet signed the contract will receive reminders at specified time intervals, which are configured here contract sdk mapping the contract or contract sdk utilizes a docx templator that can also work seamlessly with html files to generate pdf documents {{write a few use cases for contract sdk here}} the templator is designed to accept either a docx or html file as an input, with variables strategically mapped within the template these variables must be from within the configuration engine (go admin) elements including but not limited to textboxes, radio buttons, checkboxes, and so on to effectively map these variables within the contract template, a standardized format has been created for docx templates, you can use {pageid, variablename} or {variablename} to map the variables within the docx template on the other hand, for html templates, the format {{pageid variablename}} is recommended for mapping the variables within the html template for the mapping of sub flow persona details, a closed loop must be defined using the keys {#personadata} and {/personadata} within these two keys, the details of the sub flow persona should be defined with this simple snippet, the final pdf generated will replicate for every persona, ensuring consistency across all sub flows getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at