Apr 2, 2026
A Real-Time AI Fraud Decision Engine Under 50ms
A deep dive into how GeekyAnts built a real-time AI fraud detection system that evaluates transactions in milliseconds using a hybrid multi-agent approach.
Author


Book a call
Table of Contents
Inside a high-performance Real-Time AI Fraud Decision Engine, a system that reviews a financial transaction and returns a decision in under 50 milliseconds.
Every time you tap your phone to pay for something, a quiet competition is taking place. On one side are fraudsters looking to steal money. On the other side are detection systems trying to stop them in the time it takes to blink.
The Problem With Fraud Today
Digital payments have grown at a pace that has outrun traditional fraud prevention. The scale alone is staggering: large financial platforms process tens of thousands of transactions every minute. No team of human analysts can review that volume in real time.
Four problems sit at the heart of the challenge:
- Volume. Thousands of transactions arrive every minute, far beyond human review capacity.
- False alarms. Many older systems block payments from real customers. These false declines push people away from digital banking.
- Speed of attack. Once a fraudster gains access to an account, funds can be moved within minutes.
- No clear explanations. Legacy systems often return error codes with no reasoning behind them, making it hard to communicate decisions to customers or regulators.
Three Layers of Intelligence
Rather than rely on a single tool, the team built a system that combines three distinct layers of decision-making:
- A machine learning model that scores the risk of each transaction based on behavioral patterns.
- A rules engine that checks transactions against known fraud patterns.
- AI reasoning agents that generate written explanations of why a transaction was flagged.
How a Transaction Gets Reviewed
When a transaction arrives, it passes through a sequence of specialized processes, each one focused on a specific task.
Step 1: Signal Collection
The system gathers and organizes the raw data attached to the transaction: device information, location, transaction amount, and account history. These are converted into a standard format the system can work with.
Step 2: Fraud Category Identification
Not all fraud looks the same. The system checks which of nine fraud categories the transaction might belong to such as account takeover, card misuse, or wire transfer fraud. Identifying the category helps apply the right detection logic.
Step 3: Risk Scoring
A machine learning model evaluates fifteen risk signals to produce a fraud probability score. These signals include device risk, transaction speed, geographic location, and whether a VPN or proxy is in use, among others.
Step 4: The Decision
Using the risk score and pattern matching against 27 known fraud scenarios, the system decides one of three outcomes: approve the transaction, challenge it (for example, by requesting additional verification), or decline it.
Step 5: The Explanation
In the background, an AI reasoning process generates a written summary of why the decision was made. This explanation is stored for compliance teams, auditors, and customer support, anyone who needs to understand the reasoning later.
Two Paths, One Decision
The architecture separates speed from depth. The fast path handles the core decision in 5 to 15 milliseconds using the machine learning model and the rules engine. This is what keeps the payment experience smooth for the end user.
The enrichment path runs in the background and completes within 200 milliseconds. It produces a fuller picture: threat severity, attack patterns, and recommended actions, all written in plain language rather than code.
Splitting the two paths means the payment does not have to wait for deep analysis. Both can happen without slowing each other down.
Why A Single Method Is Not Enough
Machine learning is good at identifying unusual behavior—transactions that deviate from a user's normal patterns in ways that are hard to put into words. Rules, on the other hand, are good at catching specific, well-documented attack patterns with high confidence.
The Nine Fraud Types the System Covers
The system is built to recognize a wide range of fraud types common in digital finance:
- Account Takeover. When a fraudster gains access to someone else's account, often through stolen credentials.
- Transaction Fraud. Unauthorized payments were made from a legitimate account.
- Card-Not-Present Fraud. Fraud occurs when a physical card is not required, which is common in online purchases.
- Mobile Banking Fraud. Attacks that target users through mobile apps or devices.
- Onboarding and Identity Fraud. False identities are used to open new accounts or pass verification checks.
- Digital Wallet Fraud. Unauthorized use of payment apps and wallet services.
- Loan and Credit Fraud. Applications for credit or loans using false information.
- Wire Transfer and Business Email Fraud. Attackers impersonating executives or vendors to redirect payments.
- Internal Employee Fraud. Misuse of system access by people within an organization.
Across these nine categories, the system models 27 distinct fraud scenarios, specific attack patterns that the decision engine checks for during each review.
The performance targets were set with real payment flows in mind. A decision that takes several seconds is too slow; customers expect near-instant responses.
- Core decision time: 5 - 15 milliseconds
- Full analysis with explanation: under 200 milliseconds
- Fraud categories covered: 9
- Fraud scenarios modeled: 27
What Building This System Taught Us
- Speed is not optional. In payment flows, a slow decision is as disruptive as a wrong one.
- Explainability matters as much as accuracy. A system that cannot explain its decisions is a liability for compliance and customer communication.
- Hybrid systems outperform single-method systems. Rules and machine learning cover different failure modes.
- Observability is essential. Being able to trace each decision through the pipeline makes debugging complex systems possible.
- Rules remain necessary for critical decisions. AI reasoning is a valuable layer, but deterministic logic still provides the reliability that high-stakes decisions require.
The Bigger Picture
This multi-agent architecture reflects the direction that real-world fraud prevention is taking. Financial institutions increasingly depend on layered systems that combine structured rules, statistical models, and AI-generated reasoning to keep pace with attackers.
Subscribe to Our Newsletter
Subscribe to RSS
Press & Media Hub RSS FeedRelated Articles.
More from the engineering frontline.
Dive deep into our research and insights on design, development, and the impact of various trends to businesses.

Jun 19, 2026
We Built a 114-Second AWS-to-Azure Failover. Here’s What We Learned
A practical guide to building a 114-second multi-cloud disaster recovery failover between AWS and Azure — what we built, what broke, and what we learned.

Jun 17, 2026
Google I/O 2026 Mobile Playbook: AI Studio, Android CLI, and Antigravity for App Development
Google I/O 2026 shifted mobile development from code assistance to full lifecycle delivery. This blog breaks down what that means for Android, Flutter, and React Native teams.

Jun 17, 2026
Beyond the Chatbot: Architecting Enterprise Workflows with Managed Agents in the Gemini API
A practical guide to building production-ready agentic workflows with Google's Managed Agents API, covering architecture, governance, and where enterprise teams should start.

Jun 16, 2026
Integrating AI with Wearable Healthcare Apps: Architecture, Compliance & ROI
A technical and compliance-focused guide for U.S. healthcare founders and providers on building AI-enabled wearable healthcare apps across architecture, compliance, and ROI.

Jun 16, 2026
HL7 and FHIR for AI Healthcare Platforms: What It Takes to Build for Production
A practical guide covering the HL7 and FHIR standards, production readiness requirements, implementation roadmap, architecture considerations, and compliance controls that AI healthcare teams need to address before enterprise deployment.

Jun 12, 2026
Cloud-Native and Cloud-Agnostic Are Not Ideologies; They Are Business-Stage Decisions
This blog explains how organizations can balance speed, scalability, and operational flexibility as they grow from startup to enterprise scale.