ACH Payments
Project Synopsis

The ACH Project was initiated to securely collect customers' ACH information when not already on record. The primary objective was to identify gaps in our database and prompt customers to provide their information via a portal, through a secure link sent via email. This information would then be securely stored alongside their existing records.

However, what seemed like a straightforward endeavor posed numerous challenges when we encountered compatibility issues among our systems. These complexities stemmed from version discrepancies, where certain tools were running outdated versions that couldn't be easily updated due to licensing constraints and compatibility issues with other systems. To overcome these obstacles and achieve our goals, innovative thinking was crucial.

My Role and Responsibilities

I collaborated closely with our Database Administrator to address these compatibility issues from the outset. We invested time investigating the root causes, which were not documented in the known tool specifications. Initially, upgrading to a newer software version seemed plausible, and my role expanded to include data formatting and tool navigation support.

Yet, it became apparent that a simple software upgrade wasn't feasible. It necessitated costly license updates and extensive data refactoring across the organization, which didn't align with our timelines and budget constraints. Instead, I proposed leveraging PHP as an intermediary between the software components.

I implemented new API endpoints within the API framework I had developed, enabling seamless data exchange between incompatible tools. This approach shifted much of the complexity into PHP, circumventing the inherent limitations of the software tools.

Moreover, this solution addressed additional project requirements. Utilizing PHP and APIs, I orchestrated an email notification system featuring uniquely coded links that directed users to the ACH information input page, also powered by PHP. Subsequently, securely captured information was transmitted back to the appropriate systems for storage.

Overall, this project presented unique challenges that allowed me to expand upon the API infrastructure I had built. It was a stimulating experience to ensure secure data transactions across diverse systems, involving extensive research into encryption and security as well as implementation efforts.

Prior to integrating the PHP/API components, managing ACH information relied heavily on manual inputs across multiple systems, often complicated by vendor data retrieval challenges. The new system significantly reduced errors and garnered positive feedback from our vendors.

Key Technologies Utilized
  • PHP 5 - 8.3
  • TinyButStrong
  • HTML5
  • CSS3
  • Jquery
  • Javascript
  • Ajax
  • XML
  • Json
  • Apache
  • Internal API
  • Curl
Internal Api
Unified Customers