Start here: EBICS

Windows/Unix

EBICS, Electronic Banking Internet Communication Standard, is a B2B transport protocol used most notably in Germany and France for bank-to-client transmission as well as inter-bank clearing processes. EBICS shares many similarities with the ETEBAC 3 protocol, but is based on an IP network as opposed to X.25. Additionally, EBICS can use HTTP with TLS encryption (HTTPS) for data transport.

When discussing EBICS implementation in Transfer CFT in this document, all types of financial institution are generically referred to as banks. Subscriber refers to bank customers or clients.

General architecture

Axway Transfer CFT is positioned as the client in this Client-to-Server schema and manages subscriber exchanges with the bank's EBICS server.

Subscriber initialization

To use EBICS for bank exchanges, subscribers must go through a series of steps to enable and secure bank interactions. The following flow chart displays a simplified version of the process. As you work through the tasks described in the General implementation topic, details and specifics are provided.

Step overview of subscriber initiating the process by sending keys to EBICS bank server

Related topic

General implementation: EBICS

Related Links