How to Test The Temenos Payment Hub in T24
- Josef Mayrhofer

- 3 days ago
- 4 min read
Temenos Payment Hub (TPH) is a sophisticated payment module designed to streamline the posting and processing of transactions.
TPH is made up of two modules: PP, or payment processing, which is an end-to-end payment process from start to finish, and PI, or payment instruction, which is used to set instructions for executing the payment. The banks must choose both modules to fully deploy TPH. We must perform functional testing and related regression testing to test the TPH in T24. It entails the subsequent actions:
Identify Transaction Types to Test
Based on your integration context and typical TPH usage, include the following transaction types:
SWIFT Payments
Clearing Payments
Instant Payments
Direct Debits
Book Transfers
Bulk Payments
Inward Payments
Payment Amendments, Cancellations, and Error Handling
Fraud Check and Screening Integration (filtering and sanction screening)
Restriction, Fee, Reservation Posting, and Customer Status Reports (pain.002)
Multi-company Scenarios
Prepare Test Scenarios
For each transaction type, define functional test scenarios including:
Payment Initiation:
From channels or external systems
Via POA (Payment Order Application) in TPH
Payment Processing:
Validation of payment data and business rules
STP (Straight Through Processing) flow execution
Supervisor approval workflows for bulk payments
Integration Points:
Message routing and transformation
Interaction with external systems (screening engines, fraud check, clearing systems)
Accounting entries creation via FT or PEMINT interfaces
Error and Exception Handling:
Payment filtering failures and negative CSR processing
Handling of rejected or failed payments and corresponding reversal flows
Reporting and Status Updates:
Verification of status messages and reports
Confirmation of reservation and posting accuracy in Transact
Test Data Preparation
Create realistic test data sets for each payment type, including:
Valid and invalid payment orders
Bulk payment files with varying sizes and order types
Edge cases such as currency mismatches, insufficient funds, or blocked accounts
Multi-company payment scenarios, if applicable
Execute Functional Tests
Use TPH test tools or manual test execution to submit payment orders and bulk files.
Validate end-to-end processing
Payment acceptance and validation
Routing and transformation correctness
STP flow and approval processing
Integration with screening and fraud check systems
Posting and reservation in Transact via PEMINT or FT
Monitor logs and ENQ commands for processing status and errors.
Verify Outputs and System Behavior
Confirm that payments are processed according to business rules and SLA requirements.
Check that error scenarios trigger appropriate compensating actions (e.g., reversals, notifications).
Validate that multi-company postings are correctly routed and posted.
Ensure that bulk payment workflows, including amendments and cancellations, function as expected.
Verify that all integration points (screening, fraud, accounting) behave correctly.
Regression and Automation
Automate repetitive functional tests where possible using UPM tools or custom scripts.
Maintain regression test suites to validate new releases or configuration changes.
Sample transaction posting and viewing in TPH:
Sl No | Steps | Expected results |
1 | Log in with valid T24 credentials | Should be able to log in to T24 |
2 | Navigate to User
| Order Entry Outgoing Transfer screen will be launched |
3 | Enter the details below
Commit the Record Go to the record in view mode and note down the Transaction Reference Number BNKXXXXXXX | The record should be committed |
4 | Please ensure the following services are running in the background | PAYMENT.STPFLOW.HEAVY PP.INTERFACE.UPDATE SWIFT.OUT.LISTENERother related services |
5 | Navigate to Payment Operations
| Pending and Processed Payments screen will be launched |
6 |
| Payment Information The screen will be launched |
7 | Select 'Outgoing Message' in the dropdown Note: To process the transaction, the below services should be run CHECK.FILTER.STATUS.SERVICEPAYMENT.STPFLOW.HEAVY | MT103 message Information screen will be launched |
Load and Performance Testing in TPH:
Validate TPH system stability, throughput, and responsiveness under expected and peak transaction volumes, ensuring it meets SLAs and business requirements.
Test scenarios include single payments, bulk payments (up to 2000 orders), fraud and sanction screening, message routing, and approval workflows.
Tools Used:
Universal Performance Metrics (UPM) tools to simulate realistic business transactions and generate load.
Performance Health Checker (PHC) to monitor system resource usage and health during tests.
Execute Load and Performance Tests
Start with baseline low-load tests.
Gradually increase load to peak and stress levels.
Monitor CPU, memory, JVM, database, MQ, and network metrics continuously.
Capture detailed logs and transaction status for analysis.
Special Focus Areas:
Bulk payment processing impact.
Fraud and sanction screening latency.
Multi-company and multi-interface scenarios.
There are a lot of configurations in TPH, interlinked tables, and a sequence of steps to be followed to track the payment in each stage to understand the TPH flow. This is similar to FT while posting any transaction, but in order to track the status, we need to understand the complete setup.
Our experts help you with TPH training, TPH Implementation, and TPH testing in your bank. Get in touch with us at Performetriks if you need any support. We're always happy to assist.
Happy Performance Engineering!




Comments