Signer Authentication for Secure eSignatures

No. Authentication is optional and should be used based on the sensitivity of the document. For low-risk agreements, basic verification may be enough. For high-value or regulated documents, stronger authentication is recommended.

Email OTP sends a one-time password to the signer’s email, offering a simple and familiar experience.
SMS OTP sends the code to a mobile number, enabling faster response and tying verification to a physical device for added assurance.

• For fast and simple signing → Email OTP
• For quick action and better assurance → SMS OTP
• For flexibility with known recipients → Access code
• For strong identity proof and compliance → ID verification
• For stronger authentication without ID upload → Knowledge-Based Authentication

Use ID verification for high-value, sensitive, or regulated documents where strong identity assurance is required, such as legal agreements or compliance-driven workflows.

You create a code during document setup and share it with the signer through a separate channel. The signer must enter this code to access the document.

Yes. You can assign different authentication methods to each signer within the same document based on their role or the level of verification required.

No. Authentication is quick and efficient, usually taking just a few seconds, so it doesn’t slow down the signing process.

Yes. Authentication methods like OTPs and ID verification help prevent unauthorized access and reduce the risk of fraud by confirming the signer’s identity before signing.