Germany · Die Sparkasse Bremen · EBICS
Connect Sparkasse Bremen without learning EBICS.
The bank publishes its EBICS address, its bank key hashes and itemised set-up fees. EBICS 2.5 and 3.0, a 20:00 cut-off, and statements in camt or MT. We handle the payments 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>
Published by the bank
The bank's imprint and annual report.
Bank details
| BIC | SBREDE22 |
| Bank code | 290 501 01 |
| Legal name | Die Sparkasse Bremen AG |
| Registered office | Universitätsallee 14, 28359 Bremen |
| Register | HRB 21770, Amtsgericht Bremen |
| Owner | Finanzholding der Sparkasse in Bremen — 100%, a free savings bank |
Published by the bank
The bank's own annex and price list, plus our live check.
Access data
| EBICS address | https://hb6ebics.sparkasse-banking.de/ebicsweb/ebicsweb |
| Host ID | E86-ELKO |
| Protocol versions | H004 (02.50) and H005 (03.00) |
| Gateway operator | Finanz Informatik — one instance per institute |
| Bank key hashes | Four, published — E001, X001, E002, X002 |
| Distributed signature | Supported in full |
| Statement formats | camt and MT — C53, C52, C54, STA, VMK |
| Same-day cut-off | 20:00, Monday to Friday, remote data transmission |
| Direct debit lodgement | At the latest 1 business day before due date, by 11:30 |
The gateway is a Sparkassen-Finanzgruppe platform with one instance per institute. Sending a sibling savings bank’s Host ID to this address returns a plain HTTP 404, not an EBICS error, so a wrong Host ID looks like a network fault to a client that only watches for EBICS return codes.
Published by the bank
The schedule the bank publishes, dated May 2023.
Order types published by Sparkasse Bremen
| 2.5 | What it does | Dir | Message | Service | Scope | Option | Container |
|---|---|---|---|---|---|---|---|
| CCT | SEPA credit transfer | Send | pain.001 | SCT | — | — | — |
| CCC | SEPA credit transfer, XML container | Send | pain.001 | SCT | DE | — | XML |
| XCT | SEPA credit transfer, wages and salary | Send | pain.001 | SCT | BIL | — | — |
| CCU | Same-day urgent transfer in euro | Send | pain.001 | XCT | DE | URG | — |
| AZV | Foreign credit transfer, DTAZV | Send | dtazv | XCT | DE | — | — |
| CDD | SEPA core direct debit | Send | pain.008 | SDD | — | COR | — |
| CDC | SEPA core direct debit, XML container | Send | pain.008 | SDD | DE | COR | XML |
| CDB | SEPA B2B direct debit | Send | pain.008 | SDD | — | B2B | — |
| C2C | SEPA B2B direct debit, XML container | Send | pain.008 | SDD | DE | B2B | XML |
| 2.5 | What it does | Dir | Message | Service | Scope | Option | Container |
|---|---|---|---|---|---|---|---|
| C53 | End-of-day account statement | Download | camt.053 | EOP | DE | — | ZIP |
| STA | End-of-day statement, SWIFT MT940 | Download | mt940 | EOP | DE | — | — |
| C52 | Intraday transactions, not yet booked | Download | camt.052 | STM | DE | — | ZIP |
| VMK | Intraday transactions, SWIFT MT942 | Download | mt942 | STM | DE | — | — |
| C54 | Debit and credit notification, batch detail | Download | camt.054 | STM | DE | — | ZIP |
| CRZ | Payment status report, credit transfers | Download | pain.002 | REP | DE | SCT | ZIP |
| CIZ | Payment status report, instant transfers | Download | pain.002 | REP | DE | SCI | ZIP |
| CDZ | Payment status report, direct debits | Download | pain.002 | REP | DE | SDD | ZIP |
| C29 | Resolution of a recall request | Download | camt.029 | REP | DE | — | ZIP |
| BKA | Account statement as a signed PDF | Download | EOP | DE | — | ZIP |
Fourteen more cover service-centre submission, foreign-exchange rates, card services and documentary credits.
The rest are key management and protocol housekeeping. You never see one — we run them during setup and afterwards.
This schedule is dated May 2023, so it predates payee verification and carries no order types for it. The bank confirms in prose that payee verification applies from 5 October 2025 and that instant credit transfers can be submitted over EBICS, but does not publish the codes. Your agreement fixes which order types you get, and it is worth asking for those two explicitly.
Published by the bank
The bank's price and services list, July 2026.
What the bank charges to set it up
| Set up a Kunden-ID | 59,50 EUR |
| Set up a Teilnehmer-ID | 23,80 EUR |
| Set up an account | 11,90 EUR |
| Set up a service data centre's account | 35,70 EUR |
| Set up the WebSocket credit-advice service | 29,75 EUR |
| Other changes, e.g. order types | 11,90 EUR or by agreement |
| Remote data transmission, no electronic signature | 11,90 EUR per account per month |
| Electronic statement, camt.052 or camt.053 | 7,50 EUR per account per month |
Few banks publish these at all. Per-transaction pricing depends on your account model and is not in this table.
BankConnector
What is built and shipped for this bank today.
What our engine produces
| 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 |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Read back | camt.053, camt.052, camt.054, pain.002 — one format |
| Not supported | Direct debits |
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
- Not published
The bank’s own EBICS keys are replaced across the savings-bank platform, and yearly after. Sparkasse Bremen has not published its date. Each institute sets its own, so ask the bank rather than taking a sibling’s.
The older SEPA format versions are withdrawn, AXZ replaces DTAZV for foreign payments, and addresses must be structured or hybrid. We produce pain.001.001.09 and have never produced DTAZV.
Every EBICS key pair has to reach 4096 bits. New keys and a new initialisation letter.
If all of this looks like a lot · it does not have to be
Five steps to a live Sparkasse Bremen 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 Sparkasse Bremen
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 Sparkasse Bremen 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 Sparkasse Bremen will check. You sign it by hand and send it.
- 4
Verify Sparkasse Bremen 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
You are now in production with Sparkasse Bremen
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — the bank’s EBICS page, its Anlage 1 for the electronic account-keeping service, its published order-type schedule dated May 2023, its price and services list dated July 2026, its terms for electronic statements, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Die Sparkasse Bremen AG.
How BankConnector handles the November 2026 pain.001.001.09 migration for Sparkasse Bremen →