EBICS API as communication module

The API for EBICS clients

With its multi-bank capability, EBICS has become an indispensable part of payments for corporate customers throughout Europe. Therefore, your customer systems and web solutions for online banking and electronic payments should also be able to communicate via EBICS. TRAVIC-EBICS-API takes care of this.

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!

EBICS communication made easy

A multi-talented tool – overview of the core features of TRAVIC-EBICS-API
**A multi-talented tool for connecting EBICS clients**
TRAVIC-EBICS-API can handle many versions, users and threads at the same time and is ideally suited for connection to the EBICS payments network.

The importance of the European communication protocol EBICS for customer-bank as well as bank-bank communication is steadily increasing. TRAVIC-EBICS-API implements the syntax and security procedures of the EBICS protocol for EBICS clients. The API can be integrated into the respective applications as a self-contained communication module. Manufacturers of e-banking and payments applications as well as platforms with banking functions can concentrate entirely on the technical development of their systems.

WebSocket interface for real-time notifications

TRAVIC-EBICS-API optionally supports real-time notifications according to Appendix 2 of the RDT agreement for EBICS by the German Banking Industry Committee (DK). With this function, EBICS clients can receive push notifications from financial institutions and, triggered by the WebSocket notification, automatically initiate EBICS download orders.

The following TRAVIC-EBICS-API variants are available for developing customer systems:

TRAVIC-EBICS-API as Java API supporting the EBICS versions 2.4, 2.5 and 3.0
TRAVIC-EBICS-API with C/C++ interface supporting the EBICS versions 2.4, 2.5 and 3.0