Setup Signing Policies, Visual Appearances & API

Enterprise signing must be consistent, repeatable, and compliant. Khatim Sign Server allows administrators to define flexible signing policies that standardize how every document is signed while still supporting diverse business requirements.

Policies can be created for formats such as PAdES-BES, PAdES-T, PAdES-LT and PAdES-LTA, giving teams control over cryptography, validation data, visual presentation, and operational status.

Administrators can configure:

• Policy ID and description

• Signature format

• Signing certificate alias

• Hash algorithm

• Approval or certification signatures

• Visible or invisible mode

• X/Y coordinates and target page

• Reason, location, and contact information

• Active or inactive state

For advanced profiles, Khatim automatically handles timestamps and revocation retrieval using configured OCSP and CRL sources. Whether the timestamp service is local or external, the complexity stays inside the server — not in the business application.

Configurable Signature Appearances

When visible signatures are required, branding and clarity matter. Khatim Sign Server lets administrators centrally manage how signatures appear across all documents, ensuring professional, uniform output.

Options include:

• Custom logos aligned with corporate identity

• Optional display of reason, location, and contact details

• Automatic removal of fields when values are not provided

The result is a predictable, standards-aligned signature appearance without per-application customization.

Developer-Friendly REST APIs

Khatim provides a simple RESTful interface that allows business systems, workflows, and portals to submit documents for signing in a secure and controlled way.

No PDF logic.
No revocation handling.
No timestamp plumbing.

Just send the request and receive a trusted, policy-driven signature.

Accept: application/json
Content Type: application/json  
Verb: POST
Body: multipart/form-data

File: "dataToSign":"file",
"signParameters":{
}	

Optional parameters are:
signingPolicyId, documentName, pdfSignatureReason, pdfSignatureLocation, pdfSignatureContact
pdfSignatureApTemplate, pdfSignatureCoord, pdfSignaturePage