Signed, and provable.
Your client signs in the portal. What comes out is not a picture of a signature but a sealed PDF with a record that reveals any later change.
Request a signature
Acceptance_GroundFloor.pdf
Due: 14 Oct 2026
Two factors
- Signed in to the portal
- One-time code by email
Sealed and returned
Seal in the PDF · PAdES
Log, chained
The problem
The pain points we hear most often in customer conversations about this area:
- Approval arrives as “fine by me” over WhatsApp — and is worth nothing in a dispute.
- Every signature means someone drives over or paper goes back and forth.
- A signature vendor charges per signature and shows your client its logo, not yours.
- When questions come up, nobody can say who saw what, and when.
How Portenia solves it
Our take on this area — editor, platform and everyday practice combined:
Two factors, not one
Signed in to the portal plus a one-time code to the address on file. Only both together tie a signature to a person.
A seal inside the document
The finished PDF is sealed (PAdES). Any checker will then show whether the file changed after signing.
A record that cannot be smoothed over
Requested, viewed, code sent, signed — each step with time and origin, and each entry carries the previous one. Change or remove a line and the chain breaks visibly. Including for us.
Visible on paper
The last page carries the drawn signature, name, timestamp and reference. Anyone printing or forwarding the PDF sees the signature — not just a verification tool.
Under your own name
Everything happens in your portal, on your domain, with your logo. Your client needs no third-party account.
Forms included
A form can require a real signature on its record after submission — a switch, not a second tool.
Preview
Recreated from the product — this is what your team’s day looks like.
Your client signs in the portal
They are signed in, read the document, enter the one-time code and confirm. They can add a handwritten signature — it is not required.
Awaiting your signature
Acceptance ground floor
Acceptance_GroundFloor.pdf
3 pages · from Your Company Ltd
Acceptance_GroundFloor.pdf · 3 pages
One-time code
Code sent to k•••@example.com
I have read the document and sign it as binding.
Handwritten signature (optional)
Sealed in the PDF, visible on paper
The last page shows the signature, name, time and ID. Any PDF validator shows whether the file has changed since it was signed.
Last page
Signed by
Klaus Miller
7 Oct 2026, 14:32 CEST
ID: SIG-2026-0412
Acceptance_GroundFloor.pdf
- Signature valid
- Unchanged since signing
- PAdES format
A log that cannot be smoothed over
Requested, viewed, code sent, signed — every step with time and origin. Each entry carries its predecessor; change or remove a line and the chain visibly breaks.
- 1
Requested
7 Oct 09:10
Anna Kraus · Origin: 203.0.113.20
#3f9a…c21e
- 2
Viewed
7 Oct 14:28
Klaus Miller · Origin: 203.0.113.21
#8b07…5d4a ← Previous #3f9a…c21e
- 3
Code sent
7 Oct 14:29
System · Origin: 203.0.113.22
#e1c4…9f02 ← Previous #8b07…5d4a
- 4
Code confirmed
7 Oct 14:31
Klaus Miller · Origin: 203.0.113.23
#52ad…77b1 ← Previous #e1c4…9f02
- 5
Signed
7 Oct 14:32
Klaus Miller · Origin: 203.0.113.24
#c90e…1a6f ← Previous #52ad…77b1
- 6
Sealed
7 Oct 14:32
System · Origin: 203.0.113.25
#7d3b…e48c ← Previous #c90e…1a6f
What it looks like in practice
Three steps from setup to everyday use.
- 1
1. Pick the document
From the file list or under “Signatures”: choose the PDF, set subject and deadline. Your client gets an email.
- 2
2. The client reads and confirms
They see the document in the portal, request their code, tick the box and sign. They can draw their signature as well.
- 3
3. Sealed and returned
The PDF is sealed and available to both sides. Next to it you see the full history and can have it verified at any time.
See Portenia in action.
We are starting out with our first customers. Sign up or talk to our sales team — we will get back to you.