Connect Helaba without learning EBICS.
EBICS 2.5 and 3.0 on Host ID HELABA, eleven published order types, and payee verification since October 2025. We handle the payments, the statements and every protocol step underneath.
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
HELABA
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.43 s
Published by the bank
The bank's imprint and its owners and capital page.
Bank details
| BIC | HELADEFF |
| Bank code | 500 500 00 (Frankfurt am Main) |
| Legal name | Landesbank Hessen-Thüringen Girozentrale, Anstalt des öffentlichen Rechts |
| Registered office | Neue Mainzer Straße 52-58, 60311 Frankfurt am Main |
| Second registered office | Bonifaciusstraße 16, 99084 Erfurt |
| Register | Amtsgericht Frankfurt am Main HRA 29821 and Amtsgericht Jena HRA 102181 |
| LEI | DIZES5CFO5K3I5R58746 |
| VAT ID | DE 114 104 159 |
| Owners | Sparkassen- und Giroverband Hessen-Thüringen 50.0%, Land Hessen 30.1%, Rheinischer Sparkassen- und Giroverband 4.1%, Sparkassenverband Westfalen-Lippe 4.1%, FIDES Alpha 4.1%, FIDES Beta 4.1%, Freistaat Thüringen 3.5% |
Helaba is a public-law institution with two registered offices, Frankfurt am Main and Erfurt, and a separate commercial register entry for each.
Checked live
Measured against the live host.
Access data
| EBICS address | https://ebics2.helaba.de |
| Host ID | HELABA (upper case, case-sensitive) |
| Protocol versions | H004 (02.50) and H005 (03.00) |
| Your IDs | Partner ID and User ID, issued at contract |
| Distributed signature | VEU, but the way it is used must be agreed with the bank |
| Signature classes | E single, A first, B second, T transport |
| Bank-side keys | The subscriber fetches the bank's public key and checks its certificate |
| Self-blocking | SPR blocks the User ID it is sent under |
| Technical specification | Published at www.ebics.de |
Published by the bank
The bank's cash management briefing and payee-verification notices.
Order types published by Helaba
| 2.5 | What it does | 3.0 BTF | Direction |
|---|---|---|---|
| CCT | SEPA credit transfer, payee check opt-out | SCT//VOO/pain.001/ | Send |
| CTV | SEPA credit transfer, payee check opt-in | SCT//VOI/pain.001/ | Send |
| CIP | Instant credit transfer, payee check opt-out | SCI//VOO/pain.001/ | Send |
| CIV | Instant credit transfer, payee check opt-in | SCI//VOI/pain.001/ | Send |
| CCC | SEPA credit transfer in an XML container, opt-out | Not published | Send |
| XCT | CGI file submission, opt-out | Not published | Send |
| CCS | Service data centre SEPA credit transfer, opt-out | Not published | Send |
| VCS | Service data centre SEPA credit transfer, opt-in | Not published | Send |
| CCX | Service data centre authorisation, opt-out | Not published | Send |
| VCX | Service data centre authorisation, opt-in | Not published | Send |
| VPZ | Payee verification status report | REP/DE/VOP/pain.002/ZIP | Download |
Payee verification went live on 5 October 2025 for SEPA credit transfers and SEPA instant. Urgent payments and foreign payments sit outside it. Opting out is only permitted for a bulk file holding more than one transaction; a single transaction sent under an opt-out order type is rejected and has to be resubmitted under an opt-in one.
An opt-in file becomes visible for authorisation only once its VPZ report is final. The result is then taken whole: authorise the file or cancel it. Correcting one payee name means cancelling the file and submitting it again.
Published by the bank
The bank's instant-payments notes and its Webbanking answers.
Cut-off times and execution
| SEPA credit transfer | Not published, as it is set per order type in the customer contract |
| Urgent transfer and foreign payment | Not published |
| Instant credit transfer | Executed within 10 seconds of entering the payment system |
| Instant amount ceiling | None, since the former EUR 100,000 limit was removed |
| Submission channels | Webbanking and EBICS only, since 5 October 2025 |
| Paper, fax and secure email | Not accepted as a rule, since 5 October 2025 |
Helaba publishes no cut-off table. Its own answer is that cut-off times are defined in the customer contract for each type of order.
Published by the bank
The bank's cash management briefing of 30 April 2025.
Formats
| SEPA credit transfer | pain.001 |
| Payee verification report | pain.002, one or more messages in a ZIP container |
| CGI submission | Accepted under XCT |
| MT940 and MT942 | Mandatory support ended 23 November 2025 |
| camt.052, camt.053 and camt.054 | Version 02 mandatory support ended 23 November 2025 |
| MT101 relay | Moves to RTX, a pain.001 relay, with no end date published |
| pain.001.001.09 | Not published |
| DTAZV | Not published |
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 |
| Batch booking | False |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Character set | Latin, transliterated before the bank sees it |
| Payment types built | SEPA credit transfer, SEPA instant, domestic account transfer and international |
| Read back | camt and pain.002, normalised into one format |
| Not supported | Direct debits |
BankConnector
Questions
- What is Helaba's EBICS Host ID and URL?
- Host ID HELABA, address https://ebics2.helaba.de. The Host ID is case-sensitive and must be upper case. Your Partner ID and User ID are issued at contract conclusion.
- Which EBICS versions does Helaba support?
- EBICS 2.5 (protocol H004, revision 02.50) and EBICS 3.0 (H005, 03.00). BankConnector connects over EBICS 3.0 (H005).
- Does Helaba support Verification of Payee?
- Yes, since 5 October 2025, on SEPA credit transfers and SEPA instant credit transfers. Urgent payments and foreign payments are outside it. The check is chosen by order type: CCT and CIP opt out, CTV and CIV opt in, and VPZ returns the result as a pain.002 in a ZIP container. Opting out is only permitted for a bulk file holding more than one transaction; a single transaction submitted under an opt-out order type is rejected and must be resubmitted under an opt-in order type.
- What is Helaba's payment cut-off time?
- Helaba does not publish cut-off times. Its own answer is that cut-off times are defined in the customer contract for each type of order. Instant credit transfers are executed within 10 seconds of entering the payment system, and the former EUR 100,000 ceiling has been removed.
- Has Helaba published a pain.001.001.09 or DTAZV date?
- No. Helaba has published no date of its own for pain.001.001.09 and none for the end of DTAZV. What it has dated is 23 November 2025, when mandatory support for MT940, MT942 and version 02 of camt.052, camt.053 and camt.054 ended.
- How do I submit a payment file to Helaba?
- Since 5 October 2025 Helaba accepts SEPA credit transfers only through Webbanking or EBICS. Paper submission, fax and secure email are no longer accepted as a rule. A file submitted under an opt-in order type is authorised or cancelled as a whole through the distributed electronic signature after the payee-verification report is available.
- Can I connect my ERP to Helaba?
- Yes. You send canonical JSON and BankConnector produces the pain.001 credit transfer file the German DK Anlage 3 rulebook requires, then reads camt and pain.002 back into one normalised format. SEPA credit transfers, SEPA instant, domestic account transfers and international payments are supported. Direct debits are not.
If all of this looks like a lot, it does not have to be
Five steps to a live Helaba 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 Helaba
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 Helaba 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 Helaba 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 Helaba 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 Helaba: payments go out as pain.001, statements come back as camt, and the connection runs unattended from here.
Sources: Helaba’s conditions for remote data transmission, version July 2025, in force from 5 October 2025, its explanatory notes on instant payments, its cash management customer briefing of 30 April 2025, the corporate-customer information on payee verification in the EBICS procedure that it publishes, its imprint, its owners and capital page, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Landesbank Hessen-Thüringen Girozentrale.
How BankConnector handles the pain.001.001.09 migration, bank by bank →