Cut fraud and cover the AML mandate, from the app layer to the transaction, on one agent.
Live flow: attacks stopped at each layer, your real users served.
Financial institutions lose money two ways at once: fraud that moves through the application and payment layer, and a regulator that can pull a license. Both are now more likely than ever, and both live on the layer Nemesis owns.
The threat
The attacks draining banks and fintechs are the ones traditional antivirus and signature WAFs never see: zero-days, AI-crafted exploits, API abuse, and account takeover. In one recent year a single national market lost tens of billions to fraud, most of it structured through APIs and mobile apps to slip past static checks. At the same time, regulators now mandate real-time transaction monitoring, sanctions screening and suspicious-transaction reporting, with hard deadlines.
What Nemesis does
One agent installs on your servers, with no DNS change, and does three things on one shared view of every customer and device:
Application Shield protects your apps and APIs with positive security. It learns how each service normally behaves and blocks the rest, so zero-days and API abuse are stopped by default-deny, no signature required.
Edge absorbs the DDoS and bot floods aimed at your platform.
Omniguard watches every transaction for fraud tuned to local typologies (SIM-swap, account takeover, mule networks) and generates goAML-ready STR filings for your compliance team.
Because the same agent sees the attack and the transaction together, an exploit attempt against your API instantly raises the fraud score on the account behind it, a signal no unbundled set of point tools can share.
Why it's different
A signature firewall only knows attacks it has seen before, so a brand-new exploit walks straight through. Nemesis learns your normal and blocks everything else. It runs in your own environment, so customer data stays in-country, and it draws on a fraud-and-compliance-AI heritage rather than a generic rules engine.
Getting started
Start with a free 30-day pilot on one service, observe-only until you say go. We show you exactly what is hitting your apps and moving through your accounts, on your own traffic, before you commit to anything.
Integrate Nemesis
Plug Nemesis into your stack
One agent runs all three. Start with whichever you need. Most begin with Omniguard for the money, add Application Security for the apps behind it, and Edge to keep it all standing.
See it working - live demo
A real, working app for this sector, deployed twice: one build protected by Nemesis end to end, one left unprotected. Run the same attacks on both - fraud, injection, account takeover, BOLA and mule cash-outs - and watch the protected build block what the other lets through. It opens a guided walkthrough so you can run the end-to-end tests yourself.
Whatever your setup, there is a way in. You might own every line of your payment code, sit on a managed core that only exposes APIs, get nothing but a read-only export, or run the platform other banks depend on. Pick who you are and get the exact path, mapped to your fraud typologies and your CBN / NFIU obligations.
Free to start
Screen every customer and counterparty against sanctions, PEP and enforcement lists, free, before you ever touch the paid engine. 100 screens a day, no card, no function to build. Search it now or wire the API, then grow into full transaction scoring when you are ready.
POST https://shield.nemesislabs.xyz/api/v1/omniguard/verify { "check":"sanctions_pep", "subject":"…" } # free · no function needed
1 Who are you?
High volume across branch, mobile, USSD and cards, usually on a managed core.
Your access to transactions
Managed core (Finacle / T24 / Flexcube). Often read-only feed; some action APIs.
Recommended: Read-only feed · T+seconds · or Provider API / connector
✓ Real-time transaction monitoring✓ Sanctions & PEP screening✓ STR/SAR to the NFIU (goAML)✓ CTR on cash ≥ ₦5m / ₦10m✓ 5-year record keeping✓ NIBSS fraud reporting
2 How do you reach your transactions?
Read-only feed · T+seconds
Your provider gives you only a read-only view of transactions - a database replica, an SFTP file drop, a CSV/JSON export or a Kafka topic. The feed connector polls it every few seconds, scores new transactions, and triggers an intervention while the money can still be recovered.
LatencyT + seconds · inside the claw-back window
EnforcementFreeze / recall before the funds are cashed out
Best forMicrofinance and payment-service banks on a managed core with no write APIs, and anyone whose provider offers only a read-only transaction feed.
1
Create a function, get your key
Same function + ingest token. Rules are seeded for your sector and event.
2
Point the connector at your read-only source
A DB replica, an SFTP folder, a webhook, a CSV/JSON drop or a Kafka topic. The connector reads new rows on a short interval; nothing is written back to the core.
Map the export's columns to the Omniguard contract once. New files/rows are normalized automatically.
4
Score new transactions on a short poll
Every few seconds the connector scores the latest transactions with /score and keeps the high-risk ones.
5
Intervene inside the window
For NIP/instant payments the funds sit briefly before cash-out. On a block, Post-No-Debit the beneficiary, request a NIBSS recall, and alert ops - T+seconds, not next-day.
if (r.verdict === "block") {
pndBeneficiary(txn.counterparty_account) // freeze
requestNipRecall(txn.transaction_id) // claw back
ops.alert(txn, r.reasons)
}
6
Report to the NFIU
The same case → goAML STR/CTR export, validated to survive NFIU auto-reject.
Mapped to CBN & NFIU compliance
Transaction monitoring
CBN AML/CFT/CPF Regulations - ongoing, risk-based monitoring of every transaction.
Real-time /score with the fraud + AML rule engine (structuring, mule, velocity, cross-signal, graph).
Sanctions screening
Screen parties against the Nigeria Sanctions List (TPCA 2022) plus UN, OFAC, EU and UK.
/verify sanctions_pep + the Nemesis watchlist (OFAC / UN / EU / UK / PEP / EFCC).
PEP identification & EDD
Identify politically exposed persons and apply enhanced due diligence.
PEP screening flags the party and routes it to review / EDD instead of a silent pass.
Suspicious Transaction Reports
File STR/SAR to the NFIU on the goAML platform, with a valid predicate, category and indicators.
goAML-format STR export, auto-tagged and validated to survive NFIU auto-reject.
Currency Transaction Reports
Report cash at or above ₦5m (individual) / ₦10m (corporate).
Aggregated-cash CTR rule flags reportable cash; export the CTR XML.
KYC / CDD
Verify customer identity at onboarding (BVN, NIN) and keep it current.
/verify bvn / nin / passport against the identity network.
Fraud reporting & records
Report fraud (NIBSS) and keep records for five years.
Every scored transaction is logged with its reasons, source provenance and verdict - a ready audit trail.
Risk-based approach
Apply controls proportional to risk.
Calibrated 0-100 risk score with tiered review / block thresholds per function.
The whole flow in four calls
# 1 · create a function → get your key (or do it in the console)
POST https://shield.nemesislabs.xyz/api/v1/omniguard/functions { "name":"…", "industry":"…", "event":"…" }
# 2 · score a transaction before it commits
POST https://shield.nemesislabs.xyz/api/v1/omniguard/score { "function_id":"fn_…", "amount":…, "counterparty_account":"…" }
→ { "verdict":"block", "overall_score":97, "reasons":[…], "transaction_id":"…" }
# 3 · screen a party (no function needed, screening is free)
POST https://shield.nemesislabs.xyz/api/v1/omniguard/verify { "check":"sanctions_pep", "subject":"…" }
# 4 · report the outcome + file the STR
POST https://shield.nemesislabs.xyz/api/v1/omniguard/outcome { "transaction_id":"…", "outcome":"fraud" }
GET https://shield.nemesislabs.xyz/api/v1/omniguard/reports/{id}/goaml → goAML STR XML for the NFIU
Wire all of this from your AI coding agent. Add the Nemesis MCP server to Claude, Cursor, Windsurf or VS Code, then just ask - the agent calls the real tools (create a function, score a transaction, screen a name, protect the app) and ships it for you. Sanctions and PEP screening is free.
Or one command: npx -y @nemesis-shield-autogon/mcp
2 · Ask your agent
Add Nemesis to my transfer API: create an Omniguard function for banking transfers, score every transfer for fraud and AML before it sends, and screen the beneficiary name against sanctions and PEP lists. Then protect the API itself with Application Security.
Would rather we set it up with you?
Not every team wants to wire this in themselves. Tell us your setup and our engineers will map the integration to your stack and walk you through it end to end, from first call to enforce.
Screen every customer and counterparty before the money moves
One consolidated watchlist covering OFAC, EU, UN and UK sanctions, global politically exposed persons and adverse media, over 60,000 entities, matched with an alias-aware engine tuned for local names. Try it free on any name, then wire the same screening into onboarding and every transaction through the Omniguard API.
