Connect OLB without learning EBICS.
OLB answers on Host ID OLBOLDEN across four EBICS versions, 2.3 to 3.0. In November 2026 it withdraws the older SEPA formats and MT940 together.
The host, checked live
<ebicsHEVResponse xmlns="http://www.ebics.org/H000"> <ReturnCode>000000</ReturnCode> <ReportText>[EBICS_OK] OK</ReportText> <VersionNumber ProtocolVersion="H002">02.30</VersionNumber> <VersionNumber ProtocolVersion="H003">02.40</VersionNumber> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.00</VersionNumber> </ebicsHEVResponse>
Host ID
OLBOLDEN
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.42 s
Published by the bank
The bank's imprint and company pages.
Bank details
| BIC | OLBODEH2XXX |
| Bank code | 280 200 50 |
| Legal name | Oldenburgische Landesbank AG |
| Registered office | Stau 15/17, 26122 Oldenburg |
| Register and LEI | HRB 3003, Amtsgericht Oldenburg (Oldb); 5299008I0TO44SUINZ71 |
| Owner | TARGO Deutschland GmbH, Crédit Mutuel Alliance Fédérale (closed 2 January 2026) |
| Merged in | Degussa Bank, 2024 |
| Supervision | BaFin and the European Central Bank |
Checked live
Measured against the live host.
Access data
| EBICS address | https://ebanking.olb.de/ebics/EbicsServlet |
| Host ID | OLBOLDEN (upper case, case-sensitive) |
| Protocol versions | H002 (02.30), H003 (02.40), H004 (02.50), H005 (03.00) |
| Return code | 000000, [EBICS_OK] OK |
| Response time | 0.42 s |
| Bank keys on file | 2 key hashes and 2 certificate hashes, for authentication and encryption |
| Your IDs | Partner ID, User ID and System ID, issued with the contract |
OLB does not publish the address or the Host ID. They arrive with the contract documents, along with your Partner ID, User ID and System ID.
Published by the bank
The bank's notice on the withdrawal of the older formats.
Formats OLB withdraws in November 2026
| Payment type | Withdrawn | From Nov 2026 | Order type |
|---|---|---|---|
| SEPA credit transfer, SEPA instant | pain.001.002.02, .002.03, .003.03, .001.03 and .001.02 | pain.001.001.09 | Not published |
| SEPA direct debit | pain.008.002.01, .002.02, .003.02 and .001.02 | pain.008.001.08 | Not published |
| Foreign payment | MT101 and DTAZV | pain.001.001.09 | RFT for MT101 |
| Same-day urgent transfer | pain.001.001.03 and older | pain.001.001.09 | CCU |
| Account statements | MT940 | camt.053.001.08 | Not published |
| Pre-advised items | MT942 | camt.052.001.08 | Not published |
OLB names the month and no day. Address data has to be hybrid or structured from the same point, in fields for street, house number, postcode, city and country.
Published by the bank
The bank's terms for remote data transmission, effective 5 October 2025.
Terms for remote data transmission
| Conditions | Bedingungen für die Datenfernübertragung, effective 5 October 2025 |
| Open to | Customers who are not consumers |
| Channel | EBICS |
| Order type from 3.0 | The Business Transaction and Format (BTF) counts as the order type |
| Authorisation | Electronic signature, or a signed submission slip where agreed |
| Participants | Users authorise; technical participants exchange data only |
| Limits | The disposition limits agreed with the bank |
| Record keeping | Every file reproducible for 30 calendar days from its execution or due date |
| Log | One machine-readable log per submission and per download |
Published by the bank
The bank's payee-verification notice and its transfer terms.
Payee verification
| Mandatory since | 5 October 2025 |
| Applies to | SEPA credit transfers and SEPA instant, before authorisation |
| Price | Free for payer and payee |
| Answer time | A few seconds for a single transfer |
| Results | Match, near match (with the account holder's name shown), no match, or not possible |
| Bulk file | The order type chosen per order decides opt-in or opt-out |
| Single payment | Checked whatever the order type, because the bank is obliged to check it |
| After an opt-in check | The file becomes an order only once the user releases it |
| Opt-out | Non-consumers only; the company carries full liability for the payee data |
| Not possible | Not a current account, payee's bank does not support it, or bank outside the EU |
Two rules decide how an automated flow behaves. A file holding a single credit transfer is checked whatever the order type. And after an opt-in check the file becomes an order only once the user releases it.
Published by the bank
The bank's price and services list, effective 1 October 2025. Electronic covers remote data transmission.
Cut-off times and fees
| SEPA credit transfer, electronic | 16:30 on bank business days |
| SEPA-Urgent transfer, electronic | 15:00 on bank business days |
| Euro transfer outside SEPA, electronic | 16:30 on bank business days |
| Transfer in another EEA currency, electronic | 16:30 on bank business days |
| Foreign payment, electronic | 16:30 on bank business days |
| SEPA instant | 24 hours, every calendar day |
| SEPA core direct debit | 1 business day before the due date, 13:30 |
| SEPA B2B direct debit | 1 business day before the due date, 12:30 |
| SEPA instant amount cap | None (the 100,000 euro limit ended in October 2025) |
| Urgent transfer without an advice flag | 10,00 euro |
| EBICS access | Not published |
BankConnector
What is built and shipped for this bank today.
What our engine produces
| Bank key | olb-de |
| Payment format | pain.001.001.03 |
| Also produced | pain.001.001.09, live for other banks today |
| 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 | SEPA credit transfer, SEPA instant, domestic account transfer and international |
| Protocol | EBICS 2.5 and 3.0; we connect on 3.0, not on 2.3 or 2.4 |
| Read back | camt and pain.002, in one normalised format |
| Not supported | Direct debits |
BankConnector
Questions
- What is OLB's EBICS Host ID and URL?
- Host ID OLBOLDEN, address https://ebanking.olb.de/ebics/EbicsServlet. The Host ID is case-sensitive and must be upper case. OLB does not publish the address: it arrives with the contract documents, together with your Partner ID, User ID and System ID.
- Which EBICS versions does OLB support?
- Four: EBICS 2.3 (protocol H002, revision 02.30), 2.4 (H003, 02.40), 2.5 (H004, 02.50) and 3.0 (H005, 03.00). BankConnector connects over EBICS 3.0 (H005).
- What changes at OLB in November 2026?
- OLB withdraws the older SEPA formats up to version 3.6. SEPA credit transfers and instant payments move to pain.001.001.09, direct debits to pain.008.001.08, foreign payments off MT101 and DTAZV to pain.001.001.09, and same-day urgent transfers to pain.001.001.09 under order type CCU. MT940 and MT942 end at the same time, leaving camt.053.001.08 and camt.052.001.08. Address data must be given hybrid or structured. OLB publishes the month and no day.
- Does OLB support Verification of Payee?
- Yes, mandatory since 5 October 2025, free for payer and payee, answered in a few seconds, on SEPA credit transfers and SEPA instant before the transfer is authorised. Two rules matter for automation. In a bulk file the order type chosen per order decides opt-in or opt-out. A file holding a single credit transfer is checked whatever the order type, because the bank is obliged to check it. After an opt-in check the bank reports the result and the file becomes an order only once the user releases it.
- What is OLB's payment cut-off time?
- 16:30 on bank business days for a SEPA credit transfer submitted electronically, 15:00 for a SEPA-Urgent transfer, and 16:30 for foreign payments and transfers in other EEA currencies. SEPA instant runs 24 hours a day on every calendar day. SEPA core direct debits are due one business day before the due date by 13:30, B2B direct debits by 12:30.
- Can I connect my ERP to OLB?
- 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.
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
OLB withdraws the older SEPA formats, up to version 3.6. Credit transfers and instant payments move to pain.001.001.09, direct debits to pain.008.001.08. The bank publishes the month and no day. .09 is one of the two versions our engine produces, and other banks run on it today.
Foreign payments leave MT101 and DTAZV for pain.001.001.09. We have never produced DTAZV.
Same-day urgent transfers move off pain.001.001.03 to pain.001.001.09 under order type CCU.
MT940 and MT942 end. Account and transaction information comes back only as camt.053.001.08 and camt.052.001.08, both of which we already read.
Address data has to be given hybrid or structured, with street, house number, postcode, city and country in their own fields. Canonical input 1.1 has taken those as separate fields since it shipped.
If all of this looks like a lot, it does not have to be
Five steps to a live OLB 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 OLB
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 OLB 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 OLB 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 OLB 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 OLB: payments go out as pain.001, statements come back as camt, and the connection runs unattended from here.
Sources: OLB’s EBICS page, its imprint and company pages, its notice on the withdrawal of the older SEPA and account-information formats, its FAQ on payee verification and instant payments, its terms for remote data transmission effective 5 October 2025, its price and services list effective 1 October 2025, the LEI record published by GLEIF, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Oldenburgische Landesbank AG.
How BankConnector handles the November 2026 pain.001.001.09 migration for OLB →