EBICS

EBICS (Electronic Banking Internet Communication Standard) is an international electronic communication protocol used primarily for corporate-to-bank financial file transfers within Europe. It provides a standardized and efficient way for organizations (Clients and TxB) to exchange payment instructions, account statements, and other financial data. EBICS is used for sending internet-based XML (ISO 20022 compliant) file transfers, secured through encrypted HTTPS connections, with the aim to ensure the integrity and confidentiality of the financial data. TxB supports EBICS v2.5.

Key Features

• Global availability: TxB clients can use the EBICS protocol to initiate credit transfers and receive reports to/from any of their accounts in the EU, the UK, or the US.

• Enhanced Security: EBICS employs various security mechanisms, including strong encryption (TLS/SSL), digital signatures (RSA), and secure protocols (HTTPS), to protect sensitive financial data during transmission.

• Comprehensive File Support: EBICS is designed to work with various file formats, including the ISO 20022 XML standard. A full list of supported file types and versions is outlined in the File Support Dictionary.

Connectivity pre-requisites

To establish secure EBICS connectivity with TxB, clients need to complete a key exchange and configuration process. This ensures mutual authentication and facilitates secure data transmission.

IP Whitelisting

Clients are required to provide their public IP addresses or CIDR (Classless Inter-Domain Routing) ranges to TxB to enable secure communication and allow client inbound requests to pass through TxB firewalls. This whitelisting process restricts access to TxB’s EBICS endpoints to only authorized and recognized network locations.

Exchange Host and Server Information

Clients need to configure TxB’s EBICS Host ID and server URL(s) in their EBICS Client software:

• EBICS Host ID

  • CIT: GSTEST
  • PROD: GSPROD

• EBICS URL of the bank server

  • CIT: https://qa-ebics.txb.gs.com/ebics/EbicsServlet
  • PROD: https://ebics.txb.gs.com/ebics/EbicsServlet

Generate and Exchange Public Keys

Clients generate multiple public/private RSA key pairs for different security purposes (signature, identification, authentication, and encryption).

Sending Client’s Public Keys to TxB

• INI Keys (Electronic Signature Key): The client's public key for electronic signatures (e.g., A006) is sent using the EBICS INI order type. This key is crucial for digitally signing financial instructions.

• HIA Keys (Identification, Authentication, and Encryption Keys): The client's public keys for identification, authentication (e.g., X002), and encryption (e.g., E002) are transmitted via the EBICS HIA order type. These keys are fundamental for securing the connection and encrypting the data exchanged.

• INI Letter: EBICS client software will generate a combined INI letter (INI and HIA keys). Clients must print, sign, and physically submit an INI letter to TxB via Lockbox. This letter serves as a critical "second, independent communication path" to verify the authenticity of the electronically transmitted public keys, a prerequisite for activating the EBICS connection.

Acquiring TxB's Public Certificate

• Clients use the HPB order type to download TxB' public certificate. This certificate contains TxB public keys for verification.

• Upon successful validation, TxB sends an HPB response containing these public keys. The client’s EBICS software should then validate these bank keys against the internal records to activate the connection.

Activation and Testing

After the key exchange, TxB will activate the Client’s EBICS access. Once activated, it is recommended to perform test transactions to establish whether the connection and file transfers are functioning correctly.

EBICS Order Types

TxB supports a range of EBICS Order Types. Some of the most popular Order Types for sending and receiving files are listed in the table below.

'TxB processes payments received via the EBICS CCU order type as ordinary wire transfers