The evolution of ACI Worldwide’s flagship retail payment engine transitioned from its legacy architecture to the current BASE24-eps platform through distinct architectural milestones.
This detailed technical timeline breaks down the development of BASE24-eps by era, tracking its underlying software stack, hardware compatibility, and primary features.
1. The Precursor Era: BASE24 “Classic” (1982 – Early 2000s)
Before the birth of BASE24-eps, the global standard for electronic payment switching relied completely on a proprietary, monolithic framework.
- Core Technology: Written primarily in TAL (Transaction Application Language) and SCOBOL.
- Database: Tandem Enscribe (hierarchical/flat file) and early non-relational structures.
- Operating Infrastructure: Tied strictly to the proprietary, fault-tolerant Tandem Computers platform (later acquired by Compaq, then HP) running Guardian OS.
- Technical Limits: Characterised by rigid, single-channel logical boundaries (e.g., separate license instances required for BASE24-atm and BASE24-pos).
2. The Genesis & “Open Systems” Era: BASE24-es / Early eps (2001 – 2006)
To capture the growing internet and mobile banking markets, ACI re-architected its core engine into an open, multi-platform system originally released as BASE24-es (Enhanced Services) before being officially rebranded to BASE24-eps (Enterprise Payment System).
- Core Technology: Complete codebase migration to object-oriented C++ and modular Java.
- Architecture Evolution: Shifted from monolithic design to an Object-Oriented Analysis and Design (OOAD) framework. Introduced the Scripting Engine allowing institutions to program custom authorization logic natively without altering core binaries.
- Platform Expansion: Severed the Tandem hardware lock. By 2003, it successfully processed transactions live across HP NonStop (Integrity), IBM zSeries mainframes (z/OS), IBM pSeries (AIX), and Sun Solaris UNIX platforms.
- Key Feature Modules: Deployed the Transaction Security Services (TSS) module to support emerging compliance mandates like Triple DES, and the Automated Key Distribution System (AKDS) for automated ATM security key refreshment.
3. The Mainframe Optimization & Standardization Era (2007 – 2013)
During this phase, ACI established BASE24-eps as its mainstream market offering, sun-setting standard maintenance for classic TAL-based BASE24 in November 2011. Development focused heavily on deeply integrating the C++ engine with IBM’s high-volume hardware architecture. [1, 2]
- Release Highlights: Major market iterations included Version 08.2 (2008), Version 09.2 (2009), and Version 11.1 (2012).
- IBM “Blue Stack” Optimization: Integrated natively with IBM CICS (Customer Information Control System) on z/OS. Utilised VSAM RLS (Virtual Storage Access Method Record Level Sharing) for configuration/data files and WebSphere MQ for transaction queuing subsystems.
- Security Integration: Hardened security by offloading cryptographic workloads onto dedicated hardware like IBM Crypto Express2 and managing identity access via RACF (Resource Access Control Facility).
- Globalized Messaging: Added extensive multi-byte character support (UTF-8/Unicode) to expand switching functionality across APAC and Middle Eastern markets.
4. The “Universal Payments” (UP) Framework Era (2014 – 2019)
As real-time rails (such as SEPA Instant and FedNow) took shape, ACI integrated BASE24-eps into its overarching Universal Payments (UP) ecosystem to process real-time, account-to-account payments.
- Architecture Evolution: Positioned BASE24-eps alongside the UP Framework (SOA-based middleware wrapper). This design allowed older classic clients to pass transactions to modern clearing houses through the UP layer without a complete “rip-and-replace” upgrade of their core engine.
- Operating Infrastructure: Broke reliance on high-cost UNIX and proprietary database systems by validating support for Red Hat Enterprise Linux (RHEL/x86_64), introducing compatibility with enterprise x86 hardware clusters running standard Oracle or IBM DB2 databases.
- Compliance: Full engineering alignment with PA-DSS (Payment Application Data Security Standard) auditing benchmarks.
5. The Modern Cloud-Native & AI Co-Processing Era (2020s – Present)
The current era centers on modernizing the underlying runtime environments to eliminate latency when executing low-overhead transaction workloads.
- Core Technology: Hybridized deployment models supporting containerized micro-peripherals alongside the heavy C++ engine.
- Cloud-Native Transition: Smooth modernization paths link legacy footprints directly to cloud-ready platforms like ACI Connetic, allowing containerized components to sit on platforms like Red Hat OpenShift.
- Low-Latency AI Scoring: Integrated directly with on-chip silicon inferencing (such as the AI accelerators on modern IBM Z microprocessors). This architecture routes incoming transaction payloads through sub-millisecond fraud models inside the live authorization loop before the 200ms processing window closes.
PROject Templates 