EBICS Client Architecture

Understanding the EBICS Client architecture will help you when using EBICS Client in Sterling B2B Integrator.

EBICS Client is deployed over Sterling B2B Integrator and reuses some of the following core functionality of Sterling B2B Integrator:
  • Creating and managing trading partner
  • Managing digital certificates
  • Creating and managing mailboxes
  • Creating users
  • Running services and adapters
  • Scheduling business processes
The following diagram illustrates the EBICS Client architecture.
Figure 1. EBICS Client architecture
The EBICS Client architecture diagram displays the elements in the EBICS Client architecture. The elements are, Subscriber, EBICS Client application, Sterling B2B Integrator and EBICS Client Schema, Sterling B2B Integrator Platform, Subscriber mailbox, EBICS Banking Server, Back-end that is used by a technical user to upload payloads.

The following sections describe the components of EBICS Client architecture.


A subscriber uses EBICS Client to perform bank transactions. The subscriber or user communicates with the EBICS Client application using the HTTP protocol to send and receive messages.

EBICS Client Application

EBICS Client application provides a dashboard interface to enable you to configure and manage the following EBICS entities:
  • User
  • Bank
  • Offers
  • File format
  • User permissions
  • Order submission
  • Pending tasks
  • Bank key validation
  • Keys
EBICS Client application interfaces with Sterling B2B Integrator and EBICS schema database to retrieve and store subscription and order related data.

Sterling B2B Integrator and EBICS Client Schema

Sterling B2B Integrator and EBICS Client schema tables are stored in a common database to enable the EBICS Client application to access the following data:
  • Native Sterling B2B Integrator data in Sterling B2B Integrator schema tables.
  • EBICS Client data in EBICS schema tables.

Sterling B2B Integrator Platform

The Sterling B2B Integrator platform on which the EBICS Client is deployed.

Subscriber Mailbox

The Subscriber Mailbox provides a safe access mechanism to send and receive messages between EBICS Client and EBICS Banking Server. The following mailboxes are configured for each user:
The EBClientOrderMetadata mailbox is a common mailbox associated to all users. OrderMetadata associated with a payload is posted in the EBClientOrderMetadata mailbox for processing the payload submitted by a technical or non-technical user.
Download (Inbox)
The Download mailbox is used for posting downloaded response in case of HEV order type and unpacked data in case of download orders.
Upload (Outbox)
The Upload mailbox is used for posting the payloads.
When an upload (FUL) order type is submitted, the payload is routed to the Upload mailbox and the related OrderMetadata is routed to the EBClientOrderMetadata mailbox. The arrival of an OrderMetadata in the EBClientOrderMetadata mailbox, either for an upload (FUL) or download (FDL) order type, triggers an EBICS Client request workflow.


A Sterling B2B Integrator adapter that can trigger the EBClientOrderPreProcess business process is used to submit orders automatically from the back-end.

EBICS Banking Server

The EBICS Banking Server is installed in a bank. EBICS Client communicates with the EBICS Banking Server application using the HTTP or HTTPS protocol to send and receive information about users, trading partners, digital certificates, order data, file formats, and order types. For more information about EBICS Banking Server, see the Sterling B2B Integrator EBICS Banking Server documentation.