Let’s take an example of building a complete digital journey for opening a bank account. To create a complete digital process for opening a bank account, your mobile/web application will guide the customer through several steps/pages/screens. These include verifying their identity and address, providing basic and employment details, declaring FATCA information, performing a liveness check and face match, and collecting nomination details.

Once the application gathers all the required data from the customer, it will populate a predefined bank account opening form specifically tailored for each customer. This form, known as the "contract/agreement," will be generated. Subsequently, the customer will be guided through a digital signing process to obtain their digital signature on the bank account opening form (contract/agreement).

It consists of 4 steps:

The objective of this stage is to produce a contract or agreement that can be digitally signed. This is achieved by utilizing a pre-designed template and integrating customer-specific information. There are two available methods to generate the contract/agreement PDF for digital signing:

In this step, you can upload a template, gather customer data, merge the data with the template, and create a final PDF document that can be digitally signed.

Here is a step-by-step process to create your own contract/agreement PDF document for digital signing.

In short, you can design your own contract PDF, request digital signatures from the customer, and provide them with the final PDF to sign digitally.

eStamping is a digital alternative to traditional paper-based stamping. It validates legal and financial documents electronically by using virtual stamps or seals instead of physical ones. eStamping saves time, reduces costs, and enhances document security by eliminating the need for physical stamps. We provide eStamping services for a large number of states of India. We provide 2 ways of doing eStamping.

In eStamping, we obtain the stamp papers from authorized vendors. Prior to procuring the stamp papers, it is necessary to determine the quantity, denomination, and state of the stamp papers. In this scenario, only the acquired stamp papers can be utilized, and the denomination cannot be altered during the process.

The eGRAS (Government Receipt Accounting System)/Franking is an online platform that allows users to make payments to the government for various services, including the purchase of stamp papers. Upon completing the payment, a challan is generated, serving as evidence of payment for the stamp papers. Subsequently, any amount from the challan can be used from a virtual wallet, enhancing the convenience of acquiring and utilizing stamp papers.

Aadhaar eSign is a digital signature service provided by the Unique Identification Authority of India (UIDAI) that allows individuals to digitally sign documents using their Aadhaar credentials. It enables a convenient and secure way to electronically sign various agreements, forms, and applications, eliminating the need for physical signatures. Aadhaar eSign leverages the biometric and demographic information stored in the Aadhaar database to authenticate the signer's identity, ensuring the integrity and authenticity of the digitally signed documents.

OTP, which stands for One-Time Password, is a popular method used for e-Authentication in Aadhaar eSign. With OTP-based e-Authentication, individuals are required to provide their Aadhaar number and registered mobile number. A unique OTP is then sent to their registered mobile number. Once the OTP is verified, the e-signing process is successfully completed.

Biometric-based e-Authentication is another method utilized in Aadhaar eSign. This method involves the use of an individual's unique biological characteristics, such as fingerprints, face or iris scans, to verify their identity. During the e-Authentication process, individuals' biometric data is captured using specialized devices. This data is then compared with the biometric information stored in the Aadhaar database. If the biometric data matches, the individual's identity is confirmed, and the e-Signing is considered successful.

Once the eSign is completed by the end user, we have 3 scenarios:

In this scenario, the eSign is successfully completed by the end signer and the output PDF is available to you for showing it to the end signer on the mobile app/web application.

In this scenario, the eSign is not successfully completed by the end signer and it can happen for multiple reasons. For example, the Aadhaar number is not linked to the mobile and as such, OTP can't be triggered and eSign can’t be completed.

If someone tries to use an unauthorized Aadhaar eSign (electronic signature), and you provide the additional details like name, gender, and year of birth, we'll check if these details match the information on record. If there's a mismatch, it will be considered a "success with deviation." This means the eSign was technically successful, but there's a discrepancy in the provided information. We'll give you the received details from Aadhaar in the output and you can show it to the user on your mobile/web application. If needed, you can give the option to the signer to retry. You can also set a limit on the number of retries.