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
<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>
Host ID
BEGO
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.12 s
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 | HRA 42659 |
| LEI | 529900UC2OD7II24Z667 |
| Ownership | Independent private partnership, no banking group |
Checked live
Measured against the live host.
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 and pain.002, in one normalised format |
| Not supported | Direct debits |
BankConnector
Questions
- What is Berenberg's EBICS Host ID and URL?
- Host ID BEGO, address https://mc.berenberg.de/. Your own Kunden-ID and Teilnehmer-ID arrive from the bank once your contract is checked.
- Which EBICS versions does Berenberg support?
- Three: EBICS 2.4 (protocol H003, revision 02.40), EBICS 2.5 (H004, 02.50) and EBICS 3.0 (H005, 03.00). BankConnector connects over EBICS 3.0 (H005).
- Can I connect my ERP to Berenberg?
- Yes. You send canonical JSON and BankConnector produces the pain.001 credit transfer file the German DK Anlage 3 rulebook requires, then reads camt.053 and pain.002 back into one normalised format. SEPA credit transfers, SEPA instant, domestic and international payments are supported. Direct debits are not.
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
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.
If all of this looks like a lot, it does not have to be
Five steps to a live Berenberg connection.
You do not need to know what any of the codes above mean. Our setup guide walks you through it one screen at a time.
- 1
Request the agreement from Berenberg
EBICS starts with paperwork. We draft the email, you send it, and you tell us when it has gone. There is nothing to configure until the bank replies.
- 2
Set up and send your keys
Enter the values from the agreement Berenberg returns. We already hold the ones that are public, so most of the form is filled in. Then one press generates your three key pairs and sends the public halves.
- 3
Prove your identity on paper
EBICS confirms the key exchange on paper, by design. We print the initialisation letter carrying the fingerprints Berenberg will check. You sign it by hand and simply email the bank a scan; the original goes by post only if the bank asks for it.
- 4
Verify Berenberg and go live
While you wait, we fetch the bank's public keys and check them against the fingerprints it gives you over a separate channel. When that lands, you choose which approval policy governs payments here, and the connection switches on.
- 5
Go live with one small payment
Start with one small payment and follow it all the way to your statement. Then you are in production with Berenberg: payments go out as pain.001, statements come back as camt, and the connection runs unattended from here.
Sources: Berenberg’s imprint, its Corporate Portal documentation, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Joh. Berenberg, Gossler & Co. KG.
How BankConnector handles the November 2026 pain.001.001.09 migration for Berenberg →