Today, every financial institution relies on solutions designed to combat financial crime. Financial Crime Mitigation (FCM) platforms enable banks to prevent regulatory fines, detect fraud, and safeguard their reputation, while also enhancing operational efficiency and reducing operational costs. These solutions support the risk-based approach that modern banks follow when managing compliance and financial crime.

Temenos Payments Hub (TPH) is a solution that provides banks with a single platform to configure different payment types without requiring software changes.

As transactional systems evolve, databases accumulate large volumes of historical data that are rarely accessed but still required for compliance and analysis. Keeping this data in the primary database can impact performance and increase costs, making data archiving a critical practice.

The Performance Health Review (PHR) tool acts as a checklist (configuration collector) to verify whether all the performance-related properties are in place before running the performance tests. It helps to identify the current configuration against the recommended configuration (based on previous performance tests and benchmarks).

In Temenos, the ‘bnk’ folder serves as the primary directory for all applications. It primarily comprises the following subdirectory structure, with each directory designated for specific storage functions. Bnk.data: This directory holds all application and transaction data. Bnk.dict: This directory contains the dictionary files associated with the applications. Bnk.help: This directory contains the help text files for the applications. Bnk.jnl: This directory

The Temenos Data Hub (TDH) was originally created for data extraction purposes and has since been enhanced to serve as a real-time data management solution, equipped with the ability to integrate with external tools.

Services in the T24 Core Banking System In this blog, we will talk about some of the most commonly used operations or modules in T24: TSA Services. What is a TSA Service? It stands for Terminal Service Agent and allows us to schedule a task to be executed within the core banking system. This task can, in turn, be defined as a set of smaller steps or jobs. It is beneficial as a solution for executing heavy or repetitive tasks.

Banking requires speed, reliability, and high availability. If you work with Temenos T24, you know how critical it is to keep operations running without interruption.

One topic that is rarely mentioned but extremely important in the world of APIs is the use of cache. To dive into the subject, let’s first understand what cache is. A cache is a mechanism by which an application temporarily stores API responses or data to reuse them in subsequent requests, thereby avoiding repeated calls to the server and improving performance, latency, and resource consumption.

To start the new year 2026 on the right foot, we have decided to begin this new post to share basic knowledge about T24, where we will review concepts, main structures, and other topics. In this first post, we will explain the main data component in T24: Applications. Application An Application is a structure used for data storage in T24. Applications perform field-by-field validations of the entered information and also allow the execution of functions such as leaving

Optimizar el rendimiento y reforzar la seguridad del core bancario es fundamental para cualquier institución financiera que utilice T24 Transact

Did you know that there is a tool to analyze the performance and configuration of your Transact environment? It is called Performance Health Review (PHR), and it is a tool provided by Temenos. It performs an overall analysis of your environment and delivers a report with recommendations.

This guide explains the configuration needed for Warmup and provides details about the supported applications. Warmup is used to accelerate the first transaction in a session.

The performance of your core banking system is essential to ensure high-quality service for your customers. More importantly, however, is ensuring that all their information and account access remain fully secure. Since one of the primary ways to expose your T24 banking services is via APIs, this section covers the key security mechanisms Temenos provides for your IRIS APIs.

When creating technological services, design often determines long-term performance and scalability. Even clients with robust T24 Core Banking systems may experience performance bottlenecks if the architecture isn’t properly designed.

This post dives into one of the most critical yet technical aspects of database maintenance in Temenos Transact: promoted columns within Data Lifecycle Management (DLM).

Learn how SEAT automates testing in T24 covering script creation, execution, result validation, and error tracking.

In T24 Core Banking, one of the most overlooked yet critical components is the TAFJ Lock Manager. It silently safeguards data integrity by managing concurrent access to records through pessimistic locking, which operates at both the process and database levels.

This blog explains the bulk payment workflow in T24, outlining how payment data usually uploaded via a CSV file—is processed through the FILE.UPLOAD application. Once uploaded, a MAIN bulk payment record and related ITEM records are created for each transaction.

Effective COB monitoring is essential for ensuring smooth overnight processing and timely service at the start of each banking day. Temenos Transact provides several enquiries and tools that give real-time visibility into COB operations.