New · Docu Signing

Sign PDFs with verified identity.

Docu Signing gives regulated teams identity-bound electronic signatures, signer consent capture, signed PDF artifacts, webhooks, and SHA-256 evidence packages from the same Horkos KYC engine.

Try demo signing Read API docs

Hosted signing link KYC-bound signer Evidence package

Identity-boundSigner KYC linked to the session

Tamper-evidentPDF and evidence hashes

Audit-readyConsent, intent and timeline

API-firstHosted flow and webhooks

How it works

From PDF upload to signed evidence in four steps.

Your backend creates the signing request. Horkos handles the signer journey, KYC handoff, consent, signature event, and final artifact generation.

Create request

Upload an immutable PDF and create a signing session with signer metadata through the Horkos API.

Verify identity

The signer opens a hosted link and completes Horkos KYC when your policy requires identity verification.

Review and sign

The signer views the PDF, accepts electronic signing consent, and confirms intent with document hash matching.

Receive artifacts

Your system receives webhooks and downloads the signed PDF, evidence package, and certificate PDF.

Evidence package

Built for audit, disputes, and regulated workflows.

Docu Signing produces metadata and hashes that show who signed, what they saw, what document was signed, and when the signature event happened.

Signed PDF

Final PDF package with certificate attachment and SHA-256 integrity hash.

KYC reference

Metadata-only verification result summary; raw passport, selfie, liveness, and portrait media are not copied.

Consent record

Consent version, signer timestamp, IP address, user agent, and signature event hash.

Certificate PDF

Human-readable certificate with document hashes, signer metadata, and media-retention statement.

API integration

Create signing sessions from your backend.

Use tenant API keys for server calls, opaque hosted tokens for signer pages, and Horkos-signed webhooks for completion events.

Open Swagger Talk to sales

ExamplePOST /v1/signing/sessions

{
  "//": "Authorization: Bearer ",
  "document_id": "doc_uuid",
  "document_version_id": "version_uuid",
  "verification_required": true,
  "signer": {
    "external_signer_id": "partner-user-123",
    "name": "Jane Signer",
    "email": "jane@example.com"
  }
}

Privacy & security

Clear boundaries between signing artifacts and KYC raw media.

Docu Signing stores legal artifacts and evidence metadata. KYC raw media remains temporary and is not copied into signing tables.

Raw KYC media not copied

PDF and evidence hashes

HMAC-signed webhooks

Retention policy for artifacts

Tenant-scoped access

Use cases

For agreements where identity matters.

Financial agreements

Bind onboarding, loan, investment, or payment documents to a verified signer identity.

Supplier onboarding

Collect signed agreements with identity checks and a structured evidence package.

Employment documents

Remote workforce agreements with signer consent and identity verification trail.

Government forms

Hosted document signing for workflows that need verification before submission.

FAQ

Common questions.

Is this a qualified electronic signature?

Docu Signing is an identity-bound electronic signature with a cryptographic evidence package. We do not claim QES/eIDAS status unless that is separately certified for your deployment.

Can we use it without KYC?

Tenants can configure whether KYC is mandatory, optional per session, or enforced platform-wide for every signing request.

How do we receive the result?

Horkos sends signing webhooks when sessions are signed, artifacts are ready, and finalization completes.

What is retained?

Signed PDFs, evidence JSON, certificate PDFs, hashes, consent metadata, and KYC summary metadata. Raw KYC media is not copied into signing records.

Get started

Request a Docu Signing demo

We will show the hosted signer flow, API setup, webhooks, and evidence package.