BetaTrust and Identity squad

AI identity verification that shows its evidence

Iris Verma, Senior AI Identity Verification Specialist, an AI agent by FluxForceIris Verma — Senior AI Identity Verification Specialist

Iris 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.

Iris Verma
Iris Verma, Senior AI Identity Verification Specialist, an AI agent by FluxForce
Onboarding check #30592
IllustrativeSent to analyst
Identity risk 0.74 · high
Flag explained
“Font mismatch in date of birth, weak selfie match, liveness passed.”
FATF R.10RBI KYC
REPORTS TO
Your Head of Onboarding or MLRO
Shadow mode first
How Iris works with your team
Shadow mode
first: nothing acts until you say so
3 bands
of autonomy you configure
Every decision
has a replayable record
1 per agent
kill switch
SaaS · on-prem · hybrid
deployment
Product controls, not performance claims. Performance is measured on your data, in shadow mode.
The problem

The verification problem behind every onboarding queue

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.

ONBOARDING QUEUE
By eye

how most documents get checked

Edited documents are built to pass a glance.

Synthetic identity

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.

Tampered documents

Edits that pass a quick look

Changed dates, swapped photos and altered fonts are hard to see on a phone photo. An analyst checking dozens a day will miss some.

Expiry drift

Documents expire quietly

Customer due diligence needs current documents. Without a trigger, expired IDs sit on file until the next scheduled review.

Job description

What Iris Verma does Job description

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.

AI AGENT · TRUST AND IDENTITY SQUADBeta
Iris Verma, Senior AI Identity Verification Specialist, an AI agent by FluxForce
IRIS VERMA
Senior AI Identity Verification Specialist
REPORTS TO
Your Head of Onboarding or MLRO
WORKS WITH
Your onboarding app, document capture vendor and KYC system
DEPLOYED
Shadow mode first, then the autonomy you set
KEY RESPONSIBILITIES
01Check identity documents for tampering, template mismatches and data that doesn't add up
02Compare the selfie with the document photo and review the liveness result
03Flag signs of synthetic identity, such as details shared across unrelated applicants
04Track document expiry and start re-verification before documents lapse
05Send unclear or risky cases to an analyst with the evidence attached, and record the reason for every outcome
AUTONOMY MODEL
Low risk
Can complete clear checks with a reason, if you allow it
LOW
Medium risk
Goes to an analyst by default
MEDIUM
High risk
Always goes to an analyst
HIGH
You set the threshold per rule.
Kill switch: Turn Iris off at any time
Shadow mode

What to measure in shadow mode on your own data

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.

01
Analyst agreement
How often your analyst's decision matches Iris's recommendation, by risk band.
02
Missed-fraud review
Every confirmed fraudulent identity Iris scored low. Read this number first.
03
Good customers sent to review
How many genuine applicants Iris would send to an analyst, and why.
04
Tamper findings confirmed
Share of documents Iris flagged as edited that your team confirms.
05
Synthetic links found
Applicants who share details with other, unrelated applications.
06
Expiry coverage
Share of customers with a document expiry date on file and a re-verification trigger set.
07
Time to case-ready
Minutes from submission to a case an analyst can decide on.
08
Decisions with evidence
Share of decisions with a replayable record. The target is all of them.
Shadow mode results belong to you. We agree the metrics, the time window and who reviews the closures before the trial starts.
How it works

How AI identity verification works with Iris Verma

Iris Verma connects to your onboarding flow and document capture tools through APIs. Your customer journey stays where it is.

01

Capture

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.

02

Check

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.

03

Route

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.

04

Explain

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.

Want to see this on your data?

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.

Request a shadow mode trial
Compliance and regulatory mapping

Regulatory frameworks Iris Verma supports

Iris doesn't make you compliant. She produces the verification evidence these frameworks expect you to keep.

FATF Recommendation 10
Customer due diligence includes identifying and verifying the customer. Iris records how each identity was checked.
FinCEN CDD Rule
US institutions identify beneficial owners at 25% ownership plus one control person. Iris verifies the individuals your team names.
RBI Master Direction on KYC
Indian regulated entities follow RBI KYC rules, including V-CIP. Iris can review the documents and liveness results your V-CIP process captures.
UK MLRs 2017
UK firms apply customer due diligence when they start a business relationship. Iris prepares the verification evidence your team relies on.
UAE federal AML law
UAE institutions supervised by CBUAE, DFSA or FSRA verify customers before onboarding. Iris keeps the record of each check for your MLRO.
GDPR, UK GDPR and DPDP Act 2023
Selfies and liveness data are personal data. Iris records what was checked and why, under the retention rules you set.
Analyst view

What your onboarding analyst sees

Fewer documents checked by eye. Each risky one arrives with its evidence.

BEFORE IRIS VERMA
Every document checked by eye
Edits spotted only when they're obvious
Shared details across applicants go unseen
Expired documents found at periodic review
Decision reason typed into a notes field
AFTER IRIS VERMA
Clear checks completed with a reason, where you allow it
Tampering signals listed with the area of the image affected
Linked applicants shown side by side
Re-verification started before documents expire
Every decision replayable for an examiner
Options

How the options compare

CRITERIA Manual reviewPoint verification vendor Iris Verma, Senior AI Identity Verification Specialist, an AI agent by FluxForceIris Verma
Time to first results A training cycle for new staffVendor integration Shadow mode on your live applications
Who decides AnalystVendor pass or fail, then analyst Analyst, inside risk bands you set
Why a check failed Analyst notes, varies by personVendor code or score Plain-English reason with the checks behind it
Sees across applicants RarelyUsually one check at a time Yes, shared details are flagged
Document expiry Periodic reviewNot usually tracked Tracked, with re-verification started on time
Where it's weaker Slow and inconsistent at volumeA pass or fail your examiner can't question Only as good as the image and liveness capture it receives
Trust Builders

Built for Regulated Financial Institutions

01

Configurable autonomy

Low 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.

02

Kill switch

Turn Iris off without touching the other agents or your core systems. The switch, and who used it, is stamped on the record.

03

Shadow mode

Run Iris on live data with nothing blocked or closed. Compare the calls with your team's before anything changes.

04

Explainability

Every decision answers why, in plain English, with the signals and the rule or policy behind it.

05

Audit trail

Each decision is stored with its inputs, its reasoning and the person who approved it, in tamper-evident evidence storage.

06

No migration

Agents connect beside your systems through APIs. Your core banking, screening and case tools stay where they are.

Questions? We Have Answers

Frequently Asked Questions

FluxForce

Still have questions?

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.

Shadow mode trial

See Iris on your data before anything changes

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.

  • Runs in shadow mode on your own data, next to your team
  • You agree the metrics, the time window and who reviews the results
  • Kill switch and a replayable record of every decision from day one
  • SaaS, on-premise or hybrid, with data residency agreed up front

Shadow mode results belong to you.

Take the first step

AI agents that prepare the case. Your team makes the call.

Start with one workflow in shadow mode, then decide how much each agent does on its own.

How we start
Discovery and scoping
Integration beside your systems
Shadow mode
Controlled autonomy
Govern and improve