Sterling B2B Integrator - Configuration Requirements

Configuring an existing Sterling B2B Integrator user as an EBICS Client user is the first step towards transacting with the bank.

This includes specifying values for attributes, such as, user type, certificate type, and so on. Three types of users can be configured on EBICS Client;

• EBICS Client Admin
• EBICS Client Operator
• EBICS Client User

Another user type, technical user can also be configured. EBICS Client supports X.509 and RSA Keys standards to define digital certificates. User configuration attributes vary based on the user type and certificate type. Configuring Certificate and key related information is not required for an EBICS Client admin or EBICS Client operator. For more information about user types, see Managing Profiles for Users.

There are three order types used for user initialization: H3K, INI, and HIA. H3K is the simplest and transmits all three public certificates at the same time. However, H3K cannot be used in all cases, such as if trusted keys are used or with protocol version H003. If you cannot, or prefer not to, use H3K, you can use INI and HIA together to transmit the public certificates. For more information about user initialization, see Initializing a User in the EBICS Client User documentation.

A bank is the primary entity in an EBICS transaction. It hosts the server with which a partner and users who are associated with the partner can perform EBICS transactions.

An integral part of the bank configuration is the bank ID or host ID. After a contract is signed, the bank shares the bank ID or host ID together with the URL of the bank with the partner. An EBICS Client admin creates a bank profile using the information shared by the bank with the partner. If the bank URL uses a secure HTTP protocol, then an HTTPS certificate is required. The HTTPS certificate for the bank is created on Sterling B2B Integrator and configured using EBICS Client.

The format or type of file that is uploaded or downloaded is identified by the File Format attribute. An order type can have zero or more file formats. A file format can contain the country code and supported order types.

An offer is a super set of order types and file formats. An offer is associated with a bank ID to specify the possible order types and file formats that can be used when transacting with the bank. Offers provide the advantage of grouping many bank transactions and handling them together.

User permissions define the offers, order types, and file formats, an EBICS Client user can process on EBICS Client.