Introduction to Messaging Framework
Temenos Payments requires a flexible and integrated framework to support all types of messages. Messaging Framework is a component of Temenos Payments that deals with validation, transformation, mapping and handling of the messages (XML, non-XML) in Temenos Payments, from and to the clearing or external systems.
- XML - Can be ISO20022 based or proprietary
- Non-XML – Text based formats that are fixed length records or with field de-limiters
Once the messages are mapped, the Temenos Payments processing engine processes the payments and books the payment or generates outgoing messages specific to the target system (such as, Clearing).
The framework is highly configurable and can be adapted to any Clearing by only mapping the messages to and from the Temenos Payments’ understandable formats. It is built using Apache Camel open-source integration framework and is available as an out-of-the-box solution.
Incoming Message Flow
Incoming Message Flow is the flow of messages received from the customer feeders or Clearings.
The functions performed in Temenos middleware are tabulated below:
Function | Description |
|---|---|
Input Folders or Queues or API | The framework can accept messages from the Clearings or customer feeders through folders or queues. Every folder or queue or API is linked to a logical queue |
Signature check | The framework provides a hook to extract the signature from the incoming messages and perform validation using a Keystore for integrity check before further processing |
Schema validation | The framework provides an in-built capability to validate XML messages using XSD’s and hooks to add validation API’s for validation of non-XML messages |
Checksum and control sum validation | Apart from above validation, it also has a provision to do checksum and control-sum validation at the file and bulk levels |
Message transformation | Once the message is accepted after validation, it is transformed to TPH understandable generic format (neutral format) using stylesheet (XSLT). TPH owns two neutral XML message formats:
|
Debulking | Debulks the message into individual transactions for posting to Temenos Payments for processing |
Exception Handling | The framework provides exception handling capabilities for any technical failures during message acceptance |
The functions performed in the TPH layer are:
- Determining Source and channel
- Checking Message Format
- Validating at Message Acceptance Layer in TPH
- Enriching at acceptance level
- Checking file duplicate
- Checking bulk duplicate
- Enriching at Mapping level
Outward Message Flow
The process of outward payment generation using outward message flow is described below.
The functions performed in Temenos payments are tabulated below:
Function | Description |
|---|---|
Clearing configuration for outward message generation | Based on the requirement of clearing, the bulking related fields can be configured by the user which decides the file generation |
Enrich outward generic format event | The framework provides enrich API using which the emitted neutral format can be enriched |
Message Transformation | It transforms the emitted TPH IF event to clearing specific format using XSLT |
Message Validation | It provides an in-built capability to validate XML messages using XSD’s and hooks to add validation API’s for validation of non XML messages |
Signature check | It provides hooks to generate and add the signature to outgoing messages |
Exception handling | Any error occurring in the middleware layer is captured in the payment system |
Output Folders or queues | The generated target message can be sent to the clearing or external system using folders or queues |
In this topic
