API'S FOR OUR SERVICES

Signature

The Signature API contains a number of operations which can be selected to fit specific requirements

Seal

The Seal API handles documents to be sealed and returns sealed documents. The legal person's authorization to seal is included in the communication

Timestamp

Comfact Timestamp receives a hash/"fingerprint" of data and returns a timestamp from the TSA

Delivery

Integrating Comfact Delivery with a business application will allow communication to be handled directly from the application

Validation

When Comfact Validation is integrated with a business application, it will allow for all documents to be included to be validated beforehand

Preservation

Comfact Preservation can be integrated with business applications using our API

SIGNATURE API'S

Comfact provides different solutions for electronic signatures in order to meet customers' requirements, such as complying with:

eIDAS, ETSI and CEN standards for remote signature
Cloud Signature Consortium
OASIS Digital Signature Services
The national Swedish Normative Specification
Basic simple signature

As more alternatives become available, we will develop solutions for these. In some cases you can view standard APIs as a "black box" doing signature "magic". Signature services complying with these standards provide more of a statement of their capabilities.

EXAMPLE OF SIGNATURE COMMUNICATIONS VIA A WEB BROWSER

The signatory uses a browser to signify their intent to sign a document using Comfact Signature or another signature provider. Comfact Signature sends the sign request to Comfact DSS. Comfact DSS then sends an authentication request to the identity provider which returns an authentication response containing the signatory's identity/attributes. Then Comfact DSS sends the sign response back to Comfact Signature with the signed document.