CWBI EBICS Connector
The Electronic Banking Internet Communication Standard (EBICS)
EBICS, the Electronic Banking Internet Communication Standard, represents a standardized, bank-neutral transmission protocol developed by the German Banking Industry Committee, which is now widely used in Germany, France, and Switzerland, as well as in other countries of the European community.
EBICS is an open TCP/IP communication protocol for SEPA exchanges, not only between customers and banks but also between banks and Clearing & Settlement mechanisms. They can use EBICS to exchange financial messages with each other, such as corporate payment transactions, between an organization and a bank.
In terms of benefits, EBICS is a solution that offers:
- A single, common and open standard for corporate-to-bank communications – both the technical details of the data transfer, as well as the particulars regarding permissions and order types are standardized in EBICS;
- An underlying technology (XML, HTTPS, TLS, and SSL) that is globally recognized and conforms to industry standards;
- The highest security of messages through electronic signatures and certificates with encryption at transport and application level, offering an end-to-end trusted solution;
- A single access for all business transactions and the ability to process high volumes, including direct debits, credit transfers, and account statements;
- A SEPA compliant protocol that can support industry standard formats such as ISO 20022 XML and SWIFT MT messages (MT101 and MT940);
- A neutral platform that allows data files to be exchanged regardless of standards and message formats, and which is interoperable within the global marketplace, as well as being sustainable and scalable to future market requirements.
As such EBICS is an alternative to Host-to-Host (H2H), manual file uploads or SWIFT.
EBICS 3.0, which went live in November 2018, allows banks to provide access for multiple countries based on one standardized and fully harmonized infrastructure that can also be used for clearing access for Single Euro Payments Area (SEPA) payments.
What improvements does EBICS 3.0 bring?
- Complete interoperability between the implementations from different countries, with cross-border EBICS communications;
- Simplified configuration and implementation;
- Accelerated processing and automatic verification of data during the transfer.
CWBI EBICS Connectivity Solution
CWBI, recognized as Frontrunner Service Provider for the supply of EBA CLEARING’s RT1 Instant Payment solution (whose characteristics offer the option of using either the SIANet network or the EBICS network), and the first provider to implement a SCT Inst exchange message solution on EBICS, proposes its modular solution that can be integrated into any client architecture, by using HTTP (REST) and/or Code MQ protocols for message exchange.
The CWBI EBICS Connector offers the possibility of:
- interconnection between group banks via EBICS 3.0 or EBICS 2.5 protocol (FR and DE version);
- interconnection to EBA CLEARING STEP2 Intraday Switch.
The solution is available in two options: On-Premises Mode (installed at client’s facility) or On-Service Mode (used via REST Web-services, MQ, File Transfer, etc.).
In order to minimize the interventions required from the client’s side, the recommended implementation is On-Service Mode, illustrated below.
How does it work?
To facilitate the client set up, the process of adopting this solution was made fast and simple: after the EBICS Connector is activated, it allows the bank to connect to CWBI system.
The exchange of messages between the bank and CWBI takes place:
- Through https protocol and signature of the body of the messages exchanged;
- Through MQ protocol on the VPN connection between the bank and CWBI.
In order to assure a smooth implementation, the bank’s activities are limited to a minimum, like to define the integration process from FTP, REST Interfaces, MQ Server OVER VPN.
For the configuration and the monitoring activities of the exchanged messages, the bank operators can log in to the administrative console using the credentials (login + password + OTP).
For more information, get in touch with us in the Contacts section.