Skip to content

ezSign Signing Service

The ezSign Signing Service is the central service that actually applies the electronic signature. When you sign a document in ezSign, the Signing Service is what performs the signing.

It is a behind-the-scenes service. You never use it directly - ezSign talks to it for you.

What it does

  • Signs the fingerprint, not the document. ezSign sends only a secure fingerprint of your document, and the Signing Service signs that. Your document content never reaches it.
  • Uses keys kept on secure hardware. Signing keys are held in a hardware security module through Key Management, which is what makes the signatures qualified for eIDAS.
  • Serves many organizations. It is a shared, central service run on {{ product_name }} infrastructure.

How it fits in

flowchart LR
    WebApp["ezSign<br/>(in your network)"] -- "fingerprint only" --> Signing["ezSign Signing Service"]
    Signing --> Keys["Key Management<br/>(secure hardware)"]

Figure: ezSign sends only a fingerprint to the Signing Service, which signs it using a key held on secure hardware. Your document stays in your network.

Good to know

  • It never sees your document - only the fingerprint, so document content stays private.
  • It is managed for you. {{ product_name }} runs and configures the Signing Service; your organization connects to it during ezSign setup.

FAQ

Does the Signing Service ever see my document?

No. It only ever receives a secure fingerprint of the document, which is what it signs. The document content stays inside your organization's network.

Are the signatures legally recognized?

Yes. Signing keys are kept on secure hardware, which is what allows the signatures to be qualified under the EU eIDAS framework. Validity can be checked with the Validator.

Do I need to set this up?

No. The Signing Service is run and configured by {{ product_name }}. Your organization simply connects to it while setting up ezSign.