26/03/2025, 17:53 Introduction to TPH Interfaces

 Guides   
Introduction to TPH Interfaces
 Updated On 08 November 2024 |  7 Min(s) read  Feedback
Temenos Payments interacts with many transact applications, external bank host systems and clearings and payment gateways to successfully process a
payment request and to send outward payment messages to the recipient. This guide describes the different modes of interfaces of Temenos Payments.

Temenos Payments can be integrated with the banks’ channels to:

Initiate payment requests online or offline.

The diagram below depicts the various interface touch points to Temenos Payments and the associated message formats.

The table given below defines the Temenos Payments Interfaces.

https://docs.temenos.com/docs/Solutions/Installation/TPH_Interfaces/TPH_Interfaces/Misc/Introduction.htm# 1/3
26/03/2025, 17:53 Introduction to TPH Interfaces

Interface Description

Online Channels Customer-facing channels that interface with Temenos payments for payment processing. The interface method used is APIs.

Offline or External bank channels that send payment requests in the form of pain.001 (either a single or bulk payment).
Straight-Through
Processing (STP)
Channels

Interaction Temenos Transact framework that is used for all interactive interfaces. Bank’s online channels can send API requests directly to
Framework (IRIS) Temenos Payment Hub (TPH) or through POA and/or Debit Collection Application (DB). IRIS performs the following functions.
Acts as an API gateway for external or internal applications to call-in to process payment requests and enquire on payment
statuses using published APIs.
Enables banks to interact with any API based clearing gateways for sending out and receiving response for payments.

NOTE:
IRIS internally uses Open Financial Service (OFS) for communication.

Integration Temenos Transact framework that is used by Temenos Payments to receive and send messages in ISO XML format. This can be used
Framework by bank’s STP channels to send messages for payment initiations and to receive status reports.
(CAMEL)

Incoming message The messages are received by TPH through CAMEL layer in an asynchronous mode of communication. The CAMEL layer polls the
incoming message queue, performs syntax validation (XSD validation in cases of XML messages), file duplicate checks, validates
digital signature, and transforms the message to a Temenos Payments neutral format. The message is then post by the CAMEL layer
into incoming queue where TPH listens to and picks messages.

Outgoing message TPH emits payment messages in a proprietary XML format and post into outgoing queue. The CAMEL layer transforms the messages
in to target format, performs XSD validation, applies digital signature if configured to do so, and pass the payment to the respective
clearing gateway.

Debit Collection DB validates and routes the requests received from branch or back office using standard Temenos Transact Interface to Temenos
Application (DB) Payments. It performs the following functions.
Capture DD collection requests (manually)
Validate and pre-process DD requests
Route the DD requests only to Temenos Payments system

DB supports capturing collection request for different types of clearings, such as Automated Clearing Houses (ACH) and Instant
Payments. It supports only creation and capture of single Direct Debit (DD) collection requests. Debit Collection module receives
API based payment requests from online channels through IRIS layer and forwards the request to TPH for processing.

Payment Order POA is an integral part of the Temenos Payments Solution and Temenos Transact core banking suite. This handles order capture,
Application (POA) management functionality and supplements the payments processing engine. The key features of POA are as follows:
Interfaces with a variety of payment initiation channels, both in interactive and STP modes. Initiation channels include
customer facing and electronic feeder channels (STP), bank’s branch or potentially in-house bank host systems that can raise a
payment request.
Performs order validation, pre-processing and storage until processing date.
Performs manual repair and release for payments in exception.
Helps in routing of the orders to appropriate payment system based on payment characteristics.
Generates payment status reports, and customer advice and alert notifications

POA receives API Payment Initiation requests or Message based Payment Initiation requests from Online/STP channels and sends
the payment requests to Temenos Payment Hub. It uses OFS mode for communication. Read Payment Initiation guide for more
information.

https://docs.temenos.com/docs/Solutions/Installation/TPH_Interfaces/TPH_Interfaces/Misc/Introduction.htm# 2/3
 26/03/2025, 17:53 Introduction to TPH Interfaces

Interface Description

Master Data MDAL acts as a microservices gateway through which Temenos Payments fetch account and party related information from
Access Layer Arrangement Micro Service (AMS) that holds accounts static information and Party Micro Service (PMS) that holds customer static
(MDAL) information respectively. TPH sends request and receives response through MDAL from AMS and PMS for account and party related
information. When TPH is deployed with TRANSACT as a sub-system (Microservices are not used), MDAL methods is an internal call
within TRANSACT to get account and customer static information during payment processing. Read Microservices and MDAL for
more information.

Temenos Delivery It offers Temenos Business modules a framework to exchange the ISO20022 messages with a SWIFT messaging interface,
Module supporting the main elements of the SWIFTNet Interact message structure. Temenos Payment Hub uses the Delivery capabilities to
send or receive Interact messages to SWIFT Alliance. Read Temenos Delivery Module for more information.

Sending and Receiving ISO XML Messages

When a bank or financial institution uses Transact as the core banking system, the orchestration of events emitted by TPH through CAMEL layer is handled
by Payments External Messaging Interface (PEMINT) module out of the box. Here, client does not need any integration to consume the integration events. In
the case of a non-Transact core banking system, the client needs to develop integration for consuming various integration events emitted by TPH and
provide responses.

When deployed with Transact, banks must have an additional license called PEMINT installed in Temenos Transact instance for Temenos Payments to
operate with the Temenos Transact core banking. The PEMINT module provides out of the box integration of Transact with Temenos Payments (through
Integration Framework – CAMEL) to enable DDA operations in Transact required for Payments processing.

https://docs.temenos.com/docs/Solutions/Installation/TPH_Interfaces/TPH_Interfaces/Misc/Introduction.htm# 3/3