The problem
Banks and credit unions were running core processing on systems that were hard to customize and tied officers to a single desktop workflow — every change request meant a development cycle, and day-to-day account and transaction management wasn’t accessible from the field.
One platform, two markets
The same core processing platform shipped under two names:
- CoreSoft Core Processing — for the US market, serving credit unions such as Corporate America Credit Union.
- Wings — for the Indian market, serving cooperative banks including Shri Arihant Co-op. Bank and Vikas Souharda Co-Operative Bank, among others.
Both share the architecture and UI described below, adapted to each market’s institutions.
My role
Owned the application architecture and led the team building it — assigning work, enforcing development standards, and building the automated monitoring and reporting that kept day-to-day operations visible to the client institutions.
Approach
Built Wings as a device-agnostic core processing suite — the same interface working across desktop, tablet, and smartphone — with a role-based access control layer so officers only see what their role permits, a unified search and management view over member details and transactions, and automated reporting for financial statements, statutory forms, and audit logs that previously had to be assembled by hand.
The platform handles real-time, high-volume transactions across multiple channels, is highly customizable — many changes take a few clicks rather than a development cycle — and integrates with each institution’s own security solutions.
Outcome
Gave banks and credit unions back the operational time previously spent on manual reporting and desk-bound workflows — replacing report generation that used to take a dedicated back-office effort with an automated pipeline built into the platform.