COMPREHENSIVE MARKET

Use cases for issuer-attested verification

Live Verify: the next logical step up from the iPhone's Live Text.

Live Verify turns a printed claim into a trustable handshake: snap the document, OCR locally, hash it, and confirm the issuer domain still serves that hash. Think of it as a trust primitive for the physical world: readable text that can also be checked.

Industries

Use Cases

with

Further Derivations

Start here How it works What “Verified” means Privacy model Explore use cases

Start here: the flagship cases

There are hundreds of use cases below. If you have a few minutes, start with these — the five clusters where issuer-attested verification is most consequential, each speaking to a different audience.

1. High-stakes “threshold” verification

Protecting the vulnerable at the door

Police-officer verification — a citizen verifies the badge at a traffic stop or home visit; the device walks the authority chain to a sovereign root while the human judges the domain (dual-channel trust).
Utility / field-worker verification — the “bogus caller” defence: an elderly homeowner confirms through the window that the worker is on-duty and assigned to this address right now.
School pickup authorization — staff confirm a third party (grandparent, nanny) is currently authorized to collect a child.

2. Financial & integrity audit

For bankers, lenders, and regulators

Bank statements (the KYC counter) — page-at-a-time hashing includes the transaction rows, so a deleted withdrawal or padded balance fails to verify, not just an altered total.
Mortgage / income verification — lenders verify pay stubs and W-2s against the payroll provider’s own domain, stopping income-padding at the source.
Regulatory census audits (e.g. sanctions licences) — 100% verification of every document in a firm’s evidence set (Merkle rollups on a USB stick), replacing the 5%-sampling “forgery gamble”.

3. Professional & academic qualifications

Serving the unserved long tail

Credential evaluations & the “ornate certificate” — an institution keeps its traditional diploma and offers a plain-text hash an HR manager can verify in seconds.
Letters of good standing — doctors, lawyers, engineers carry portable proof that bridges back to their licensing board’s registry, defeating “state-hopping” by struck-off practitioners.

4. High-value asset provenance

Portable trust between private silos

Fine art & collectibles — a certificate of authenticity or appraisal proves provenance against the auction house’s domain, enabling high-value loans without public-database exposure.
Thoroughbred & livestock pedigrees — a buyer verifies the lineage and health of a high-value animal on a doorstep or at auction, where social pressure discourages manual lookups.

5. Novel post-GenAI primitives

For policy makers and platforms

AI content disclosure — a platform self-attests whether media is AI-generated or camera-original, a domain-bound claim that survives screenshotting and re-hosting.
Platform age-assurance audit — a parent performs a non-overridable OS gesture on a child’s app icon to see what age the platform claims to believe they are (verification turned back on the platform).
Ad-placement provenance — a user right-clicks an ad to see which network is liable for placing it, removing the anonymity that fuels malvertising.

Snap → OCR → hash → check

Documents carry a verify: line that points to the issuer’s domain. Live Verify automates the rest: capture, OCR, normalization rules, SHA-256, then GET the issuer URL with the hash. The app flashes “Claim Verified” only if that domain currently vows to that exact text hash.

Snap
Use the camera app to frame the verification mark.

OCR + normalize
Text is normalized on-device (rules only) before hashing.

SHA-256
Hash the normalized text, not the image.

Verify
GET https://issuer.example.com/claims/<sha256>; 404 = not found, 200 = status returned (OK / REVOKED / etc.).

Example verification line:
verify:issuer.example.com/claims ... implies a lookup at ...
https://issuer.example.com/claims/<sha256>
The phone trusts the domain only if the hash matches and the issuer returns an affirming status (e.g., “OK”). Status meanings can be described in verification-meta.json.

What “Verified” means

The issuer domain now attests to the same exact normalized text hash.
The issuer stands by the claim while it remains “OK”; if they don’t, they change it (e.g., “REVOKED”) or delete the record entirely.
You decide whether that domain is an authority for the claim.
Look out for lookalike/typosquatted domains: verifiers should see the domain clearly before trusting it.

Verifications are revocable

Revocation is part of trust. If an ID is stolen, a license suspended, or a credential withdrawn, the issuer can change the response so verifiers stop treating the printed claim as current. Some issuers may return an operational instruction, e.g. Stolen ID — please retain/cut in half and contact <policy URL> (quoting reference Nnnnnnn).

Sovereign, no gatekeeper

Issuers keep authority by publishing from their own domains, and verifiers choose what they trust. There’s no single global registry to control access—at the cheapest end, a static web server can host the hash lookups.

The result is anti-fraud without friction: the familiar camera flow becomes “Snap → Verified / Denied” at the point of use.

Privacy

OCR, normalization, and SHA-256 run entirely on-device, and the only outbound call is the hash lookup. Learn why one-way hashes are safe to publish via our one-way hash explainer and see the full protocol in the Privacy Declaration.

Explore use cases

Search the catalog or browse categories to see how Live Verify meets fraud, compliance, and operational needs across industries.