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

sp/ARCHITECT-BANK originally developed by The Software Partnership (TSP), Runcorn, Cheshire

The Software Partnership Logo

The core electronic banking software product sp/ARCHITECT-BANK was originally developed by The Software Partnership (TSP), a highly specialized British software house co-founded by Nigel Walsh in Runcorn, Cheshire.

Engineered to deliver high-availability, fault-tolerant electronic and desktop home-banking services, it ran natively on Tandem NonStop mainframe computers (now HPE NonStop).

The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire

Over the decades, the product evolved through major corporate acquisitions, eventually being integrated into enterprise-level banking suites like CONNEX Advantage under eFunds and FIS.

The detailed timeline of the product, broken down by corporate era and year, is provided below by Mark Whitfield.

Click the previous link for more sp/ARCHITECT BANK project level detail between 1990 thru 1995.

Also, here is a LinkedIn group for the company Alumni.

🌅 Era 1: The Inception and Independent Software House Era (Mid-1980s–1993)

During this foundational era, The Software Partnership engineered the core product from scratch to meet the emerging demand for “Direct Electronic Banking” before the commercial internet became prevalent.

1985: The Software Partnership (TSP) is co-founded by Nigel Walsh in Runcorn, Cheshire. Development begins on a standard product architecture designed specifically for the transaction processing monitor (PATHWAY) and operating system (Guardian) of Tandem Computers.
1988–1989: The company establishes sp/ARCHITECT (and its core module, sp/ARCHITECT-BANK) as a premier client-server base package for corporate and home-office electronic banking.
1990: The engineering team scales up to build standard product releases written in COBOL85 and utilizing NonStop SQL databases. They develop proprietary testing utilities like sp/TESTBED to simulate PC-to-mainframe interfaces. Mark Whitfield joins the company after graduating in Computing in late 1990.
1991: Major deployment begins for the high-profile Barclays Business Master II (BBM II) desktop corporate banking application, with TSP placing teams (including Mark Whitfield) on-site at Barclays in Knutsford, Cheshire.

Barclays, Radbroke Hall, Knutsford, Cheshire

1992: A batch billing and invoicing suite of modules is engineered over 3-months and appended to the Barclays installation at Poole, Dorset. Mark Whitfield is assigned to this HPE NonStop (Tandem) billing/ invoicing development on the UK south coast. Simultaneously, TSP expands internationally into continental Europe.

1993: TSP develops an automated, touch-tone voice menu system for Girofon (Denmark). The code interfaces phone lines through Periphonics Interactive Voice Response (IVR) hardware directly into the back-end Tandem banking system. Concurrently, the core application handles desktop money transfers and early logic checking for clearing giants TSB and Bank of Scotland. Mark Whitfield is also involved with supporting this IVR technology.

🤝 Era 2: The Deluxe Data International Era (1994–1999)

Recognizing the massive European banking client footprints of sp/ARCHITECT, US-based electronic funds transfer (EFT) specialist Deluxe Data acquired TSP to merge their direct banking and card processing capabilities.

1994: Deluxe Data Corporation acquires The Software Partnership. The Runcorn offices are reorganised as Deluxe Data International Operations.

Deluxe Data International Operations, Wingate House, Northway

1995: The product undergoes heavy code optimization to satisfy customer acceptance loops for international clearers, notably deploying direct electronic banking solutions for major Dutch institutions like Rabobank. Mark Whitfield moves on from Deluxe Data (after 5 years) to Insider Technologies Limited in Salford Quays in late 1995. This to continue HPE NonStop programming work for both monitoring and diagnostic products like Reflex 80:20.
1996: Development transitions toward hybrid enterprise networking. The sp/ARCHITECT system is updated with custom TCP/IP software interfaces to allow newer mid-range UNIX servers (such as IBM RS/6000) to safely communicate with the core Tandem server environment.
1997: Deluxe Data expands the core platform’s messaging logic using Tandem’s Remote Server Call (RSC) facility. This enables early Windows NT operating systems to request live financial data from the sp/ARCHITECT host.

1998: An automated, multi-process file transfer protocol is integrated natively into the bank database, leveraging Connect:Direct transport layers to securely transfer corporate SWIFT financial data files.

🚀 Era 3: The eFunds & Corporate Consolidation Era (2000–2006)

Deluxe Data’s technologies spun off into a new corporate entity called eFunds Corporation, altering the delivery model of the legacy software.

2000: Deluxe Electronic Payment Systems officially merges with other divisions to form eFunds Corporation (EFD). The sp/ARCHITECT package becomes a core pillar of eFunds’ international banking portfolio.
2002–2004: To modernise the transaction handling backbone, components of the sp/ARCHITECT platform are refactored. The system’s underlying communication routing is systematically aligned with CONNEX, a dominant market-leading Electronic Funds Transfer (EFT) processing engine.
2005–2006: eFunds transitions the direct client-server software layers into highly secure corporate portals, providing the foundational logic for what would eventually be rebranded as the CONNEX Advantage banking solution.

🏢 Era 4: The FIS Integration and Legacy Modernisation Era (2007–Present)

The final stage of the product timeline represents its absorption into global banking infrastructure software, where its high-availability DNA remains active in institutional transaction environments.

2007: Financial technology behemoth Fidelity National Information Services (FIS) acquires eFunds Corporation for approximately $1.8 billion. Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.

Fidelity National Information Services (FIS) Aegon House in Daresbury, Warrington 2007 — Fidelity National Information Services (FIS) Aegon House, Warrington (in 2007)

2010: FIS fully absorbs the remaining codebase, utilizing its core Tandem architecture algorithms to fortify transaction processing stability.
2015–2020: The architectural concepts pioneered by sp/ARCHITECT-BANK continue to govern high-volume legacy systems. The logic stays preserved in COBOL85 code bases running on modern HPE Integrity NonStop (Intel Xeon-based) fault-tolerant environments.
2020s–Present: Modern banking infrastructures gradually migrate from the classic database frameworks toward microservice configurations and open-banking APIs. However, the core system layout remains a primary point of historical reference for designing high-throughput, 24/7/365 fault-tolerant banking systems.

sp/ARCHITECT-BANK originally developed by The Software Partnership (TSP), Runcorn, Cheshire

sp/ARCHITECT-BANK Code Evolution Timeline

The timeline below details how the code’s core design, language implementations, and application deployment strategies transformed by era and year.

1. The Monolithic & TAL Foundation Era (1980s – Early 1990s)

During this era, the application focus was strictly high-throughput, fault-tolerant electronic funds transfer (EFT) and point-of-sale (POS) switching systems natively built for Tandem Guardian environments.

Late 1980s: The core design of sp/ARCHITECT is established using TAL (Tandem Application Language). Applications are deployed as single-system monoliths. Code optimization focuses heavily on low-level bit manipulation and message structuring to survive CPU or inter-process failures without losing in-flight transactions.
1991–1993: Structuring of modular execution libraries. Early iterations of the codebase segment transaction processing routes from core database logging routines. The introduction of Tandem’s newer NonStop SQL forces early integration layers to transition from standard unstructured unstructured file systems (Enscribe) to early relational tracking.

2. Distributed Client/Server & pTAL Migration Era (Mid 1990s – Early 2000s)

The architectural demands shifted from single-frame monoliths toward distributed banking systems, giving rise to “Distributed Monoliths” and client/server network structures.

1995–1996: Hardware evolutions transition from the older CISC-based Tandem systems to RISC architectures (MIPS processors). sp/ARCHITECT undergoes a massive compilation shift to pTAL (portable TAL) to preserve legacy code performance across new instruction sets.
1998–1999: Tandem’s acquisition by Compaq pushes the software suite to handle open standard protocols. The application code begins abstracting system calls to prepare for broader networking interfaces.
2001–2003: Deluxe Data / eFunds eras. The code sees the introduction of C/C++ wrappers around the legacy pTAL components. Systems are decoupled into a clear 3-Tier architecture: front-end terminal networks, back-end pTAL transactional engines, and standardized clearing houses.

3. Open Systems, Modern Middleware, & Java Integration Era (Mid 2000s – 2010s)

Following HP’s acquisition of Compaq and subsequent software realignments, the sp/ARCHITECT codebase was re-engineered to prevent vendor lock-in and adopt modern enterprise standards.

2005–2007: Java is introduced into the sp/ARCHITECT ecosystem. New application modules, specifically merchant portal interfaces and settlement reporting tools, are written entirely in Java and run via OSS (Open System Services) environments.
2010–2012: FIS acquisition era integration. Legacy pTAL code blocks are systematically refactored or heavily wrapped in C++ using object-oriented principles to ensure long-term maintenance. The transaction routing engine is altered to support early SOA (Service-Oriented Architecture) paradigms via web-services hooks.
2015–2018: Mainstream deployment of COB (Core Banking) standard formats within the application layer. The system moves away from old proprietary network messaging layouts to ISO 20022 compliance frameworks, utilizing dedicated conversion engines native to the sp/ARCHITECT stack.

4. Modern Cloud-Adjacent & Hybrid Infrastructure Era (2020s)

The current evolutionary footprint centers on maintaining the absolute sub-millisecond reliability of the core architecture while exposing capabilities to dynamic cloud endpoints.

2021–2023: Modernization of the application payload. High-performance micro-frontends handle real-time fraud monitoring and data streaming using asynchronous event-driven pipelines (e.g., Kafka event consumers interfacing directly with the NonStop core runtime environments).
2024–2026: Transition to containerized orchestration and cloud-adjacent infrastructure. The sp/ARCHITECT footprint utilizes x86-based virtualized NonStop systems (NSX), enabling legacy core modules (derived from the original TAL logic) to execute seamlessly on modern virtual environments alongside Linux-based multi-tenant applications.

Insider Technologies Limited (ITL), Company Overview and Timeline by Year

ITL is a specialized UK-based software house & service provider that engineers high-availability monitoring, tracking, and cybersecurity solutions

Insider Technologies Limited is a specialized UK-based software house and service provider that engineers high-availability monitoring, tracking, and cybersecurity solutions for business-critical, 24/7 mission-critical architectures. I worked at ITL in Salford Quays from 1995 through to 2013.

Mark Whitfield attending an EBUG conference
(BASE24 User Group) — Attending an EBUG conference
(European BASE24 User Group)

Foreground, attending a British Isles TANDEM User Group (BITUG) — Foreground, attending a British Isles
TANDEM User Group (BITUG)

Insider Technologies Limited, ITL, website in 2009 — Insider Technologies Limited
(website author in 2009)

Company Overview

🏢 Corporate Identity & Status

Legal Name: Insider Technologies Limited
Founded: 27 February 1989
Headquarters: Manchester, UK (Albert Street, Eccles)
Ownership: Operating as a private independent software company, recently integrated as part of PartnerOne.
Strategic Partnerships: Certified Microsoft Gold Partner for Application Development and long-standing Hewlett Packard Enterprise (HPE) partner.

Insider Technologies Limited (ITL) in 2001, Salford Quays, Chandlers Point

🌐 Core Domain & Industries Served

The company delivers real-time, event-driven diagnostic, tracking, and compliance middleware solutions across three main highly-regulated global verticals:

Banking & Financial Services: Monitoring real-time electronic payments, ATM/POS systems, and transaction workflows (e.g., BASE24, XPNET environments).
Government & Defence: Secure enterprise military messaging tracking and digital evidence handling.
Telecommunications: Tracking data traffic and critical infrastructure middleware.

🛠️ Core Technology Stack & Competencies

Insider Technologies specializes in niche high-availability operating environments—specifically HPE NonStop (historically Tandem Computers and HP NonStop) running Guardian and Open System Services (OSS) environments—alongside enterprise Windows, Linux, and Unix systems. Their expertise spans database transaction management, BASE24 XPNET monitoring, IBM WebSphere MQ tracking, and low-level development (SQL, TAL, TACL, COBOL85, C++, Pathway).

Insider Technologies, the
Core products in 2003 — Insider Technologies –
Core products in 2003

In-Depth Product & Political-Technical Timeline

This timeline breaks down how Insider Technologies evolved its software suite. It demonstrates how their technical development directly responded to shifting geopolitical landscapes—ranging from late-Cold War military messaging security to post-9/11 financial regulations and modern European cloud autonomy initiatives.

🔹 The Foundation & Legacy Tandem Era (1989–1999)

Political Context: The final years of the Cold War and the 1990s globalization boom demanded high-security, fault-tolerant mainframes for NATO-aligned military communications and early global banking clearing networks.
Technical Context: Tandem Computers dominated the un-interruptible 24/7 market. Software was required to monitor these platforms without causing processing overhead.
1989
- Company Incorporation: Insider Technologies is incorporated in the UK to engineer bespoke software for highly robust technical ecosystems.
1990–1995
- Reflex (Core Release): Release of Reflex, a foundational service management and real-time transaction diagnostic tool built specifically for the Tandem Guardian operating system.
1996–1999
- MultiBatch Software: Further Develop and Extend MultiBatch to orchestrate and safely automate complex batch processing on Tandem machines alongside the evolution into HP NonStop computing frameworks.
- Y2K Compliance Focus: Technical adjustments were deployed across Reflex and MultiBatch to assure financial institutions that automated transaction logging would not fail during the millennium rollover.

🔸 The Multi-Platform & Financial Compliance Era (2000–2015)

Political Context: Following the September 11 attacks, global anti-money laundering (AML) and counter-terrorism financing (CTF) frameworks heavily expanded. Financial regulators demanded exact, audible end-to-end payment tracking.
Technical Context: Enterprises began migrating away from single-architecture mainframes toward heterogeneous IT environments, requiring tools that could jump across Windows, Unix, and Linux simultaneously.

2002–2004
- Sentra Development: Launch of Sentra, expanding the firm’s portfolio beyond HPE NonStop into cross-platform environment monitoring for Windows, Linux, and Unix systems.
- Reflex 80:20 & Reflex ONE24: Advanced variations of the Reflex tracking system were built to cater to specialized real-time electronic payment flows like BASE24 with XPNET.
2005–2010
- RTLX Reactor (page 12) and Middleware Monitoring: The release of RTLX Reactor provided message tracking capabilities tailored for IBM WebSphere MQ, allowing institutions to trace various payment and other data through complex middleware chains.

RTLX Reactor, 2013 article -
The Connection Journal — RTLX Reactor, 2013 article –
The Connection Journal

BASE24-eps extraction and RTLX — BASE24-eps extraction
and RTLX (in 2007)

2011–2015
- Corporate Structuring: The creation of Insider Technologies (Holdings) Limited reinforced corporate expansion as the company deepened its footprint in secure military messaging for government defense bodies.

🔹 The Cyber Autonomy & Sovereignty Era (2016–Present)

Political Context: Escalating nation-state cyber warfare, strict GDPR regulations, and the UK/EU push for technological sovereignty and domestic digital ecosystem resilience heightened the reliance on trusted, onshore technology suppliers.
Technical Context: High-threat environments demand zero-trust visualization, time-accurate logging across digital evidence files, and advanced protection against internal exfiltration vectors.
2019
- 30-Year Milestone & Modernization: The company celebrates its 30th year, accelerating development on modern mobile application extensions to permit real-time, remote secure alerts for operations teams.
2022–2025
- PartnerOne Integration: Insider Technologies aligns its operations under the PartnerOne portfolio, preserving its UK identity while supercharging its enterprise-scale data infrastructure solutions.
- Corporate Integration combines Insider’s expertise with PartnerOne’s portfolio to deliver advanced analytics and secure messaging systems to banking, defence, and telecommunications markets.
- Defense and Public Safety Porting: Technical deployment of specialized capabilities covering digital evidence security, timekeeping tracking, and legacy virtualization modules aimed explicitly at helping the UK Government maintain its historical tech stacks safely.

Insider Technologies Limited (ITL), Company Overview and Timeline by Year

The Insider RTLX product at ETI-NET is now called C-Deep for Transaction Monitoring;

C-Deep (Transaction Monitoring)

The Insider Reflex product at ETI-NET is now called Sentinel for NonStop Monitoring;

Sentinel (Nonstop Monitoring)

C-Deep for Transaction Monitoring & Sentinel for HPE NonStop Monitoring

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.

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):

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

HPE NonStop Tandem Programming Languages and Development Timeline

The development of programming languages on the HPE NonStop platform (originally founded as Tandem Computers) is tightly bound to its architectural hardware transitions: from custom CISC stack machines to MIPS RISC, Intel Itanium, and eventually standard Intel x86-64 infrastructures.

Detailed List of NonStop Programming Languages

1. Core Proprietary & System Languages

TAL (Transaction Application Language): The foundational system programming language for Tandem. It is a block-structured, machine-dependent procedural language designed to compile directly into highly efficient machine instructions. It features ALGOL/Pascal-like syntax but implements C-like semantics, structural pointers, and weak data typing.
pTAL & epTAL: Specialized evolutions of TAL. Rather than rewriting legacy codebases from scratch during architecture shifts, pTAL was introduced to compile existing TAL code natively into MIPS RISC architectures. Later, epTAL was developed to target Intel Itanium microprocessors.
TACL (Tandem Advanced Command Language): A built-in command interpreter and interpreted scripting language. It functions like a Unix Bash shell but features highly complex macro capacities used to orchestrate system configurations, monitor processes, and automate failover procedures.

2. Enterprise & Enterprise Legacy Languages

COBOL85 (and older COBOL74): The undisputed workhorse of NonStop commercial workloads. HPE’s tailored implementation of the COBOL85 standard natively interfaces with the Guardian OS. It allows programmers to embed SQL/MP statements and program fault-tolerant Process Pairs through HPE NonStop Pathway (TS/MP).
SCOBOL (Screen COBOL): A specialized, high-level structural derivative of COBOL utilized exclusively to build blocks for character-cell terminal interfaces (such as the 6530 terminal environments) running within Pathway architectures.
NonStop SQL (SQL/MP and SQL/MX): While technically a database system, its embedded syntax acts as a declarative language integrated into C and COBOL. SQL/MP works with the legacy Guardian file system, while SQL/MX brings ANSI-compliant SQL closely bound with the Open System Services (OSS) environment.

3. Standard Mainstream Languages

C & C++: Heavily introduced during the RISC transition to allow software portability. Mainstream development on modern NonStop systems uses standard C/C++ cross-compilers. They run in either the native fault-tolerant Guardian personality or the standard POSIX-compliant Open System Services (OSS) environment.
Java: A first-class language layer deployed natively on NonStop. HPE optimizes the Java Virtual Machine (JVM) to scale across multi-CPU shared-nothing frameworks, allowing modern enterprise web apps to run with out-of-the-box system availability.

4. Modern Open-Source Options

Python, Go, & JavaScript (Node.js): Modern procedural and script utilities provided by HPE. These environments leverage the OSS POSIX platform layer, running modern DevOps orchestration, microservices, and hybrid-cloud pipelines alongside the native database engines.

Detailed Timeline Breakdown by Era and Year

The evolution of NonStop languages maps directly across distinct engineering ownership eras.

The Proprietary Foundation Era (Tandem Computers: 1974–1989)

1976: Tandem ships the original Tandem/16 (NonStop I). TAL is the only available language on the platform. The entire Guardian Operating System is written completely in TAL.
1981: The NonStop II hardware is introduced. Tandem expands language support to include COBOL74, FORTRAN, and BASIC to attract mainstream banking clients.
1983: Tandem releases the Transaction Monitoring Facility (TMF) and Pathway application management software. SCOBOL is introduced alongside them to program secure terminal entry interfaces.
1985: TACL is deployed, completely modernizing the command line shell ecosystem with scalable macros and structured operational control.
1986: Tandem launches NonStop SQL, the first linearly scalable, fault-tolerant relational database engine. Embedded SQL syntax is integrated directly into TAL and COBOL compilers.
1988: Compilers undergo a major update to natively support the newly established COBOL85 standard, which quickly replaces COBOL74 for all mission-critical banking transactions.

The Open Systems & Hardware Transition Era (Compaq: 1990–2001)

1991: Hardware migrates from CISC stacks to MIPS RISC architectures with systems like the Cyclone/R. To protect client software assets, Tandem delivers the pTAL compiler to translate TAL source code into native RISC binaries.
1995: Tandem introduces Open System Services (OSS), a POSIX-compliant UNIX subsystem running over the Guardian kernel. This brings full-scale, native native compliance for standard ANSI C and C++ programming.
1997: Compaq acquires Tandem Computers. Engineering shifts heavily toward implementing Java on NonStop, targeting cross-platform, enterprise internet-banking codebases.
2000: NonStop SQL/MX is released. It allows developers to use embedded SQL statements within standard C, C++, and emerging Java applications inside the OSS runtime environment.

The Corporate Alignment & Itanium Era (Hewlett-Packard: 2002–2014)

2002: HP merges with Compaq. Java is designated as a first-class citizen on the platform, receiving deeper optimization to tie into native clusters seamlessly.
2005: HP releases the Integrity “NonStop i” servers, moving processors away from MIPS onto Intel Itanium architectures. The epTAL compiler is rolled out alongside standard C/C++ updates to seamlessly compile older environments onto Itanium.
2011: Open-source scripting engines, including early ports of modern Python, are introduced to the OSS environment, easing the system-management burden for engineers unfamiliar with legacy TACL.

The Modern Enterprise Era (Hewlett Packard Enterprise: 2015–2026)

2015: HP splits, and the platform transitions to HPE. Standard Intel x86-64 hardware dominates with the NonStop X architecture. Compilers utilize an standard GCC/LLVM-based back end, allowing normal Linux/Unix C++ programs to build on NonStop with minimal alteration.
2020: Sales of Itanium systems officially terminate. Legacy languages like TAL are deprecated for new software creation but are preserved to support older, foundational logic.
2023–2024: HPE rolls out modern cloud-ready DevOps Starter Kits. Full, native support is added for modern languages such as Go, modern Python 3.x, and Node.js, allowing them to integrate into modern automated CI/CD build environments.

HPE NonStop Tandem Programming Languages and Development Timeline

ACI Worldwide XPNET Message-Oriented Middleware, MOM

XPNET (often distributed as part of the NET24 suite) is a proprietary, mission-critical Message-Oriented Middleware (MOM) and network management infrastructure developed by ACI Worldwide.

It is designed to run primarily on fault-tolerant HPE NonStop (Tandem) systems. XPNET acts as the foundational layer for ACI’s globally dominant payment engines, BASE24 and BASE24-eps.

It provides the multi-node network architecture, data routing, inter-process communication, and transaction logging required to safely process hundreds of millions of ATM, Point of Sale (POS), and mobile payments daily.

Key Architectural Technical Description

Core Function: XPNET acts as the vital gateway between terminal devices (ATMs, POS terminals), regional interchanges (Visa, MasterCard), and a bank’s back-end host system.
Network Environment File (NEF): All physical and logical configurations of an XPNET deployment—including nodes, links, processes, stations, and communications lines—are centrally defined inside the NEF.
Fault Isolation: XPNET monitors processes using a distributed architecture. If an interface process or line drops, XPNET safely queues or reroutes transactions to achieve “five-nines” (99.999%) financial system uptime.
Audit and Tracing: XPNET intercepts all systemic message traffic, managing the core Transaction Log File (TLF) and generating event messaging for fraud monitoring and performance profiling.

Detailed XPNET Historical Timeline Breakdown

The evolution of XPNET is deeply intertwined with ACI’s flagship software, scaling alongside the transformation of global electronic funds transfers (EFT).

1982 – 1989: The Genesis Era

1982: ACI launches BASE24 to manage early ATM networks. To handle low-level Tandem interprocess communication, ACI designs precursor communication layers.
1986: ACI scales internationally to 131 major clients across 14 countries, increasing the demand for a standard, highly secure, policy-driven message-switching architecture to accommodate disparate global telecommunication protocols.

1990 – 1999: NET24 and XPNET Standardisation

1993: ACI is reorganised under Transaction Systems Architects (TSA). The communications infrastructure is formalised as NET24-XPNET, decoupled cleanly from application logic.
1995: ACI goes public on NASDAQ. XPNET becomes the mandatory structural platform for any financial institution deploying BASE24 “Classic”.
1998: ACI acquires IntraNet. XPNET is updated to handle wholesale wire transfers and high-value Automated Clearing House (ACH) data alongside retail consumer swipes.

2000 – 2009: The Next-Gen Transition (BASE24-eps)

2002: ACI launches BASE24-eps (Enterprise Payments System). XPNET is radically re-engineered to support both classic structural architecture and next-generation message formats, utilizing its Common Transport Subsystem (CTS) to act as a Tandem Pathway client/server.
2008: ACI optimises BASE24-eps for IBM System z architectures, but updates the NonStop-native XPNET to Version 08.2 to handle expansive regional payment networks across Europe and Asia.

2010 – 2019: Litigation and Global Footprint Consolidation

2011 – 2014: Third-party performance suites, such as IR Prognosis XPNET Manager, Insider Technologies XPERT24 and Reflex ONE24 explode in popularity, allowing banks to map live visual diagnostics of their XPNET lines and queues.
2017: ACI and MasterCard reach an agreement to resolve a massive legal dispute. As part of the settlement, MasterCard purchases a perpetual components license for NET24-XPNET middleware to legally fuel its core debit-switching network infrastructure.

2020 – 2026: Legacy Modernisation & The API Era

2021: With financial institutions pivoting toward digital microservices, ACI introduces hybrid compatibility layers. Companies like NuWave introduce direct API bindings to XPNET, allowing legacy HP NonStop payment architectures to map to modern REST web services without rewriting base COBOL/C code.
2025 – 2026: ACI celebrates 50 years of enterprise infrastructure engineering. While cloud-native solutions like ACI Connetic roll out for real-time rails, NET24-XPNET Version 4.x remains a heavily maintained, actively running baseline layer across tier-1 legacy banking systems worldwide.

ACI Worldwide XPNET Message-Oriented Middleware, MOM

XPERT24 Product Overview

XPERT24 (XPNET Performance Monitoring and Tracking) is a specialised financial middleware software product developed by Insider Technologies Limited. It provides real-time transaction tracking and operational counter monitoring for the BASE24™ transaction processing infrastructure.

Product Description

XPERT24 functions as a critical diagnostics layer for companies running BASE24 bank card payment systems. Built to sit on HP NonStop systems, the software uses PATHWAY servers to automatically detect, capture, and analyse data points from the underlying network. Its core features include:

XPNET Counter Monitoring: Tracks infrastructure health via rate, state, and data queue counters.
Interchange Performance: Monitors live transaction metrics, including approval and denial rates for ATM and POS transactions.
Throughput Optimization: Provides clear system visibility to avoid high-volume traffic jams or transaction delays.

Detailed Timeline Breakdown

The lifecycle of the XPERT24 software package moved from initial technical specification into corporate ecosystem expansions:

2001 — Initial System Baseline & Prep

Training and Scoping: Insider Technologies Limited launched internal Sales & Marketing campaigns to map mid-market banking software demands.
System Language Adaptation: Engineering teams refined core HP NonStop transaction tracking metrics.

2006 — Structural Architecture Layout

Design Initiatives: Product groups commenced documentation guidelines to build customer-facing technical literature.
Database Modeling: Initial designs mapped how transaction records could safely pass without lagging the live bank engine.

2007 — Server Logic Creation

Server Infrastructure Setup: Developers initiated building structural frameworks inside development kits.
Pathway Server Logic: Logic was written to make sure the software query scripts safely gathered data without interrupting processing.

2008 — Production Release & Launch Era

Official Software Launch: Insider Technologies launched the operational XPERT24 system to production status.

Hypervisor UI Integration: The company produced dedicated BASE24-eps™ and XPNET layer Hypervisor graphical displays.
Industry Showcase: Technical user interfaces were presented directly to the Electronic Banking User Group (EBUG) and the Satellite Transaction User Group (SATUG).

2009 — Data Query Expansion

SQL Interoperability: Product upgrades integrated better SQL handling to build structured transaction logs.
Web Monitoring Foundations: Teams rolled out technical requirements to present live transaction counters into standard web browsers.

2011 — Project Management & Standardization

Agile Shift: Development pipelines migrated entirely onto the Scrum framework.
Process Alignment: The product management structure was retrofitted to follow strict PRINCE2 guidelines to help service major government and banking institutions.

ActionView.400 Monitoring Tool for OSI/MHS X.400 Subsystem on HPE NonStop

ActionView.400 is an enterprise tracking and diagnostics software solution developed by Insider Technologies Limited. It was purpose-built as a dedicated monitoring tool for the Open System Interconnection / Message Handling System (OSI/MHS) X.400 subsystem deployed on Tandem, Compaq, HP, and HPE NonStop server platforms.

The software acts as a critical infrastructure layer used heavily by banking institutions, telecommunications providers, and government/military defense sectors.

It ensures that high-volume, secure electronic mail infrastructure meets strict Service Level Agreements (SLAs) by allowing engineers to account for every message, calculate end-to-end processing times, and issue real-time tracking metrics.

Detailed Timeline Breakdown by Year

1989: Insider Technologies Limited is incorporated in Manchester, England, by a collective of IT industry veterans. The firm initially focuses on building service management and custom tracking middleware for the rapidly expanding Tandem NonStop server ecosystem.
1990s (Early to Mid): As X.400 protocols become the global standard for secure EDI (Electronic Data Interchange) and military messaging, Insider Technologies develops ActionView 400. The product is integrated directly into Tandem’s core software stack and begins shipping natively with Tandem NonStop platforms.
1997: Tandem Computers is acquired by Compaq. ActionView 400 is sustained through this transition to maintain critical operations for tier-one banks and national military infrastructures relying on NonStop systems.
2002: Compaq merges with Hewlett-Packard (HP). ActionView 400 is bundled under the HP NonStop software catalog (product designation T8443), managing and diagnosing log audits like the AUDLOG framework.
2000s (Mid to Late): Insider Technologies starts shifting forward-looking tracking requirements toward its newer central architecture platform, Sentra. While ActionView 400 continues handling legacy X.400 pipelines, Sentra begins acting as a unified web console to consolidate both X.400 and modern SMTP/MIME email flows across multi-vendor systems.
2015: HP splits its corporate structures. The NonStop computing line and the management of ActionView 400 shift over to Hewlett Packard Enterprise (HPE).
2018: In December 2018, HPE officially moves ActionView 400 to Obsolete status, marking the formal end of its product life cycle and standard vendor service life.
2019 – Present: Despite official obsolescence on the HPE hardware list, Insider Technologies continues to directly support and maintain the solution for deep-legacy military, defense, and governmental bodies. Because these sectors still mandate uncompromised, zero-loss X.400 message accounting, the software remains active, feeding tracking telemetry directly into Insider’s modern Middleware Monitoring and Sentra platform interfaces.

Sentra - unified web console to consolidate both X.400 and modern SMTP / MIME email flows across multi-vendor systems — Sentra – unified web console to consolidate both X.400 and modern SMTP / MIME email flows across multi-vendor systems

Are you Still on Track?

HPE NonStop MultiBatch is an advanced workload automation & scheduling manager

HPE NonStop MultiBatch is an advanced workload automation and scheduling manager designed explicitly for mission-critical HPE NonStop environments. Originally created to support complex scheduling needs in banking and finance, it automates job flows and parallel processing across multiple CPUs.

Detailed Description

The original NonStop batch scheduler (NetBatch) was built for basic sequential job queues. As large enterprises required deeper integration with databases, real-time events, and complex parallel schedules, MultiBatch (developed originally by Insider Technologies, now part of ETI-NET) emerged.

Core Functions: It automates job submission, tracks job flow, handles conditional parameters, manages event timers, and triggers jobs “On Demand” based on real-time system events.
High Availability: Like the underlying HPE NonStop system, MultiBatch is engineered for fault tolerance, ensuring automated workflows do not fail due to hardware or software interruptions.
Enterprise Integration: It supports Open System Services (OSS) and standardizes auditing, security, and menu-based operations across distributed NonStop systems.

Breakdown by Year / Era

The evolution of MultiBatch parallels the architectural changes of the HPE NonStop platform.

1985–1990s: Tandem Era & Origin

1985: Conceived. MultiBatch was developed by Insider Technologies specifically to meet the complex batch schedule demands of large financial institutions that exceeded native NetBatch capabilities.
Early 1990s: The system was officially rolled out for Tandem processors to automate transaction data loads and daily reconciliation tasks for ATMs and financial ledgers.

1997–2014: Compaq & Early HP Era

1997: Following Compaq’s acquisition of Tandem, MultiBatch was adapted to support the NonStop Himalaya systems and server software, which expanded data and network scaling.
2000s: During the HP Itanium and MIPS Era, MultiBatch evolved to support more dynamic processing pools and expanded job limits, increasing fault tolerance under the HP-UX integrated environment.

2014–2020: Transition to NonStop X & Modernization

2014: As HPE shifted the platform to standard Intel x86-64 processors (NonStop X), MultiBatch was updated for L-series operating systems to run efficiently on high-speed InfiniBand fabrics.
2019: Insider Technologies made significant updates to MultiBatch to modernize the GUI and improve code stability for the new generation of NonStop users transitioning to X-series hardware.

2020–Present: MultiBatch 10 & 10.2

2023: MultiBatch 10 was released. It included a new Operations GUI Server, significantly increased configuration limits (e.g., supporting up to 2,500 jobs), enhanced conditional parameters, improved processing of Open System Services (OSS), and “On Demand” job capabilities.
2025: MultiBatch 10.2 was released by ETI-NET. This update focused heavily on digital resilience, providing deep alignment with the NIST Cybersecurity Framework to protect against operational and cyber threats.
Current Status: Fully integrated into modern systems supporting the HPE GreenLake consumption-based cloud model, MultiBatch 10.2 serves as the primary automation engine for large enterprises executing complex HTAP (Hybrid Transaction/Analytical Processing) workloads.

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this: