Germany · M.M.Warburg & CO · EBICS
Connect Warburg Bank without learning EBICS.
Warburg’s host speaks EBICS 2.5 and 3.0, delivers statements as camt.053 only, and moved to a new address in May 2026. We handle the payments and the statements, and every protocol step underneath. You follow five steps.
No EBICS knowledge needed. We draft the emails, generate the keys and print the letter the bank asks for.
Warburg’s new host, checked live
10 Sep 2026<ebicsHEVResponse xmlns="http://www.ebics.org/H000"> <SystemReturnCode> <ReturnCode>000000</ReturnCode> <ReportText>[EBICS_OK] OK</ReportText> </SystemReturnCode> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.00</VersionNumber> </ebicsHEVResponse>
Published by Warburg
From the bank's own EBICS customer flyer and its IT-migration page.
The May 2026 migration
Warburg moved onto the Atruvia platform, and seven of the values a payment system holds about this bank changed at once. We have been through all seven, and checked them against the live host on 10 September 2026.
| What | Until 8 May 2026 | From 11 May 2026 |
|---|---|---|
| EBICS address | https://ebics.warburggruppe.eu/EBICS/ | https://ebics.multivia-suite.de/ebicsweb/ebicsweb |
| Host ID | BANK | MULTIVIA |
| Bank key fingerprints | The old server's | Four new ones, published by the bank |
| Account statements | camt.053 or MT940 | camt.053 only, as C53 |
| Payee verification | Not offered | CTV, released again in the VEU folder |
| Instant payments | Not offered over EBICS | CIP and CIV |
| Bank code | One per acquired house | 201 201 00 for everyone |
The old address is not a redirect. A system still holding it does not get a bank error it would recognise. It hangs, then times out.
BankConnector
What is built and shipped for this bank today.
Exactly what we have done for Warburg
Warburg is not a generic EBICS target in our system. It has its own bank profile, carrying the German rulebook, the field limits and the scheme coverage.
Payment files
Your canonical JSON becomes the pain.001 credit transfer Warburg expects under the German DK Anlage 3 rulebook. Charge bearer SLEV, remittance capped at 140 characters, names at 70, and non-Latin characters transliterated before the bank ever sees them.
Statements back
We read camt.053 end-of-day statements and pain.002 status reports and normalise both into one format. Warburg withdrew MT940 at the migration, so camt is the only way in — which is the format we were already reading.
The Host ID is shared
MULTIVIA is a gateway on the Atruvia platform, not a Warburg-specific name. Other German banks in our registry answer at the same address, so the Host ID names the platform. What identifies you is the Partner ID and User ID on your EBICS agreement.
Both protocol versions
The host offers 2.5 and 3.0, and answered on both when we asked it on 10 September 2026. We speak both, with A006 signatures, so the 3.0 move is a setting on the connection rather than a project.
Four fingerprints, not two
Warburg publishes X002 and E002 hashes twice over: one pair for keyed EBICS and a second pair for the certificate-based 3.0 profile. All four are the ones we already hold on file for this gateway. The one exchange that cannot be re-verified later is verified before it happens.
Two signatures on a payment
Warburg supports the distributed signature, and so do we. It matters more here than at most banks: a payee-checked CTV submission comes back to that folder for a second release after the check, so the approval step is part of the payment path rather than an option.
The paperwork
We generate your keys, print the initialisation letter as a signed-ready PDF carrying the fingerprints Warburg checks, and draft the email that opens the agreement. Private keys never leave the system.
Published by Warburg
From the bank's EBICS flyer, plus our own live check of the host.
What Warburg supports
Warburg publishes the access parameters openly, down to the fingerprints of the gateway’s own bank keys. A treasury team can see the shape of the connection before speaking to anyone at the bank.
| Host ID | MULTIVIA — since 11 May 2026 |
| EBICS address | https://ebics.multivia-suite.de/ebicsweb/ebicsweb |
| Protocol versions | H004 (2.5) and H005 (3.0) |
| Retired address | ebics.warburggruppe.eu · Host ID BANK — stopped 8 May 2026 |
| Minimum key length | 2048 bits, refused below that since the migration |
| Bank key hashes | Four — X002 and E002, keyed and certificate-based |
| Distributed signature | Supported — and payee-checked orders return to it |
| Statement formats | camt only — MT940 withdrawn 11 May 2026 |
| Same-day cut-off | 16:00 — SEPA, SWIFT and TARGET2 |
| Bank code | One for every customer — 201 201 00 |
| BICs served | WBWCDEHH · LOEBDEBB (Bankhaus Löbbecke, Berlin) |
Published by Warburg
Only the codes the bank names in its own flyer.
Order types published by Warburg
| Code | What it does | Direction | Message | BankConnector |
|---|---|---|---|---|
| CTV | SEPA credit transfer with payee verification | Send | pain.001 | Supported |
| CIV | Instant credit transfer with payee verification | Send | pain.001 | Supported |
| CIP | Instant credit transfer without the check | Send | pain.001 | Supported |
| C53 | End-of-day account statement | Download | camt.053 | Supported |
| HPB | Fetch the bank's own public keys | Download | — | Supported |
| VEU | Distributed signature — raise, then release | Both | — | Supported |
Published by Warburg
Published by the bank and by DK; what we do about each is ours.
What is still ahead
Four dates, and the first two are one cutover rather than two. Each is covered.
The SEPA formats change at 00:01. pain.001.001.09 replaces pain.001.001.03. Our engine emits both, so it is a setting on the connection. Nothing changes in what you send us.
Addresses must be structured. Free-text postal addresses stop being accepted. We have taken street, building number, post code, town and country as separate fields since canonical input 1.1. It asks only that your ERP holds them separately too.
RSA 2048 keys stop being enough. Every key pair has to reach 4096 bits. Our generator is sized per bank and already issues 4096 where it is required. It needs new keys and a new initialisation letter, which we print as we did at setup.
IBAN forwarding ends. Warburg redirects payments addressed to a pre-migration IBAN until then, and after that an old IBAN is simply wrong. We validate per connection, so a stale one is caught before the file reaches the bank.
If all of this looks like a lot · it does not have to be
Five steps to a live Warburg 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 Warburg
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 four values from the agreement Warburg returns. The public ones are known, so most of the form is filled in. Then one press generates your keys 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 Warburg will check. You sign it by hand and post it.
- 4
Verify Warburg and go live
While you wait, we fetch the bank's public keys and check them against the four hashes Warburg publishes. When that lands, you choose which approval policy governs payments here, and the connection switches on.
- 5
You are now in production with Warburg
Payments go out as pain.001 and statements come back as camt.053. The connection runs unattended from here.
Sources — Warburg’s own page on the IT migration, its EBICS customer flyer and the EBICS specifications published by Die Deutsche Kreditwirtschaft. Host response and the retired address both measured 10 September 2026. M.M.Warburg & CO (AG & Co.) KGaA is headquartered in Hamburg. BankConnector is not affiliated with M.M.Warburg & CO.