Security & trust
Cheaper pricing should not mean weaker evidence.
VisiSign changes how e-signatures are priced. It still treats signing as legal infrastructure: audit trails, signer event history, signed PDFs, certificates, API authentication, and verifiable webhooks.
Signing Certificate
Completed document evidence
b8e2f4a8c9d1e6f03a7b91c2e4d58f6a0c3b7d8e9f102a4c6d8e0f1a2b3c4d5e Trust model
We changed the pricing model, not the evidence model.
The goal is to make signatures feel like infrastructure: predictable to price, programmable to automate, and concrete enough to prove what happened.
Record the signing journey
Signer views, consent, field completion, signing, decline, completion, and finalization events are captured with timestamps.
Preserve document integrity
Final signed PDFs are hashed with SHA-256 and distributed with a signing certificate for verification.
Secure automation paths
API keys are hashed and scoped. Webhooks are signed so downstream systems can verify deliveries.
Audit trail
Show what happened, when it happened, and who took action.
VisiSign records audit events around the signing lifecycle. Signing events include timestamped action names and signer context such as IP address and browser user agent.
Viewed, consented, filled fields, signed, declined, reminders, completion, and finalization events are recorded with timestamps.
Signer IP address and browser user agent are recorded for signing events.
Completed envelopes generate a signed PDF and a signing certificate.
The certificate includes SHA-256 hashes for the original version when available and the finalized signed PDF.
Audit trail
Service AgreementMay 14, 2026 09:14:08 UTC
signature_request.sent Agreement sent to Jane SmithMay 14, 2026 09:17:22 UTC
signer.viewed Signer opened the signing linkMay 14, 2026 09:18:03 UTC
signer.consent Signer agreed to use electronic signaturesMay 14, 2026 09:19:44 UTC
field.filled Required fields completedMay 14, 2026 09:20:12 UTC
signer.signed Document signed from 203.0.113.42May 14, 2026 09:20:18 UTC
envelope.finalized Signed PDF and certificate generatedSecurity controls
Concrete controls, not vague badges.
This page intentionally describes implemented controls and avoids claims that require separate certification.
Transport security
Production traffic is forced over HTTPS with secure cookies and HSTS enabled by the Rails production configuration.
Document storage
Uploaded and generated PDFs are stored in private object storage. Primary document storage encrypts objects and metadata at rest automatically; archived documents are stored in a private bucket with server-side encryption enabled.
API authentication
API keys use the `vsk_` prefix, are shown once, stored as SHA-256 digests, scoped by capability, and expire within a maximum 90-day window.
Webhook verification
Webhook endpoints receive a signing secret and deliveries include a Stripe-style `X-VisiSign-Signature` HMAC-SHA256 header over the timestamp and raw body.
Webhook destination safety
Webhook URLs must use HTTPS and are checked against private or reserved IP ranges before creation and delivery.
File validation
PDF uploads are size-limited, content-type checked, and validated against PDF magic bytes before processing.
Audit event protection
Signer IP address and user-agent values are stored on audit events and encrypted at the application layer.
Document integrity
Finalized signed PDFs are hashed with SHA-256 and the hash is included in the signing certificate.
Legal context
Electronic signatures rely on evidence.
VisiSign helps capture evidence around consent, signer events, document completion, and document integrity. Some use cases may require stronger identity proofing or legal review.
VisiSign is designed to support common U.S. electronic signature workflows by recording signer consent, event history, timestamps, and completion evidence.
VisiSign can support standard electronic-signature workflows, but it does not currently claim qualified electronic signature status.
A signing link plus email evidence is not the same as government ID verification. Additional access-code and SMS verification options can raise assurance when needed.
Enforceability depends on document type, jurisdiction, signer identity, consent, and your workflow. Review high-stakes use cases with counsel.
Questions technical buyers ask
Trust FAQ
Will a VisiSign signature hold up?
VisiSign records consent, signer events, timestamps, IP/user-agent context, a signed PDF, and a signing certificate. Legal enforceability still depends on the use case and jurisdiction.
How can I prove what was signed?
Completed envelopes include a finalized signed PDF and a certificate with SHA-256 document hashes, signer details, and audit trail entries.
Are documents encrypted at rest?
Yes. Primary document storage encrypts objects and metadata at rest automatically. Archived documents are stored in a private bucket with server-side encryption enabled.
How are webhooks secured?
Each endpoint has a signing secret. Deliveries include an HMAC-SHA256 signature header so receivers can verify the payload and reject stale timestamps.
Are API keys stored in plaintext?
No. API keys are shown once when created and stored as SHA-256 digests. The dashboard stores metadata such as prefix, creation time, expiration, and last use.
What happens if a webhook endpoint fails?
Deliveries are retried by the job system. Endpoints with repeated failures are disabled after consecutive failures so broken integrations do not retry indefinitely.
Signatures are infrastructure. Treat trust like infrastructure too.
Use VisiSign for flat-rate team signing, API-only signing, and automation workflows with verifiable signing evidence.