Signature levels
Three levels under eIDAS - matched to the document
SES - simple signature
For internal and low-risk documents. The lowest barrier for the signer, with the event fully recorded on the system side.
AES - advanced signature
Uniquely linked to the signer, with identity verified before signing. The standard for commercial contracts.
QES - qualified signature
The legal effect of a handwritten signature. For contracts where law or company policy requires the qualified form.
Choosing the level
You pick the signature level when sending, not in a separate tool
The document goes out for signature from the same place where it was drafted and approved. On this screen you decide one thing only - which form it gets signed with.
Choose the signature type
A contract template can enforce a specific signature type - the sender then cannot lower it on their own.
On the signer's side
Your counterparty signs from a link, without an account
The real brake on electronic signing is not the technology - it is the barrier for the other party. So signing starts with a click on a link, not with registration.
- Signing without creating an account or installing anything
- One-off qualified signature - for a counterparty with no certificate of their own
- Signing on a phone or a computer, with no card reader
- Automatic reminders and live status for the sender
Identity verification
A method matched to what is at stake
Online banking
Identity confirmed against the data held by the signer's bank.
eID card
Verification through the electronic layer of the national ID card.
mObywatel
Identity confirmed with the Polish mObywatel app on the signer's phone.
Video-ID
Verification in a video call with an identity document presented on camera.
SMS-OTP
A one-time code sent to a phone number - for the lowest-risk documents.
Closing the loop
The signed document returns where it came from
Sent for signature
The approved version goes to the signers straight from the process, in the required order.
Identity verification
The signer confirms their identity using the method set for this document.
Signature
The signature is applied at the chosen level - SES, AES or QES.
Timestamp and validation
The system timestamps the file and validates the signatures of all parties.
Back to the repository
The signed file lands in the repository with its metadata and the full record.
Signature evidence
Who signed, when, and where the document stands
The signing process is not a black box between sending and a finished file. You see the roles and the status of every person - together with the date the signature was applied.
Signed2026-09-02 10:41Signed2026-09-02 11:04
Opened
SentOnce the last signature is applied, the document returns to the repository with the full set of evidence - the version, the approvals and the dates.
Other solutions
The two remaining pillars
Contract workflow and approvals
Document generation, approval paths and initials, process automation - instead of versions circulating over email.
See the solutionDocument audit and control
Every file's history, audit trail, metadata, retention and reports - a complete record ready for an audit.
See the solutionDPT
One platform. Three pillars.
Signature is the Trust pillar - but it only makes sense when it ends a process instead of starting a separate one.
Decision
Create. Negotiate. Automate.
What goes for signature is the version approved in the process, not a file dragged off someone's desktop.
Proof
Track. Audit. Comply.
The signature keeps the verification method, the moment it was applied and the validation result.
Trust
Identify. Sign. Verify.
SES, AES and QES under eIDAS, with a one-off qualified signature for counterparties without a certificate.