Integrations · NCALayer · state e-signature
Document signing via NCALayer (Kazakhstan e-signature)
Client:
NDA
Category: Integrations
Stack: Bitrix24 D7, NCALayer (WebSocket), PHP, XML/CMS signature, state CA certificate validation
Timeline: 2–3 weeks
Problem
Some documents legally had to be signed with the state digital signature rather than a third-party e-signature service — the signing process ran separately from the CRM, with signed files attached by hand.
Constraints
NCALayer runs through a local WebSocket on the user's machine rather than a cloud API, so the integration has to talk to the client's browser, not just the server; the certificate and signature validity had to be verified.
What I did
- Signing a document via NCALayer right from the deal page — no manual saving and moving of files
- Talking to the local NCALayer WebSocket service from the user's browser
- Verifying the certificate and signature validity before saving the document in the CRM
- Storing the signed file and the signing status on the deal card
Architecture
Deal card
→ Client browser
→ NCALayer (local WebSocket)
→ State CA certificate check
→ CRM document
Result
State-signature signing became part of the same flow as every other deal document — no separate "sign and attach by hand" step.
What can be reused
NCALayer WebSocket integration from the browser
State CA certificate validation
Pattern for storing a signed document on the deal