Skip to content
Markdown
ConceptForEveryoneWith or without Foxden Admin

Corsac, e-signatures ​

Corsac lets your company send a PDF for signature and get back a sealed copy that anyone can check later, without an account. It runs on your own server, so your agreements and the evidence of how they were signed stay with you.

You upload a PDF, say who signs it, place the fields they fill, and send it. Corsac emails each person a link, walks them through signing, and when everyone has finished it seals the document, adds a certificate of completion and gives you a verify link.

Who uses Corsac ​

  • People who can use Corsac upload documents, send them, follow them and keep templates. They see their own documents and the ones shared with the members.
  • People who can manage Corsac also set it up for the company: signing policy, the seal certificate, people, branding, API keys and webhooks. See Set up Corsac for your team.
  • The owner of a document is the person who uploaded it. Only the owner changes who can see it, names readers or turns on a view link.
  • People outside the company take part through the links Corsac emails them. They never need an account:
    • a Signer fills their fields and signs;
    • an Approver approves or declines, with no fields;
    • a Viewer confirms they have read it, with no fields;
    • a CC gets the finished copy and takes no part in signing.

A signer's side of it is on Sign a document.

What a sealed document proves ​

When a document reaches its end (completed, declined, voided or expired), Corsac seals it. The sealed copy is the original PDF with the filled fields stamped on it and a digital seal over the whole file. A declined, voided or expired copy carries a DECLINED, VOIDED or EXPIRED band on its first page, so it cannot pass for a signed one.

Four pieces of evidence travel with every sealed document:

PieceWhat it isWhat it proves
The sealA digital signature over the PDF, made with your server's seal certificateThe file has not changed since Corsac sealed it
The trusted timestampA stamp from an outside timestamp authority, added on top of the sealThe sealed file existed at that time, by a clock that is not your server's
The audit trailEvery event in the document's life (sent, opened, code checked, signed, declined, voided) in a chain where each event's hash covers the one beforeNothing was removed or rewritten after the fact
The certificate of completionA PDF with the parties, the event log and the fingerprints of the original and the resultA readable record you can file or hand to someone

The verify link (on the document's page and in the completion email) opens a public page where anyone can see the verdict, download the signed PDF, the certificate and the evidence chain, and check the seal's fingerprint. See Verify a signed document.

Limits ​

  • It is not a qualified or advanced electronic signature service. Every certificate of completion says so: the seal is cryptographic tamper evidence, not an eIDAS advanced or qualified signature. Corsac's own /limitations page on your server lists what it is not, in full.
  • The seal certificate is self-signed unless you import your own. Nothing outside your server vouches for it, so a PDF reader may warn about it, and the EU DSS validator reports INDETERMINATE / NO_CERTIFICATE_CHAIN_FOUND. That means "not qualified", not "not valid". To have the seal chain to a certificate authority, import a certificate from one (see Set up Corsac for your team).
  • If no timestamp authority answers, the document is still sealed, but the sealing time is your server's own. The document page and the verify page say so.
  • Corsac sends no email until email is set up on the server. A new install starts with mail off. Documents can still be sent, but you copy each signer's link and pass it on yourself, and email codes cannot arrive. See Set up email.
  • The evidence chain carries each signer's IP address and browser. Anyone with the verify link can download it. The verify link only travels with the signed document.

Pages in this section ​

Corsac in the sales path, from a website form to a signed agreement filed in Library, is on From enquiry to signed agreement.

Foxden is open source under Apache-2.0.