EktarSignatures validBook a demo

Document signing & integrity · ekSign

Signing inside your own channel. Proof that outlives the session.

ekSign brings document signing back inside the bank. Customers sign in your own app or branded page — with the MFA they already use, and a signature that's cryptographically bound to the document so tampering is detectable forever.

ekSign · execution status2 of 3 signed
Primary borrowerSigned
Co-borrowerSigned
GuarantorAwaiting
AuthenticationBank MFA · national ID
Seal 7d2x·91qz — any alteration after signing fails verification
Why banks move signing in-house

A third-party portal breaks the journey and holds your record.

Most banks sign through an external e-signature platform. That means a customer receives an email that is not from the bank, is redirected to another brand's portal, and verifies with that platform's own SMS OTP — an event with no link to their banking identity. The signed documents and the audit trail then live in the vendor's platform, where the bank is a tenant and pricing or availability changes affect access to its own records.

Experience

The journey leaves the bank

Another brand's email, domain and portal sit in the middle of a regulated banking action.

Identity

Signing is not tied to the customer

A vendor OTP proves access to an inbox or a phone number, not that your verified customer signed.

Custody & cost

The bank does not own the record

Audit trail held externally, priced per envelope. ekSign replaces that with a marginal cost per signing event on infrastructure the bank already runs.

How it works

Two capabilities, joined into one product

Every signature is mathematically bound to the exact document and to a verified identity — so nothing about it can be faked, altered, or disputed later.

01

Tamper-evident by design

Alter one character after signing, and verification fails immediately.

02

Bound to a verified identity

The bank's existing MFA fires at the moment of signing, so the signature is tied to a real, verified customer.

03

Non-customers verified too

Guarantors and co-applicants sign using national digital ID — no bank account or new app required.

04

One complete audit record

Every signature, chained to the ones before it, held entirely on the bank's own systems.

Who can sign, and how

One customer, many parties, one process

01

A single customer

A push notification, a review inside the banking app, and one authentication step — the same MFA already used for transfers.

02

Multiple signatories

Loan agreements, joint accounts, and mandate changes often need more than one signature. ekSign supports signing in sequence, in parallel, or a mix of both — the bank's workflow decides the order.

03

Guarantors and other non-customers

A secure link sent from the bank's own domain, opened on a bank-branded page, verified with national digital ID — no bank account or app required.

ekSign vs a third-party portal

The same signature, on your side of the wall.

Third-party e-signature platformekSign
Customer redirected to another brand's portalCustomer signs inside your own app or branded page
Authenticated by vendor SMS OTP or emailAuthenticated by the bank's own MFA, or national digital ID
Audit trail held by the vendor — the bank is a tenantFull audit trail owned and held by the bank
Fixed per-envelope licence feeMarginal cost per signing event, on infrastructure the bank already runs

Replace a recurring licence with a capability you own.