Provenance-gated claim capture

A photo can be faked
in ten seconds.
Yours can't.

Generative AI broke evidence. CapSeal makes claim photos trustworthy at the moment of capture - cryptographically sealed on the device, verified against an open standard, so honest claims pay instantly and fabricated ones never get on the road.

CLAIM #MTR-4471 / front-left
SEALED / AUTO-PAY
sha256:9f2a...c41e · SecureEnclave · C2PA v2.2
98%
of insurers say AI editing tools are fuelling digital claim fraud
Verisk, State of Insurance Fraud 2026
only 32%
feel confident they can detect a deepfake in a claim
Verisk, 2026
20-30%
of claims may now include altered images or fabricated documents
Shift Technology estimate, 2026
The shift nobody's core system was built for

Detection came too late. So we moved upstream.

Every incumbent fraud tool asks the same question after the fact: does this uploaded photo look fake? Against generative AI, that's a losing arms race - fakes now pass traditional checks over 90% of the time. CapSeal asks a different question, and asks it at capture.

The old question post-hoc

"Here's a photo the claimant uploaded. Does it look real?"

Forensics guesses at pixels after the fact. Every new image model resets the game. You're always one release behind the fraudster, and the honest customer waits weeks while you check.

The CapSeal question at capture

"Can this photo prove it came from a real phone, at a real moment, unaltered since?"

That's not an opinion - it's math. A sealed photo is trustworthy by construction. Fabricated evidence can't produce the seal, so it never enters the fast lane in the first place.

Capture to decision, in one flow

Four steps. No new app for your customer.

CapSeal drops into the claims app you already run. Your customer photographs the damage the way they always have - the trust happens invisibly, on the device.

STEP 01

Capture

The claimant photographs the damage inside your existing app, powered by our capture SDK.

STEP 02

Seal

The image is signed on-device using the phone's hardware security chip - bound to device, time, and place before anything can touch it.

STEP 03

Verify

Our engine checks the seal and runs anti-spoofing: a real lens saw a real scene - not a screen, not an injected feed.

STEP 04

Decide

You get one verdict, with a proof you can re-check yourself.

AUTO-PAY · REVIEW · REJECT
Why you can trust the verdict

You don't trust us. You trust the math.

CapSeal removes itself from the trust equation. Every seal rests on three things your business already trusts without us - and your own engineers can verify each one independently.

01 / HARDWARE

Apple & Google's own chips

The "real, un-tampered device" guarantee comes from Secure Enclave and Play Integrity - built by Apple and Google, not by us.

02 / CRYPTOGRAPHY

The same math as your bank

Standard cryptographic signing. Change one pixel and the seal provably breaks. Your team can verify it on your own servers, offline.

03 / OPEN STANDARD

C2PA Content Credentials

An open industry standard backed by Adobe, Microsoft and the BBC - not a black box only we can read. Your auditors already recognise it.

Honest about the limit: the seal proves the evidence is real - real device, real moment, unaltered. It doesn't read intent. That's why the intelligence layer sits behind it. We tell buyers exactly what each layer can and can't promise - because a vendor who names the limits is the one worth trusting.

Why this is a business, not a feature

Sealing is open source. The value sits on top.

The signing itself is a free, open standard - and that's the point. We stand on it, the way a payments company stands on cryptography. The product is the four layers no single carrier can build alone.

1

Capture integrity

Defeat screen-of-screen, injected virtual cameras, and rooted devices. The open libraries sign whatever the camera hands them - we guarantee what the camera hands them is real. Adversarial, insurance-specific, continuously hardened.

CORE IP
2

The verdict engine

Turn a raw seal into an auditable insurance decision - tuned to your lines, with graceful handling of no-chip phones, offline capture, and legacy uploads, so honest claims are never blocked.

3

The verification network

A sealed capture, verifiable across insurers, repairers and reinsurers - so one loss can't be sold twice. No single carrier can build this for its competitors.

DURABLE MOAT
4

The intelligence layer

Every verdict feeds an entity-graph engine that answers the question the seal can't: is the intent honest? Provenance for the evidence, intelligence for the intent.

Who it's for

One champion. One metric. One line of business.

THE BUYER

Head of Claims / Fraud

Signs on one number that moves on day one: the share of claims you can pay instantly without fraud risk. No consortium to assemble, no historical data to train.

THE INTEGRATOR

Your app team

Drops the SDK into the claims app you already ship. Days, not quarters, using primitives your security team already trusts.

THE END USER

The claimant

Photographs the damage the way they always have. The trust happens invisibly. Zero adoption friction, because there's nothing new to learn.

Start where fraud is loudest:
motor claims.

Highest photo volume, highest fraud, simplest integration. Prove it on one line, then expand across the book.

Book a pilot with Syptime
The pilot offer
Scope1 line of business (motor)
Duration60-90 days
IntegrationSDK drop-in, days not quarters
Success metricagreed up front, auto-pay rate
Pricingper claim verified + platform floor