Skip to content

Card fraud reviews:
35% fewer false alerts

We built a streaming ML fraud platform for a card issuer that scores transactions in milliseconds, learns from analyst reviews and logs every decision. False positives fell 35%, and analyst workload fell 28%.

Industry: FinTech & Financial ServicesService: AI & Automation

Fewer false positives
35%
Less analyst workload
28%
p95 scoring time
12ms

Overview

Project
at a glance

Industry
FinTechA growing card issuer whose fraud checks had to fit inside sub-second card authorisations.
How we worked
Dedicated product teamAn ML architect, data engineers and an MLOps lead worked inside the client's risk division.
Goal
Leaner fraud operationsCut false alerts without missing more fraud or weakening the audit trail.
What we built
Streaming ML fraud platformReal-time transaction scoring that learns from analyst reviews and logs the reasons behind every decision.

Client

Who we
built it for

Fortitude Archives

Growing card issuer

FinTech
About the client
A growing card issuer whose fraud checks had to fit inside sub-second card authorisations.
What they needed
Cut false alerts without missing more fraud or weakening the audit trail.
Where they were
The issuer's older fraud system used fixed rule chains that couldn't keep up with how customers' spending changed during seasonal peaks. Its false-positive rate was 35% higher than industry benchmarks.

Engagement snapshot

Industry
FinTech
Service
AI & Automation
Engagement
Dedicated product team
Delivered
Streaming ML fraud platform
Headline result
35% · Fewer false positives

The challenge

What was getting
in the way

The issuer's older fraud system used fixed rule chains that couldn't keep up with how customers' spending changed during seasonal peaks. Its false-positive rate was 35% higher than industry benchmarks.

Analysts were buried in alerts, legitimate customers were being declined, and the risk committee had already rejected ML models that couldn't explain their decisions.

  • Alert fatigue

    The volume of false alerts built a 24-hour review backlog, which slowed the response to coordinated fraud waves.

  • Customer churn

    Declining legitimate transactions cut into merchant lifetime value (MLV).

  • Compliance burden

    Without secure, traceable reason codes, the risk committee had rejected earlier ML models.

The solution

What
we built

  1. 01

    Reliable streaming features

    Behavioural features are computed on the transaction stream in under a second, with locked schemas that stop features drifting.

    Type
    Stream-native
    Schema
    Protobuf-locked
    Response time
    Under a second
  2. 02

    Banded active learning

    Review queues are split by risk band, and analysts' decisions feed back into the feature store to improve the model.

    Loop
    Human in the loop
    Feedback
    Active labelling
    Rollout
    Shadow mode
  3. 03

    Traceable decision logs

    Every decision is saved with its contributing features and model version IDs, so it can be traced later.

    Explainability
    SHAP values
    Persistence
    Write-ahead log
    Controls
    SOC 2-ready

Key features

What made it
useful

  • REAL-TIME SCORING

    Scores transactions on the live stream

    The fraud model scores transactions using behavioural features computed on the live stream in under a second.

    Business impact

    12ms p95 scoring

  • ACTIVE LEARNING

    Learns from analysts, explains every decision

    Analyst decisions retrain the model, the likeliest fraud is reviewed first, and every decision carries reason codes.

    Business impact

    35% fewer false positives

  • THROUGHPUT

    Fast feature store

    Shared behavioural features update with every transaction, so the model always works from a consistent state.

    Business impact

    Zero feature drift

  • CONTROLS

    Explainable AI (XAI) gates

    Each decision comes with its contributing weights as reason codes, to meet regulatory requirements.

    Business impact

    100% audit-ready decisions

  • EFFICIENCY

    AI prioritisation routing

    Queues are ordered so analysts work on the most likely fraud waves first.

    Business impact

    28% load reduction

Before and after

How the work
changed

Detection logic

Before

Static thresholds

Signals were judged in isolation, so normal changes in spending were often blocked.

After

Behavioural patterns

Unusual sequences and peer-group anomalies are spotted within sub-second streaming windows.

Controls

Before

Manual justification

There were no consistent reason codes, so audits relied on scattered analyst notes.

After

Audit-first decisions

Secure, traceable logs hold the exact feature state at the moment of each decision.

Throughput

Before

Batch backlogs

Queues spiked at busy times, delaying manual transaction approvals.

After

Stream-native scale

Scoring stays under 12ms however much transaction volume spikes.

Results

The business
difference

  1. ACCURACY

    35% Noise Reduction

    False-positive reduction

    Modelling each customer's behaviour in context cut false alerts while keeping fraud detection coverage.

    Before: Rule-HeavyAfter: 35% Lower

  2. OPS EFFICIENCY

    28% Throughput Lift

    Analyst queue throughput

    Better routing let the existing team handle 28% more volume without adding headcount.

    Before: CongestedAfter: Automated

  3. RELIABILITY

    12ms p95 Response Time

    Scoring time (p95)

    Streaming scoring takes 12ms at p95, so fraud checks don't slow down card authorisations.

    Before: < 20msAfter: 12ms

Testimonial

What the client
says

“False alerts were taking up too much of our analysts' time. Since the new fraud model went live, false positives are down 35% and analyst workload 28%, and every decision carries a reason code we can trace.”
Joyce EdwardsHead of Fraud Operations, Fortitude Archives

Key results

  • 35% fewer false positives
  • 28% less analyst workload
  • 12ms p95 scoring

Trust and control

How we kept it
safe and reliable

  • 01

    Model explainability

    Each decision carries SHAP reason codes mapped to policy, so regulators can see why it was made.

    COMPLIANCE READY
  • 02

    Data privacy

    Unneeded personal data is stripped out, and workflows are built to SOC 2 and GDPR requirements.

    SOC 2-READY
  • 03

    Growth and reliability

    The cloud-based streaming platform scales reliably during sudden traffic surges.

    CLOUD NATIVE
  • 04

    Code and IP ownership

    The issuer owns 100% of the models, workflows and reusable modules from project completion.

    100% OWNED

Faster delivery

Built on tested foundations

Starting from tested components saved about 5.5 weeks of setup work. That time went into the active learning loop and the reason-code logs.

  • Behavioural identity module

    Our tested behavioural identity module gave the model a profile of each cardholder's usual activity to compare transactions against.

  • Fraud feature store module

    A reusable feature store module held the shared behavioural features and took analyst labels back in.

  • Live monitoring platform

    An existing monitoring platform tracked scoring times and model health in production.

  • FinOps safety controls

    Pre-built cost controls kept streaming compute spend predictable during seasonal traffic spikes.

FAQ

Straight
answers

Have a different question? Ask it on a 30-minute call.

Book a call

We replaced fixed rule chains with streaming ML that scores each transaction against behavioural patterns in under a second. Analysts review cases in risk-banded queues, and their decisions feed back into the model. False positives fell by 35% while fraud detection coverage was maintained.

Cut false fraud alerts without missing fraud

If rule-based checks are flooding your analysts and declining good customers, we can help you move to streaming ML that explains each decision.