Skip to content
Evidence and verification

The record is the part you shouldn't DIY

A row in your own database is yours to edit. We seal and store live records, then add external timestamps and checkpoint proofs asynchronously. Verify exported evidence packages offline.

Recordrec_Z4m8
simple · L1
RecordedWritten durably, receipt signed with ES256
TimestampedExternal RFC 3161 token over the record hash
AnchoredPublic anchor pending
Checkbox changed by a trusted user eventobserved
Terms of Service, version dv_3kT9observed
Server time 2026-11-21T15:03:20.291Zobserved
Signer email dana@example.orgasserted
record_hash sha256:5be7…example record

What a record holds

Depending on the ceremony, records include signer details, verification results, document hashes and render matches, presentation and consent events, the intent control and exact label, event times and request metadata, copy delivery, and the seal.

Provenance

Observed or asserted

Evidence fields distinguish observed from asserted facts. The measured facts are sealed; advisory conformance judgments are stored separately.

  • observedSeen by Esign Comply directly from the signer's device, or generated by Esign Comply.
  • assertedSupplied by you with the session: the signer's name, external ID, and state, and the facts you pass.
  • customer-suppliedSent by you after signing. Sealed by Esign Comply with its own receipt time.

What we record and check

  • We capture, seal, and store events that the service receives.
  • We check conditions on our own record, such as whether the document version matches.
  • A blocking failure prevents the seal; a warning stays with the record.

What you build after signing

The prompt lists the steps that follow a signature. You build them, and you can send us a report of each one to seal beside the record.

Your obligations

You build the steps that follow a signature: renewal reminders, cancellation handling, and delivery of required copies. Esign Comply sends the signer a receipt when a signer email is known, unless your L1 acceptance profile uses customer delivery.

What we recommend

The generated prompt keeps "Your obligations" apart from "Recommendations" and suggests what to send us. A recommendation never blocks a session or adds a required step.

Prompt generator
POST /v1/supplements

Send us what you have

Use POST /v1/supplements to send free text, JSON, or files as customer-supplied material. Attach it to a record, session, signer, document version, or your domain.

  • We accept custom types and fields, seal the material with our server receipt time, and list it separately in the evidence report.
  • You can request a separate list on a certificate.
  • The seal shows what you reported and when we received it.
  • Sending a supplement is optional and never changes the sealed record or a check result.

How it is sealed

The API stores the record before responding and normally returns a signed receipt. The external timestamp and public anchors follow asynchronously.

recordedtimestampedanchored
  1. 01

    Canonicalize

    The API serializes the record using RFC 8785, adds a random 256-bit salt, and hashes it with SHA-256.

  2. 02

    Chain

    The API durably writes the record and its per-domain ledger entry before responding. Live records are hash-chained per domain.

  3. 03

    Seal

    Normally the API also returns an ES256-signed receipt. Receipts are signed with hardware-backed keys held outside the database in a separate AWS account.

  4. 04

    Timestamp

    An external RFC 3161 authority timestamps each live record hash asynchronously. Two authorities per region provide failover.

  5. 05

    Batch

    Ledger entries are batched into signed regional Merkle checkpoints every 60 seconds.

  6. 06

    Anchor

    Public anchors follow asynchronously. Protected checkpoint bundles are kept in write-once storage.

  7. 07

    Prove

    After timestamping and checkpoint inclusion, the evidence package carries the timestamp token and the inclusion proof for the record.

Timing targets are 60 seconds for the external RFC 3161 timestamp, 2 minutes for checkpoint inclusion, and 2 hours for public anchoring. The external timestamp shows that the record hash existed no later than the time the outside authority states.

Where keys are held

What you can download

PDF, per record

Evidence report

The per-record PDF is an evidence report titled "Electronic Signature Evidence Report" or "Electronic Acceptance Evidence Report," depending on the ceremony. It shows what the service received and how it was recorded.

  • It omits IP addresses and raw device data by default.
  • The embedded signature authenticates the receipt fields.
Export

Evidence package

The evidence package includes the record, signed receipt, available timestamp and checkpoint proofs, retained document bytes, public keys, and verification instructions.

  • Where captured, it also includes the assent-region markup and a reconstruction of the region from that markup.

How to verify

Check an exported evidence package with the open-source verifier, offline and without an account.

  1. 01

    Offline verifier

    Run the open-source esigncomply-verify over an exported package without network access.

  2. 02

    Signed receipt

    Submit the full signed receipt to POST /v1/verify for proof status.

  3. 03

    Public verification page

    The public verification page is a generic entry point: a record ID alone reveals neither record existence nor metadata.

  4. 04

    Signer view

    Signers use a one-time code to see their own record and copies.

Anyone you give the package to can verify it offline, without an account.

Statements on request

Get a sealed statement of what Esign Comply recorded and when.

On-request certificate

Contemporaneous Record Statement

This on-request certificate is a dated, sealed PDF for a timestamped live record or a set of records. Request it in the dashboard or through the API.

It separates browser-reported times from server receipt times and reports the external timestamp under RFC 3161, the public anchor when available, capture mode, later history, the process in force, and fresh integrity checks. If a check fails, no certificate is issued or charged.

Use it as a supporting exhibit when you hand the evidence package to someone else.

Human service

Custodian declarations

A named Esign Comply records custodian signs the separate "Certification of Custodian of Records" about our system, recording practices, and observations. The federal form is written for the procedures in Federal Rule of Evidence 803(6) and Federal Rule of Evidence 902(11), (13), and (14). Rules 902(13) and (14) are federal procedures.

The declaration covers what Esign Comply observed and recorded. Your counsel gives the notice those rules call for.

Delivery is within 5 business days. Starter pays $250 per request; Unlimited includes 5 per subscription year, then charges $250 each; Enterprise terms are contracted.

Wording variants

For eligible original records, the federal wording is "made at or near the time" under Federal Rule of Evidence 803(6). For deferred or imported records, the statement gives the time Esign Comply received the report and labels the reported act time as a customer assertion.

Verify it without us.

Free plan: 10 live signatures a month and a full test mode. No card required.

Working with an AI tool? This page is also available as Markdown: /product/evidence.md