Operations as a product
Transaction monitoring and case management were designed as a dedicated system with explicit workflows instead of a collection of administrative endpoints.
05
Casha Fintech
Consumer finance backed by traceable operational systems
TypeScriptRBACOpenAPIMobile
Overview
Casha is a global-finance application for spending, investing, understanding where money goes, and sending funds across borders with rates and fees visible before confirmation. My work at Casha Technologies connected that customer experience to the secure operational systems, integrations, and internal controls behind it.
Move and grow money,
across borders.
My role at Casha Technologies
Senior Fullstack Engineer
June—October 2026
Abuja, Nigeria
I worked across the systems customers see and the controls they depend on.
- 01
Built and shipped version one of Casha’s Transaction Management System for transaction monitoring, risk, and case management.
- 02
Led backend development of the next-generation TMS, including fine-grained roles and permissions, audit logging, authentication security, and complete API documentation.
- 03
Designed KYC remediation for legacy NGN customers, preserving account access while safely gating sensitive operations until verification was complete.
- 04
Integrated endpoints in the mobile app, resolved critical login and crash issues, and delivered TestFlight builds for internal testing.
- 05
Supported partner Microfinance Bank integrations for local bank-to-bank transfers alongside the senior lead engineer.
- 06
Built and shipped the responsive Casha company website with interactive product showcases and cross-device app-store journeys.
01 / Challenge
The conditions that shaped the system.
A useful architecture begins with the real constraint.
A simple money movement experience depends on complex operational safeguards. Transaction monitoring, legacy-customer KYC gaps, staff permissions, auditability, partner-bank integrations, mobile stability, and public product communication all had to evolve together inside a lean engineering team.
02 / System map
From input to outcome
01Customer & operations
→02Web and mobile clients
→03Typed APIs
→04KYC & RBAC controls
→05Partner MFBs
→06Monitoring & audit trail
03 / Approach
How the build was organised.
Make the boundaries clear, then move.
- 01
Built and shipped version one of the Transaction Management System for internal monitoring, risk review, and case management, then led backend development of its next generation.
- 02
Designed legacy-customer KYC remediation that preserved account access while gating transfers, withdrawals, and mandates until BVN and email requirements were complete.
- 03
Worked vertically across backend, web, DevOps, and mobile: integrating partner banks, resolving login and crash issues, shipping TestFlight builds, and delivering Casha’s responsive product website.
Decisions that carried the product.
Progressive KYC controls
Existing customers retained appropriate access while sensitive operations remained gated until required identity checks were completed.
Security in the platform
Fine-grained permissions, audit logging, password recovery, failed-login lockouts, and documented API contracts made control part of the system itself.
What changed after the work.
- ↗Shipped the first Casha Transaction Management System and established the architecture for its next generation.
- ↗Delivered KYC-remediation, role-based controls, audit trails, account-security features, and complete Swagger/OpenAPI documentation.
- ↗Improved mobile reliability, supported partner-MFB transfer integration, and shipped Casha’s new responsive company website.
