Independent, cryptographic verification for documents
Documents lose trust when they leave your system.
Authena lets third parties verify issuer and integrity instantly — without access to internal systems. Works for common formats like PDFs, images, and other files.
No file storage. Files are not uploaded or stored. Authena stores only fingerprints (hashes) + signatures.
The trust gap appears when documents are forwarded, re-uploaded, screenshotted, or leave closed platforms.
Problem
Digital documents are easy to modify — and hard to verify.
In open workflows, recipients often can’t tell whether a document is authentic and unchanged — especially when it’s shared across organizations.
- PDFs and screenshots can be edited in minutes.
- Verifiers typically don’t have access to issuer systems.
- Disputes happen when there’s no independent proof.
Solution
Stop trusting files. Verify them.
Authena turns a document into a verifiable artifact. Third parties can verify issuer + timestamp instantly — and optionally confirm file integrity.
Provenance by linkVerify that a proof record exists — who issued it and when.
Integrity by file checkOptional: confirm the exact file matches the signed fingerprint.
Privacy-friendlyNo file storage — only fingerprints (hashes) + signatures.
Verifier workflow
Detect manipulated documents before they impact your decisions.
Not every document is pre-signed. For uploaded PDFs from outside your system, Authena can also provide an initial document risk check based on structural PDF signals.
Upload a PDFRun a simple manual screening flow for externally received documents.
Get risk signalsFlag suspicious metadata, multiple revisions, and risky embedded features.
Support decisionsUseful when platforms must assess uploaded documents before trusting them.
Important: This is a screening workflow, not forensic proof. It helps identify suspicious documents that deserve closer review.
Why not just digital signatures (eIDAS)?
Authena complements signatures — it solves a different gap.
Digital signatures prove who signed a document. Authena focuses on a different problem: enabling independent third-party verification when documents leave closed systems and are forwarded across organizations.
Identity vs. verification UXSignatures are identity/certificate-centric. Authena provides a simple public verification page.
Cross-org workflowsMany documents are exchanged outside issuer systems. Authena is built for that handoff.
Works alongside eIDASIf you already use signatures: great. Authena can add an independent verification reference (link/QR).
Practical note: A link/QR verifies the proof record exists. Integrity is confirmed by a file check (hash comparison).
How verification works
1) Verify by linkCheck issuer record + timestamp (provenance).
2) Optional file checkConfirm integrity by comparing the file’s hash locally.
3) No storageThe verifier’s browser computes hashes; only hashes are sent.
Use cases
Where verification really matters
The best fit is where verifiers have real pressure to verify — and can demand proof (payments, compliance, approvals, audit).
Invoices & confirmationsRecipients verify authenticity before payment / booking.
Banking & finance PDFsStatements, balance confirmations, official letters shared externally.
HR & employment docsSalary letters, contracts, references verified by third parties.
Public sector certificatesNotices, permits, certificates — verified outside the issuing authority.
Compliance & audit artifactsProof packages shared across org boundaries.
Vendor / supplier documentsDocuments exchanged across procurement chains and portals.
Developer API
Embed verification into your document workflow.
Integrate into ERP/DMS/portals. At document output, sign a hash and embed a verification URL/QR into the file.
Issuer-controlled keysIssuer signs records. Verification can be public.
Verifier UX includedPublic verification page for third parties (no login).
Minimal dataStore only fingerprint + signature (plus optional metadata).
Demo
Try verification in seconds
Use the verifier UI as a standalone page, use the upload risk check, or use the demo signer to generate a verification link.
