ISAT

Real-time fraud & risk engine · Lagos, Nigeria

Score the transfer before the money moves.

ISAT is a real-time fraud and risk engine for Nigerian digital payments — it scores a transfer the moment it is initiated and shows the reasons behind the score, so banks and fintechs can allow, step up or hold it before the money moves.

ISAT · decision queue scoring · rules v1
  • ₦15,000Bank transfer · 13:02 · recipient 540dNo risk rules triggered—0Allow
  • ₦600,000Bank transfer · 09:41 · recipient 800dLarge amount (₦500,000 or more)A2 +20 · 1 more30Step up
  • ₦180,000Card · 20:17 · recipient 45dNew device for this senderD1 +15 · 4 more38Step up
  • ₦350,000Bank transfer · 23:48 · recipient 3dRecipient account under a week oldR2 +18 · 6 more79Hold
thresholds 0–29 allow · 30–65 step up · 66–100 holdlatency target <50 ms
Product design — illustrative. Every row is scored by the rules-based engine on this page (try it below). The learned model is in training on cloud NVIDIA H100 GPUs; the real-time API and bank integrations are in development.

Today The risk engine scores a transfer in the browser from transparent rules, and we are training the learned model on cloud NVIDIA H100 GPUs.

Next Real-time scoring at payment latency.

On NVIDIA We are training ISAT's risk model on cloud NVIDIA H100 GPUs: NVIDIA RAPIDS and CUDA run feature engineering across millions of transfers, and a PyTorch graph model learns how money moves between accounts. Next, we will score each payment in real time with NVIDIA Triton and NVIDIA Morpheus.

Why now Nigerian banks and fintechs lost ₦25.85 billion to payment fraud across 67,518 incidents in 2025 (NIBSS).

Works today · Rules-based demo

Try the engine

Describe a transfer and the engine scores it the way the production rules do: a 0–100 risk, the reasons ranked by weight, and the action a bank would take. Everything runs in your browser; nothing is sent to us. This is the rules engine as it stands today — transparent rules you can read — not a trained model.

ISAT risk engine

The transfer

Scores update as you type. Thresholds: 0–29 allow · 30–65 step up · 66–100 hold.

The rule table · maximum weight per signal

  • Amount+303 tiers from ₦100,000
  • Amount vs the sender's usual+254 tiers from 2×
  • Recipient account age+254 tiers under 90 days
  • Transfers in the last hour+254 tiers from the second transfer
  • Hour of day+12late night; a smaller weight at the edges of the day
  • New device+15flat weight
  • Channel+6USSD and card; bank transfer is the baseline
  • Combinations+18new device + new recipient · unusual amount + unusual hour

Weights add up and are capped at 100. One tier fires per signal; the two combination rules fire on top.

Risk score · 0–100

Hold

Pause the transfer for review before any money moves.

Reason codes · ranked by weight

  • R2Recipient account under a week old+18
  • D1New device for this sender+15
  • H2Late-night hour (23:00–04:59)+12
  • A1Above-average amount (₦100,000 or more)+10
  • U13× the sender's usual amount+10
  • X1New device paying a recipient under a week old+10
  • V0Second transfer within the hour+4

Sum of weights 79 → capped at 100 → score 79

Rules-based demo. Runs in your browser; no request leaves this page. Not a trained model and not a decision on any real payment.

Product

A score with its reasons, in the payment flow

Most teams score risk with static rules that fraudsters learn to route around. ISAT gives banks, fintechs, microfinance banks and payment processors a real-time, explainable score — every number comes with its reason codes — built so the learned model now in training can take over from the rules without changing the interface.

Works today

Explainable score

Every transfer gets a 0–100 risk and the reasons behind it, ranked by weight: the amount against the sender's pattern, how new the recipient is, velocity, device and hour. An analyst can read the decision, and a customer can be told why.

79 · Hold · R2 recipient under a week old · D1 new device · H2 late-night hour

In training

Learns the patterns

Static rules are written once and fraudsters learn their edges. The learned model is trained on money-movement patterns instead, so it adapts as new fraud shapes appear — and keeps returning reason codes, not a black box. Training is under way on cloud NVIDIA H100 GPUs; the model is not yet finished or deployed.

In training · PyTorch money-movement graph model · RAPIDS + CUDA features · cloud NVIDIA H100 GPUs

In development

Real-time at payment latency

The score has to arrive inside the payment flow, not after it. The target is a decision in under 50 milliseconds, so the transfer is allowed, stepped up or held before the money leaves.

Target · <50 ms · NVIDIA Triton

Works today

The rules engine

A static web app: a transfer goes in, a score, ranked reason codes and an action come out. Try it above — it is the same rule table the hero console uses.

  • 0–100 risk score from transparent, readable rules
  • Ranked reason codes with the weight each one adds
  • Three actions: allow, step up, hold
  • Seven inputs: amount, channel, hour, recipient age, velocity, device, amount vs usual
  • Runs in the browser; no request leaves the page
  • Thresholds and weights published on the page

How it works

Transfer in, decision out

Four steps, designed to sit inside a bank's or fintech's payment flow. Today the scoring step is a rule table; the learned model now in training will sit behind the same interface, so the reason codes and the three actions stay the same.

01 · InputTransfer initiated

The payment request as it arrives, before any money moves.

  • amount · channel · hour
  • sender · recipient · device
02 · FeaturesContext

The transfer is placed against what is normal for this sender.

  • amount vs sender's usual
  • recipient account age
  • transfers in the last hour
  • known or new device
03 · ScoreRisk 0–100 + reason codes

Each triggered rule adds its weight; the list is returned ranked, largest first.

  • today: transparent rule table
  • in training: learned model, same output
04 · ActionBack into the payment flow

One of three actions, returned inside the latency budget.

allow 0–29step up 30–65hold 66–100
Why reason codesAn analyst can see what fired and by how much; a customer can be told why a transfer was held; a regulator can audit the decision. The learned model will keep this contract.
Why thresholdsAllow, step up and hold map to what a bank can actually do in the moment: release, ask for a second factor, or pause for review. Each institution tunes the two cut-offs to its own risk appetite.

Why now

Fewer naira lost, no fewer attempts

Industry coordination cut the value lost to payment fraud in 2025 by about half. The number of incidents did not fall with it, transfers remain among the largest loss channels, and the regulator is warning of new fraud patterns as digital payments grow. The next gain comes from smarter, real-time, adaptive scoring — not from more static rules.

₦25.85bn

lost to payment fraud by Nigerian banks and fintechs in 2025.

Source: NIBSS, 2026

67,518

fraud incidents reported in 2025. The attempts did not fall with the losses.

Source: NIBSS, 2026

−51%

value lost versus 2024 (₦52.26 billion), after a year of industry coordination.

Source: NIBSS, 2026

TransfersTransfers remain among the largest channels for fraud losses — the channel this engine scores first.Source: NIBSS, 2026
Lagos63.43% of reported fraud was concentrated in Lagos, where ISAT is based.Source: NIBSS, 2026
Reporting gapFraud reports fell 34% in the fourth quarter of 2025 — a blind spot, not necessarily fewer attempts.Source: NIBSS, 2026
RegulatorThe Central Bank of Nigeria has warned of new forms of bank fraud as digital payments grow.Source: CBN, 2026

Nigerian banks and fintechs lost ₦25.85 billion to payment fraud across 67,518 incidents in 2025 (NIBSS).

Technology

Rules in the browser. A model in training on NVIDIA.

The demo needs no GPU; it is a static web app. The learned model does: feature engineering over millions of transfers with graph features is GPU work, and that training is running now on cloud NVIDIA H100 GPUs. Serving the model inside a payment's latency budget is the next step.

Today · in use
  • We are training ISAT's risk model on cloud NVIDIA H100 GPUs: NVIDIA RAPIDS and CUDA run feature engineering across millions of transfers, and a PyTorch graph model learns how money moves between accounts. Next, we will score each payment in real time with NVIDIA Triton and NVIDIA Morpheus.
  • Train the model — NVIDIA RAPIDS (cuDF, cuML) and CUDA run feature engineering over millions of transfers; a PyTorch money-movement graph model learns how funds move between accounts; all on cloud NVIDIA H100 GPUs. The model is in training and not yet finished or deployed.Workload · Data Science
  • The rules engine on this page is a static web app. The score, reason codes and action are computed in the browser from a published rule table; nothing is sent to a server.
Next · in development
  • Serve in real time — NVIDIA Triton Inference Server returns the score and reason codes inside the payment latency budget (target under 50 ms).Workload · Trustworthy AI / Cybersecurity
  • Streaming fraud pipeline — NVIDIA Morpheus for the real-time pipeline and graph-based fraud detection across the flow of transfers.Workload · Trustworthy AI / Cybersecurity
  • Both steps keep the contract the rules engine already has: a 0–100 score, ranked reason codes, and one of three actions.
Today · scoringBrowser rules engine

Static web app, no GPU. Transparent rule table, reason codes, three actions.

Today · trainingRAPIDS · CUDA · PyTorch

Feature engineering and a money-movement graph model, in training on cloud NVIDIA H100 GPUs.

Next · serveNVIDIA Triton

Score and reason codes returned in under 50 ms, inside the payment flow.

Next · streamNVIDIA Morpheus

Real-time pipeline and graph-based detection over the stream of transfers.

Company

Who is behind ISAT

Incorporated in Nigeria, 2026. Today: the risk engine scores a transfer in the browser from transparent rules, and we are training the learned model on cloud NVIDIA H100 GPUs. Next: real-time scoring at payment latency.

Stage: prototype, pre-revenue. The engine is built for banks, fintechs, microfinance banks and payment processors in Nigeria.

abdulazeez@isatai.com

Sole founder

AbdulAzeez Babatunde Adeyinka

Founder

Founded and built by AbdulAzeez Babatunde Adeyinka, Founder.

ISAT has one person on it: the founder designs the engine, writes the code and runs the company.