top of page

How to integrate T24 Core Banking into your existing banking landscape?

Banking transactions are entirely automated these days. However, looking closely at trade transactions, portfolio overviews, account statements, or payments, we notice that everything is connected, and insights must be available in real time.

During the design phase of your core banking integration, you must make critical decisions that could impact the performance and reliability of your entire system. Typically, you have to select one of these integration scenarios

  1. API level

  2. MDB and EJB

  3. IF

  4. IRIS

API level

Your 3rd party application uses the available OFS API to send and query data from the T24 core banking engine. From a performance perspective, we see the following problems

  1. OFS API issues

  2. Validation

  3. Version related problems

  4. Design of enquiries

  5. Wrong usage of events

If API level integration is your choice, please remember that response times depend on the number of parallel requests.

MDB and EJB Integration

Message Driven Beans and Enterprise Java Beans provide a flexible way for all integrations. You specify a port and IP and describe the mapping configuration in application server configuration files.

Integration Framework

When software components talk to each other, we use the Integration Framework. There are two types of these integration frameworks

  1. IF inbound to publish content to an Enterprise Service Buds

  2. IF outbound to expose business services or native messages

Interaction Framework

When users interact with T24, we use the Interaction Framework. It uses the OData protocol and follows a RESTful mindset allowing us to execute GET, PUT, POST, and DELETE requests. The benefit of this interaction framework is that we can access all core banking services and fully decouple user interfaces from T24.


No matter which integration approach you to select, be aware that such design decisions significantly impact your banking applications' reliability. Furthermore, choosing the wrong integration can dramatically increase development and maintenance costs.

Please get in touch with us anytime if you have questions or additional insights. We are here to support your core banking projects.

Happy Performance Engineering!

145 views0 comments


bottom of page