Sign agreements tied to a verified identity.

Kenal Sign is in development. We are inviting a small group of institutions to work with us ahead of general release. The signing flow, evidence record and offline verification are built and can be demonstrated today. Institutions that join get a working environment for their own agreements, a direct line to the product team and a say in the templates, channels and integrations we prioritise.

Kenal Sign ties each signature to a verified person, not just an email address. The signer's identity comes from Kenal eKYC, and the one-time code goes only to the contact channel bound to that verified identity. The document, the signer, their consent and the code are sealed together into one tamper-evident record that shows who signed and that nothing has changed.

No. Customers verify once with Kenal eKYC, and that identity is reused for later signings. At each signing they confirm the document, give consent and enter a one-time code sent to their verified channel. That keeps repeat signings quick for long relationships such as loans and mandates, while every signature still traces back to a verified person.

Anyone holding the signed document can verify it offline, without contacting Kenal. The evidence record travels with the signed PDF, and the verifier checks that the document is unchanged, the seal is valid, the timestamp is intact and the audit trail has not been edited. That matters when an agreement is challenged years after it was signed.

Talk to our team and tell us what you need signed, by whom and in what volume. We will show you the current build, agree a scope for an early deployment and connect it to Kenal eKYC if you already use it. Kenal Sign suits banks and lenders with long agreements, remote customers and repeat signings.