🔗Integration
OFS, SWIFT, MQ, APIs, file interfaces, and event-driven architecture — how T24 talks to the outside world and what breaks when it does not.
15 articles in this topic.
T24 fundamentals
OFS is how the outside world talks to T24. A plain-English introduction to the message structure, request types, OFS.SOURCE configuration, security, and what breaks when integrations go wrong.
Read the articleT24 fundamentals
A plain-English introduction to SWIFT messaging in Temenos T24 — what SWIFT actually does, how messages get in and out, what MT and MX mean, and why your payment is stuck in a repair queue.
Read the articleIndustry shift
The SWIFT MT to MX (ISO 20022) migration is coming for retail banks. What changes, what stays the same, and what T24 teams need to do before the deadline.
Read the articleInfrastructure
A high-level look at running Temenos Transact in containers, orchestrating TAFJ workloads with Kubernetes, and migrating to AWS, Azure, or Temenos Cloud.
Read the articleArchitecture
An overview of API patterns in Temenos Transact — from classic OFS and SOAP to the modern Temenos Integration Framework (IRIS) and REST APIs, with guidance on when to use each approach and how they compare to event-driven integration.
Read the articleIntegration architecture
A practical guide to T24's three integration paradigms — OFS for real-time, APIs for modernisation, and batch for volume — with decision criteria for each.
Read the articleIntegration architecture
How IBM MQ and other message queue technologies integrate with T24 for reliable, asynchronous, and guaranteed-delivery messaging patterns.
Read the articleIntegration architecture
How T24's event-driven architecture works with IRIS, Kafka, and publish-subscribe patterns to enable real-time integration.
Read the articleIntegration architecture
How T24 integrates with mainframe and legacy host systems — the protocols, patterns, and practical realities of connecting old and new.
Read the articleIntegration architecture
Why flat files, CSV exports, and batch file transfers remain the backbone of T24 integration — and why they are not going anywhere.
Read the articleIntegration operations
When the ActiveMQ Artemis paging-store directory grows during TAFJ operation, the first question is whether it is expected or a signal of a deeper issue. A practical guide to reading the evidence safely — queue metrics, consumer checks, safe containment, and when to escalate.
Read the articleIntegration & Production support
A systematic diagnostic sequence for tracing a failed OFS request from entry point to T24 processing — transport, authentication, syntax, validation, posting, and response-delivery failure stages, with log sources and redaction guidance.
Read the articleIntegration support
A systematic diagnostic sequence for when a T24 messaging queue has depth but no consumer is processing — distinguishing inactivity from connectivity, channel, application, retry, and dead-letter conditions.
Read the articleIntegration troubleshooting
When an E-Advice PDF arrives with the wrong content — or no content at all — the problem is almost never the PDF itself. A systematic guide to diagnosing parser errors caused by unexpected response content, covering response type, headers, encoding, upstream error pages, document generation, and transport.
Read the articleOFS troubleshooting
Diagnose T24 OFS response failures by transport, authentication, syntax, validation, authorisation, posting, and response-delivery stage.
Read the article