Why T24 Became Temenos Transact

At some point in your career you were in a meeting where someone said “Temenos Transact” and you said “T24” and a project manager from a consulting firm suggested you should probably align on terminology going forward. You nodded. You went back to your desk. You kept calling it T24.

You are not wrong. But the name change was not entirely arbitrary either. There are real reasons behind it — some architectural, some commercial, some that have more to do with slide decks than actual software. This article explains all three.

The name that made sense in 1999

T24 got its name from a specific promise: 24-hour, around-the-clock banking. When that name was coined, continuous availability was a genuine differentiator. Most bank systems ran batch processes overnight and were inaccessible outside business hours. A core banking system that could handle transactions around the clock was a credible claim to make.

By 2019, 24/7 availability was not a selling point. It was a minimum expectation. Naming your flagship product after a feature that every competitor also offered was no longer positioning — it was just a product code.

The name had also become difficult to extend. T24 referred to a single product. Temenos was trying to sell a family of products. “T24 Payments” and “T24 Wealth” sounded like modules bolted onto one system. “Temenos Payments” and “Temenos Wealth” sounded like a portfolio. The language was shaping commercial conversations in the wrong direction.

What actually changed — and what did not

Let us be precise about this, because the answer is less dramatic than the marketing materials suggest.

What changed: The product name, the documentation terminology, the way Temenos presents it in sales materials, and the packaging of the product portfolio.

What did not change: The underlying BASIC codebase — now compiled via TAFJ — the file structure, the application names, the COB architecture, the way OFS messages work, the way AA products are built, the way developers actually spend their working day.

If you were a T24 developer on 1 January 2020 and you became a Temenos Transact developer on 2 January 2020, your morning looked identical. You opened the Browser. You worked with the same applications. The same error codes appeared. The same COB jobs ran overnight. The rebrand happened at the brand level. It did not reach the code level.

This is both reassuring and slightly absurd, which is the normal ratio for enterprise software rebranding exercises.

The product family behind the name

The more substantive change was not the name itself but the product architecture the new name reflects. Temenos restructured from a single-product company toward a product family model:

• Temenos Transact — the core banking engine (formerly T24)
• Temenos Payments — the payments hub (TPH and related products)
• Temenos Wealth — wealth management suite
• Temenos Digital — digital and self-service channels
• Temenos DataSource — data and analytics
• Financial Crime Mitigation — compliance and screening

The idea is that a bank should be able to take any of these components independently. A bank that already has a core banking system might only want Temenos Payments. A bank building digital channels might want Temenos Digital connecting to its existing core. You cannot sell that story under a name that implies everything lives inside one monolith called T24.

Whether banks are actually deploying them as fully independent components is a more complicated conversation. But the architecture is moving in that direction, and the naming reflects the intent.

The architectural changes that matter more than the name

Behind the rebrand is a real technical evolution that has been in progress for years, and which is more relevant to professionals working with the system than any name change.

TAFJ

The move from the interpreted TAFC runtime to Java-compiled code is the most operationally significant change most T24 teams have dealt with. This is not cosmetic. It changes how code is deployed, how debugging works, how monitoring is done, and how performance is tuned. The TAFC to TAFJ migration is the rebrand that actually matters to people doing delivery work.

API-first design

Temenos has been progressively opening Transact through REST APIs. The Interaction Framework became the API Framework. The direction is toward Transact as a headless core, consumed by external applications via API rather than exclusively through the Browser UI. This is a genuine architectural shift — not just a terminology update.

Microservices

Temenos has built a microservices layer around certain capabilities, particularly in Payments and Wealth. The Business Microservices suite allows specific functions to be decomposed and deployed independently from the monolith. This is early-stage for most banks, but the direction is clear.

Temenos Banking Cloud

SaaS deployment of Transact, managed by Temenos on major cloud platforms. For banks that want to outsource the infrastructure and focus on configuration rather than hosting, this removes the version-upgrade burden and moves toward a continuous-delivery model. No more big-bang upgrades every two or three years. For consultants and contractors who have built careers around upgrade projects, this changes the nature of the work available.

What experienced professionals should actually think about this

If you have been working with T24 for ten years, the rebrand itself requires nothing from you. Call it T24 if that is what feels natural. Every experienced person you work with knows exactly what you mean. The system is the same system.

Where the name change does matter is in how you talk about it to stakeholders making decisions about deployment, integration, and architecture. Temenos's commercial direction is toward cloud-native, composable, API-first banking. If you are advising a bank on Transact architecture, ignoring that direction means your advice will age badly.

Pay attention to TAFJ if you have not already. The TAFC runtime is not where Temenos is investing. New features, performance improvements, and cloud-native capabilities are being built for TAFJ. Banks that have not completed the migration are accumulating technical debt against a platform that is being left behind in the tooling and documentation.

Understand OFS and API coexistence. Banks that have been on T24 for years have extensive OFS-based integration. As they modernise, those integrations need to be mapped to REST API equivalents. Knowing both layers — OFS for legacy interfaces, REST APIs for new development — is the relevant skill set for Transact professionals going forward.

The upgrade model is changing. Traditional T24 ran on major releases with significant upgrade projects. Temenos Banking Cloud moves toward continuous updates. Banks that move to SaaS are no longer running their own upgrade projects. This changes what the delivery work looks like and where the demand for experienced professionals is moving.

The honest version

Temenos renamed T24 to Temenos Transact because the brand strategy required a product portfolio that could be sold in parts, the old name was anchored to a 1990s value proposition, and enterprise software companies rebrand their products every decade or so regardless.

The underlying system is largely the same. The TAFJ migration is the most disruptive technical change, and it has nothing to do with the name. The architectural direction — cloud-native, API-first, composable — is real and worth taking seriously, but it is a multi-year journey that most banks are somewhere in the middle of at best.

If someone in a meeting corrects you for saying T24 instead of Temenos Transact, nod pleasantly and carry on. The people who actually built and operate this system have been calling it T24 for twenty years and will be calling it T24 for the foreseeable future.

The name on the box changes. The box stays the same.