Skip to content
Developing a Custom Money Services Business Platform
Orchestrating Architecture, Business Processes, Integration, and UI
Customer Snapshot
- Money Services Provider
- Startup
Solution Snapshot
- Business platform
- Batch processing
- High availability
- Scalable
- Multiple third-party integration points
Skills Needed
- ANT
- Eclipse
- HTML/CSS
- IVY
- Java
- JavaScript
- Jenkins
- JQuery
- JSPs
- Spring Framework
- SQLServer
- SVN
- Version One
Key Differentiators
- Brazilian Offshore capability
- Multi-location team
- Scrum Methodology and Project Management
- Established Java Coding Standards, Tools, Architecture, Training, Best Practices, and Processes
The client wanted to offer money transfer services for unbanked users that transferred funds to chosen destinations via one or more intermediaries. The users needed to be able to choose how often they would send money and to whom automatically on a recurring basis.
They needed a custom money services application developed with the following key requirements:
- User enrollment and management
- Pricing profiles
- Transfer settings
- Authentication / Authorization
- Batch generation and management of the money transfers
- SDN match processing
- Currency purchase
- Transfer Network consumer interface for the ACH interface
- Reporting integration including compliance and SAR reports
- IVR integration
- ACH integration
- Security
- International calling capabilities
- Integration with intermediaries’ systems
QAT Global’s Approach
The QAT Global Scrum development process was used to plan, define requirements, develop and integrate using the QAT WebDaptive and QAT JDaptive architecture frameworks. A team of 15 developers, analysts, and architects from QAT Global worked with the client to refine the requirements, streamline business processes, create the user interface, and develop the software.
The custom money services project was designed to be completed in two phases with the initial phase being a minimum viable product (MVP). The MVP included the initial requirements are listed above. After the initial production MVP rollout, the second phase with extensive additional requirements was planned. The MVP was completed in approximately one year from conception to requirements gathering to testing.
