1. Home
  2. Dokumente
  3. sign
  4. Implementation Scenarios

Implementation Scenarios

Please note that the implementation of AUTHADA sign requires the user’s identification in order to allow a legally secure qualified electronic signature. Therefore, AUTHADA ident is included in the signing process. For more information on AUTHADA ident, please refer to the respective product documentation. 

Standalone (AUTHADA Frontend)

As of right now, it is possible to implement AUTHADA sign as a standalone solution, which allows a fast and easy integration. Integrating AUTHADA sign via SDK is currently not possible but our software engineers are working on this feature. The current implementation scenario (“Standalone”) allows for minor design modifications (e.g. inserting logos). More comprehensive design modifications will be possible with the SDK implementation. 

In this scenario, the AUTHADA sign web frontend is used in order to easily integrate AUTHADA sign into existing web applications. 

It is up to the service provider to initialise the session, upload the documents, and start the signing process. The user is then redirected to the AUTHADA sign frontend. Identification data can be retrieved by the service provider either between the identification and the signing process or after the whole process has been completed. After completion, the user is redirected to the service provider’s frontend. 

SDK (Customer’s Frontend)

Instead of using the AUTHADA frontend, it is also possible to implement and use your own frontend.