eSignLive Developer: Authentication and System Requirements
In this blog, I will go over what you might have missed in the eSignLive Developer Community during the week of February 19th, 2018. Let's get straight to it.
When creating a transaction in eSignLive, the default authentication method is by email. The recipient is sent an email from eSignLive that contains a link to the Signing Ceremony. The signer is automatically authenticated upon clicking this link. However, additional security can be added to verify the identity of the recipient. A signer can be authenticated by: • A series of questions to be answered (Q&A) • A numeric pass code sent by SMS • Knowledge-Based Authentication (KBA) With Q&A, the recipient must answer a series of questions set by the sender in order to gain access to the transaction. If SMS authentication is chosen, a pass code is sent to the recipient’s mobile number that they must enter before continuing the signing process. Lastly, a recipient can also be authenticated by Knowledge-Based Authentication. KBA requires knowledge of personal information of an individual to grant access to protected material. eSignLive currently supports Equifax US and Equifax CA. Upon receiving the transaction, the recipient will be presented with a series of questions related to his personal credit report. To enable Knowledge-Based Authentication, please contact our support team at [email protected]. Link to Guide
Elsewhere, integration with eSignLive is secured via an SSL certificate issued by GlobalSign. Hence, if your environment has strict rules regarding certificates, this GlobalSign intermediate certificate must be installed. You can find a summary of the software requirements for integration with eSignLive. Link to Documentation If you have questions regarding this blog or anything else concerning integrating eSignLive into your application, visit the Developer Community Forums: developer.esignlive.com. That's it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn. You can find all of my previous blogs by going to my author page.