Skip to main content
Neural Defend

KYC NeuroVerify

Your KYC checks who it is. NeuroVerify checks if it’s real.

Deepfakes now pass selfie and liveness checks. NeuroVerify inspects the face your KYC journey already captures and returns one risk score in under 200 ms. Your customer never sees a new step.

NeuroVerify does not verify documents or approve customers. It tells your policy whether the face is real.

Your KYC stack + NeuroVerifyAny region
01Identity checksDocument · Face match
02Is it real?Image · Video · Audio
03Your policyApprove · Review · Block
Public benchmark#1 of 36 systems on VendorBench-100

Two KYC journeys

Same customer. Same deepfake. Two outcomes.

Both journeys run the same identity checks. Only one asks whether the face is real.

Both journeys, side by sideStage 01 / 06
01 · Without Neural Defend

Traditional eKYC

Document, selfie, face match, approve. Every check passes, and a deepfake walks through the front door.

Playing
01Start eKYC
9:41●
Secure onboarding

Complete your eKYC

Verify your identity to continue onboarding.

Consent required

Customer enters details, gives consent, and starts verification.

02Document capture
9:41●
‹

Scan identity documents

ID card Tax ID
Identity card with masked detailsID card
Second identity document with masked detailsTax ID
Scanning both documents

Customer captures their identity document in the guided frame.

03Selfie & liveness
9:41●
‹SELFIE CHECK
Customer completing a selfie check

AI-generated selfie submitted

Deepfake input enters the regular eKYC flow.

A synthetic face passes the camera prompt like a real one.

04Face match
Fictional customer selfieSelfie
=
Fictional identity document portraitID photo

The existing provider compares the selfie with identity media.

05Policy decision
KYC RESULT

KYC successful

ID documents Face match Basic liveness AI-generated / deepfake Passed

AI-generated image / deepfake attack passed.

Every check passes. Nobody asked if the face was real.

02 · With NeuroVerify

eKYC + Neural Defend

The same journey, one API call added. NeuroVerify checks the selfie before your policy decides.

Playing
01Start eKYC
9:41●
Secure onboarding

Complete your eKYC

Verify your identity to continue onboarding.

Consent required

Customer enters details, gives consent, and starts verification.

02Document capture
9:41●
‹

Scan identity documents

ID card Tax ID
Identity card with masked detailsID card
Second identity document with masked detailsTax ID
Scanning both documents

Your existing provider still verifies the document.

03Selfie capture
9:41●
‹SELFIE CHECK
Customer completing a selfie check

Capturing selfie...

Keep your face inside the oval.

Authorized face media is captured inside the existing journey.

04Neural Defend’s NeuroVerify Unified Trust LayerFace authenticity
9:41●
Powered byNeural Defend
Customer undergoing Neural Defend face analysis
Inspecting media…NeuroVerify Unified Trust Layer
Parallel running
Parallel analysisAll six checks active
Analysing…

Six checks run in parallel on the same selfie. Under 200 ms.

05Face match
Fictional customer selfieSelfie
=
Fictional identity document portraitID photo

The existing provider keeps ownership of identity comparison.

06Trust result & policy
UNIFIED TRUST RESULT

Deepfake attack detected

Identity checks Face match Parallel checks Policy route Block / review

AI-generated image / deepfake attack captured by the Trust Layer.

The deepfake is stopped before your policy approves it.

Your KYC provider still verifies identity. NeuroVerify tells you if the face is real. Your policy makes the final call.

What liveness misses

Liveness asks if someone is there. Not if they’re real.

Your checks can work exactly as designed and still approve a fake. These are the three attacks that get through.

01

The face swap

A real person on camera, wearing someone else’s face in real time. They blink, turn and smile on cue, so liveness passes.

02

The face that never existed

An AI-generated selfie, paired with stolen or synthetic data. It matches the photo it was built to match.

03

The injected stream

A virtual camera feeds pre-made video straight into the app. The capture screen never sees a real lens.

NeuroVerify

One call. Six checks. One answer.

Send the selfie, video or voice sample. NeuroVerify runs six checks in parallel and returns one score with the evidence behind it.

01Media input
Customer selfie
ImageCustomer selfie
Customer video frame
VideoCapture frames
Customer voice sample
AudioVoice sample
Secure media stream
02 · NeuroVerifyParallel authenticity analysis
Visual Safety ScreeningChecking…
Live Presence VerificationChecking…
Face Manipulation DetectionChecking…
AI Generative Model AnalysisChecking…
AI Pixel-Level ManipulationChecking…
AI Content ComplianceChecking…
All six running in parallelUnified engine
Powered by Neural Defend'sAtlas 1B™ Foundation Model
03Unified result
Media authenticity

Deepfake detected

High-risk authenticity evidence is ready for customer policy.

Risk stateReview

Why NeuroVerify

Ranked first. Fast enough to be invisible.

Accuracy that is independently measured, speed your customer never notices, and one answer your policy can use.

#1 of 36

Independently ranked

Top of VendorBench-100 with an MCC of 0.876. The next-best vendor scored 0.646.

<200 ms

Fast enough to sit inline

p95 on eligible image requests under defined test conditions. Your customer never waits.

6 → 1

Six checks, one score

Every signal runs on the same request. Your policy reads one score, with the evidence behind it.

0

New steps for your customer

NeuroVerify reads the selfie or video you already capture. The journey looks exactly the same.

Easy integration

Keep your KYC journey. Add one call.

Step 1

Get your API key

A scoped key for your app, backend or KYC orchestration layer.

Step 2

Add one call after the selfie

Drop in the mobile SDK, or call it from your backend. Two lines of code.

Step 3

Send what you already capture

The onboarding selfie, liveness video or voice sample.

Step 4

Route on one score

Approve, review or block inside the KYC policy you already run.

SDK-first integration

One API.
Every stack.

Native SDKs for Android, iOS and Flutter, plus Python, TypeScript, Go and Java for your backend. Add NeuroVerify after the selfie step and go live in under 24 hours.

Sign in for API access
$ npm install @neuraldefend/sdk

import { NeuroVerifyClient } from "@neuraldefend/sdk"
const result = await new NeuroVerifyClient().detectImage("selfie.jpg")

Mobile SDKs

Native capture apps
  • KAndroid (Kotlin)
  • SiOS (Swift)
  • FFlutter

Backend SDKs

Server-side checks
  • PyPython
  • TSTypeScript / Node.js
  • GoGo
  • JJava

REST API

For everything else

Already have capture? Send the image to POST /detect/image and get every signal back in one JSON response.

AI agents

MCP server

Give approved AI assistants bounded image and video authenticity tools, with API keys kept outside prompts.

Two lines to integrate<200 ms p95Live in under 24 hours

Who it’s for

Anywhere a selfie opens an account.

Banks, fintechs, insurers, exchanges and platforms in any country. If a face decides who gets in, NeuroVerify belongs in front of it.

01

Banks

Remote account opening

Stop a deepfake before it becomes an account, a card or a mule.Selfie · Video KYC
02

Fintech and payments

Wallet and card onboarding

Keep sign-up fast while synthetic faces get caught inline.Onboarding · Step-up
03

Lending

Loan applications

Check the face behind the application before the money moves.Application · Disbursal
04

Insurance

Policy and claims identity

Verify the person buying the policy is the person claiming on it.Onboarding · Claims
05

Crypto and trading

Exchange and brokerage accounts

Close the door that deepfake account farms rely on to open accounts at scale.KYC · Re-verification
06

Marketplaces and gig

Seller, driver and worker onboarding

Make sure the person who signs up is the person who shows up.Onboarding · Re-checks

Deployment

Run it where your customer data must stay.

Managed cloud API

Fastest path to production. Neural Defend runs the service.

Private cloud / VPC

A dedicated deployment in your network and chosen region.

Secure container

A portable runtime inside your approved environment.

On-premises

Runs inside your own data-centre infrastructure.

Air-gapped

Fully isolated, with no external network path.

ISO/IEC 27001 · ISO/IEC 27701 · ISO/IEC 42001 · SOC 2 Type II. How we handle product data

Use cases

Find your KYC journey.

48 journeys, from bank account opening to video KYC. Each one shows where the deepfake gets in and where NeuroVerify stops it.

Questions

What KYC teams ask first.

We already run liveness. Why add NeuroVerify?

Liveness asks whether someone is in front of the camera. It does not ask whether the face is real. A face swap or injected video can pass a liveness prompt. NeuroVerify checks the same media for manipulation and AI generation, and returns a score your policy can act on.

Do we have to replace our KYC provider?

No. Your provider keeps document checks, face match and the decision. NeuroVerify adds one call after the selfie step and returns authenticity evidence to your existing policy.

Does NeuroVerify check ID documents?

No. NeuroVerify analyses face images, video and audio. Document verification stays with your existing provider.

Will it slow down onboarding?

Eligible image requests return in under 200 ms at p95 under defined test conditions. The methodology is available during evaluation.

Where does our customer data go?

You choose: managed cloud, your own VPC, a secure container, on-premises or fully air-gapped. Neural Defend holds ISO/IEC 27001, 27701 and 42001 certifications and a SOC 2 Type II report.

Can we test it on our own media first?

Yes. Book an evaluation and run NeuroVerify against your own approved selfies and known attacks before you go live.

See it on your own media

Bring your hardest selfies.

Run NeuroVerify against your own approved captures and the attacks you worry about. See the score, the signals and the speed before you commit.