One-time Signatures (Hash)

One-time hash signatures allow users to sign documents without a pre-existing integration, using Evrotrust certificates issued based on the Client's identity verification. This approach uses hash-based signing rather than uploading full documents, providing significant advantages in performance, privacy, and security. On the differences between document signing and hash signing pls refer to respective section.

This workflow allows organizations to leverage their own Know Your Customer (KYC) processes for identity verification, with Evrotrust relying on the identification performed by the Client. In this model, the Client acts as a Registration Authority to Evrotrust, enabling document signing based on existing customer relationships or in-person verification procedures.

How it works:

The signing process follows these phases:

1. Identity Verification: The Client verifies the user's identity through their own KYC procedures (either at the current moment face-to-face or based on historical identification).
2. RA IDV Statement: A registration agent from the Client organization provides a signed RA IDV statement to Evrotrust, either signed within the Evrotrust app or signed separately and uploaded via API.
3. Initialise Certificate: Initialize a one-time certificate for the signer by submitting the required identity information and document details'
4. Activate Certificate: Activate the issued certificate by having the user confirm the activation request via OTP or other verification method
5. Send file(s) for signing: Submit the document hash(es) to be signed using the activated certificate
6. Check signing status: Monitor the status of the signing process to confirm when documents have been signed
7. Download signed files(s): Retrieve the signed documents once the signing process is complete

Key characteristics:

• Leverage existing KYC: Utilize your organization's established customer identification processes
• No duplicate verification: Users already identified by the Client don't need to repeat identity checks
• Third-party reliance: Evrotrust trusts the Client's identification procedures and acts upon the Registration Authority declaration
• Two implementation options: RA IDV statement can be signed within the Evrotrust app or signed separately and uploaded via API
• Compliance: Meets regulatory requirements through delegation to the Client as Registration Authority

This approach is ideal for financial institutions, government agencies, or other organizations with robust existing KYC processes who want to extend qualified electronic signature capabilities to their verified customer base without redundant identity checks.

The following endpoints enable this workflow: