The signature soft pad, which is included with the Document Viewer, is used to capture a signer's graphic signature. This SVG image is patched into the signature field and digitally signed.

This process is already secure because the data is added, the signature is added and the document is digitally signed and therefore tamper-proof. However, there are some legal requirements that make it necessary to prove that a signature belongs to a particular person. Therefore, the raw signature data will be available in a future version of the Document Viewer.

Signature Points

An array of SignaturePoint arrays is included in the SignatureData object passed by the viewer. The location of each captured signature point and a timestamp are stored in the SignaturePoint class.

Learn More

Learn how to handle signature requests server-side. The most common server-side Web API methods for handling electronic signatures are described in this article.

Common Web API Methods for Handling E-Signature Workflows in ASP.NET Core C#

Calculate the Duration

For example, you can use this jagged array to calculate the total time of signature capture.


This array could be serialized and stored in a database or encrypted in the document for later comparison with the actual signature stored for the signer. In the event that the signer doesn't have a specific signature stored, the way in which the signer creates his or her own signature can be played back and compared.

Replay the Signature

Based on the timestamps, the following JavaScript code replays the array, including the write speed.


This can be used to compare a signer's actual signing with stored signature data.

Signature Replay

The new feature adds an extra layer of security to the process of signing electronic documents.

Stay tuned for more features!