Veridi / docs

e-Sign vendor selection

How Veridi picks the active PSrE for digital signatures, and what tenants should know about the trade-offs.

Indonesian law (UU 11/2008 ITE Act §11 + PP 71/2019) recognizes two signature classes: tanda tangan elektronik tersertifikasi (TTE Tersertifikasi, certificate-backed) and tanda tangan elektronik tidak tersertifikasi (TTE Tidak Tersertifikasi, non-certified). Only the certified variant is admissible in court without additional evidentiary burden. To issue a TTE Tersertifikasi the signing certificate must come from a Penyelenggara Sertifikasi Elektronik (PSrE) registered with Kominfo.

How the platform handles vendor choice

Veridi exposes a single ESignProvider interface; the active vendor is selected per deployment via the ESIGN_PROVIDER env variable. Tenant-facing API contracts (/esign/sign, /esign/verify, SDK methods, webhook events) stay identical across vendors so a switch doesn't require any tenant code changes — only a new contract on our side.

Selection criteria

  • Active Kominfo PSrE registration (non-negotiable)
  • Per-signature cost at our projected volume (1k → 100k / month)
  • API maturity, SDK availability, documentation quality
  • Audit trail and revocation flow
  • Tenant ergonomics: white-label support, multi-language
  • Operational fit: payment terms, support tier, incident history

Vendor comparison

Privy

Registered PSrE #001/PSrE/2018
Pros
  • Largest installed base in Indonesia (banks, P2P lenders, telecom)
  • Battle-tested API; SDKs for Web, iOS, Android, server
  • Audit trail surfaces in their compliance portal
Cons
  • Higher per-signature cost vs newer entrants
  • Branded signing experience — white-label requires Enterprise contract

VIDA

Registered PSrE #002/PSrE/2019
Pros
  • Strong identity-verification-first product (KTP + biometric on the same signing flow)
  • Cheaper per-signature than Privy at similar volume
  • Newer API design; OpenAPI spec available
Cons
  • Smaller installed base; less third-party tooling
  • Audit trail UI less mature than Privy

Peruri

Government-owned PSrE (Perum Peruri)
Pros
  • Government-owned — strongest legal posture if the regulator pushes harder
  • Lower price for government and SOE tenants
  • Integrates directly with PrivyID and JakOne ecosystem
Cons
  • Procurement requires BUMN-friendly contract terms
  • API maturity behind private competitors

Current default

Privy is the launch default — it has the broadest installed base and the easiest path to a signed Indonesian-law agreement that we can show regulators in the first compliance review. Tenants whose contracts require a different vendor can request a per-tenant override; raise it with sales@veridi.id.

This page is operational guidance, not legal advice. Last reviewed 2026-05-15.