Legal

Technical features of the advanced electronic signature (AES) solution

Last updated: 14 November 2026

This is a courtesy translation: in the event of any conflict, the Italian text prevails. Read the Italian version

This page describes the technical features of the advanced electronic signature (AES; under Italian law, Firma Elettronica Avanzata, FEA) solution made available by Grem S.r.l., with registered office at Via Matteo La Fragola, 4, Salerno (SA), VAT no. / tax code IT06136730659 (hereinafter "DOCUJET" or "we"), pursuant to Article 57 of the Italian Prime Ministerial Decree (DPCM) of 22 February 2013 ("Technical rules on electronic signatures"). Publishing the technical features is an obligation of the entity that provides an AES solution under the model referred to in Article 55(2)(a) of the same decree.

1. Subject matter and delivery model

DOCUJET makes it possible to sign electronic documents with electronic signatures of different levels under Regulation (EU) 910/2014 (eIDAS) and Italian Legislative Decree 82/2005 (Codice dell'Amministrazione Digitale, CAD): Simple Electronic Signature (SES) and Advanced Electronic Signature (AES), where the technical requirements are met. DOCUJET provides the AES under the autonomous model (Article 55(2)(a) of the DPCM of 22/2/2013): DOCUJET is both the entity that builds the solution and the one that makes it available to signers.

DOCUJET's AES meets the requirements of Article 26 eIDAS: it is uniquely linked to the signatory (point (a)), capable of identifying them (point (b)), created using data that the signatory can use under their sole control (point (c)) and linked to the signed data in such a way that any subsequent change is detectable (point (d)).

2. Identification of the signer

Identification takes place remotely, before signing, using methods proportionate to the level required.

2.1. Simple Electronic Signature (SES)

The signer is reached at a personal contact point (mobile number or email address) and confirms the signature by entering a single-use OTP code sent there. Possession of the contact point and entry of the code constitute the signing tool.

2.2. Advanced Electronic Signature (AES)

In addition to the OTP, an enhanced identity check is carried out, which the signer completes, at their choice, in one of the following two ways.

a) SPID or CIE digital identity. This option is offered when the sender requires identity verification for the document and the method is active on DOCUJET. SPID and CIE are used to identify the signer, not to sign: the signature is still applied with the OTP.

  • login with SPID (Sistema Pubblico di Identità Digitale, the Italian public digital identity system) at level 2 or higher (two-factor authentication) or with the CIE (Carta d'Identità Elettronica, the Italian electronic identity card, through "Entra con CIE"), as permitted for the AES by Article 27(1)(b) and (c) of Italian Decree-Law 76/2020 (converted into law by Law 120/2020); authentication takes place with the digital identity provider (for the CIE, the Italian Ministry of the Interior) and DOCUJET never receives the signer's credentials;
  • from the identity provider DOCUJET receives only the first name, surname, tax code (codice fiscale) and date of birth, together with the authentication level obtained;
  • comparison of the name attested by the identity provider with the one entered by the sender (name match): if they do not match, the check fails and the signer can try again or choose the other method;
  • retention of the response digitally signed by the identity provider, which documents the authentication process, for at least 20 years (Article 27(2) of the same decree).

b) Identity document and liveness check (KYC):

  • capture of the identity document (front and, where present, back) and a short live recording of the signer's face, on the KYCJet verification page;
  • extraction of the data from the document (OCR) and comparison of the name with the one indicated in the document to be signed (name match);
  • biometric comparison between the recorded face and the photo on the document (face match), a liveness check and anti-money-laundering screening of the name (politically exposed persons, sanctions lists).

In both cases a declaration of acceptance is also required from the signer, who confirms their identity and the exclusive use of the contact point used for the OTP.

The images of the document, as well as the response signed by the digital identity provider, are encrypted at rest with AES-256-GCM. The outcome of the check is recorded in a structured way; for SPID and CIE the audit trail records the cryptographic hash (SHA-256) of the response, without any personal data.

2.3. Identification by the sender

For sender organisations that DOCUJET has expressly enabled, the signer may be identified by the sender itself, with its own procedure, including in person or otherwise outside the platform (for example at a counter, when the contract is concluded or within an existing relationship). In this case the signer does not carry out the identity verification described in section 2.2 and signs with the OTP, after the declaration of acceptance by which they confirm their identity and the exclusive use of the contact detail.

In this mode the sender uses DOCUJET's solution in its dealings with its own signers and takes on itself the obligations to identify the signer with certainty by means of a valid identity document and to keep the related documentation for twenty years (Article 57(1)(a) and (b) of the DPCM of 22 February 2013). DOCUJET does not verify the signer's identity. The sender may attach a copy of the identity document to the document: the attachment is optional, is encrypted at rest (AES-256-GCM), is not shown to the signer and is not verified by DOCUJET.

The audit report of every document signed in this mode states that the identification was carried out by and under the responsibility of the sender, lists any attachments with their cryptographic fingerprint (SHA-256) and names the signers for whom no document was attached. The same statement is recorded in the audit trail when the document is sent.

3. Signing process and architecture

Each signature follows a technical sequence tracked end to end:

  • Full viewing of the document, verified on the server side (scrolling through all the pages);
  • acceptance of the versioned consents, for which the cryptographic hash (SHA-256) of the exact text accepted is kept, together with the date/time, IP address and user agent;
  • entry of the OTP and confirmation of the signature;
  • Qualified Electronic Seal (eIDAS Art. 35) applied by the qualified device of the trust service provider Namirial, to guarantee the integrity and origin of the document;
  • Qualified time stamp (eIDAS Arts. 41-42) for a legally certain date (data certa) that can be relied upon against third parties;
  • PAdES format, with long-term enrichment (PAdES B-LT): the certificates and revocation information are frozen in the PDF, so the signature can be validated independently over time;
  • anchoring of the hash on the Bitcoin blockchain (OpenTimestamps), as a public and independent proof of integrity;
  • immutable audit trail based on a chain of linked hashes, verifiable end to end, which records every relevant event of the signature.

For sender organisations that DOCUJET has enabled for custom clauses, the consents the signer accepts are those written by the sender, which replace DOCUJET's statements described on this page (electronic signature, reading the document, declaration of acceptance). Their content and completeness are the sender's responsibility; DOCUJET still keeps their exact text, cryptographic fingerprint and the date and time of acceptance.

4. Security

  • Data transmission protected in transit (TLS) and encryption at rest of identity artefacts (AES-256-GCM);
  • segregation of data by organisation (multi-tenant) and provider credentials stored in encrypted form;
  • automatic approval only when name, document and face match; otherwise a person decides, or the signer uses SPID or CIE.

5. Allocation of responsibilities

DOCUJET (provider of the solution) is responsible for:

  • building and maintaining the solution in compliance with Article 26 eIDAS and Article 57 of the DPCM of 22/2/2013;
  • identifying the signer using the methods described in sections 2.1 and 2.2 (not in the case of section 2.3);
  • keeping the required documentation (section 6) and making the revocation procedure available (section 7).

The signer is responsible for:

  • providing truthful data and a contact point of which they have exclusive use;
  • safeguarding their contact point and the OTP code, and not sharing them with third parties;
  • checking the content of the document before signing it.

The sender that uses identification by the sender (section 2.3) is responsible for:

  • identifying the signer with certainty, before signing, by means of a valid identity document;
  • checking that the contact detail used for the OTP is under the sole control of the signer;
  • keeping a copy of the identity document and the evidence of the identification for at least 20 years.

6. Retention

The signed document is retained and, if the service is enabled, placed in compliant long-term preservation (conservazione a norma under Italian law) with an accredited preservation provider, to guarantee that it remains unaltered and legible over time.

7. Withdrawal of consent to the use of the solution

The signer may at any time withdraw their consent to the use of the AES solution by writing to support@docujet.it. Withdrawal does not affect the validity of signatures already applied, whose documentation remains stored to meet legal obligations.

8. Legal references

  • Regulation (EU) 910/2014 (eIDAS), in particular Articles 25, 26, 35, 41 and 42;
  • Italian Legislative Decree 82/2005 (CAD), in particular Article 20;
  • Italian Decree-Law 76/2020 (converted into law by Law 120/2020), in particular Article 27;
  • Italian Prime Ministerial Decree (DPCM) of 22 February 2013 ("Technical rules on electronic signatures"), Articles 55-57.

9. Contact

For information on the AES solution or to withdraw your consent: support@docujet.it. For requests about the processing of personal data, please see the Privacy notice.