Creating Your Connection

Setting up your first EBICS connection takes about 10 minutes once you have your bank credentials. Here's what you'll need from your bank relationship manager:

• Host URL - Bank's EBICS server address

• Host ID - Bank's unique network identifier

• Partner ID - Your company's contracted number

• User ID - Specific user/technical account

EBICS API includes a built-in Bank Server Stub — use it to practice the full flow (create connection, initialize, confirm activation, import accounts, run orders) with no real money involved.

The Initialization Process (One-Time Setup)

Before you can send real payments, the bank must verify and approve your keys. The process varies by country and bank:

1. Click "Initialize Keyring" in your connection dashboard Your EBICS server sends an INI and HIA order to the bank

2. Download INI letter with activation codes and send it to your Bank for verification

3. Click "Confirm Activation" in your connection dashboard. Status changes to CONFIRMED — you're live!

Status flow: NEED_INIT → NEED_CONFIRM → CONFIRMED. Your connection progresses through these states as keys are generated, the bank verifies them, and the keyring is confirmed.

Connection Keyring

The Keyring Details modal provides a complete overview of the connection's cryptographic keyring. It displays the keyring version, certification status, and whether it is certified by the bank's authority, with certificates available for download. User certificates — authentication (A005/A006),  signature (X002), and encryption (E002) — are listed with their serial numbers,  subjects, issuers, and validity periods, and may be renewed once the keyring is activated. Bank certificates are likewise presented and can be refreshed. The keyring itself may be downloaded for backup or transfer. This view enables verification of certificate validity, monitoring of expirations, and renewal when required.

Connection Logs

Connection logs provide a comprehensive record of all EBICS orders exchanged with the bank. Logs can be filtered by type, order type, or date range, and attached files can be previewed or downloaded. Bank history, retrieved directly from the bank via order HAC, reflects the bank's authoritative view of those transactions. Together, these views enable auditing and verification of all banking activity. Whereas the bank retains its history for a limited period of approximately one month, local connection logs may be stored indefinitely, ensuring comprehensive archival for audit and compliance purposes.

Connection Accounts

A connection serves as the secure communication channel with your bank, while accounts represent the actual bank accounts (IBANs) operated through it. Payments cannot be processed without linked accounts. SEPA accounts are associated with a connection so that credit transfers, direct debits, and statement downloads are directed to the appropriate account. Each account is attributed to a bank party — the legal entity identified by name, address, and country. Accounts may either be created manually or imported those already hosted by the bank via the order HTD.

Connection Access

Connections may be controlled at two levels. Through sharing, a connection owner can grant access to designated users or make the connection public, enabling collaboration while sensitive material — such as Partner ID, User ID, and keyring certificates — remains concealed. Through API keys, access can be granted for programmatic integration: each key is bound to a specific  connection and restricted by permissions (Info, Download, Upload, or Sign) and, optionally, by allowed IP addresses. Together, these mechanisms provide granular control over who may access a connection and which operations they may perform, with the ability to revoke or adjust access at any time.

Connection Health Monitoring

 The Connection Health Monitoring widget provides a concise overview of each connection's performance over the trailing 30 days. For every connection, it presents the number of successful, warning, and error log entries, with each figure linking directly to the corresponding filtered log view for further investigation. The connection's status icon reflects the keyring status, allowing expirations or inactive keyrings to be identified at a glance. This enables prompt detection of emerging issues — such as rising error rates or certificate expirations — before they affect payment processing.

Connection Certificate Renewal

Certificate renewal ensures the continuous validity of the connection's cryptographic credentials. As certificates approach expiry, the connection may be renewed by generating a new keyring — after which the bank's approval is obtained and the new certificates activated — or, where applicable, the bank's own certificates may be refreshed, without disturbing the user's credentials. Renewal is initiated from the connection's Keyring Details, which also serves as a reference for certificate validity periods and notification of upcoming expirations. Proactive renewal prevents interruptions in payment processing, as all orders cease to be accepted once certificates lapse.