Have questions? Start here.

Yes. You create an envelope with one or more documents, place signature fields on the PDF and define who signs and in what order (sequential, parallel, mixed or conditional flows). Each signer receives a single-use link, signs with a drawn or typed signature plus an OTP code, and once everyone is done they all receive the final document with the signatures stamped and its completion certificate.

No. The signer receives a link by email, reads the document in the browser (mobile included), signs and verifies their identity with a code sent to their email. No sign-ups, no downloads.

Certums implements simple electronic signatures (SES) with strong evidentiary support — consent, OTP, chained cryptographic fingerprints, RFC 3161 timestamping and a PAdES-signed completion certificate — and supports advanced (AES) and qualified (QES) levels through trust service providers. Admissibility depends on the jurisdiction and the type of act: see our legal validity page.

A contract repository with terms, value and renewal alerts, a library of reusable clauses, negotiation with proposals and diff (redlining), no-code automations and AI-powered data extraction reviewed by humans.

Yes. The entire platform is available as a versioned REST API with API keys, HMAC-signed webhooks and embedded signing via iframe to bring the ceremony into your app. See the developers page.

A Secure Verification Code: a unique, non-enumerable, high-entropy alphanumeric string that acts as the document’s public locator. Anyone can enter the CSV at certums.com/v/... and verify the document. The CSV does not replace the digital signature; it identifies the document within Certums.

Individuals, businesses, SMBs and institutions. There are Personal plans (1 user, storage and retention suited to individual use) and Business plans (multi-user, with branding, policies and SLA).

Because verification is the foundation of the document’s public trust. Charging per verification discourages its use. Abuse protection is handled technically (rate limiting, captcha, monitoring) and does not affect your plan.

PAdES B-LT by default on Essential / Starter plans and up, and B-LTA on Pro / Growth / Institutional. Signing is performed with keys managed by an HSM, KMS or a QTSP — never with keys on the server’s disk.

The document moves to the “revoked” state with a reason and an audit trail. Public verification reflects the change immediately: anyone who verifies the CSV again will see the new state.

You issue a new document (with its own CSV) that links to the previous one. Public verification of the original CSV shows the “superseded” state and, if the policy allows it, a reference to the new CSV.

Yes. Each institution is a closed tenant, validated by organizationId on every query and by automated isolation tests. Not even the Certums team can access your documents without an audit trail.

In an S3-compatible store (MinIO in local deployments, institutional infrastructure or Cuban institutional cloud). Signed files are immutable and subject to your plan’s retention policy.

Yes. The Enterprise plan includes a dedicated deployment on a VPS, Cuban cloud or your own institutional infrastructure, with integration with your cryptographic keys and personalized support.

Not the CSV itself; what expires is the document. The expiration policy is defined per document type: no expiration, fixed expiration or by period. Once expired, public verification reports it explicitly.