Implementation > EBICS > EBICS Server > EBICS Server administration > Bank objects

Bank objects

A Bank object represents a bank or component service (department, branch, agency, filial, and so on) of a bank.

The Bank Server is capable of managing the customers of several banks. To do so, you can configure individual Bank objects in the Banks menu item.

Creating a Bank

  1. In the EBICS Server UI, select the Banks menu item.
  2. Select Create new bank.
  3. Complete the fields:
    4. Field Description
    Name Enter a unique name that is used to identify a bank at various points in the administration interface.
    Host ID Enter the bank EBICS identifier.
    Configuration-letter generator If you want to change the way the configuration letter is generated by the bank for a customer, specify the class name of a new generator.
    Length of hash-value input Enter the hash value length.
    Long IDs The EBICS 2.4 standards permit the use of Host IDs with lengths up to 35 characters. EBICS 2.3 limited Host IDs to 8 characters. Select this option to indicate the use of the updated standard for character length.
    EBICS support Activates or deactivates EBICS for the bank you are creating. If you activate EBICS support, all keys required for EBICS encryption are generated automatically.
    EBICS Host-ID Enter the bank EBICS identifier.
    URL

    Enter https://<host>:8443/ebics/EbicsServlet

    Do not change the ebics/EbicsServlet part of this URL.
    Import PKCS12 file

    Select this option if you want to import a PCKCS12 file to store private keys with accompanying public key certificates.

    This option is only available if you have installed a server package that includes PassPort security services.
    Encryption key

    This field is only visible if you select the Import PKCS12 file option above.

    Enter the path to the encryption key you want to use.
    File password

    This field is only visible if you select the Import PKCS12 file option above.

    Enter the password for access to the encryption key file.
    Signature key

    This field is only visible if you select the Import PKCS12 file option above.

    Enter the path to the signature key you want to use.
    File password

    This field is only visible if you select the Import PKCS12 file option above.

    Enter the password for access to the signature key file.
    Key length

    This field is visible if you do not select the Import PKCS12 file option above.

    1024
    Protocol versions

    Select the EBICS standard version you intend to use for exchanges between the bank and remote clients.

    • H002
    • H003
    Signature versions

    Select the EBICS signature versions you intend to use between the bank and remote clients.

    • A004
    • A005
    • A006
    Force certificates Select this option to require the customer to use X.509 certificates.
    Key generation

    Select which format to use for bank keys:

    • Self-signed certificates
    • Key pairs without certificates
    • Import PKCS12 file
  4. The bank details page displays details of the selected bank. It displays the hash value of the key. Click the hash value to display the public details of the keys: modulus and exponent. For security reasons, the private details are stored in the database but are not displayed.
  5. Click Save.

CFONB compliance

EBICS Server in FEX checks for CFONB compliance if certain conditions are met when the Bank is created.

Ensuring CFONB compliance

During bank creation, ensure that the following parameters are set in the EBICS Server UI. All transfers to the banks on the EBICS Server side will then be checked for CFONB compliance.

Checkbox Requirement for CFONB compliance
Long IDs Checked
Protocol versions - H003 Checked
Signature versions - A005 Checked
Signature versions - A006 Checked
Force certificates Checked

CFONB overlay requirements

For the CFONB overlay, here are the most important requirements:

Related topics

Example EBICS Server configuration

EBICS Server example: Create a Bank