Criipto is now Idura. Read why here →

AES: From signing to proof

When a PDF leaves your system, it is often opened, forwarded, and validated in other tools (typically Adobe). We build signatures that make it easy to see who has signed and whether the document has changed.

Get PDF signatures where Adobe shows the signer's name - not the name of the signing service. Think of it as "person-based signing."

  • Clear validation in Adobe Reader
  • Integrity: changes can be detected
  • Evidence package for audits and disputes

Built for teams that send contracts and want to validate in Adobe Reader.

 

GRX_ID_3

How it works

1. The signer is identified/validated according to your flow

2. A Remote Signing Service issues a personal certificate "on-the-fly"

3. Idura inserts the certificate into the PDF and generates the signature

4. The recipient can validate in Adobe and see the signer's name

Why AES?

Many signing flows stop at "it was signed". We focus on what comes next: how the recipient sees and verifies the signature and how you document it afterward.

When the recipient opens the PDF in Adobe Reader, Adobe retrieves the name from the certificate inside. With sealing, this is typically the company behind the signing service.

With AES, it is the person who signed.

Result:

  • Clearer signer identity in Adobe
  • Same PDF integrity and tamper detection
  • Better fit for processes where the counterparty expects a person's signature
Book a 20-minute clarification
NO_BankID_intext

What is AES?

In the Nordics, we work with three basic digital signing methods:

  • Sealing: The certificate is issued to the signing service → Adobe displays the name of the service
  • AES: The certificate is issued to the signer → Adobe displays the signer's name.
  • QES: AES + qualified setup → used when "handwriting-like" level is required.
minimized_switch-eid

What does the recipient see in Adobe?

Adobe displays the name from the certificate inside the signed PDF.

Sealing

  • Certificate is issued to the signing service/organization
  • Adobe typically shows the service/company name
  • Best for: origin + integrity (automatic document stamping)

AES

  • Certificate is issued to the person signing
  • Adobe shows the signer's name
  • Best for: agreements where a person needs to appear as a signatory

QES = AES with qualified setup (used when there are formal "handwriting" requirements).

What you get in early access

We combine a personal signature in the PDF with what you would expect from enterprise: traceability, evidence, and a reliable flow. Great when you need both the "who" and "what was signed".

  • Person's name in Adobe Signatures Panel
  • PDF signature with integrity protection (changes can be detected)
  • Audit trail/evidence package (if you use Idura's signing flow)
  • Integration via Idura (same API/flow as today)
Get a review of your case
iphone on station-girl

Answer 5 questions - we'll get back to you within 1-2 business days

Frequently asked questions

Is it QES?

No - AES is not the same as QES. If you require QES, we'll tell you upfront.

What do you need from us?

Typically: which countries, identity levels, and where the signature will be used (contracts, HR, etc.).

When can we get access?

We're running early access for a limited number of customers and are accepting cases on an ongoing basis.

Send me a price quote