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.
The host, checked live
<ebicsHEVResponse xmlns="http://www.ebics.org/H000"> <ReturnCode>000000</ReturnCode> <ReportText>[EBICS_OK] OK</ReportText> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.00</VersionNumber> </ebicsHEVResponse>
Host ID
MULTIVIA
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.13 s
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.
| 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, and that 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. |
| EBICS 3.0 | The host runs 2.5 and 3.0, and answers on both. We connect over EBICS 3.0 (H005), with A006 signatures. |
| 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 a required part of the payment path. |
| 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 with 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 for SEPA, SWIFT and TARGET2 |
| Bank code | One for every customer: 201 201 00 |
| BICs served | WBWCDEHH and 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 |
BankConnector
Questions
- What is Warburg Bank's EBICS Host ID and URL?
- Since 11 May 2026 the Host ID is MULTIVIA and the EBICS address is https://ebics.multivia-suite.de/ebicsweb/ebicsweb. The previous Warburg EBICS bank server at ebics.warburggruppe.eu, Host ID BANK, was retired with the migration and no longer answers. MULTIVIA is a shared gateway operated on the Atruvia platform, so the Host ID names the platform rather than the bank: what identifies you to Warburg is your Partner ID and User ID.
- Does this connection cover Bankhaus Löbbecke?
- Yes. Bankhaus Löbbecke in Berlin is a branch of M.M.Warburg & CO and uses the same EBICS connection: Host ID MULTIVIA at https://ebics.multivia-suite.de/ebicsweb/ebicsweb. Its own BIC, LOEBDEBB, is current in the Bundesbank bank directory against bank code 100 305 00. Warburg is consolidating every customer onto a single bank code, 201 201 00.
- Which EBICS version does Warburg Bank use?
- Both. The gateway answers on EBICS 2.5 (protocol H004) and EBICS 3.0 (protocol H005). BankConnector connects over EBICS 3.0 (H005).
- Does Warburg Bank still support MT940?
- No. Warburg states that from 11 May 2026 electronic account statements are provided in camt.053 only, delivered by the C53 order type. MT940 was available up to the migration and is not available after it. A system that can only read MT940 cannot be pointed at this bank.
- Does Warburg Bank support Verification of Payee?
- Yes, since 11 May 2026. Warburg submits payee-checked credit transfers under the CTV order type. There is a change of behaviour worth planning for: a CTV submission lands in the distributed-signature folder and has to be authorised again before it is booked, which is not what CTV did before the migration.
- Did my IBAN change in the Warburg migration?
- It changed for some customers. Warburg consolidated its bank codes into a single one for every customer, 201 201 00, the Hamburg head office code, which retires the separate codes the acquired houses used. Affected customers were told separately. Credits and debits addressed to a previous IBAN are forwarded automatically until April 2028, and payment files have to carry the new IBAN from 11 May 2026.
- When is Warburg Bank's same-day payment cut-off?
- 16:00. Warburg guarantees same-day booking for orders raised and released by 16:00, across SEPA, SWIFT and TARGET2. Orders after that are held for the next execution day, and weekends and public holidays are not execution days.
- Can I connect my ERP to Warburg Bank?
- Yes. BankConnector connects an ERP or any other system to Warburg Bank over EBICS. You send canonical JSON and we produce the pain.001 credit transfer file Warburg expects under the German DK Anlage 3 rulebook, then read 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
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 the values from the agreement Warburg 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 Warburg 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 Warburg 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 Warburg: payments go out as pain.001, statements come back as camt, and 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. M.M.Warburg & CO (AG & Co.) KGaA is headquartered in Hamburg. BankConnector is not affiliated with M.M.Warburg & CO.
How BankConnector handles the November 2026 pain.001.001.09 migration for Warburg Bank →