MIFOS / Metalloid Capital
A permission-aware loan operations platform that turns Mifos/Fineract records into actionable collections, communication, reporting, and data-exchange workflows.
- My role
- Full-stack developer · Laravel APIs, Vue operations UI, lending workflows, access control, reporting, integrations, and technical documentation
- Technology
- Laravel
- Vue.js
- MySQL
- Mifos/Fineract
- Redis
- Laravel Sanctum
- PrimeVue
- SFTP
01
The problem
Core lending records lived in Mifos/Fineract, but collections teams needed a focused operational layer for monitoring arrears, documenting follow-ups, assigning responsibility, escalating difficult accounts, communicating with borrowers and guarantors, and preparing partner or credit-reporting files. The challenge was to support those workflows without creating a second financial system of record or weakening access boundaries around sensitive loan data.
02
Architecture and decisions
I worked within a two-application architecture: a Vue 3 and PrimeVue SPA for the staff workspace, backed by a Laravel 10 API and relational operational store. Mifos/Fineract remains authoritative for clients, loans, installments, payments, charges, and accounting; the local application owns assignments, follow-ups, notification state, dashboard materialization, batch metadata, and support workflows. Sanctum bearer tokens, roles, permissions, work-status checks, and assignment-based scoping protect the API. Scheduled Laravel processes coordinate synchronization, reminders, notices, reports, and file delivery, while Redis supports selected cache and mailbox indexes and SFTP boundaries isolate CBS/EveryData and CRIF exchanges.
03
Key features
- Synchronized and live views of clients, loans, installments, transactions, balances, documents, and loan history
- Delinquency monitoring with arrears visibility, follow-up records, next-follow-up reminders, attachments, and combined timelines
- Permission-aware officer assignment plus approval-based escalation to attorneys and external collection teams
- Template-driven client, guarantor, and officer notifications with generated notices, statements, and collection documents
- Snapshot-based CBS/EveryData and CRIF submission workflows with validation, packaging, metadata, and SFTP handoff
- Operational dashboards, exception and collection reports, unified mailbox communication, activity history, and an error-support toolbox
04
Outcomes
- 01
Established a clear ownership boundary between authoritative Mifos financial records and the platform’s local operational workflow state.
- 02
Unified 7 operational concerns—portfolio monitoring, follow-ups, assignments, escalations, communications, reporting, and data exchange—in one permission-aware workspace.
- 03
Coordinated 5 integration surfaces—Mifos/Fineract, Redis, Zoho mail, CBS/EveryData, and CRIF—through explicit API, mailbox, cache, and SFTP boundaries.
Metrics are included only where they were measured or documented.
Inside the product
Interface highlights






