LiveThreat squad

AI fraud detection that explains every flag

Aiden Flux, Senior AI Fraud Risk Analyst, an AI agent by FluxForceAiden Flux — Senior AI Fraud Risk Analyst

Aiden Flux is an AI agent that scores every transaction and monitoring alert against velocity, device, location and the customer's own baseline. Clear false positives can close with a recorded reason, only where you allow it. Everything else reaches your analyst with the evidence already gathered.

Aiden Flux
Aiden Flux, Senior AI Fraud Risk Analyst, an AI agent by FluxForce
Alert #48213 scored
IllustrativeSent to analyst
Risk score 0.81 · high
Flag explained
“Velocity 6x baseline, new device, location mismatch.”
FATF R.20BSA/AML
REPORTS TO
Your Head of Fraud or MLRO
Shadow mode first
How Aiden 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 problem your fraud team faces every shift

Your analysts start each shift with a queue built by rules that can't tell a salary payment from a mule account. Most alerts close as false positives, and each one still needs a written reason. Meanwhile, instant payment rails settle in seconds.

LIVE QUEUE
Hours

to clear an alert by hand

Instant payments settle in seconds.

Alert fatigue

The same customers, every month

Rules fire on thresholds, not behaviour. A customer paid on the 25th trips the same scenario every month, and someone has to clear it again with a fresh note.

Speed gap

Fraud moves faster than review

FedNow in the US, UPI in India, InstaPay in the Philippines and Faster Payments in the UK settle in seconds. A queue reviewed tomorrow morning is reviewing money that's already gone.

Audit gap

A closed alert with no reason is a finding

Examiners ask why an alert was closed. Whether it was closed is the easy part. If the answer lives in an analyst's head or a free-text box, nobody can replay it.

Job description

What Aiden Flux does Job description

Aiden Flux is a Senior AI Fraud Risk Analyst. He sits beside your transaction pipeline and your monitoring system, scores what comes through and prepares the case for your analyst.

AI AGENT · THREAT SQUADLive
Aiden Flux, Senior AI Fraud Risk Analyst, an AI agent by FluxForce
AIDEN FLUX
Senior AI Fraud Risk Analyst
REPORTS TO
Your Head of Fraud or MLRO
WORKS WITH
Your core banking, payment, card and case management systems
DEPLOYED
Shadow mode first, then the autonomy you set
KEY RESPONSIBILITIES
01Score every transaction and monitoring alert against velocity, device, location and the customer's own baseline
02Explain every flag in plain English, with the signals that drove the score
03Close clear false positives with a recorded reason, only in the risk bands you allow
04Send everything else to an analyst with the evidence attached
05Learn from analyst decisions, with every retrained model approved by a person before release
AUTONOMY MODEL
Low risk
Can close on its own, 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 Aiden 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 Aiden Flux produces on your data, next to your current system, before he acts on anything.

01
Alerts closed with a reason
How many alerts Aiden would close, and whether your analysts agree with each reason.
02
Analyst agreement
How often your analyst's decision matches Aiden's recommendation, by risk band.
03
Missed-fraud review
Every confirmed fraud case Aiden scored low. Read this number first.
04
Time to case-ready
Minutes from alert to a case file an analyst can decide on.
05
Repeat alerts
How often the same customer re-alerts on the same scenario.
06
Escalation quality
Share of escalated cases your team confirms as suspicious.
07
Scoring latency
Time to score a payment at your volumes, on your infrastructure.
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 fraud detection works with Aiden Flux

Aiden Flux connects beside your systems through APIs. Your core stays where it is.

01

Ingest

Transactions and monitoring alerts arrive from your core banking system, payment gateway or card processor through an API. Typical fields are amount, channel, counterparty, device, IP address, location and timing.

02

Score

Aiden combines a scored model with deterministic rules and the customer's behaviour baseline. Signals from other FluxForce agents, such as session trust from Nova Sentinel, feed the same score.

03

Route

Your autonomy settings decide what happens next. Low risk can close with a reason if you allow it. Medium risk goes to an analyst by default. High risk always goes to an analyst. You set the bands per rule, channel and transaction type.

04

Explain

Every score comes with a plain-English explanation, the signals behind it and the rule or policy it maps to. The decision, its inputs and the person who approved it go into tamper-evident evidence storage.

Want to see this on your data?

Run Aiden Flux in shadow mode beside your current system. He scores, explains and opens cases, and nothing is blocked or closed. Compare his calls with your analysts' before you switch anything on.

Request a shadow mode trial
Compliance and regulatory mapping

Regulatory frameworks Aiden Flux supports

Aiden doesn't make you compliant. He produces the evidence these frameworks expect you to keep.

FATF Recommendation 20
Suspicious transactions reported promptly. Aiden prepares the case, and your MLRO decides whether to report.
BSA / FinCEN SAR rule
US banks file within 30 calendar days of initial detection. Every alert carries a timestamped record from its first score.
PMLA and FIU-IND
Indian reporting entities get STR evidence prepared for the Principal Officer to review.
UK MLRs 2017 and POCA 2002
Suspicious activity goes to the UKFIU through your nominated officer. Aiden builds the file that officer reviews.
EU AI Act
Fraud detection is carved out of the Annex III high-risk credit scoring category, but your examiner will still ask how each score was reached.
DORA
EU financial entities classify and report major ICT incidents. Aiden's decision log shows what was scored, and when, during an incident.
Analyst view

What your fraud analyst sees

Fewer alerts to clear by hand. Each one arrives with its evidence.

BEFORE AIDEN FLUX
Every alert a threshold rule raises
The same customers re-alerting each month
Evidence gathered by hand across systems
Closure reason typed into a free-text box
Reviewed the next business day
AFTER AIDEN FLUX
Clear false positives closed with a reason, where you allow it
Repeat alerts traced to the customer's baseline
Evidence attached when the case opens
Every decision replayable for an examiner
Scored as the transaction arrives
Options

How the options compare

CRITERIA Add analystsRules-only engine Aiden Flux, Senior AI Fraud Risk Analyst, an AI agent by FluxForceAiden Flux
Time to first results A hiring and training cycleScenario build and tuning Shadow mode on your live data
Who decides AnalystRule threshold, then analyst Analyst, inside autonomy bands you set
Why a flag fired Analyst notes, varies by personRule ID and threshold Plain-English reason with the signals behind it
Learns from outcomes Through training and experienceOnly when someone retunes the rules From analyst decisions, with human approval before release
Cover outside office hours Needs shiftsYes Yes
Where it's weaker Cost grows with alert volumeStatic thresholds drift away from real behaviour Needs past decisions and a shadow period before you trust the bands
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 Aiden 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 Aiden 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.

An AI fraud agent scores each transaction or monitoring alert against signals such as velocity, device, location and the customer's own behaviour baseline, then combines that score with deterministic rules. Aiden Flux attaches a plain-English reason to every score and routes the case by the autonomy bands your team sets. Your analyst makes the call on anything that isn't clearly low risk.

Your analyst does. Aiden can close clear false positives on his own only in the risk bands you allow, and each closure carries a recorded reason. Medium risk goes to a person by default and high risk always does. A kill switch turns Aiden off without touching your other systems.

We don't quote accuracy figures from our own test data. A false positive reduction claim means little without the base rate, the scenario set and the name of whoever reviewed the closures. Aiden runs in shadow mode on your data, and you measure agreement and missed fraud yourself.

Aiden scores your live transactions and opens cases, but nothing is blocked or closed. Your analysts keep working as they do today, and you compare Aiden's calls with theirs. You decide whether, and where, to switch on any autonomy afterwards.

A transaction or alert feed with amount, channel, counterparty, timestamps and customer identifiers. Device, IP address and location data improve the score. Past analyst decisions help Aiden learn what your team treats as a false positive.

No. Aiden sits beside your current system, reads its alerts and your transaction feed, and prepares cases. You can keep your scenarios and add Aiden's scoring on top.

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 Aiden on your data before anything changes

Run Aiden Flux beside your current process. He 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