Integration layer:
This core component is always required, even in case of a separation into different variants. It collects the information provided by the individual payments products and transfers it to the respective components for further processing.
Long-term archiving with three data stores:
The payment data store (PDS) stores all operational data such as transaction flows, payments and messages as well as returns/recalls or split collector files, across all products. The contract data store (CDS) contains all administrative data as well as changes to it. This includes, for example, the specific customer master data of the payments products or the authorisation information about support users with regard to access rights to the systems. All objects that do not meet any of the criteria of PDS and CDS are archived in the object data store (ODS). This applies, for example, to reports, images and documents.
Statistics and reports:
Information that can be used for reports is stored in a structured way in the reporting database. In terms of content, this data is predominantly transaction-based and in turn originates from the processes and workflows of the connected payments products. Classic examples would be payments statistics or transaction messages.
Business activity monitoring (BAM):
This main component is used for the event-based monitoring and intelligent control of payments business monitoring. BAM analyses events from the operational processing of the connected products and filters out those that indicate a need for additional manual action. This information is transferred to a support software so that the related support agents can act in time.
The technology of TRAVIC-Service-Cockpit consists of various software artifacts connected via a modern event-based API architecture. In a way, it forms a clamp that wraps itself around the payments applications. This makes the solution maximally configurable and scalable as well as expandable by modules.
The highly modern system uses applications such as Kafka, Elasticsearch, S3 and, of course, container technology. A cloud operation is therefore possible without any problems.
