Policies signed at the counter, at the kitchen table, or on a phone
Insurance is where one signing method is never enough. The same insurer needs a pad at the branch, a bank-identity check for a remote sale, and a one-time code for a claims form. Signosoft covers all three in one product — and already runs at Kooperativa, Česká podnikatelská pojišťovna, and Generali Česká pojišťovna.
Three sales channels, three different signing problems
Most insurers end up with a different tool per channel, then discover that their evidence looks different in each one — which is exactly the wrong outcome when a claim is disputed.
At the branch
The customer is in front of you. A signature pad captures pen pressure and timing, and the adviser can identify the customer from their ID document before anything is signed. The strongest evidence available, and the fastest experience.
Remote sale
The customer is at home. Their bank identity verifies who they are — an identity the bank has already checked — and the same identity can sign the policy. No posting documents, no branch visit, no scanning.
Adviser and broker networks
The person selling is not your employee. A tokenised link and a one-time code let them get a policy signed without an account in your systems — while the protection policy and the certificate requirements stay under your control.
The paperwork insurers actually run through it
Policy origination
The policy is generated in your own system — the core platform, the CRM, the quotation engine — and handed to Signosoft as a finished PDF. The customer signs, and the signed document comes straight back into your archive through a finalisation plugin. Nothing is retyped and nothing is printed.
Templates for each product line, so field layouts are set once Initials on every page where the product requires acknowledgement Attachments — terms, product information — carried with the policy Form fields lock once signed, so nothing can be altered afterwards
Claims documentation
A claimant is not going to install anything. Publish the claim form behind a public link, let them fill it in and sign it from a phone, and route it into your claims system the moment it's finished.
Identity checks before signing
Verify the customer with their bank identity or a scan of an official identity document, and write the verified data straight into the policy. Over 12,500 document types from 240 countries are recognized.
Multi-party documents
Policyholder, insured person, beneficiary, adviser. Set who signs in what order, mark which signatures are required, and protect each participant's access separately.
Your brand, not ours
The signing screen carries your logo, your colors and your wording, on your own subdomain. For a customer signing a policy, that's not cosmetic — an unfamiliar brand at the signature step is where trust breaks.
Internal approvals
Underwriting sign-off, exception approvals, and board-level documents can demand a qualified certificate held in a QSCD, while customer-facing paperwork stays at the level that fits the risk.
Disputes and audits
When a policy is challenged, produce the validation report: document integrity, the certificate chain, revocation status, the timestamp, and the context captured at the moment of signing.
Your core system stays where it is
Insurers rarely replace the platform that generates the documents. Signosoft slots in at the signature step and hands the result back.
- 1
Your system generates the policy
The finished PDF is pushed to Signosoft over the API, with the participants, the signing order, the methods each one may use, and the minimum certificate level per field.
- 2
The customer is routed to the signature
A signing link, or the signing screen embedded in an iframe inside your own adviser portal. Any protection you've set — bank identity, ID scan, one-time code — is satisfied before the document opens.
- 3
They sign with the method that fits the channel
A pad at the branch, a bank identity at home, a code on a claims form. The evidence package is captured and sealed to the document hash in every case.
- 4
The signed policy lands in your archive
A finalisation plugin pushes it into your DMS or core system, with a qualified timestamp applied if you've connected a certification authority. Signosoft can then delete its copy.
Already running in insurance
- Czech Republic
Kooperativa
Wacom signature pads deployed across the entire branch network, in partnership with Wacom — pen pressure captured at every counter.
- Czech Republic
Česká podnikatelská pojišťovna
Signature pads across the whole branch network, on the same deployment model — one signing platform serving every counter.
- Czech Republic
Generali Česká pojišťovna
Signosoft in production for policy and customer documentation at one of the largest insurance groups in the market.
A US insurance provider in Michigan runs the same product outside the EU — evidence that the model isn't tied to one jurisdiction's identity infrastructure.
The questions that come up in an insurance review
Answered on the Trust & Security page in more detail, but these are the four that decide whether a pilot happens.
Trust & SecurityHandwritten biometric and bank-identity signatures are at advanced level. Signing with a qualified certificate produces a qualified electronic signature, and a field can require that certificate to be held in a QSCD. Which level a given policy document needs is a question for your legal team.
Bring a policy document to the demo
Bring one you actually issue. We'll set the fields up live, sign it three ways — pad, bank identity, one-time code — and validate the result in front of you.