Architecture

How SecureSign connects your portal to DSC signing through two products.

High-Level Flow

Platform Overview Mobile App and Desktop Software (same securesign:// deep link) MOBILE PATH DESKTOP PATH Browser 1 Portal 2 Hash DEEP LINK 3 securesign://sign ?requestId&hashBase64 4 Mobile App 5 DSC Token CALLBACK callbackUrl?ss_result=... Browser JS 1 Portal DEEP LINK 2 securesign://sign opens Desktop Software 3 Token, cert, PIN callbackUrl 4 Desktop Software 5 DSC Token signatureBase64 to browser Product UI (both paths) Mobile App DSC Rajesh K. 4A3B..1D PIN Sign with DSC Narrow phone — Android / iOS Desktop Software DSC Sign Rajesh K. | 4A3B2C1D valid 2027 Sign with DSC Wide window — Windows / Linux / macOS No public SDK — Mobile App + Desktop Software only | Enterprise SDK: contact enterprise@toolsbots.com
Standard products only — no public SDK distribution

Mobile Path — SecureSign Mobile App

  1. User opens your portal on Android or iPhone browser (or native app WebView)
  2. Portal generates document hash and redirects to securesign://sign
  3. SecureSign Mobile App opens, reads DSC token, collects PIN
  4. App signs and returns signature to your callbackUrl

See Mobile Browser Flow and WebView Handoff.

Desktop Path — SecureSign Desktop Software

  1. User opens your portal on Windows, Linux, or macOS desktop browser
  2. Portal generates document hash and redirects to securesign://sign
  3. SecureSign Desktop Software opens, reads DSC token, collects PIN
  4. Software signs and returns signature to your callbackUrl

See Desktop Browser Flow.

Enterprise Desktop SDK

For organizations that need custom desktop applications with signing embedded inside their own software (without launching SecureSign UI separately), licensed SDKs are available under enterprise agreement.

SDK not publicly available

We do not distribute SDK source or packages publicly. This protects Toolsbots SecureSign product code and intellectual property. Contact enterprise sales.

Backend services: Platform Services.