// // Enterprise · Certificates

Certificates

Understand KYB Verification Certificates — how they are generated, what the audit hash proves, and how to share or verify them.

What is a KYB Certificate

A Osapher KYB Verification Certificate is issued when an entity passes verification against the ABR or NZBN register and receives a CLEAN or conditionally approved verdict. The certificate provides a permanent, shareable record of the verification event.

Each certificate has a unique certificate ID in the format VRNT-KYB-[hash] and is accessible at a public URL for independent verification.

Certificate Structure

Every KYB certificate contains:

  • Legal entity name and trading name
  • ABN or NZBN and verification status
  • GST registration status
  • Verification date and expiry date
  • Verdict — CLEAN, REVIEW, or REJECT
  • Audit hash — tamper-evident record of the verification
  • Certificate ID — unique identifier for this verification event

The Audit Hash

The audit hash is a unique fingerprint generated at verification time. It is derived from the entity's verified data and the timestamp of verification. Any modification to the certificate data would produce a different hash — making tampering immediately detectable.

The audit hash is displayed on the certificate and embedded in the certificate URL. Third parties can use the hash to independently confirm the certificate has not been altered since issuance.

Hash invalidation
If the underlying entity data changes — for example, a change of legal name or ABN cancellation — the existing certificate hash will no longer match. A new verification should be run to issue an updated certificate.

Sharing Certificates

Certificates are publicly accessible at:

https://osapher.com/verify/[certificate-id]

Share this URL with counterparties, regulators, or clients as proof of KYB verification. The certificate page displays all verification details and allows independent confirmation of the audit hash.

Certificate Validity

KYB certificates are valid for 90 days from the date of issue. After expiry, run a new verification to issue a fresh certificate. Historical certificates remain accessible at their original URL for audit trail purposes — they are never deleted.