Server sign activation.
Evrotrust Automated Signing enables organizations to apply qualified electronic signatures (QES) or qualified electronic seals (eSeal) to documents automatically, as part of a system-driven business process. For more details on this product, pls refer to the Guides Section.
Getting Started
This functionality can be used only from authorized by your company employee/s for signing a specific document/s or group of documents automatically (no action is needed by the employee after this functionality is activated).
In order to activate this functionality for test environment you need to follow the below steps:
-
The authorized employee should register as a user in our Evrotrust test mobile application. For the registration please send to [email protected] the following information:
Please add testers for the company name and also activate server sign for them:
- Names
- Personal ID number
- Testing device OS: please specify Android or iOS
- Email registered Android/Apple
- Document name
- Document description
- Mandatory preview: please specify Yes or No
NB! If you plan in your process to have group of documents send for server signing, please include group documents description.
-
After you receive a confirmation by our side that the users are activated, each user should download Evrotrust test mobile app and activate the server sign option through his own profile.
For more details pls refer to the User Guide for Corporate Sign.
Signing Requests
Automated signing will be initiated, if the optional parameters automatedSignCertID or automatedSignSealID are defined with a valid certificate code. The following endpoints allow for automated signing or authentication.
| Step | Single File | Group of Files |
|---|---|---|
| Signing via App/SDK (Documents) | /document/doc/online | /document/group/online |
| Signing via App/SDK (Hashes) | /document/hash/online | /document/group/hash/online |
| One-time Signatures (Documents) | /document/doc/offline | /document/group/offline |
| One-time Signatures (Hashes) | /hash/offline/init | /hash/group/offline/init |
| e-Authentication | /document/auth/online |
The response of these endpoints also include the parameters automatedSignCertID or automatedSignSealID.
Check Signing Status
As with other signing transactions status can be checked via the following endpoints or webhooks.
| Step | Single File | Group of Files |
|---|---|---|
| All Signing | /document/thread/status | /document/thread/status |
| Signing via App/SDK (Documents) | /document/status /document/ready | /document/group/status/document/group/ready |
| Signing via App/SDK (Hashes) | /document/status /document/ready | /document/group/status /document/group/ready |
| One-time Signatures (Documents) | /document/status/document/offline/ready | /document/group/status /document/group/offline/ready |
| One-time Signatures (Hashes) | /hash/certificate/check/hash/offline/check /document/offline/ready | /hash/group/certificate/check/hash/group/offline/check /document/group/offline/ready |
The response of these endpoints also include the parameter automatedSignError.
The values for automatedSignError are:
- Certificate ID does not exist
- Certificate transaction value does not match
- Certificate ID not valid for your vendor number
- Certificate is not active