The European BASE24 User Group (EBUG) was established in the 1980s as an independent, community-led organization for users of the BASE24 payment processing system developed by Applied Communications, Inc. (now ACI Worldwide).
Originally a regional forum for IT professionals in Europe to discuss HPE NonStop (Tandem) transaction monitoring and network security, the group expanded globally over time.
Insider Technologies regularly attended EBUG, booth in 2007 – RTLX now ETI-NET C-Deep
Following ACI’s withdrawal of direct corporate backing, EBUG evolved into “The Independent Group for All Payments System Users”—affectionately known as the Everybody Belongs User’s Group—welcoming users of multiple payment platforms like Postilion.
The detailed historical timeline of EBUG and the evolution of its core system, BASE24, outlines its development from a regional user collective to a global payments forum:
The Foundation Era (1975–1989)
1975: ACI is founded in Omaha, Nebraska, initially developing software for fault-tolerant Tandem NonStop computers to connect ATMs to bank networks.
1982: The BASE24 product family is officially launched globally, acting as “baseline” software for 24-hour financial operations.
1980s:EBUG is established as a regional European community for BASE24 users to collaborate on ATM networking and transaction processing.
Early 2000s: EBUG annual conferences grow in prestige, featuring technical tracks on BASE24 transaction logging, Point-of-Sale (POS) networks, and network resilience.
2007: EBUG hosts a high-profile international conference in Istanbul, Turkey.
2008: EBUG hosts its annual meeting in Vienna, Austria, which is historically noted as a pivotal year where ACI began supporting immediate payments in Europe and discussed a strategic shift toward IBM platforms. ACI officially announces the future retirement of “BASE24 Classic”.
2009: The conference is held in Prague, Czech Republic, maintaining strong community support for BASE24 on Tandem servers despite broader industry shifts.
Global Expansion, Rebranding & The Cloud Era (2010–Present)
2012: ACI introduces BASE24-eps, their next-generation, platform-independent payments engine designed to replace the legacy BASE24 on HPE NonStop. EBUG’s technical focus shifts to real-time payments and log extraction.
2013: With ACI ending direct involvement, the user group officially rebrands as the “Everybody Belongs User’s Group” at their conference in London, expanding attendance to professionals from Mexico, South Africa, and Australia.
2015: ACI celebrates 40 years in payments. EBUG solidifies its status as a supplier-agnostic payments forum, opening sessions to non-BASE24 users.
2020s: With BASE24 Classic retired, legacy users migrate to modern systems like BASE24-eps for cloud deployments and immediate payments.
Recent Years: ACI goes live as a pioneer in the Federal Reserve’s FedNow Service, building upon the decades-long transaction switching architecture first developed in the 1970s and 1980s.
European BASE24 User Group (EBUG) Timeline from Inception
Mark Whitfield is a UK-based, SC-cleared Senior IT Project Manager and Engagement Manager with over three decades of experience in software development lifecycle (SDLC) delivery.
Mark Whitfield, High-Level Career Summary from 1990 thru 2026
Over his career, he has transitioned from deep technical engineering on legacy systems (HPE NonStop formerly Tandem Computers) to enterprise-scale digital transformation, cloud migrations, and API-led integrations. He is also the author of a comprehensive online toolkit for project delivery frameworks.
Click the ‘Company Worked‘ links below for more detail as required.
Project Management Career Breakdown:
1. Early Engineering & Technical Analysis Era (1990–1995)
Geographical Location: Salford Quays, UK (office); London, UK; Client sites across Europe/ Middle East
Clientsinclude: Global Payments, Standard Chartered, Girofon, Rabobank, CRESTCo (Euroclear), Alrajhi Bank, LloydsTSB, HSBC, Santander, Bank of Ireland, Bank of Valletta (Malta) and both Commercial and Piraeus Bank (Greece)
Main Focus Items: Infrastructure consulting, volume testing, system management & monitoring, and Service Level Agreement (SLA) monitoring for critical path payment applications. Attending related conferences, EBUG, ITUG, BITUG, SATUG
Technology Areas: HPE NonStop monitoring, ATM/POS system & transaction monitoring and stock settlement.
Geographical Location: Woking / Bracknell / UK wide
Client: Lloyds Banking Group
Main Focus Items: Modernising legacy ATM software and directing hardware/software transitions. Implementing ProClassic/Enterprise and PC/E SmartClient (Win 7) to replace the existing ProCash/NDC (Win XP) Stacks on a variety of multivendor devices.
Technology Areas: Multi-vendor hardware & software integration for ATMs.
Geographical Location: Wigan / Greater Manchester, UK
Client: Betfred Online and Mobile
Supplier Management: for external software suppliers like Degree53, Playtech, Onionsack, Intelligent Payments (Myriad), Inspired, iovation, StreamUK, Finsoft, Ineda, OtherLevels, Appsflyer, Income Access, Activewin, Virgo, Virtue Fusion, In Game Media, Satellite Information Services (SIS) and IGT
Main Focus Items: Taking new sports and virtual gaming components live, integrating payment gateways, managing app release cycles, and handling regulatory compliance.
In addition to his consultancy work, Mark Whitfield actively publishes his extensive collection of Project Management Templates, which are actively utilized across the industry for RAID Logs, Agile Burndown Charts, and Plan on a Page (POaP) blueprints.
Mark Whitfield spent 18 years (August 1995 – September 2013) at Insider Technologies Limited (ITL), a Manchester-based software house specialising in high-availability tracking, service management, and transaction monitoring. Entering as a Senior Programmer, he climbed through the ranks to become an Operations Products Manager and, ultimately, the Project Manager for Strategic Technical Initiatives.
His core technical contribution revolved around developing and managing platform-health diagnostic modules, automated event filtering, and multi-currency transaction log trackers.
He focused heavily on the HPE NonStop (Tandem) kernel, integrating these mainframes with Windows, Unix, and Linux open systems. His work protected critical banking infrastructure, such as transaction loops feeding into ACI BASE24 ATM/POS switches and major national payment clearings.
Detailed Timeline Breakdown
🔹 The Foundational Tandem Era (1995–1999)
This period focused on building out bespoke low-level mainframe diagnostic scripts, real-time logging, and bracing critical infrastructure for the millennium bug.
1995: Joined Insider Technologies Limited at Salford Quays after departing Deluxe Data. He began programming SCOBOL green screens and engineering PATHWAY servers to query raw Guardian operating system procedures.
1996: Core developer for the flagship Reflex monitoring suite (Reflex 80:20). He co-authored the Console module for HPE NonStop Event Management Service (EMS) viewing, alongside tracking blocks for system components like CPU, Disk, and Processes.
1997: Transitioned into an infrastructure consulting capacity, designing code routines to test physical hardware throughput.
1998: Formally appointed as the ITL Operations Products Manager. He orchestrated high-performance benchmarking tests on newly deployed Tandem S7000 processing hardware nodes for Euroclear (formerly CRESTCo), validating infrastructure that handled 88% of UK equities.
1999: Directed critical, deep-level automated Y2K code auditing. This guaranteed that real-time tracking loops and MultiBatch scheduling automation would accurately handle the date rollover for clearing partners like the Bank of England and Deutsche Bank.
🔸 The Operations & Middleware Integration Era (2000–2005)
This era bridged the gap between rigid standalone mainframes and modern open-system dashboards, creating cross-platform monitoring frameworks.
2000: Spearheaded deep-layer integration projects connecting legacy frameworks to distributed enterprise collectors like TIVOLI, COMMAND/POST, and third-party file monitors.
2001: Supervised 24×7 enterprise support teams handling cryptographic security frameworks for Thales e-SECURITY products, overseeing the SafeSign Authentication and Management Server lines on Windows/Unix.
2002: Led technical rollouts for ITL’s interactive Systems Training Platform, deploying patented system-cloning configurations to let institutional clients practice outage responses safely.
2003: Drove cross-platform middleware compatibility protocols, building hooks between the NonStop kernel and WebSphere MQ (MQSeries) message streams to trap transactional anomalies in real-time.
2004: Advanced to Project Manager – Strategic Technical Initiatives, implementing PRINCE2 governance for new product R&D pipelines.
2005: Began standardising the technical architecture of Reflex ONE24, transitioning the vintage monitoring code toward centralized electronic web consoles.
🔹 The Strategic Initiatives & Product Management Era (2006–2013)
Whitfield shifted into pure-play product management, expanding corporate web assets and publishing technical documentation before navigating the company through an MBO.
2006: Pioneered custom transaction parsing frameworks for payment switches, resulting in the foundational engine layout of Sentra and the Real-Time Log Extraction (RTLX) engine.
2007: Acted as the primary corporate website architect and author, modernising Insider’s public presence by building out and managing content deployments on DotNetNuke (DNN).
2008: Managed implementation pipelines for XPERT24, a highly specialized utility engineered specifically for performance tracking across complex BASE24 XPNET banking environments.
2010: Guided software engineers through logic modifications to intercept multi-currency retail POS and ATM interchange drops down to the millisecond.
2011: Coordinated agile deployment sprints for financial institutions to meet strict compliance laws surrounding automated data storage and long-term file retention.
2012: Provided the project governance behind the scenes during Insider Technologies’ internal structural transitions, supporting a £3m Management Buyout (MBO).
2013: Authored a major technical summary published globally in the recognized HP NonStop industry journal, The Connection, defining payment software lifecycles. Concluded his 18-year run at ITL in September to join Wincor Nixdorf.
(Note: The product lines Whitfield built and governed were later acquired by ETI-NET in 2015, where his original RTLX utility was rebranded as C-Deep for Transaction Monitoring.)
Focus: Electronic banking programming and development on Tandem Mainframe Computers.
Projects: Wrote, developed, and maintained software like sp/ARCHITECT-BANK and associated billing software (in Poole, 1993). This involved building early electronic banking systems for desktops long before internet banking was prevalent.
Location: Insider Technologies, Salford Quays, Manchester, UK
Focus: NonStop product management, software design, and real-time event monitoring.
Projects: Product managed software lifecycles for four monitoring products (two NonStop based). This included creating health and diagnostic tools (RTLX, Reflex 80:20, Reflex ONE24,XPERT24) for mission-critical NonStop environments. He also deployed volume testing on early HP NonStop S7000 nodes for CRESTCo in London in 1997.
Insider Technologies, Salford Quays, Manchester, UK
Location: Wincor Nixdorf & ATM/POS Financial Services, UK
Focus: Modernization and migration of legacy systems.
Projects: Managed a £5M+ replacement of legacy HP NonStop software systems at a large UK retail bank, migrating functionalities to AIX-based J2EE and Oracle architectures.
Focus: Delivery of enterprise-scale middleware, digital transformation, and cloud.
Projects: Acts as an Engagement Manager and SC-Cleared Project Manager. Focus includes Agile software delivery for Air Traffic organisations (e.g., iOS applications for military and public-facing airspace tracking) and rolling out middleware solutions.
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.
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
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.
🌅 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.
Barclays, Wimborne Road, Poole, Dorset
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, 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-BANKCode 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 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.
Attending an EBUG conference (European BASE24 User Group)
Foreground, attending a British Isles TANDEM User Group (BITUG)
Insider Technologies Limited (website author in 2009)
CompanyOverview
🏢 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:
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 – 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.
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.
RTLX Reactor (in 2012) for tracking BASE24-eps & BASE24 XPNET transactions
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;
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
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:
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
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
