Creating an Open Source Fraud Risk Management System in Order to Close the Financial Inclusion Gap
summary
An open source transactional monitoring engine (code name accio) implements a semi-attached model with a PPA payment adapter, NiFi data prep, Redis caching, Rangodb persistent store, Ambassador + Linkerd service mesh, OpenFast scaling channels, Vault/Keycloak for secrets, ELK for telemetry and Jenkins/Newman CI. MVP meets targets of 3,000 transactions per second and 35 seconds per typology for real‑time interdiction; typology 28 (scams) composes multiple rules and exports JSON cases to any CMS. A center of excellence is planned.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:34Improving Financial Inclusion
- 4:46Digital Public Goods Key To Achieving Financial Inclusion
- 5:48Mojaloop Transforms Real-Time Payments
- 6:20The Mojaloop Community
- 6:57Fraud Risk Management System
- 8:46Code Named Actio-or action
- 14:06What is it? . An open-source transactional monitoring system for fraud
- 17:10Typology breakdown
- 18:40Rules breakdown
- 20:10Rules roll-up
- 21:03Typology Modelling
- 22:06Actio Process Flow
- 25:37The typology life-cycle
- 26:42ACTIO data model
- 27:18Actio Technical Architecture
related talks
15mLoans, Accounts, and Transactions on top of Open Source Software
23mOpen Source in the world of Fintech
44mSecurity Research with Open Source Software: Vol. Omega
47m“Opening” Wall Street: Seizing The Opportunity Of Open Source In Fintech
10mOpen Source Banking
28mUnlocking Agility with Open Source: A Guide for Modern Businesses
26mBreaking New Ground in RegTech Through Open Source TechSprint Innovation
44mOpen Source in Financial Services: The Good, The Bad and the Ugly