Sherlock Agent doesn't just check the ID.It asks whether the identitymakes sense.

Investigates every KYC session after submission, like an experienced fraud analyst, and returns CLEAN or FRAUD with the reasoning spelled out.

Sherlock doesn't just check the ID. It asks whether the identity makes sense.

Trusted by 200+ compliance teams

NIVODA
Payments
BlindPay
PingPong
Grey
Keyrails
Sokin
Conduit
Nico
Airwallex
d-local
Bridge
Currencyfair
Capi
Velafi
Supply Pay
[Problem]

What point-in-time checks cannot see

A flag that says “review” and nothing else

Analysts reopen the case and hunt for whatever tripped it.

Every session judged alone

The same face returns under a new name next week and passes again.

Checks stop at the ID

Readable, matches the selfie, not on a watchlist. A quality fake clears all three.

Three questions, every session

Is the document what it claims to be? Does the identity hold together? Has this person been here before, under any name? Every session, in seconds, no added step for the user.

Investigation session VS-8F42 interface displays flagged results for fraud detection: three flagged items for images including ID front, back, and selfie; one flagged item for identity details such as name, dates, places, and document information; and linked history including 16 linked sessions and 5 names. The verdict at the bottom confirms fraud, with the session duration noted as 14 seconds.
CLEAN or FRAUD.  Nothing in between.
Every signal cites its evidence
It only raises what a real analyst would raise

CLEAN or FRAUD. 
Nothing in between.

A verdict, not a number to interpret. Every signal cites the field, image region, or prior session it came from. Your team makes the final call.

Every signal cites its evidence

Not "document anomaly." The specific field, image region, or earlier session. Reviewers confirm instead of re-investigating.

It only raises what a real analyst would raise

Calibrated on how legitimate users behave. Glare, a retry, a transliterated name, a diaspora naming convention: none of these is a flag. Sherlock hunts for what is hidden, not what is unfamiliar.

CLEAN or FRAUD.  Nothing in between.

CLEAN or FRAUD. 
Nothing in between.

A verdict, not a number to interpret. Every signal cites the field, image region, or prior session it came from. Your team makes the final call.

Every signal cites its evidence

Every signal cites its evidence

Not "document anomaly." The specific field, image region, or earlier session. Reviewers confirm instead of re-investigating.

It only raises what a real analyst would raise

It only raises what a real analyst would raise

Calibrated on how legitimate users behave. Glare, a retry, a transliterated name, a diaspora naming convention: none of these is a flag. Sherlock hunts for what is hidden, not what is unfamiliar.

Case file for session VS-8F42 showing 16 faces, 11 devices, 7 networks, and 2 ID numbers linked. Five names claimed, four dates of birth, three document types. Timeline indicates first session 11 months ago, most recent 3 days ago, with 12 of 16 passed. Risk level marked high due to same face with five identities. Option to open case file.

"I've seen this face before, under a different name."

Each session looks clean alone. Sherlock pulls every earlier session sharing a face, ID number, device, or network into one case file and works them together. In production it has tied one face to sixteen sessions across five names.

Table titled 'Coherence · Session VS-8F42' summarizing three contradictions: Portrait vs date of birth shows 'Early twenties vs 67' and contradicts, Surname vs MRZ shows 'One letter differs' and contradicts, Card version vs issue date shows 'Format introduced 2024; issue date reads 2022' and contradicts; Given vs family name origin is consistent and supports; Address vs residence is plausible and supports. Note states 'Each field alone passes validation' with a highlighted phrase 'The combination is the tell.'

"These details are each valid. Not together."

A field-matching engine sees valid strings. An analyst sees a biography. Sherlock checks whether the pieces agree with each other. Each can pass validation alone; the combination is the tell.

Contradiction, not unfamiliarity. Naming conventions and transliteration never count against an identity on their own.

[The Impact]

What teamsget back

Based on customer-reported outcomes. 
Results vary by program configuration and policy.

per session review, no onboarding latency

Seconds

KYC session investigated after submission

Every

less manual review work per session

98%

evidence cited on every signal

Full

“Sherlock Agent caught something none of us saw. The document looked clean, and it still flagged a mismatch in the issuing country that I never even entered.That's the moment I stopped thinking of it as a tool and started thinking of it as an analyst.”

Gaurav Modgill
Gaurav Modgill
Head of Operations, Bridge

Frequently asked questions

Does Sherlock Agent make the decision?
Does it add friction for users?
Will it flag people with unusual names or documents from other countries?
What does it link across sessions?
Is it a risk score?

Every session,reviewed likeyour best analyst is on it

Watch Sherlock work a real case.