BulkPayment Processing for Corporate Client

Bulkpayment workflow

This blog presents the flow used for bulk payment processing in T24. It serves as a sample guide, and it is recommended to conduct a functional requirements analysis before implementing a final solution.

The flow focuses on uploading payment information, typically via a CSV file, into the T24 application FILE.UPLOAD. The logic then continues with the creation of a MAIN bulk payment record, along with corresponding ITEM records for each account to be credited.

Once the records are created, a T24 service picks them up and processes the payments, while also updating the status of each ITEM.

An enquiry must be created and exposed as a service to allow users to check the processing status of their payments, whether they were successfully executed or encountered errors. This enquiry should be available on-demand at the client’s request.

Once the uploaded bulk data has been validated by the user, individual items can be modified to correct account details or the batch can be authorised for payment.

Since this is usually a heavy processing task, a batch-oriented approach is recommended. The client side should only handle the task of uploading the required data, minimizing the number of requests made to T24 and avoiding synchronous processing wherever possible.

If the functional requirement demands a flow with synchronous processes, it must be ensured that these processes are lightweight or reporting-related only. The massive triggering of requests to an endpoint or keeping the client waiting for the response of a heavy process should be avoided.

If you need support to ensure an efficient architecture for mass payment services that also delivers a great user experience, don't hesitate to contact us. Our company specializes in optimizing performance for your core banking system.

Keep up the great work! Happy Performance Engineering! #T24 #TemenosTransact #BulkPayment #CoreBanking