See these links for the ID methods supported by Signicat, the Sign API, the DocumentService API, the PackagingService API, the ArchiveService API, the SealingService API, signing documentation and sealing documentation. If you are not sure where to begin, read Get started with signing or Get started with long-term validation.
Digital communication as well as exchanging of digital documents is increasing. As a result of this expansion the need for safe and user friendly electronically signing of documents is increasing as well. Signicat offers electronic signing and sealing of documents, conforming to the eIDAS regulation.
Signicat Sign can be used for digitizing business processes by applying electronic signatures on documents such as contracts and loan agreements. The advantage of Signicat Sign is the ability to securely identify the user according to EU-regulations – a key component for providing compliant electronic signatures.
When the document is signed it contains, among others, information about who signed the document, when it was signed and whether the signature was valid at the time of signing. It can later be verified that the document has not been modified after it was signed. The signature information is stored in the document and can later be used as legal evidence, as well as for non-repudiation.
Sealing can be seen as a simplified form of signing, where there is no user interaction. This makes it useful for integrating in automated business processes. Sealing is typically used for audit reports, diplomas and attestations.
Supports more than 20 eID methods for identifying the user and signing documents
Physical signing on a digital device, by itself, or in combination with other eID methods
The content of this page can be downloaded as a one pager here.