EnAcademy Tech Journal

In-Branch Digital Signature

Written by Andrea Fattovich | Sep 16, 2025 1:43:58 PM

Introduction

Euronovate’s in-branch eSignature solution is designed to enable banks, insurance companies, and enterprises to capture legally binding electronic signatures directly at their service desks.
It combines hardware (EnSign11 signature pad), desktop client (EnSoft2), and server platform (EnSoftServer) into a standard architecture that is API-first, modular, and compliant with European and local regulations.
With just a few API calls, organizations can integrate secure, user-friendly digital signing into their existing business processes.

Solution Architecture

The standard architecture includes four main components:
Corporate Services – Your existing systems (CRM, core banking, ERP, etc.) where the process starts.
EnSoftServer - The central engine, on-premise or cloud, exposing REST APIs and managing the signature flow.
EnSoft2 - Windows desktop client, connected to EnSoftServer and controlling the user experience during signing.
EnSign11 - A professional 10.1” signature pad that displays the document and captures the handwritten biometric signature.

The integration point is the EnSoftServer REST API and the SDKs (Java, C#, JavaScript, REST), allowing you to launch and control the signature experience from your corporate applications.

Key Functionalities

  • Support for multi-document dossiers and multi-signer processes.
  • Biometric signature capture (pressure, speed, coordinates) securely encrypted and embedded into the PDF.
  • Operator assistance: mirroring document on the operator’s screen and navigation tools.
  • Callbacks & APIs to retrieve signed documents automatically.
    SDKs for fast integration into web or desktop applications.
    Optional add-ons such as NFC authentication or UI customization.

Execution Flow (Step by Step)

  1. Operator starts the signing process from the corporate application.
  2. Corporate backend prepares the PDF (*) and sends it to ENSoftServer via REST API.
  3. ENSoftServer returns a document ID (GUID).
  4. Corporate frontend calls ENSoft2 via SDK to start the signing process.
  5. EnSoft2 retrieves a lightweight copy of the document and displays it on the EnSign11 pad.
  6. Customer signs on the pad using the magnetic pen; biometric data is captured and encrypted.
  7. EnSoftServer applies the signature image and biometric block to the PDF.
  8. Signed document is returned to the corporate system via API callback.

(*) See how to prepare documents PDF here 

Result: a legally compliant signed PDF with full auditability.

Example API Calls

Integration with the In-Branch Signature Solution happens on two levels:

  • Server-to-Server (REST APIs) → your backend exchanges documents and metadata with ENSoftServer.
  • Client-to-Client (SDK / WebSocket) → your frontend or desktop app controls ENSoft2 and the ENSign11 signature pad.

Server-to-Server Integration (REST APIs)

Create a dossier

A dossier is a container for one or more documents and their signers.

POST /dossier/acquire
Content-Type: application/json
{
  "description": "Test description",
  "dossierType": "STANDARD",
  "locked": "NO",
  "name": "Test 1",
  "owner": "Admin",
  "technicalHeader": {
    ...
  }
}

 

Upload a document

POST /document/acquireFromStream
Content-Type: application/json

{
  "additionalData": [
    {"key": "recipient", "label": "John Doe"},
    {"key":"Name", "label":"Contract"},
…
  ],
  "documentCategoryMnemonic": "CONTRACT",
  "documentTypeMnemonic": "SIGN",
  "owner": "OWNER",
  "technicalHeader": {
    "licenceCode": "",
    "userId": "user001",
…
  },
  "pdfDocument": "BASE64_PDF"
}

 

Retrieve the GUID from the response

{
  "affectedRecords": 1,
  "document": [
    {
      "id": 21533,
      "documentFields": [
        {
          "documentGuid": "39dc635c-ac39-4f44-a7fa-66431b98aac5"
        }
      ]
    }
  ]
}

 

Client-to-Client Integration (SDK / ENSoft2)

Connect to ENSoft2

let ensoft = new ENSoftClient("ws://localhost:7000");
ensoft.open(
  (ok) => console.log(ok ? "✅ Connected" : "❌ Connection failed"),
  () => console.warn("⚠️ Connection closed")
);

 

Start signing a local PDF

const reader = new FileReader();
reader.onload = () => {
  const base64Pdf = reader.result.split(',')[1];
  ensoft.StartSign(base64Pdf);

//Attach to callback
  ensoft.OnDocumentCompleted = (documentResult) => {
    console.log("Signature completed:", documentResult);
  };
};
reader.readAsDataURL(pdfFile);

 

Start signing a server-loaded document (using GUID)

const guid = "39dc635c-ac39-4f44-a7fa-66431b98aac5";
ensoft.StartServerSign(guid);

 

These examples are illustrative. Real implementations require licensed access to ENSoftServer and ENSoft2, as well as ENSign11 signature pads connected to operator workstations.

Your Effort vs Our Services

Your Effort Our Platform Handles
Call a few REST APIs Full signature workflow orchestration
Provide your PDF documents Certificate lifecycle & compliance
Install ENSoft2 on operator PCs Secure biometric capture & encryption
Plug ENSign11 via USB Time stamping, storage & audit trail
Retrieve signed PDF via callback High availability, monitoring & scalability

 

Deployment Options

  • On-premise: ENSoftServer delivered as Docker image (Ubuntu recommended, with SQL Server, Oracle, or PostgreSQL).
  • Cloud: Delivered on Euronovate Cloud or customer’s cloud.
  • Desktop: ENSoft2 installer for Windows 7+ with ENSign11 drivers included.

Conclusion

The In-Branch Signature Solution provides a ready-to-integrate, compliant, and user-friendly way to capture electronic signatures in front of your customers.
It is simple for developers to adopt, while ensuring the highest level of security and legal compliance.

CALL TO ACTION - QUI
View full post