Tag: base24

Overview of BASE24 and XPNET plus application timeline by era

Overview of BASE24 and XPNET

BASE24 is an enterprise-grade electronic funds transfer (EFT) software suite developed by Applied Communications Inc. (now ACI Worldwide). It handles real-time transaction acquiring, authenticating, routing, switching, and authorization across ATMs, Point-of-Sale (POS) networks, and digital payment channels.

XPNET (Exchange Protocol Network) is the fundamental communications middleware layer designed explicitly for BASE24 on fault-tolerant systems. It acts as an abstraction layer managing interprocess communications (IPC), network protocols (e.g., Bisync, X.25, TCP/IP), line management, device messaging, and high-volume transaction routing. Together, they form the transactional backbone for a majority of the world’s top financial institutions.

I worked on BASE24 / BASE24-eps transaction tracking and XPNET monitoring at Insider Technologies Limited (ITL) in the early part of the millennium. See also HP NonStop Connection Journal article in 2013.

BASE24-eps extraction and ITLs RTLX in 2007
BASE24-eps extraction
and ITLs RTLX (in 2007)
RTLX Reactor (in 2012) for tracking BASE24-eps and BASE24 XPNET transactions
RTLX Reactor (in 2012) for tracking
BASE24-eps & BASE24 XPNET transactions

Deep-Dive Architecture and Technology Stack

1. BASE24 Core Design

  • Process Pair Architecture: Designed natively around Tandem’s process pairs. A Primary Process performs the active transaction switching while a Backup Process remains synchronized in a standby state. If the hardware or primary process fails, the backup takes over instantly with zero data loss or session drops.
  • Functional Modules: Divided into specific transactional entities:
    • ATM (Automated Teller Machine Device Handler): Direct control and state management of physical terminals using custom message streams (e.g., Diebold, NCR).
    • POS (Point of Sale): Merchant terminal management and merchant accounting integration.
    • Auth (Authorization Processor): Internal validation scripts against account records or stand-in limits.

2. XPNET Middleware Engine

  • Line and Station Infrastructure: XPNET maps communication through abstract configurations. A Line represents a physical or logical network pipe, and a Station represents an endpoint (e.g., an interchange gateway or terminal node).
  • Dynamic Load Buffering: Employs internal memory queue structures to absorb traffic spikes from international card networks (such as Visa and Mastercard) without spilling into disk storage.
  • Protocol Multi-threading: It decouples low-level link dynamics (e.g., CRC checking, dropouts) from core business logic, converting legacy and modern network formats into standardized internal transaction tokens.

Application Development Timeline & Political Breakdown

The timeline below details how geopolitical, regulatory, and corporate ownership developments directly shaped versioning and core code changes in BASE24 and XPNET.

Era 1: The Tandem & Expansionist Era (1975–1992)

  • Geopolitical & Industry Context: The rise of consumer credit card networks, personal checking accounts, and the physical expansion of banking via ATMs. Regional networks were fragmented, necessitating specialized software to cross-connect them.
  • Corporate Dynamics: Applied Communications Inc. (ACI) operated as an independent software house in Omaha, Nebraska, forming a deep partnership with Tandem Computers before being acquired by US West (1988) and later Tandem directly (1991).
  • Year-by-Year Code & Technical Milestones:
    • 1975–1981: Initial exploration of high-availability banking systems on Tandem NonStop computers. Developers laid the groundwork using Tandem Screen COBOL and low-level communication drivers.
    • 1982: BASE24 v1.0 officially launches. The original codebase was written in TAL (Tandem Application Language), a high-performance, structured system programming language designed specifically for NonStop systems.
    • 1985: A primitive version of XPNET is spun out from early shared-memory messaging code to support multi-protocol lines (Bisync, Async) without forcing restarts of the core application.
    • 1987: Introduction of early ISO 8583 message formatting engines within the core routing code. This allowed the software to natively interpret standard financial messaging frames across distinct interbank networks.
    • 1991: Tandem acquires ACI. Code refactoring focused heavily on optimizing interactions with Tandem’s native file system (Enscribe) and expanding the XPNET process memory layout to take advantage of new Tandem CLX architecture performance.

Era 2: The TSA Corporate & Public Market Era (1993–2000)

  • Geopolitical & Industry Context: Globalization of financial services, the consolidation of national card switches, and the commercial explosion of internet banking and POS devices.
  • Corporate Dynamics: Tandem divested ACI to a private holding company, leading to the creation of Transaction Systems Architects (TSA) in late 1993. TSA went public on NASDAQ in 1995, pushing development velocity to meet Wall Street expectations.
  • Year-by-Year Code & Technical Milestones:
    • 1993–1994: Standardized compilation routines moved to Tandem’s pTAL (portable TAL) to bridge code execution compatibility between older CISC-based architectures and the newly emerging MIPS RISC processors.
    • 1995–1996: BASE24 version 4.x introduces advanced multi-institution handling inside a single logical codebase, allowing multi-tenant processing for third-party credit card consolidators.
    • 1997: Release of BASE24 v5.x, featuring significant expansions in XPNET (v2.x) to accommodate native TCP/IP sockets alongside aging X.25 line infrastructures.
    • 1998–1999: Heavy investment into Y2K compliance remediation. Code changes involved updating binary-coded decimal (BCD) date configurations, expanding date-storage windows across Enscribe files, and deploying the BASE24 Year 2000 System Assessment frameworks globally.

Era 3: Enterprise Platform Shift & Consolidation (2001–2014)

  • Geopolitical & Industry Context: Post-9/11 regulatory changes (e.g., USA PATRIOT Act), the implementation of modern security standards like Triple DES (TDES), and the birth of the PCI-DSS (Payment Card Industry Data Security Standard). Mainframes and alternative hardware processors (IBM, HP-UX) became fierce competitors to Tandem.
  • Corporate Dynamics: TSA officially rebranded to ACI Worldwide, Inc. (ACIW) in 2007. A strategic decision was made to rewrite the platform to break vendor lock-in and provide cross-platform flexibility.
  • Year-by-Year Code & Technical Milestones:
    • 2001–2002: Standard cryptographic layers within BASE24 are systematically modified to enforce Triple DES compliance across automated teller machines.
    • 2003: ACI introduces BASE24-eps (Enterprise Payments System). This marked a foundational architecture shift, moving away from TAL/pTAL entirely to an object-oriented paradigm written in C++ and designed to execute cross-platform (HPE NonStop, IBM z/OS, AIX, Linux).
    • 2005–2006: BASE24-es/eps code integrates with enterprise middleware layers such as IBM WebSphere MQ, using CICS containers on z/OS to deliver modern service-oriented architecture (SOA) web services wrappers.
    • 2008–2010: ACI shocks the banking industry by announcing the sunsetting of standard maintenance for classic Tandem NonStop BASE24 by late 2011. Millions of lines of legacy TAL code are effectively frozen, forcing major migrations toward BASE24-eps.
    • 2011–2013: Code enhancements center around PA-DSS validation and securing encryption pathways to ensure tokenized processing. XPNET 3.x is deployed onto newer HP Integrity Itanium-based J-Series and H-Series blades.

Era 4: Modernization, Cloud-Native, and Open Systems (2015–Present)

  • Geopolitical & Industry Context: The dominance of Real-Time Payments (RTP, FedNow, ISO 20022 formats), cloud computing mandates, and aggressive cost-reduction pushes away from high-maintenance legacy hardware configurations.
  • Corporate Dynamics: ACI pivots sharply to open-ecosystem SaaS delivery, cloud partnerships (AWS, Microsoft Azure, Google Cloud), and co-development with IBM to optimize cross-platform throughput.
  • Year-by-Year Code & Technical Milestones:
    • 2015–2016: BASE24-eps code is successfully ported to Red Hat Enterprise Linux (RHEL) on standard x86 processors. This architectural pivot offered a reduction in total cost of ownership (TCO) compared to legacy hardware by providing massive processing scaling.
    • 2018–2020: The introduction of standard ISO 20022 messaging libraries into the switching matrix to support instant transaction settlement schemes globally.
    • 2021–2024: Legacy middleware systems are phased down. Modern releases feature direct REST API hooks, cloud-adaptor hooks, containerised microservices integration, and extended configuration capabilities via the ACI Desktop GUI.
    • 2025–2026: ACI partners with IBM to launch native 64-bit deployment optimizations for BASE24-eps running on IBM Z mainframes (including z16/z17 configurations), incorporating hardware-driven AI fraud analysis models and full PCI-SSF (PCI 4.0) certification.

Overview of BASE24 and XPNET plus application timeline by era

BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview

BASE24 is a market-leading, fault-tolerant Electronic Funds Transfer (EFT) software application developed by ACI Worldwide. For decades, it has served as the backbone for global banking, processing billions of ATM, Point of Sale (POS), and smart card transactions.

BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview

The product achieves its landmark 24/7/365 uptime by running natively on the HPE NonStop architecture—originally engineered by Tandem Computers.

1. Underlying Technology Stack

BASE24 Classic was built from the ground up to utilize the unique properties of the Tandem/HPE NonStop platform:

  • Operating System: HPE NonStop Kernel (NSK) / Guardian.
  • Database: Enscribe, a native hierarchical/flat file database optimized for ultra-fast, unstructured file access. Newer iterations use NonStop SQL/MX.
  • Programming Languages: Primarily TAL (Tandem Application Language), pTAL, and COBOL/SCOBOL.
  • Middleware: PATHWAY (PATHCOM), which acts as the transaction processing monitor to dynamically manage and load-balance server processes.

2. High-Level Component Architecture

BASE24 relies on an interconnected network of specialized processes that route and manage messages.

A. XPNET (The Networking Engine)

XPNET is a critical, proprietary communication subsystem. It provides the messaging infrastructure where applications interface with network communication lines. XPNET acts as the buffer layer, monitoring physical lines, enforcing transaction timing checks, and distributing data loads uniformly across CPUs.

B. Device Handlers (DH)

Device Handlers act as the translators for peripheral devices.

  • Function: They intercept hardware-specific protocol messages (e.g., Diebold or NCR formats from ATMs) and normalize them into BASE24’s internal standard message format.
  • Security: DH processes handle terminal-level PIN encryption, coordinate MAC (Message Authentication Code) keys, and initiate terminal downline loads.

C. Authorization Process (AUTH)

AUTH is the core decision engine of the application.

  • Function: It validates card restrictions, tracks card usage accumulations, and performs transaction risk checks.
  • Fallback Management: If a bank’s core system goes offline, AUTH drops into “Stand-Alone” or “Negative/Parametric Authorization” mode, approving transactions locally up to safe, pre-defined limits.

D. Host Interfaces (HI)

The Host Interface connects BASE24 to the financial institution’s primary backend core banking systems. It handles “On-Us” transactions—meaning the card used belongs to the bank owning the terminal.

E. Interchange Interfaces (II)

The Interchange Interface formats, translates, and routes transactions to global credit/debit networks (such as Visa, Mastercard, AMEX) or regional switches. It transforms internal BASE24 data formats into compliance standard formatting, such as ISO 8583. It handles “Not-On-Us” transactions.

3. Core Database & File Structure

BASE24 captures system activities across specialized transactional and tracking files, mostly utilizing Enscribe:

  • TLF (Transaction Log File): The primary log capturing every ATM event, amount, response code, and terminal ID in real-time.
  • PTLF (POS Transaction Log File): Mirrors the utility of the TLF, but optimizes records strictly for merchant POS transactions.
  • LCONF (Logical Network Configuration File): Dictates how network configurations, devices, institutions, and communication paths map into XPNET.
  • CAF (Cardholder Authorization File): Stores specific card numbers, limits, and statuses used for stand-alone authorization if host links break down.

4. Daily Operational Processes

Beyond live message switching, BASE24 executes several critical back-office operations:

  • Extract: Periodically filters transaction data from live TLF/PTLF logs to move to external billing arrays.
  • Refresh: Downloads updated data dumps (such as blacklisted cards or updated balances) from core hosts into local BASE24 database files.
  • Settlement Initiator: Aggregates transaction volumes at specified cutoff times to reconcile balanced records between ATMs, POS terminals, and clearing networks.

5. Why Tandem/HPE NonStop is Essential to BASE24

BASE24 relies on the hardware/software synergy provided by HPE NonStop to achieve near-zero downtime:

  • Shared-Nothing Architecture: Processors operate independently with their own memory stacks. If a physical CPU suffers hardware failure, it cannot corrupt the rest of the application.
  • Process Pairs: BASE24 components operate via a primary process in one CPU and a backup process in an alternate CPU. The primary constantly syncs checkpoint data with its backup. If the primary drops, the backup assumes processing instantly without interrupting transaction flights.
  • Active/Active Configuration: Utilizing replication software like HPE Shadowbase or DRNet, financial firms link distinct geographic NonStop locations. Both processing sites operate concurrently, managing localized transactions and replicating states reciprocally.

6. Product Evolution: BASE24 Classic vs. BASE24-eps

ACI Worldwide evolved the platform from BASE24 Classic into BASE24-eps (Enterprise Payment System):

Product Evolution: BASE24 Classic vs. BASE24-eps
Product Evolution: BASE24 Classic vs. BASE24-eps

BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview

2. BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview

European BASE24 User Group (EBUG) was a prominent, community-led organization

The European BASE24 User Group (EBUG) was a prominent, community-led organization dedicated to the ACI BASE24 payment processing system. It provided a vendor-neutral forum for IT professionals, banks, and processors to collaborate, share knowledge, and discuss technical tracks like HPE NonStop monitoring and payment security.

Conference Timeline

  • 1980s — Establishment: EBUG is formed as a regional community for European financial institutions utilizing the growing BASE24 platform.
  • Early 2000s — Technical Growth: EBUG annual conferences become prominent technical forums featuring specialized tracks focused on Tandem/HP NonStop hardware and payment system security.
  • 2007 — Istanbul Conference: Features heavily attended technical sessions and workshops addressing growing transaction volumes and early EMV (chip card) migrations.
European BASE24 User Group (EBUG) was a prominent, community-led organization
Insider Technologies regularly attended EBUG, booth in 2007
  • 2008 — Vienna Conference: Notable for introducing ACI’s strategic shift to support IBM platforms alongside traditional HPE NonStop environments.
European BASE24 User Group (EBUG) was a prominent, community-led organization
HP booth at Vienna EBUG, 2008
  • 2009 — Prague Conference: Continues strong advocacy and technical troubleshooting for BASE24 on NonStop despite broader industry platform shifts.
European BASE24 User Group (EBUG) was a prominent, community-led organization
HP Booth at Prague conference, 2009
  • 2012 — London TFG: A technical focus group is held in London at Trinity House, bringing together engineers and ACI product managers to debug and refine system architecture.
  • Late 2010s to Present — The “Everybody Belongs” Era: As ACI broadened its product portfolio, the user group expands its scope to include other payment technologies like Postilion. The conference formally rebrands as an independent entity, later transitioning into The Payments Knowledge Forum, to serve all payment systems users inclusively.

European BASE24 User Group (EBUG) was a prominent, community-led organization

BASE24 and BASE24-eps architecture overview

The BASE24 electronic payment system developed by ACI Worldwide exists in two primary architectural generations:

BASE24 Classic (historically deployed on HPE NonStop / Tandem fault-tolerant hardware) and

BASE24-eps (Enterprise Payments System, built using an object-oriented C++ framework deployable across open systems, z/OS, and cloud infrastructure).

Despite structural differences, both share a highly optimized, component-based transaction routing engine.

BASE24 and BASE24-eps architecture overview
BASE24 architecture overview

Core Structural Component Layers

The component architecture maps the complete end-to-end lifecycle of a financial message (such as ISO 8583) through five distinct functional sub-systems:

1. Network & Message Routing Component (XPNET)

  • Purpose: Coordinates all message traffic across internal processes and physical network nodes.
  • Function: Operates as a specialized middleware network manager that decouples low-level communication links from upper transaction routing layers.
  • Configuration: Relies on a Logical Network Configuration File (LCONF) to define active execution nodes, hardware lines, and physical stations.

2. Perimeter Access Layer (Device Handlers)

  • Purpose: Translates device-specific message protocol formats into the system’s unified internal format.
  • ATM Device Handlers (ATMDH): Manage direct connectivity to automated teller machines, unpack specific vendor dialects (such as Diebold or NCR states), and track terminal hardware statuses.
  • POS Device Handlers (POSDH): Interface with point-of-sale acquirer terminals and merchants.
  • Security Operations: Triggers immediate payload encryption/decryption and Hardware Security Module (HSM) PIN-block translation directly within this ingestion ring.

3. Core Transaction Logic (Authorization System)

  • Purpose: Determines whether a payment request should be accepted, rejected, or modified.
  • Full On-Us Authorization: Inspects internal databases for matching account records, positive balances, and velocity thresholds to issue real-time decisions.
  • Parametric/Negative Checks: Validates card status against offline negative files, usage restrictions, or custom risk parameters.
  • Scripting Engine: Modern BASE24-eps variants execute localized transaction routing scripts via customized operators without forcing a compile rewrite of the core engine core.

4. Boundary Channels (Interchange & Host Interfaces)

  • Interchange Interfaces (ICH): Package and transform the transaction payload into international network profiles (e.g., Visa, Mastercard, regional switches). It handles strict message mapping and regional network check requirements.
  • Host Interfaces (HIF): Create synchronous links back to an institution’s underlying Core Banking system to apply ledger adjustments, check balances, or execute real-time holds.

5. Offline & Administrative Subsystems

  • Extract Component: Gathers active transaction logs and streams filtered payloads out to analytical reporting databases.
  • Refresh Component: Updates terminal operational data, key packages, and card exclusion lists from parent systems down to active execution nodes.
  • Settlement Initiator: Groups, cleanses, and batches net-clearing totals to finalize payment entries into regional clearinghouses.

Architectural Divergence: Classic vs. EPS

The structural design varies significantly depending on the generation of the software deployment:

BASE24 and BASE24-eps architecture overview
BASE24 and BASE24-eps architecture overview

End-to-End Component Transaction Flow

  1. An ATM transaction arrives at the network interface layer managed by XPNET.
  2. The message is routed to the Device Handler, which strips hardware packaging and requests translation from the HSM.
  3. The clean internal message passes to the Authorization Engine.
  4. If it is a “Not-On-Us” card, the engine identifies the destination BIN and transfers routing control to the Interchange Interface.
  5. The Interchange Interface maps the payload to the external scheme standard (such as Visa) and transmits it to the external network.
  6. The outbound network response is unwrapped by the Interchange component and tracked through the core engine to log final response codes.
  7. The transaction safely records inside the active log file, allowing the Extract / Settlement components to pick it up later during batch processing.

BASE24 and BASE24-eps architecture overview

BASE24 and BASE24-eps architecture overview
BASE24 and BASE24-eps architecture overview

BASE24 Overview and Historical Timeline

BASE24 is a foundational electronic payments software suite developed by ACI Worldwide, first launched in 1982 to provide “always-on” (24/7/365) transaction processing, primarily on HP NonStop servers.

It is used by large financial institutions to acquire, authenticate, route, switch, and authorize card- and non-card-based financial transactions across multiple channels, including ATMs, point-of-sale (POS) terminals, and mobile/internet banking. 

The product has evolved from “Base24 Classic” into BASE24-eps (formerly BASE24-es), a modern, object-oriented, platform-independent payments engine designed to support high-volume, real-time transaction processing in hybrid or cloud-based environments. 

Comprehensive Historical Timeline of BASE24 

  • The Foundation Era (1975–1981): ACI (Applied Communications, Inc.) was founded in Omaha, Nebraska, in 1975, initially developing software for fault-tolerant Tandem NonStop computers. The focus was on connecting the first wave of ATMs to bank systems.
  • The Launch and Global Expansion (1982–1990):
    • 1982: BASE24 product family is officially launched, serving as the “baseline” software for 24-hour operations.
    • 1986: By 1986, ACI has 131 customers in 14 countries, expanding globally.
    • 1987: ACI receives the U.S. President’s “E” Award for Excellence in Export.
  • Public Company and Modernization (1995–2000):
    • 1995: ACI becomes a public company.
    • 1997: Adopts the name ACI Worldwide.
    • 1996–2000: Initial expansion of support to platforms beyond Tandem, including IBM mainframes and UNIX, to support rising internet commerce.
  • The Transition to Open Systems: BASE24-eps (2001–2010):
    • Early 2000s: Introduction of BASE24-es (later renamed BASE24-eps), a Next-Gen, C++ based engine.
    • 2003: BASE24-eps is live on HP NonStop, IBM zSeries, and IBM pSeries/Sun Solaris.
    • 2006: ACI announces a version of BASE24-es to support UK Faster Payments.
    • 2008–2010: ACI moves toward a unified strategy, with BASE24-eps becoming the mainstream offering while Classic matured.
  • Modernization and Cloud Era (2011–Present):
    • 2011: BASE24-eps wins the Most Innovative Financial Product Award.
    • 2015: ACI celebrates 40 years of operation and introduces advanced fraud detection (Proactive Risk Manager) integrated with BASE24-eps.
    • 2023: ACI goes live as an early adopter of the Federal Reserve’s FedNow Service, using modernized BASE24-eps technology.
    • 2024–2025: BASE24-eps becomes fully PCI-SSF compliant (PCI 4.0), running on Red Hat Enterprise Linux and supporting hybrid cloud deployments. 

Key Features of BASE24-eps

  • Fault Tolerance: Designed for high availability with near-zero downtime.
  • Multi-Channel Support: Manages ATM (NCR, Diebold Nixdorf), POS, and Mobile/Web traffic in a single engine.
  • Scripting Engine: Uses JavaScript-like scripts to allow customers to define authorization logic without modifying the core system.
  • Universal Connectivity: Supports 40+ global and regional network interfaces (Visa, Mastercard, etc.).
  • Platform Independence: Runs on HPE NonStop, IBM z/OS (CICS), and Linux/x86_64.
  • Real-time Fraud Prevention: Integrated with ACI Proactive Risk Manager. 

BASE24 Classic vs. BASE24-eps

  • Classic: Monolithic, Tandem-dependent, older technology.
  • eps: Object-oriented (C++), open systems architecture, 30% faster processing, supports cloud-native approaches. 

BASE24 Overview and Historical Timeline

BASE24 by ACI Worldwide timeline by era and year

BASE24 is the world’s most widely used payment processing platform, developed by ACI Worldwide. Originally designed for ATM networks, it evolved into a comprehensive system for acquiring, authenticating, and routing card-based and digital transactions across various channels. It is known for its high-performance, fault-tolerant architecture, processing nearly 50% of the world’s electronic transactions at its peak. 

Comprehensive Timeline by Era

Era 1: Foundations & The Rise of BASE24 Classic (1975–1990s)

This era focused on high-availability software for the emerging automated banking industry, specifically for Tandem NonStop servers. 

  • 1975: ACI founded in Omaha, Nebraska, to develop software for the new “NonStop” server computers used by banks and stock exchanges.
  • 1981: Secured its first international client, an Australian bank, marking the start of global expansion.
  • 1982: Launch of BASE24, the first global product designed for 24-hour system operations, originally focused on ATM networks.
  • 1986: Rapid growth led to 131 customers across 14 different countries. 

Era 2: Expansion & Public Transition (1995–2000s) 

The platform expanded into Point of Sale (POS) and branch systems while the company underwent major structural changes. 

  • 1995: The company went public on NASDAQ as Transaction Systems Architects (TSA).
  • 1997: Officially adopted the name ACI Worldwide.
  • Early 2000s: Introduction of BASE24-es (later renamed BASE24-eps), a next-generation platform using C++ and object-based architecture to replace the legacy monolithic design. 

Era 3: Modernisation & The “eps” Shift (2005–2015)

ACI shifted focus toward BASE24-eps, a more flexible, open-architecture version designed for multi-channel transaction processing. 

  • 2005: ACI launches BASE24-eps, featuring a modular engine capable of processing approximately 2,000 transactions per second (TPS) with extremely low latency.
  • 2007: TSA officially rebranded all operations under the ACI Worldwide, Inc. (ACIW) name.
  • 2008: Announced that BASE24 Classic would begin maturing in 2011, urging customers to migrate to the eps platform for better integration with modern systems like IBM System z.
  • 2011–2012: Release of BASE24-eps 11.1, adding support for DB2 on IBM System p, enhanced EMV acquiring, and tools for easier migration from legacy BASE24. 

Era 4: Cloud & Universal Payments (2015–Present)

The platform moved toward cloud-native capabilities and broader ecosystem integration. 

  • 2015: ACI celebrated its 40th anniversary, continuing to power electronic payments for over 6,000 organisations worldwide.
  • 2018: Introduction of UP BASE24-eps on Linux in the Cloud, demonstrating significantly reduced Total Cost of Ownership (TCO) through public and private cloud deployment.
  • Present: BASE24 remains a core pillar of ACI’s portfolio, supporting traditional card, ATM, mobile commerce, and internet banking transactions.

BASE24-eps by ACI Worldwide timeline by era and year

BASE24-eps is a modular, high-availability payment processing engine developed by ACI Worldwide. It evolved from the original “BASE24 Classic” to provide a more flexible, open-system architecture for acquiring, authenticating, routing, and authorizing electronic transactions. 

Base24-eps Overview

  • Architecture: Unlike the TAL-based Classic version, BASE24-eps uses an object-oriented design written primarily in C++ and Java.
  • Key Features:

Detailed Timeline

The Foundation Era (1970s – 1990s)

  • 1975: ACI is founded in Omaha, Nebraska, initially developing software for NonStop server computers.
  • Late 1970s: Development of the original BASE24 (now known as “Classic”), focused on high-uptime ATM processing.
  • 1981: First international customer (an Australian bank) signs on, starting the global expansion of BASE24. 

Transition & Development Era (2000 – 2005)

  • Early 2000s: ACI begins developing the “next generation” platform, initially called BASE24-es (extended systems), which later becomes BASE24-eps (enterprise payment system).
  • 2003 – 2004: The product begins migrating to open architectures, moving away from platform-specific languages. 

Mainstream Adoption Era (2006 – 2013)

  • 2007: ACI highlights BASE24-eps as its strategic future platform in investor overviews.
  • 2008: ACI announces the maturation of BASE24 Classic (ending standard maintenance in 2011), urging customers to migrate to BASE24-eps.
  • 2009: IBM Redbooks releases technical guides for BASE24-eps 08.2 on z/OS, solidifying its place in enterprise banking.
  • 2013: Release of BASE24-eps 2.0, introducing the “customer component” and enhanced service-enabling wrappers. 

Modernization & Cloud Era (2014 – Present)

BASE24 and core Networking Component XPNET timeline

The technical timeline for BASE24 and its core networking component, XPNET, reflects the evolution of high-availability payment switching on HP NonStop (Tandem) systems.

Technical Evolution Timeline

  • 1980s: The Foundation
    • BASE24 Release: Originally developed by Applied Communications Inc. (now ACI Worldwide), BASE24 was built for the Tandem Guardian operating system.
    • XPNET Introduction: Developed as the Message-Oriented Middleware (MOM) to handle all transaction routing and communications. It introduced a multi-node architecture allowing different “satellite” processes (ATM, POS, Host) to communicate.
  • 1990s: Scale and Maturity
    • Classic Era: BASE24 “Classic” became the industry standard for ATM and POS switching.
    • XPNET 3.x: Enhanced to support larger networks and more complex auditing through NCPCOM.
    • Language & DB: The system relied on TAL (Tandem Application Language), COBOL, and the Enscribe database.
  • 2000s: The Shift to BASE24-eps
    • 2003–2005: ACI introduced BASE24-eps (Electronic Payment Systems). This was a re-architecture using C++ and Java to provide platform independence.
    • XPNET 4.1: Released to support the transition, adding features like Common Transport Subsystem (CTS) for better Pathway integration and support for external processes.
    • z/OS Support: By 2009, BASE24-eps was fully ported to IBM z/OS using CICS and VSAM.
  • 2010s – Present: Modernisation & Cloud
    • 2014–2017: Continued updates to BASE24 Classic R6.0, maintaining its relevance for legacy users.
    • Cloud Enablement: Recent versions of BASE24-eps focus on REST API integration via tools like LightWave, allowing legacy XPNET paths to be exposed as web services.
    • Active/Active Environments: Modern implementations focus on “continuous availability” using GoldenGate for data replication between sites. 

Key Technical Components

  • NMM (Network Management Module): The core process of XPNET that manages the configuration of lines, stations, and links.
  • LCONF: The Logical Network Configuration File used by XPNET to define how messages route between processes.
  • Auditing: XPNET provides the primary transaction auditing mechanism, which is still utilized by both Classic and eps versions.

BASE24 and core Networking Component XPNET

Base24-eps and UPF integration

Base24-eps and UPF integration

Integration between BASE24-eps and the Universal Payments Framework (UPF) is a core part of ACI Worldwide’s strategy to bridge legacy payment systems with modern, real-time payment capabilities. The UP Framework acts as a bridge, allowing financial institutions to orchestrate diverse payment types and channels while protecting their existing investment in BASE24-eps infrastructure. 

Key Aspects of the Integration

  • Investment Protection: The UP Framework allows existing BASE24 customers to continue using their current systems for some functions while incrementally adding new payment types and volumes through the UP Framework. This approach eliminates the need for a complete “rip and replace” of legacy systems.
  • Modernization and Flexibility: The integration with UPF allows banks to rapidly introduce new payment methods, adhere to new network schemes (like real-time payments), and integrate with new partners through configuration rather than custom coding.
  • Unified Retail Payments: UP Retail Payments is ACI’s comprehensive solution that combines the strengths of BASE24-eps (a market-leading retail payment platform) and the UP Framework (which orchestrates all aspects of payments processing) into a single, end-to-end platform.
  • Data Protection & Compliance: The UPF is used in conjunction with data security solutions (like Comforte’s SecurDPS) to tokenize sensitive cardholder data before it is passed to BASE24-eps applications or stored in logs, helping institutions meet PCI DSS compliance requirements.
  • Role-Based Expertise: The integration is an area of specialized technical expertise in the payment industry, with job roles focusing on the implementation, customization, configuration, and support of both BASE24-eps and UPF modules. 

In essence, the UPF provides a flexible, open architecture that extends the life and capabilities of BASE24-eps, enabling financial institutions to manage traditional and emerging payment demands within a unified ecosystem. 

What is BASE24-eps?

BASE24-eps is a comprehensive solution for acquiring, authenticating, routing, switching, and authorizing card- and non-card-based financial transactions through various channels.

BASE24-eps is designed to:

  • Increase the profitability of payment processing by enabling a set of common transaction services to support multiple channels and different types of transactions
  • Offer organizations greater flexibility with built-in support for all major card types, devices, national and regional switches, international payment schemes and host systems
  • Create a comprehensive view of customers and ensure consistent, high-quality customer service across different points of contact
  • Reduce organizations’ total cost of ownership through complete platform independence
  • Give organizations the options to deploy on premise, in their own private or public cloud, or in a secure, cloud-based environment managed by ACI

https://www.aciworldwide.com/solutions/base24-eps

In 2013, delivered a large transaction tracking project at a retail bank in Riyadh

Retail Banking (off-shore) – in 2013, delivered a large transaction tracking project at a retail bank in Riyadh (Saudi Arabia). This involved the BASE24 Classic payment solution and the relay and optimised parsing of multiple Terabytes of tape archived POS & ATM transaction logs to a new monitoring and reporting system. Project managed the work and delivery both in Salford Quays, Manchester and locally at the bank in Riyadh.

mark whitfield wordpress_connection_HP_NonStop_to_Windows_Combined
RTLX_White_Paper+Download

( now C-Deep [Transaction Monitoring] https://etinet.com/products/c-deep-transaction-monitoring/ )