EBICS 3.0

EBICS 3.0 is a standardized EBICS version that replaces the use of banking order types (or file formats) with Business Transaction Format (BTF) services.

EBICS 3.0 defines a single, harmonized standard that uses H005 protocol and combines the processing for Germany, France, and Swiss EBICS. The most significant change within EBICS 3.0 is the way in which transaction types are recognized and validated.

Note: The current version of the EBICS Client and EBICS Server supports v2.4 and v2.5. After you upgrade EBICS Server (or EBICS Client) to v3.0, the system allows to communicate with the EBICS Client (or EBICS Server) of v2.4, v2.5, or v3.0.

Key features

Here is a list of the key features of EBICS 3.0:
  • BTF integration and removal of file format - New way to identify the exchanged payload:
    • Technical order types are called Administrative order types.
      • FUL and FDL order types are replaced with BTU and BTD respectively
      • BTU: Order type indicates upload (SEND request)
      • BTD: Order type indicates download (FETCH request)
    • BTF used to identify the payload type brought by a SEND (BTU) or a FETCH (BTD) request

    For more information, see Business Transaction Format configuration.

  • VEU signature is called Electronic Distributed Signature (EDS).
  • Key Management:
    • All keys must be managed through X.509 certificates.
    • The minimal length of keys is 2048 characters.
    • Change of hash value calculation for initialization letter data.
  • Changes to order types:
    • INI, HIA, HPB, HVU, HVZ, HVD, HVT, HVS, HAA, HVE, HEV, HAC, HKD, HPD, HTD, HCA, HCS, H3K, PUB, SPR
    • H005 request/response changes
    • Changes in error codes
  • EBICS application specific changes:
    • Offer, Contract, User Permission, Bank, and Signatory configurations integrated with BTF
    • Import/Export functionality
    • Migration from old protocol versions to H005 (Client)