A real-looking person who doesn't exist
Synthetic identities mix real and invented details. Each piece checks out on its own, so the file looks clean until the account is used for fraud.



28 specialized agentsAll systems operational
Ready to transform your security infrastructure?
Explore our complete agent library and request a custom demoView All Solutions
Aiden FluxSenior AI Fraud Risk AnalystFraud Detection & Risk Scoring
Rhea LedgerSenior AI KYC/AML Compliance DirectorKYC/AML & Sanctions Screening
Nova SentinelLead AI Zero Trust Security ArchitectZero Trust Access Security
Iris VermaAI Verification SpecialistIdentity Verification & KYC
Oscar GraySenior AI OSINT Intelligence DirectorOSINT & Threat Intelligence
Bella NovaAI BNPL Risk AnalystBNPL Risk Monitoring


28 specialized agentsAll systems operational
Ready to transform your security infrastructure?
Explore our complete agent library and request a custom demoView All Solutions


28 specialized agentsAll systems operational
Ready to transform your security infrastructure?
Explore our complete agent library and request a custom demoView All Solutions
Iris Verma — Senior AI Identity Verification SpecialistIris Verma is an AI agent that checks identity documents, selfies and liveness at onboarding and re-verification. She looks for tampered documents and synthetic identities, and flags documents near expiry so re-verification starts on time. Clear checks can complete with a recorded reason, only where you allow it. Everything else reaches your analyst with the evidence attached.

Your onboarding team checks documents by eye, under pressure to move fast. Edited documents and synthetic identities are built to pass that kind of glance. And once a customer is on the book, expiring documents slip until a periodic review catches them.
how most documents get checked
Edited documents are built to pass a glance.
Synthetic identities mix real and invented details. Each piece checks out on its own, so the file looks clean until the account is used for fraud.
Changed dates, swapped photos and altered fonts are hard to see on a phone photo. An analyst checking dozens a day will miss some.
Customer due diligence needs current documents. Without a trigger, expired IDs sit on file until the next scheduled review.
Iris Verma is a Senior AI Identity Verification Specialist. She sits inside your onboarding and re-verification flows, checks each document, selfie and liveness result, and prepares the case for your analyst.

We don't publish accuracy numbers from our own tests. The numbers that matter are the ones Iris Verma produces on your applicants, next to your current process, before she acts on anything.
Iris Verma connects to your onboarding flow and document capture tools through APIs. Your customer journey stays where it is.
Document images, selfies, liveness results and application data arrive from your app or capture vendor. Results from video KYC sessions, such as V-CIP in India, can feed the same checks.
Iris checks document structure, fonts, visible security features and whether the data is consistent. She reviews the face match and liveness result, and looks for details shared with other applicants.
Your autonomy settings decide what happens next. Clear checks can complete with a reason if you allow it. Medium risk goes to an analyst by default. High risk always goes to an analyst.
Every outcome comes with a plain-English reason and the checks behind it. The result, its inputs and the person who approved it go into tamper-evident evidence storage, and the expiry date sets the next re-verification.
Run Iris Verma in shadow mode on your live applications. She checks, explains and opens cases, while your current process makes every call. Compare her calls with your analysts' before you switch anything on.
Iris doesn't make you compliant. She produces the verification evidence these frameworks expect you to keep.
Fewer documents checked by eye. Each risky one arrives with its evidence.
| CRITERIA | Manual review | Point verification vendor | Iris Verma |
|---|---|---|---|
| Time to first results | A training cycle for new staff | Vendor integration | Shadow mode on your live applications |
| Who decides | Analyst | Vendor pass or fail, then analyst | Analyst, inside risk bands you set |
| Why a check failed | Analyst notes, varies by person | Vendor code or score | Plain-English reason with the checks behind it |
| Sees across applicants | Rarely | Usually one check at a time | Yes, shared details are flagged |
| Document expiry | Periodic review | Not usually tracked | Tracked, with re-verification started on time |
| Where it's weaker | Slow and inconsistent at volume | A pass or fail your examiner can't question | Only as good as the image and liveness capture it receives |
Iris's checks count for more when other agents carry the verified identity forward.

Takes the verified identity into sanctions and PEP screening and customer risk rating.
Meet Rhea
Links Iris's result to one identity record used across every channel.
Meet Cian
Watches the new account's first transactions for fraud signs Iris couldn't see at onboarding.
Meet AidenLow risk can run on its own if you allow it. Medium risk goes to a person by default. High risk always goes to a person. You set the bands per rule, channel and transaction type.
Turn Iris off without touching the other agents or your core systems. The switch, and who used it, is stamped on the record.
Run Iris on live data with nothing blocked or closed. Compare the calls with your team's before anything changes.
Every decision answers why, in plain English, with the signals and the rule or policy behind it.
Each decision is stored with its inputs, its reasoning and the person who approved it, in tamper-evident evidence storage.
Agents connect beside your systems through APIs. Your core banking, screening and case tools stay where they are.
What we're learning about AML, fraud and the evidence examiners ask for.






Talk to the people who build the agents. We'll answer per capability, yes or no.
It checks identity documents, selfies and liveness results, looks for tampering and synthetic identities, and prepares each case for a person. Iris Verma attaches a plain-English reason to every outcome and routes cases by the risk bands your team sets. Your analyst makes the call on anything that isn't clearly low risk.
Your analyst does. Iris can complete clear checks on her own only in the bands you allow, each with a recorded reason. Medium risk goes to a person by default and high risk always does. A kill switch turns Iris off without touching your onboarding flow.
It depends on your setup. Iris can review the results your current vendor produces, add checks across applicants and track expiry. Many institutions will run her alongside the vendor they already have.
She looks for details shared across unrelated applicants, such as the same phone number, address or device, and for data on one application that doesn't fit together. Those links go to your analyst as a side-by-side view.
Iris checks your live applications and opens cases, but she doesn't complete or turn away any applicant. Your analysts keep working as they do today, and you compare Iris's calls with theirs. You decide whether, and where, to switch on any autonomy afterwards.
Document images, selfie and liveness results, and application data. Past analyst decisions help Iris learn what your team accepts. Expiry dates from your KYC system let her start re-verification on time.
FluxForce runs as SaaS, on-premise or hybrid, built on Microsoft Azure. We agree data residency and which components run inside your environment during deployment design, before any data moves.
Run Iris Verma beside your current process. She works on your live data and records every call, and nothing is blocked, closed or sent until you decide.
Shadow mode results belong to you.
Start with one workflow in shadow mode, then decide how much each agent does on its own.