Desktop Browser Integration

Invoke SecureSign Desktop Software from desktop browsers using the securesign:// deep link — same protocol as mobile.

Overview

Desktop browsers on Windows, Linux, and macOS use the same securesign://sign deep link as mobile. Your portal redirects the browser to the deep link; the OS opens SecureSign Desktop Software, which handles token access, PIN, and signing. The signed result returns to your callbackUrl.

Deep Link Handoff

Use the same query parameters as mobile. Set documentType to hash, pdf, or xml as needed.

securesign://sign?requestId={uuid}&hashBase64={sha256}&hashAlgo=SHA256&documentType=hash&callbackUrl={encoded}&apiKey={ss_live_xxx}

JavaScript example

const params = new URLSearchParams({
  requestId: crypto.randomUUID(),
  hashBase64: sha256Base64,
  hashAlgo: 'SHA256',
  documentType: 'hash',
  callbackUrl: 'https://portal.example.gov.in/sign/callback',
  apiKey: 'ss_live_abc123xyz'
});
window.location.href = `securesign://sign?${params}`;

Full specification: Deep Link Protocol. Step-by-step flow: Desktop Browser Flow.

Installation

• Windows: Download installer from Admin Console → Downloads
• Linux: sudo apt install securesign-desktop
• macOS: brew install --cask securesign-desktop

SecureSign Desktop Software must be installed and running in the background before the user signs. Register the custom URL scheme during install so securesign:// opens the software.

Common Error Callbacks