The signing page

Modified on Thu, 28 Sep 2023 at 02:12 PM

The signing page is where the user interacts with the signing process. Here, they can upload requested documents, read them for signing, and either sign or refuse them.


We will now provide a detailed explanation of all the options the user may encounter in the signing flow.


User Authentication

When the signatory has an assigned identification method, they are required to verify their identity before accessing the documents. 

If allowed by the sender, the signatory has the option to choose their preferred method of verification. 

You have two options:

  • Entering a familiar access code, which is not sent to them. 
  • Entering a one-time code received via email or sms. 

The signing page


The signing page has two main sections, each serving distinct purposes.

  • Users can view the documents awaiting their signature in the central block, accompanied by the convenient "Refuse" and "Sign" buttons.
  • On the left-hand sidebar, they have an overview of all the documents requiring their attention, including the list of signatories, if applicable, along with a handy QR code for quick mobile access.

Template Configurations Impacting Signing Page Behaviour


Sign Button Activation


The behaviour of the "Sign" button can be configured in different ways:


  • It can always be active and accessible
  • It may only become active once the user has opened all the documents.
  • Alternatively, it can activate when the user reaches the end of the document list.


Notifications above the buttons inform users about the necessity of opening or reading the documents.


Additionally, the sidebar provides a clear indication of the status of each document.

List of Signatories


An optional feature is the inclusion of a signatory list, providing users with an overview of all parties involved in the signing process. This list is displayed in the sidebar alongside an icon denoting whether or not each signatory has completed their signature.

Refuse Button


Users may be allowed to refuse certain documents to expedite the signing process and avoid unnecessary waiting. This allows them to decline specific items without waiting for the submission to expire. Users can also provide reasons for refusal, which can be mandatory or voluntary.


As shown in one of the images above, the button is next to the Sign button. The "Refuse" button, located next to the "Sign" button, opens a pop-up window where users can enter their reasons for refusal if this feature has been enabled.

Upload documents

During this step, signatories have the opportunity to upload any required documents. Depending on the template settings, some documents may be mandatory, while others can be optional.

Furthermore, you can directly upload documents from cloud storage platforms like Google Drive or Dropbox.

Signing the documents


The template configuration and the chosen signature method influence the signing process. 


Regardless, the user experience remains consistent, with a floating window presenting relevant information and fields for entering necessary data.


It's worth noting that users only need to click the "Sign" button for simple signatures, eliminating the need for additional interactions.

Sign with OTP 


The template configuration affects three secondary factors of this signature method:

  • Code Reception: Upon entering the signing page or clicking the "Sign" button, users will receive the code.
  • Code length.
  • Allowed Attempts: Exceeding the permitted number of incorrect code entries will result in the cancellation of the submission. 


Handwritten Biometric Signature or Typed Signature

Both options are conveniently grouped within the same floating window, organised under separate tabs, and offer a seamless user experience without customisable behaviour options.

Signature with digital certificate 


To enable qualified signatures per the European eIDAS regulation, direct signing with a digital certificate from within the web browser page is not feasible. Therefore, users must select the location where their certificates are stored.

1. Computer-Based Signing


This option requires the installation of a lightweight plug-in called eSignaDesktop, which is automatically installed if not already present.


eSignaDesktop empowers users to sign with certificates stored on their computers, including those issued by, and external devices like smart card readers or USB keys.

2. Centralised Cloud Signing 


With centralised cloud signing, users can utilise certificates issued and managed by While certificates issued by other entities can be imported, they won't generate qualified signatures. On the other hand, Lleida. net-issued certificates provide the highest level of robustness and qualify for qualified signatures


Authentication is required using the username and password associated with the certificate.

3. Sign with a mobile phone 


Users must have the Wallet application installed on their Android or iPhone devices. This application empowers users to sign with certificates issued by, ensuring a seamless and secure signing experience.


To initiate the signing process, follow the prompts on the mobile app and choose the desired certificate. Once the certificate is selected, the signatory will receive an SMS and email containing a unique one-time verification password  (OTP) to ensure the security of the signing process. To complete the signing, the user can effortlessly use their fingerprint or enter their PIN.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article