Tag: base24

BASE24 and core Networking Component XPNET timeline

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

Technical Evolution Timeline

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

Key Technical Components

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

BASE24 and core Networking Component XPNET

Base24-eps and UPF integration

Base24-eps and UPF integration

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

Key Aspects of the Integration

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

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

What is BASE24-eps?

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

BASE24-eps is designed to:

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

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

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

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

mark whitfield wordpress_connection_HP_NonStop_to_Windows_Combined
RTLX_White_Paper+Download