Business monitoring, archiving and reporting of payments

Complete overview of all payments

The modular TRAVIC-Service-Cockpit provides financial institutions with an operating environment for all their payments. The monitoring, archiving and reporting functionalities of the cockpit ensure the trouble-free interaction of all connected products and at the same time fulfil the essential regulatory requirements.

Now available: payments as a service!

All TRAVIC suite products can be operated on-premises or in the cloud. Get in touch with us to learn more!

On the secure side

The mere transmission of data and execution of customer orders is by no means the end of the payments process. In this highly sensitive environment, many other work steps take place in the background – not least due to regulatory requirements. These requirements include:

Archiving of all relevant and processed data in the legally predefined manner, even over a longer period of time – from transactions and master data to customer and user authorisations
Traceability of all payments across all products
Availability of both legally required and institution-specific evaluations

In addition, business monitoring of the complete processing must be ensured – including warning messages in case of functional problems.

TRAVIC-Service-Cockpit – control station for payments

Schema of the data flow between TRAVIC-Service-Cockpit and payments processes
**TRAVIC-Service-Cockpit compiles information from the entire payments process**
Information from each individual step in the payments process is sent to TRAVIC-Service-Cockpit, where it is archived and used for control purposes or processed in reports.

PPI has geared this solution to the needs of financial institutions from the very beginning of its development. Accordingly, the core objectives were to increase customer satisfaction and efficiency by facilitating support workflows, to provide business monitoring of the payments systems and to reduce costs. Today, TRAVIC-Service-Cockpit has already proven itself hundreds of times in use. TRAVIC-Service-Cockpit is not a single piece of software but consists of six main components that can also be operated separately from the overall product in subgroups.

TRAVIC-Service-Cockpit – the main components

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.

APIs as a clamp

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.

Can we assist you?

Dr. Olaf Plähn

Product Manager

Contact

Dr. Hubertus von Poser

Head of Sales and Consulting Payments

Contact

You might also be interested in

TRAVIC-Retail

TRAVIC-Retail is the most powerful FinTS server on the market. It offers numerous access channels for online banking, many interfaces for banking connections, multi-client capability and individually expandable business transactions.

Learn more

TRAVIC-Corporate

Fail-safe, scalable, multi-client capable: TRAVIC-Corporate is the flexible, high-performance EBICS bank server for electronic banking in the corporate customer environment.

Learn more