Integration with T24 to route SMSs/Emails etc.

Hi,
           Our tech. team is somewhat bamboozled by this requirement due to the Banking system integration involved. I believe it is a system integration question. Let us say an internal banking system is being built today. The Core Banking Data can be synched. with this internal banking system using various methods. I have added some( I am not a Banking Integration Expert ).
1. Synch. Internal DBs and T24 data.
2. Synch. Kafka( or other toolsets like Hive etc. ) with T24 data.
3. Some other integration.

There are various compliance and Data Governance regulations I am missing here but that is the general idea.
Now the advent of distributing computing toolsets like Cassandra, Kafka, Cloud Messaging and the Cloud ecosystem( This is not a Cloud Integration question ) make it easy to move away from T24 as far as the notifications are concerned. Now these are my preliminary questions.

1. Can I look at BFS use cases that have integrated SMSs or any such notification from T24 with more advanced distributed Computing tools mentioned above ?
2. What are the pitfalls I should be aware of when T24 owns the data and the trigger but SMSs are supposed to be sent by tools like Kafka etc. ?
3. Does T24 integrate with IBM MQ easily to push SMSs ? Does T24 integrate with customized SMS templates by pushing to IBM MQ ?

Thanks

1. Can I look at BFS use cases that have integrated SMSs or any such notification from T24 with more advanced distributed Computing tools mentioned above ?

The SMS and EMAIL is formatted by DELIVERY Application. Formatted message (XML) is sent using DE.CARRIER/INTERFACE with attached valid EB.API routine (Jbasic/JAVA). This routine calls a JAVA application (jar file came from temenos)

You can configured the jbase program/JAVA on DE.CARRIER/INTERFACE Application and create your own as per your requirement. When routine is not specified, you can processed the message that is stored table by batch

You can also explore the other interaction interface available like Temenos Web service (Retrieve the message using exposed wsdl) or IRIS R18 (REST)

2. What are the pitfalls I should be aware of when T24 owns the data and the trigger but SMSs are supposed to be sent by tools like Kafka etc. ?

Can you be more elaborate on how t24 owns the data?

3. Does T24 integrate with IBM MQ easily to push SMSs ? Does T24 integrate with customized SMS templates by pushing to IBM MQ ?

Email/SMS is formatted using DELIVERY Application. You can format raw data, and let your middleware application reformat based on your requirement. By default, DELIVERY handles formatting (based on language and interface)

P.S. The EMAIL and SMS data is formatted using DELIVERY Application, stored on relevant table and processed by T24 Batch Service. This Batch service can processed message in bulk or realtime message

When you have database like SQL or oracle, you can still pickup the formatted message on that table and processed using your 3rd party application

Let me gave you an example, our bank requires a business event/alert for certain transactions (E.g Cash deposit. Cash withdrawal etc) and sent the message using json format on our middleware interface. Our middleware interface will sent the relevant message using sms/email based on user profile configuration setup on our online banking

Since we are not using the EMAIL and SMS interface of t24, this can be achieved using the generic delivery interface . I've created my own interface (DE.CARRIER/INTERFACE), attached a jbasic program that transform the XML to JSON and passed the data on JAVA application (jar) on our middleware/

This is pretty similar on T24 approach, the only difference is the java application of temenos accept XML and send data on EMAIL/SMS based on standard email and sms config. My application accept json and send on our own interface using exposed API link

Hello,
             Ours will most probably be a Kafka MQ Connector to pull from MQ which receives the value placeholders. We are still not sure where the phone numbers of customers
are in the internal banking system. If Kafka gets the value placeholders and template( which we have ) it can format and send to the SMS Gateway. 
We are not envisaging a batch system. It looks like a Streaming system using Kafka Streams library in the consumer group. Our weak point is the Kafka MQ Connector. How do we get the rough throughput ?  Is the general data based on customers etc. ? That pipe could be a bottleneck.
Otherwise we have to push to the DB and pick it up using Change Data Capture tools like Debezium. Either way there is no direct intergration between MQ and Kafka.

Thanks.

. We are still not sure where the phone numbers of customers

On Customer Table/Application

are in the internal banking system. If Kafka gets the value placeholders and template( which we have ) it can format and send to the SMS Gateway. 
We are not envisaging a batch system. It looks like a Streaming system using Kafka Streams library in the consumer group. Our weak point is the Kafka MQ Connector. How do we get the rough throughput ?  Is the general data based on customers etc. ? That pipe could be a bottleneck.
Otherwise we have to push to the DB and pick it up using Change Data Capture tools like Debezium. Either way there is no direct intergration between MQ and Kafka.

Im not familiar on any interface you you said.

Lets be clear on your requirement,

What info do you need from t24?
1. Customer Info like Email and mobile phone numbers only?
2. Business events - When there is a cash deposit happened, an alert will be sent to customer via email/sms?
 This included raw data (E.g Transaction amount date) or formatted message + Customer info (Email,SMS) 

This presume that you are going to retrieve the Email,SMS from T24, There are instances that this info can retrive on your online banking

Also how do you want to get this info
1. T24 will send/push this info (Email,sms and any relavant data) on your interface
2. Your interface will request this info(Email,sms and any relavant data) from T24 via  WSDL/API

1. Customer Info like Email and mobile phone numbers only?

Yes

2. Business events - When there is a cash deposit happened, an alert will be sent to customer via email/sms?
 This included raw data (E.g Transaction amount date) or formatted message + Customer info (Email,SMS) 

This presume that you are going to retrieve the Email,SMS from T24, There are instances that this info can retrive on your online banking

Formatted message including raw data (Email,SMS) 
In our banking systems Emails are owned by CRMNext.
SMSs need phone numbers. Where will they be ? Our MQ receives raw SMS data. We plan to route it internally and format it.

Also how do you want to get this info
1. T24 will send/push this info (Email,sms and any relavant data) on your interface
2. Your interface will request this info(Email,sms and any relavant data) from T24 via  WSDL/API

Our MQ receives raw SMS data.

Formatted message including raw data (Email,SMS) 
In our banking systems Emails are owned by CRMNext.

Does CRMNext also hold phone numbers? OR
Does CRMNext pulls data from T24 or CRMNext push data on T24

T24 phone and email is saved on CUSTOMER Table which is not mandatory 

As explained on previous comment, Formatted message is handled by DELIVERY Application, this included all the relevant details (Raw data or formatted message + Email and Phone number ) which is automatically pulled from customer (based on Customer preferences setup on T24 whether he want to receive via SMS/EMAIL or both) and it will send on your respective carrier (E.g MQ)

In our banking systems Emails are owned by CRMNext.

So right now does T24 send formatted message to your interface (CRMNext or MQ) which contains email info?

Our MQ receives raw SMS data.

Let me repeat

1. T24 will send/push this info (Email,sms and any relavant data) on your interface (E.g MQ)
2. Your interface (E.g MQ) will request this info(Email,sms and any relavant data) from T24 via  WSDL/API

2. What are the pitfalls I should be aware of when T24 owns the data and the trigger but SMSs are supposed to be sent by tools like Kafka etc. ?

You can send a message from T24 

1. to your prefered interface (E.g Kafka/ MQ) OR
2. retrieved by your interface(E.g Kafka/ MQ) OR
3. retrieve the message on Database (SQL/Oracle)

You can get the Phone Number and Email from CUSTOMER Table or this can be included on the message to be send on interface (E.g Kafka/ MQ).

 Does T24 integrate with customized SMS templates by pushing to IBM MQ ?

Using Delivery Module,
1. you can format the message and send on your interface OR
2. your interface can format the message which raw data came from T24

I am addressing your key points here. I hope. We miss the crucial context related to a bank's operating model.

As explained on previous comment, Formatted message is handled by DELIVERY Application, this included all the relevant details (Raw data or formatted message + Email and Phone number ) which is automatically pulled from customer (based on Customer preferences setup on T24 whether he want to receive via SMS/EMAIL or both) and it will send on your respective carrier (E.g MQ)

The customer preferences are in T24 according you. How does it get there ? In our modernized stack a Kafka topic will hold the preferences. Where is this customer table ?
Obviously we can't store the preferences in 2 locations. It appears that the user can send his preferences and instead of updating T24 we store it ourselves.
Could you point out a diagram of how T24 stores preferences and the customer table ? Does the data governance rule stipulate that preferences, email IDs and phone numbers should go into T24 only ?

Does CRMNext also hold phone numbers? OR
Does CRMNext pulls data from T24 or CRMNext push data on T24

CRMNext stores emails only. This isn't a mirror of anything in T24.

Are you aware of any diagram showing how the integration with MQ works ? I can extrapolate and include Kafka.

The customer preferences are in T24 according you

Yes however sending EMAIL/SMS is not dependent on this setup. There is a minimal setup for you to use the DELIVERY application.

The customer preferences are in T24 according you. How does it get there ? In our modernized stack a Kafka topic will hold the preferences. Where is this customer table ?
Obviously we can't store the preferences in 2 locations. It appears that the user can send his preferences and instead of updating T24 we store it ourselves.
Could you point out a diagram of how T24 stores preferences and the customer table ? Does the data governance rule stipulate that preferences, email IDs and phone numbers should go into T24 only ?

Phone number and email is stored on CUSTOMER table. However it is not required when sending alert/notifications on your interface. that information can be stored on your external Application

What exactly info do you need from t24?
1. Customer Info like Email and mobile phone numbers only?
2. Business events - When there is a cash deposit happened, an alert will be sent to customer via email/sms?
 This included raw data (E.g Transaction amount date) or formatted message + Customer info (Email,SMS) 

CRMNext stores emails only. This isn't a mirror of anything in T24.

Great, Email/Phone number is not required on t24 

Are you aware of any diagram showing how the integration with MQ works ? I can extrapolate and include Kafka.

diagrams and userguides is available on docs.temenos.com and tcsp.temenos.com. Also there is a user guide included when the core banking was deployed on your site

Our Customer Communication Platform - CORBAN from Nayamsoft, works natively with all flavours of T24 and supports traditional and modern channels like SMS, EMAIL, WHATSAPP, TELEGRAM, PUSH, etc.It's a scalable platform built on cloud native technologies for the modern banking needs

• Unlimited Static, Transaction and Periodic alerts
• Customizable business rules to notify Customers & Internal Users
• Bulk Alerts support for seasonal greetings, Anniversary wishes, etc
• Personalised individual alerts to the Customers
• Multiple languages support to send alerts in local languages
• Managed queue processing to handle heavy loads
• Scalable cloud native microservices architecture that can be deployed on premises or cloud.

This email address is being protected from spambots. You need JavaScript enabled to view it. | +91 8248471354
www.linkedin.com/feed/update/urn:li:acti...:6923633876691038208