Verification Program Guide

Operational Blueprint for Proof-Based Trust

1. Introduction

A Verification Program (VP) is a structured operational framework where an organization (the Issuer) provides digital, verifiable proof of state to consumers or partners (the Verifiers).

2. Program Design

Successful programs follow a three-step design phase:

Trust Tier Definition: Determine which credentials require simple platform-attestation vs. deeper evidence-backed review.
Payload Schema: Standardize the JSON structure for attestations to ensure interoperability.
Delivery Channel: Choose between Email-based delivery (Consumer Inbox), Mobile App Pushes, or B2B API sync.

3. Operational Flow

The "Mint-to-Verify" lifecycle in Truthlocks:

Step 1: Event Capture: Your internal system detects a "Verifiable Event" (e.g., a Diploma is issued).
Step 2: Attestation Minting: Call the Truthlocks /mint API with the relevant data.
Step 3: Signature & Checkpoint: Truthlocks signs the record and creates a transparent checkpoint.
Step 4: Bundle Delivery: Deliver the signed Proof Bundle to the recipient.
Step 5: Verification: The recipient (or a third-party partner) verifies the bundle via our Verify Portal or API.

4. Best Practices

Use Webhooks: Automate your system's response to subscription.limit warnings to avoid issuing interruptions.
Transparency Logs: Regularly audit your tenant's transparency checkpoints to ensure consistency with your internal records.
Environment Parity: Always test new attestation schemas in the Sandbox before production rollout.

5. Case Study: B2G Procurement

An infrastructure agency issues "Safety Compliance Certificates" to contractors.

Verifiers: Mainline auditors and public safety inspectors.
Benefit: Zero-trust verification of contractor standing with no paper trail and real-time revocation support.