Default settings: Signing process via e-mail
After setting up E-Signatures, the by-default-way of signing a contract will be that your customer will receive an email with the instructions to e-sign the document. However, there is a more streamlined option that can be performed directly within an application using "embedded signing".
Why embedded signing
Embedded signing enables customers to view and sign documents directly through your website, avoiding the need to switch contexts to email.
How to set it up
To use embedded signing to elevate your end-user signing experience, get in tough with Signable's customer support.
Security Measures for Signable Integration
Signable may ask whether the integrator (Kinnovis) has implemented specific security measures. We can confirm that the integration has been developed with the following safeguards in place:
Secure Embedded Signing: The embedded signing process is protected through an SSL-secured HTTPS page.
Customer Identification via Hashing: When a customer submits their contact details, we generate a unique hash specific to that customer. This hash is used throughout the checkout process to ensure data consistency and security.
Two-Step Verification: Before the signing process begins, we collect the customer’s payment data. This provides an additional layer of security by introducing two verification stages.
Keywords: esignature, signature, sign, esigning