Germany · Berenberg · EBICS
Connect Berenberg without learning EBICS.
Berenberg’s host serves EBICS 2.4, 2.5 and 3.0 under Host ID BEGO. We handle the payments, the statements and every protocol step underneath. You follow five steps.
The host, checked live
10 Sep 2026<ebicsHEVResponse xmlns="http://www.ebics.org/H000"> <ReturnCode>000000</ReturnCode> <ReportText>[EBICS_OK] OK</ReportText> <VersionNumber ProtocolVersion="H003">02.40</VersionNumber> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.00</VersionNumber> </ebicsHEVResponse>
Published by the bank
The bank's imprint, corroborated by the host's TLS certificate.
Bank details
| BIC | BEGODEHH |
| Bank code | 201 200 00 |
| Legal name | Joh. Berenberg, Gossler & Co. KG |
| Registered office | Überseering 28, 22297 Hamburg |
| Register · LEI | HRA 42659 · 529900UC2OD7II24Z667 |
| Ownership | Independent private partnership — no banking group |
Checked live
Measured against the live host on 10 September 2026.
Access data
| EBICS address | https://mc.berenberg.de/ |
| Host ID | BEGO |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.00) |
| Your IDs | Kunden-ID and Teilnehmer-ID, issued after contract check |
BankConnector
What is built and shipped for this bank today.
What our engine produces
| Payment format | pain.001.001.03 |
| Rulebook | German DK Anlage 3 v3.9 / 2025-03 |
| Charge bearer | SLEV |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Character set | Latin — transliterated before the bank sees it |
| Read back | camt.053, pain.002 — one normalised format |
| Not supported | Direct debits |
Published by the bank
Published by DK; the response is ours.
What is still ahead
pain.001.001.09 replaces pain.001.001.03 across German banks. Our engine emits both, so it is a setting on the connection.
Payments with unstructured addresses are rejected. Canonical input 1.1 has taken street, building number, post code, town and country as separate fields since it shipped.
Every EBICS key pair has to reach 4096 bits. New keys and a new initialisation letter, which we generate and print as we did at setup.
Five steps to a live connection.
You do not need to know what any of this means.
- 1
Sign the agreements
Berenberg's route is three documents: the Corporate Portal agreement, the agreement on remote data transmission, and the data-protection agreement. We draft the request and tell you what each one is for.
- 2
The bank returns your EBICS user data
Berenberg checks the contract and sends your Kunden-ID and Teilnehmer-ID, together with the EBICS data sheet carrying the parameters and the bank's key hash values.
- 3
Send the initialisation letter
We generate your keys and print the letter. Berenberg's own instruction is to sign it and email it to the eBanking desk. Private keys never leave the system.
- 4
Verify the bank and go live
We fetch the bank's public keys and check them against the hashes on your data sheet. Then you choose the approval policy and the connection switches on.
- 5
In production
Payments go out as pain.001, statements come back as camt.053, unattended.
Sources — Berenberg’s imprint, its Corporate Portal documentation, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. Host response and protocol versions measured 10 September 2026. BankConnector is not affiliated with Joh. Berenberg, Gossler & Co. KG.