Khatm

Implementation · From sandbox to production

Your integration, all the way to production.

You validate the integration in the sandbox. We prepare production with you: signing flow, branding, signer identity, certificates and rollout.

Five steps, one point of contact.

Each step ends with a deliverable your teams sign off before we move on.

  1. Scope Your current process, signer roles, business rules and volumes. Deliverable : Scoping note and agreed scope
  2. Adapt The Khatm flow to your brand, languages and scenarios. Deliverable : Flow validated on your mockups
  3. Integrate The API and webhooks inside your application, with your developers. Deliverable : Integration tested in the sandbox
  4. Connect Signer identity and the certificates chosen for production. Deliverable : Certificates and identity connected
  5. Deploy Testing with your teams, then a gradual production rollout. Deliverable : Monitored go-live

What the demo proves, what production defines.

The sandbox proves the flow. Production depends on the trust choices made for your project.

Demo and sandbox · Sandbox · today

  • Complete flow: preparation, signing, tracking
  • PAdES signature with a test certificate
  • Signed PDF with PDF and JSON evidence
  • Files deleted 10 days after upload
  • An “unknown identity” warning is expected in PDF readers

Your project in production · Production · with you

  • Certificate from your PKI, HSM or trust service provider
  • Signers identified through your identity provider
  • RFC 3161 timestamps when your provider supplies them
  • Retention period agreed with you
  • Rollout planned with your teams

What we adapt.

The scope is defined with you, then validated against your test scenarios.

Signing flow

  • Business rules : Signing order, roles and approvals that match your organization.
  • Brand and languages : Your visual identity, in Arabic, French and English.

Integration

  • Inside your application : The signing link appears in your interface or portal.
  • Joint engineering : Data exchange, webhooks and rollout planned with your developers.

Trust

  • Signer identity : Your identity provider or authentication flow, with no Khatm account imposed.
  • Certificates : The PKI, HSM or trust service provider chosen for production.

Trust comes from your infrastructure.

Khatm orchestrates the flow. What gives the signature its value is connected project by project.

  • PKI : Certificates from your company or certificate authority.
  • HSM : Signing keys kept in a secure hardware module.
  • Timestamping : RFC 3161 timestamps supplied by your provider.
  • Identity : Signers identified through your identity provider.

Khatm is not a qualified trust service provider and does not issue certificates. Legal value depends on the infrastructure and identification chosen for your project.

Questions we often hear.

Can Khatm replace DocuSign or another market tool?

Not as a turnkey service. Khatm is a signing engine you build into your software, under your brand, which we connect to the trust layer that fits your market.

Do you offer white label?

Yes, as part of an integration project: the flow uses your brand, languages and tone. There is no self-service white-label offer yet.

Is Khatm a qualified trust service provider?

No. Khatm orchestrates PDF signing. It issues neither qualified signatures nor certificates: in production they come from the infrastructure you choose.

Why does Adobe show “unknown identity” on a demo-signed PDF?

The demo certificate is self-signed and outside any public chain of trust. That is expected in the sandbox. In production, the certificate comes from your provider.

Does the demo have legal value?

No. It validates the technical flow and user experience. Legal value depends on your trust choices and your advisers’ opinion.

How much does an integration cost?

It depends on scope: application, volumes, languages, connections and signature level. We prepare a proposal after scoping.

What is the first concrete step?

Try the demo or the API sandbox, then send us your use case: application, sample document, signers and volumes. We come back with a scoping proposal.

Tell us about your project.

Describe your application, a sample document, your signers, volumes and constraints. We come back with a scoping proposal.

contact@khatm.io