Report Verification

Verify an APEXLyn report

Approved APEXLyn evidence reports are hashed and recorded in the evidence ledger at the moment of generation. A person holding a valid verification code can check approved verification metadata and confirm whether the submitted code matches an APEXLyn report record, without relying only on vendor assertion or the organization that supplied the report.

Evidence Ledger
HASH: f2a64c8d9e...1b9RECORDED
HASH: 8b3d9f1a2c...4e7RECORDED
APEXLyn ReportAPX-8829-10A
f2a64c8d9e...1b9
Match Confirmed

Check a report

The code appears on the report cover page and inside its QR code.

How verification works

Generated and hashed

When an approved APEXLyn evidence report is generated, the report hash is recorded as an event in the evidence ledger.

Verification-metadata check

The verification endpoint confirms approved metadata such as report hash, timestamp, framework versions, and scope without exposing tenant evidence.

Verify approved metadata

Verification returns only approved verification metadata and a valid, invalid, or offline result.

Evidence metadata that can support independent review

Authorised reviewers can verify approved APEXLyn report metadata where verification is enabled. That is the difference between unsupported claims and evidence-backed review.