Document Verification

Check an institutional provenance reference.

Approved recipients can upload a document, scan a Bridge28 QR code, or enter an audit reference / document number to identify the sealed record and authenticate the document hash without exposing private deal-room content.

Upload actual documentSHA-256 is calculated locally before comparison with the sealed Bridge28 record.

Reference lookupQR payload, audit reference or document numberUse the reference printed on a Bridge28 receipt, QR code or audit record.

Reference authenticatedThe sealed Bridge28 record can identify the document. Upload or hash the document to authenticate the content.

Bridge28 demonstration mandate recordAuthenticated Bridge28 provenance record

Document typeMandate and attribution record

Document numberB28-MANDATE-2026-019

Audit referenceB28-AUD-2026-0719-5F2C

Identifier lineageREG-2026-0142 -> TC-2026-0881 -> TXN-2026-0319

QR / reference lookupMatched Bridge28 sealed record

Document content hashPending upload or fingerprint

Authentication decisionAwaiting document hash comparison

Method

Verification receipt valuesbridge28://verify/B28-DOC-2026-0719-5F2C

Document SHA-256Pending upload or fingerprint calculationMerkle batchPending matched document hashChain anchorPending Merkle batch proofPublic receiptbridge28://verify/B28-DOC-2026-0719-5F2C

Verification Architecture

Hash-only proof, consent-controlled disclosure and identifier lineage.

Hash-chained ledgerEvery event is sealed with SHA-256 into an append-only record.

Merkle-proof verificationAny document or decision can be independently proven without exposing private content.

Identifier lineageOne thread runs from registration (REG) through transaction coordination (TC) to settlement (TXN).

Consent-controlled disclosureNothing is shared without a recorded consent event.