verintySignature — Verinty Vocabulary

DefinedTerm — Verinty Vocabulary

verintySignature

https://verinty.com/vocab/verintySignature

A cryptographic SHA-256 audit signature issued by Verinty Global ATS, verifying a business entity's legal identity, jurisdiction, and operational status against national government registries. Embedded in structured data as a PropertyValue identifier within a Certification node, the signature enables AI search engines and validators to cryptographically confirm that a published schema was audited by Verinty.

Format Specification

A verintySignature is a 64-character lowercase hexadecimal string produced by SHA-256 hashing the entity's canonical identity fields. Verification certificates are identified by a VRNT- prefixed cert ID derived from the audit's UUID.

// Signature format (SHA-256, 64 hex chars)
verintySignature: "a3f2b1c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2"

// Certificate ID format
auditHash: "VRNT-<32-char-uuid-stripped-of-hyphens>"

// Example
auditHash: "VRNT-800c5eb726bd440d978efd545c64d208"

Field	Type	Description
verintySignature	string (64 hex)	SHA-256 hash of entity identity fields: legalName, taxID, streetAddress, countryCode
auditHash (VRNT-)	string	Stable certificate identifier linking to the public verification record at verinty.com/verify/
auditId	UUID v4	Unique run identifier generated per audit — used to look up the full certificate
nextReviewDue	ISO 8601 date	Certificate expiry — 90 days from audit date. After this date the schema should be re-audited.

How the Signature Is Computed

The signature is produced by the Verinty CORE engine using the Web Cryptography API (crypto.subtle.digest). The input is a deterministic JSON serialisation of four canonical identity fields, with keys sorted alphabetically and values uppercased and trimmed:

// Input object (keys sorted, values normalised)
{
  "countryCode": "AU",
  "legalName":   "ACME PTY LTD",
  "streetAddress": "123 MAIN ST SYDNEY",
  "taxID":       "12345678901"
}

// Process
msgBuffer = TextEncoder(JSON.stringify(input))
hashBuffer = await crypto.subtle.digest('SHA-256', msgBuffer)
signature = hex(hashBuffer).padStart(64, '0')

The signature is deterministic — the same entity data always produces the same hash. This makes it suitable for change-detection: if a business updates its registered address or ABN, the signature changes and signals that re-verification is required.

Where It Appears in Structured Data

The signature is embedded inside a DigitalDocument / Certification node in the JSON-LD graph, within the identifier array:

{
  "@type": ["DigitalDocument", "https://schema.org/Certification"],
  "@id": "https://verinty.com/#certification",
  "name": "Verinty Sovereign Identity & Trust Certification",
  "identifier": [
    { "@type": "PropertyValue", "propertyID": "auditHash",
      "value": "VRNT-800c5eb726bd440d978efd545c64d208" },
    { "@type": "PropertyValue", "propertyID": "verintySignature",
      "value": "a3f2b1c4d5e6f7a8..." },
    { "@type": "PropertyValue", "propertyID": "auditId",
      "value": "800c5eb7-26bd-440d-978e-fd545c64d208" },
    { "@type": "PropertyValue", "propertyID": "nextReviewDue",
      "value": "2026-07-06" }
  ]
}

Jurisdiction Coverage

Verinty verifies entities against official national registries. The countryCode field in the hash input reflects the jurisdiction used:

Jurisdiction	Registry	ID Type
AU	Australian Business Register (ABR)	ABN — 11 digits
NZ	New Zealand Business Number (NZBN)	NZBN — 13 digits

Certificate Lookup

Every Verinty-audited schema contains a public certificate. Use the auditId from the structured data to look up the full verification record, including legal name, ABN, trust score, and expiry date.

Verify a Certificate

Enter an audit ID from the structured data to look up the full certificate.