Contract

in general, a contract is a legally binding agreement between two or more parties, in which each party agrees to perform certain obligations or provide certain goods or services in exchange for something of value in the context of digital onboarding, a contract may refer to a digital agreement or terms of service that a user must agree to in order to use a particular platform or service we use the contract page to get the merchant's consent on the information he has provided during onboarding and get his e signature done on it these contracts are usually presented in the form of checkboxes or electronic signatures and are legally binding options to customize contract 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 choose language the language of the contract can be chosen here 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 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 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 prefill signers the signers can be prefilled the name and email of the signer can be hardcoded by giving a hardcoded value or name or can be prefilled by selecting the pages where it is to be prefilled and giving it a variable name 5\ 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 6\ 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 7\ redirection if a circumstance arises then, we can be redirected to the page that is chosen by providing the url the redirection time can also be chosen contract 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