Pragma Edge — Powering your connected enterpriseLet's connect ↗
PRAGMA EDGE / BLOG

Sterling B2B Integrator - EBICS Client Architecture and Key Features

Electronic Banking Internet Communication Standard (EBICS) is an Internet-based communication and security standard. EBICS is a European banking standard. EBICS is primarily used for remote data transfer, such as corporate payment…

The EBICS Client architecture and key features section provides an overview of the EBICS Client architecture and describes the key features of EBICS Client.

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

EBICS Client is deployed overSterling B2B Integratorand 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.

The following sections describe the components of EBICS Client architecture.

Subscriber

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 withSterling B2B Integratorand EBICS schema database to retrieve and store subscription and order related data.

Sterling B2B Integrator and EBICS Client Schema

Sterling B2B Integratorand EBICS Client schema tables are stored in a common database to enable the EBICS Client application to access the following data:

  • NativeSterling B2B Integratordata in Sterling B2B Integratorschema tables.
  • EBICS Client data in EBICS schema tables.

Sterling B2B Integrator Platform

TheSterling B2B Integratorplatform 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:

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.

Back-end

ASterling B2B Integratoradapter 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 theSterling B2B Integrator EBICS Banking Serverdocumentation.

EBICS Client consists of two major components: EBICS Client Graphical User Interface and EBICS Client Runtime. Both the components use mailboxes (Upload, Download, and EBClientOrderMetadata) assigned to the individual subscribers.

When a subscriber posts an EBICS request, the EBICS Client Business Process picks the posted request from the Upload and EBClientOrderMetadata mailboxes and based on the order type request, delivers the request to the EBICS Banking Server. The response received from the server is processed according to the order type and is posted to the subscriber Download mailbox.

The following diagram illustrates the components of EBICS Client.

The following sections describe the components of EBICS Client.

EBICS Client Graphical User Interface

EBICS Client Graphical User Interface consists of the following components:

EBICS Client Runtime

EBICS Client Runtime consists of the following components:

Mailbox

The mailbox component interfaces between the EBICS Client Graphical User Interface and EBICS Client Runtime components. EBICS Client uses the following mailboxes to store and process order request and responses:

  • EBClientOrderMetadata. This is a common mailbox associated to all users.
  • Download (Inbox)
  • Upload (Outbox)

Separate upload and download mailboxes are created and assigned to each EBICS Client user.

EBICS Client Schema

EBICS Client-related data are stored in the EBICS Client Schema tables. The EBICS Client Graphical User Interface and EBICS Client Runtime components access the tables to retrieve information about users, banks, offers, user permissions, and orders.

This section describes some of the key features of EBICS Client.

  • Managing profiles for users
    You can configure permission types to enable a user to access the EBICS Client dashboard interface.
  • Managing certificates and keys for users
    EBICS Client supports both Keys and X.509 certificate types for user's identification and authentication, encryption, and electronic signatures.
  • Submitting orders
    An order type defines the nature of an EBICS transaction.
  • Pending Signatures
    Depending on the configuration settings that are defined in an offer, multiple signatories might have to sign the order to process the order data.
  • Recovering Transactions
    Order recovery is an important feature of EBICS Client. For an upload transaction, order processing error might occur at the bank's end. For download transactions, response processing errors might occur at the subscriber or customer's end. Apart from the processing errors, transport errors might also occur.
  • Searching transactions and viewing reports
    You can search for orders and view the summary of the orders on EBICS Client dashboard interface based on a combination of parameters.
  • Tracking EBICS transactions
    EBICS Client generates events that are related to orders. All events are predefined and metadata is populated in the system. A user cannot define the events. The events are logged against an order ID and there are no stand-alone events in EBICS Client.
  • Restore Tables
    Archiving transaction data, such as order, event, and pending signature-related data protects critical data. Archiving conserves database disk space and file system disk space, which improves the efficiency of EBICS Client.

Previous Topic

Sterling B2B Integrator - Overview of EBICS

Parent Topic

Sterling B2B Integrator - EBICS Client Overview

Next Topic

Sterling B2B Integrator - Configuration Requirements

TURN IDEAS INTO ACTION

Make the next step specific.

Bring your operating context, priorities and questions. We’ll help identify the relevant next step.

Start a conversation ↗
Services and Accelerators →Technologies We Support →More perspectives →
Pragma Edge / Let’s Connect

Start a conversation.

Tell us what you’re working on. We’ll help shape the next step.

Your inquiry goes directly to the Pragma Edge sales team.

Or email sales directly