Server Processing

DOCUMENT CONTENT LEAVES YOUR INFRASTRUCTURE

In Server Processing mode, your documents are sent in clear text to Certifaction for signing. Certifaction can access, log and process document content. Server Processing does not provide the end-to-end encryption benefits of Local Processing.

Server Processing is intended for use cases where running the Local Client is not practical — for example, a low-volume workflow launched from an environment where deploying additional software is not an option.

How Server Processing works

Unlike Local Processing, the whole document — not just its hash — leaves your infrastructure. Every step that touches document content happens inside Certifaction.

Moving to Local Processing

Switching to Local Processing is straightforward: deploy the Local Client in your environment and route your signature requests through it instead of directly to the Certifaction API. The API surface stays the same, so your existing integration code carries over — the only difference is that the Local Client hashes and encrypts documents on your side, and only cryptographic material leaves your infrastructure.