Electronic Signature Application

When every application uses its own signing tool, you get driver issues, version conflicts and piles of waiting documents. The E-Signature Application provides a single signing layer for all of the institution's systems.

Managers see pending documents in one list and bulk-sign the ones that are ready; people in the field keep processes moving with mobile signature. Every signature gets a timestamp compliant with Law No. 5070, and a public verification screen lets anyone check a signature's validity.

Under Law No. 5070, a qualified signature's private key can never leave the card or token — so the signature itself is created where the key lives, and everything else is managed in the cloud. Your document reaches the API; the hash and PAdES structure are prepared server-side, the timestamp and verification record are produced server-side, and the signed PDF is archived.

When signing with a card or token, the thin client on the user's computer does exactly one job: it signs the prepared digest with the card and returns the result to the API. On the mobile-signature channel no installation is needed at all — the whole flow runs in the cloud and the user approves with a PIN on their phone.

Your EBYS or your own application talks to a single REST API; because the client carries no business logic, update and support costs stay minimal. When remote (cloud) qualified signing becomes widespread through trust service providers, it plugs into the same API as another channel.

The productised form of this service, eimzaonay (eimzaonay.com), adds qualified electronic signatures compliant with e-Signature Law No. 5070 to applications through a single REST API: PAdES, CAdES and XAdES formats, smart-card and mobile-signature channels, timestamping and public QR verification. The private key never leaves the user's card or phone.