Capture to certificate.
One unbroken chain.
Every Verifact photo carries its own proof — where it was taken, when, on which device, and that nothing changed since. The platform covers each link in that chain.
Proof starts on the device, not in the back office.
A photo can only be trusted if it was born trustworthy. Verifact capture apps sign every photo at the moment of capture, with a key that lives in the phone's secure hardware and never leaves it.
Open standards. No proprietary trust.
Each capture is wrapped in a C2PA manifest — the same open provenance standard adopted by camera and software makers worldwide — signed with Ed25519 and anchored to an independent RFC 3161 timestamp authority. The proof is in the file itself, not in our database.
Anyone can check. In seconds.
Drop a file on the verifier and the full signature chain is re-checked: capture signature, manifest integrity, timestamp, and recorded location. A modified byte breaks the chain — and the verdict says so.
A workspace built around the claim.
The insurer portal brings capture, verification, and triage together: claims and their evidence in one place, verification results at a glance, and team and API-key management for your organisation.
Everything the portal does, your systems can do too.
A REST API under /api/v1 covers the full claim lifecycle: verify photos, create and read claims, upload signed evidence, and pull investigation reports and usage — all with per-tenant scoped API keys and predictable rate limits.
The full API reference — endpoints, scopes, and copy-paste examples — is available in the portal after sign-in.
See the chain hold.
Talk to us about bringing capture-to-certificate proof to your claims — or read how each link is built.