Document authenticity infrastructure

Authenticate official documents. Reduce document fraud.

Docseal enables trusted organizations to make their official documents cryptographically verifiable by third parties, with visible-reference, restricted-visible or hash-only policies. Powered by VeriSeal Core.

Document authenticityAnti-fraudHash-onlyThird-party verificationVeriSeal CorePilot first

For a first meeting

ObjectiveControlled pilot on one document flow

Use caseDocuments that circulate outside the issuer

CommercialScoped PoC from EUR 5,000

ContactDocseal website contact form

01

Problem and proof model

A simple question: does the received file match the official document?

Official PDFs, certificates and attestations circulate after issuance. A copied QR code or a clean-looking PDF is not enough. Docseal verifies the file itself by comparing the received hash with the sealed reference hash.

Issuer document

→

Local SHA-256 hash

→

Docseal manifest

→

VeriSeal Core proof

→

Public Verify

Result	Business meaning	Recommended action
authentic	The received file matches the sealed reference and the registry status is valid.	Continue process
tampered	The file does not match the sealed reference. A visible QR code may still be copied.	Reject or fraud review
unknown	No matching seal is found for the submitted file or identifier.	Request source document
revoked / replaced	The document existed, but its operational status changed.	Check current registry status

Hash-only option: Sensitive content can remain outside Docseal. Verification can be performed by comparing the received file hash with the sealed reference hash.

02

Use cases

One model, multiple sectors

Docseal is not limited to banking. The same verification model applies wherever an organization issues a document that another party must trust.

Sector	Documents	Verifier need
Banking	Bank statements, proof of funds, banking certificates.	Banks, brokers, lenders, compliance and credit operations.
Insurance	Insurance certificates, information statements, claims or subscription records.	Insurers, brokers, banks, employers and digital platforms.
HR & Payroll	Payslips, employer certificates, income attestations.	Landlords, banks, recruiters, administrations and onboarding teams.
Real Estate	Rental files, income proofs, domicile proofs, guarantor documents.	Agencies, landlords, guarantee platforms and lenders.
Public Administration	Tax certificates, permits, official attestations, compliance documents.	Administrations, banks, regulated companies and public services.
Education	Diplomas, certificates, transcripts, training credentials.	Employers, universities, public bodies and credential platforms.

Issuer

Creates the seal and controls policy.

Verifier

Checks the received file, not only the QR code.

Registry

Tracks valid, revoked, replaced and expired statuses.

Not a qualified electronic signature by default. Docseal is a document authenticity, integrity and verification layer. It can coexist with electronic signatures, electronic seals and qualified trust services when the use case requires them.

03

Pilot and next steps

Pilot scope and operating model

Docseal should be evaluated through a controlled pilot: one issuer, one document family, one verification workflow and clear success criteria.

1Select document

One family with visible verification pain.

2Define policy

Visible, restricted-visible or hash-only.

3Seal samples

Create seals, receipts and Verify URLs.

4Test cases

Authentic, tampered, unknown, revoked.

5Measure

Fraud detection, time saved, integration fit.

Scope	Indicative budget	Purpose
Scoped PoC	From EUR 5,000	One issuer, one document type, one verification flow.
Controlled pilot	EUR 15,000-40,000	Depending on volume, integration depth and support.
Production	Custom quote	Platform fee, sealing volume, verification usage and gateway support.

Transparency for regulated buyers

For regulated organizations, Docseal should be assessed with security, DPA/privacy, reversibility, proof export and vendor-risk requirements. ISO 27001/SOC 2 are not claimed as completed unless formally achieved.