SmartPay
The chief drivers of the modernized SmartPay system are to move away from their licensed Sybase data repository and use cloud-based, less expensive, and managed alternatives. The initial design was essentially an S3 data lake but that migrated to include Redshift as the primary data repository because of its ACID properties and the need to update the data store routinely. One of the more important concerns, especially in the beginning, was around securely handling and storing Payment Card Industry (PCI) data but that concern subsided when the data scope was limited to the new (SP3) data specification which did not contain PCI data.
Business and Requirements Overview
A high-level explanation of the business functions and users that SmartPay serves and what the core requirements are for the system's future state.
Read Overview
System Architecture
A breakdown of the architectural components involved in the SmartPay Data Warehouse.
System Architecture
Technical Approach
The approach to the SmartPay Modernization, including how the system partnered with FCS to bring added value to their user community.
Technical Approach