Docseal
EN
EnglishFrançaisRomânăItalianoEspañolNederlandsDeutschالعربية

Guided demo

Two PDFs. Same apparent context. Only one authentic file.

Download both files, open them, then verify them. Docseal does not judge the PDF layout: it compares the exact fingerprint of the received file with the official sealed record.

02

Falsified copy

This copy may still look credible, but its file fingerprint is different.

Open falsified copy

The decision rule

Received file fingerprint = official fingerprint

Result: Authentic

Received file fingerprint is different

Result: Tampered

Official sealed reference

This reference is the source of truth. Every tested file is compared with this record.

Seal IDDSL-DEMO-BANK-2026-0001
IssuerVeriSeal Core Bank
Document typeBank statement
Statusvalid
Visibility policyvisible reference
Reference hashSHA-256 · cf3922396223ee37…

Compare the two files

Docseal does not just verify a QR code. It computes the fingerprint of the received file and compares it with the official sealed fingerprint.

01

Original PDF

This is the exact file sealed by the issuer.

Expected result: Authentic

Not tested yet

02

Falsified copy

The visible context may still look the same, but the file has been modified.

Expected result: Tampered

Not tested yet

03

Received file

Select the PDF or document you received to check whether it matches the sealed record.

Result depends on the selected file

Not tested yet

Technical evidence

Registry recordReceipt JSON
Banking verification profile

Cryptographic profile

This registry receipt uses a classical document-integrity proof profile. DocSeal is designed to support crypto-agile and hybrid post-quantum evidence profiles for long-retention banking deployments.

Current proof profileClassical document integrity
Integrity hashSHA-256
Post-quantum statusCrypto-agile ready
Post-quantum signatureNot enabled in this demo profile
Hybrid migration pathClassical + ML-DSA
Long-term validationPeriodic resealing supported
DocSeal does not claim this demo profile is post-quantum protected end-to-end. The current claim is crypto-agility: a hybrid signature layer can be added without changing the document workflow.