Connect SozialBank without learning EBICS.
SozialBank’s host speaks EBICS 2.5 and 3.0, publishes 46 order types, and changes the format of every one of them in November 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.36 s
BankConnector
What is built and shipped for this bank today.
Exactly what we have done for SozialBank
SozialBank is not a generic EBICS target in our system. It has its own bank profile, carrying the German rulebook, the field limits, the scheme coverage and the bank’s own key fingerprints.
| Payment files | Your canonical JSON becomes the pain.001 credit transfer SozialBank 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, camt.052 intraday and camt.054 notifications, plus pain.002 status reports, and normalise all four into one format. SozialBank splits its status reports three ways (CRZ, CIZ and VPZ), and you see one shape. |
| The Host ID is shared | MULTIVIA is a shared gateway, so the Host ID names the platform, not the bank. What identifies you is the Partner ID and User ID on your EBICS agreement. We hold the rest, so the setup form arrives filled in. |
| EBICS 3.0 | The host runs 2.5 and 3.0. We connect over EBICS 3.0 (H005), with A006 signatures on RSA 2048 keys. |
| Bank keys | SozialBank publishes its E002 and X002 fingerprints. We hold both on file. The one exchange that cannot be re-verified later is verified before it happens. |
| Two signatures on a payment | SozialBank supports the distributed signature, and so do we. A payment can be raised by one person and released by another, with your approval policy deciding who, and the bank enforcing it. |
| The paperwork | We generate your keys, print the initialisation letter as a signed-ready PDF carrying the fingerprints SozialBank checks, and draft the email that opens the agreement. Private keys never leave the system. |
Published by the bank
From the bank's own EBICS page and its order-type schedule, dated April 2026.
What SozialBank supports
SozialBank publishes its access parameters openly, down to the fingerprints of its own bank keys. A treasury team can see the whole shape of the connection before speaking to anyone at the bank.
| Host ID | MULTIVIA |
| EBICS address | https://ebics.multivia-suite.de/ebicsweb/ebicsweb |
| Protocol versions | H004 (2.5) and H005 (3.0) |
| Signature version | A006 with RSA 2048, rising to 4096 in Nov 2027 |
| Bank key hashes | E002 and X002, published for both versions |
| Distributed signature | Supported: HVE, HVS, HVD, HVT, HVU, HVZ |
| Order types | 46 (25 business, 21 technical) |
| Statement formats | camt only, no MT940 or MT942 |
Published by the bank
SozialBank EBICS order types, all forty-six, mapped to 3.0
EBICS 3.0 replaces the three-letter order type with a business transaction format: a service, a scope, an option and the ISO 20022 message it carries. SozialBank publishes both columns side by side, so a 3.0 migration can be planned from the document. The last column is ours: what BankConnector drives on your behalf, and what it leaves alone.
| 2.5 | What it does | Dir | Service | Scope | Option | Message | Container | BankConnector |
|---|---|---|---|---|---|---|---|---|
| CCT | SEPA credit transfer, payee check opt-out | Send | SCT | VOO | pain.001 | Supported | ||
| CTV | SEPA credit transfer, payee check opt-in | Send | SCT | VOI | pain.001 | Supported | ||
| CCC | SEPA credit transfer, XML container | Send | SCT | DE | VOO | pain.001 | XML | Supported |
| CIP | Instant credit transfer, payee check opt-out | Send | SCI | VOO | pain.001 | Supported | ||
| CIV | Instant credit transfer, payee check opt-in | Send | SCI | VOI | pain.001 | Supported | ||
| CCU | Same-day urgent transfer in euro | Send | XCT | DE | URG | pain.001 | Supported | |
| AXZ | Foreign credit transfer, ISO 20022 | Send | XCT | DE | pain.001 | Supported | ||
| AZV | Foreign credit transfer, DTAZV (retires 14 Nov 2026) | Send | XCT | DE | dtazv | Not used | ||
| CDD | SEPA core direct debit | Send | SDD | COR | pain.008 | Not used | ||
| CDC | SEPA core direct debit, XML container | Send | SDD | DE | COR | pain.008 | XML | Not used |
| CDB | SEPA B2B direct debit | Send | SDD | B2B | pain.008 | Not used | ||
| C2C | SEPA B2B direct debit, XML container | Send | SDD | DE | B2B | pain.008 | XML | Not used |
| CCX | Service-centre release, credit transfer opt-out | Send | SCT | DE | 0CCX | pain.001 | SVC | Not used |
| VCX | Service-centre release, credit transfer opt-in | Send | SCT | DE | 0VCX | pain.001 | SVC | Not used |
| CDX | Service-centre release, core direct debit | Send | SDD | DE | 0CDX | pain.008 | SVC | Not used |
| C2X | Service-centre release, B2B direct debit | Send | SDD | DE | 0C2X | pain.008 | SVC | Not used |
| 2.5 | What it does | Dir | Service | Scope | Option | Message | Container | BankConnector |
|---|---|---|---|---|---|---|---|---|
| C53 | End-of-day account statement | Download | EOP | DE | camt.053 | ZIP | Supported | |
| C52 | Intraday transactions, not yet booked | Download | STM | DE | camt.052 | ZIP | Supported | |
| C54 | Debit and credit notification, batch detail | Download | STM | DE | camt.054 | ZIP | Supported | |
| CRZ | Payment status report, SEPA credit transfer | Download | REP | DE | SCT | pain.002 | ZIP | Supported |
| CIZ | Payment status report, instant credit transfer | Download | REP | DE | SCI | pain.002 | ZIP | Supported |
| VPZ | Verification of payee status report | Download | REP | DE | VOP | pain.002 | ZIP | Supported |
| CDZ | Payment status report, direct debit | Download | REP | DE | SDD | pain.002 | ZIP | Not used |
| BKA | Account statement as a signed PDF | Download | EOP | DE | ZIP | Not used | ||
| BKI | Account document collection, PDF | Download | DAR | DE | ZIP | Not used |
Six of those twenty-five are marked bilateral in the schedule: the four service-centre releases and the two PDF downloads. They exist only if you and the bank agree them separately, so treat them as available on request.
The remaining twenty-one are key management and protocol housekeeping. They keep their three-letter names in 3.0 and carry no business transaction format. These are ours end to end: you never see one, and we run them for you during setup and afterwards.
Published by the bank
Read out of the order-type schedule.
Verification of payee has been live since October 2025
SozialBank has separate order types for checked and unchecked submission, on both ordinary and instant credit transfers, plus a dedicated status report. The check can be declined per batch, which is why each rail has two codes.
| Rail | Opt in to the check | Opt out | Status report |
|---|---|---|---|
| SEPA credit transfer | CTV | CCT, CCC | VPZ |
| SEPA instant | CIV | CIP | VPZ |
| Service-centre release | VCX | CCX | VPZ |
BankConnector
Questions
- Which EBICS version does SozialBank use?
- Both. SozialBank's EBICS host answers on EBICS 2.5 (protocol H004) and EBICS 3.0 (protocol H005), which the bank states on its own EBICS page. BankConnector connects over EBICS 3.0 (H005).
- What is SozialBank's EBICS Host ID and URL?
- The Host ID is MULTIVIA and the EBICS address is https://ebics.multivia-suite.de/ebicsweb/ebicsweb. MULTIVIA is a shared gateway rather than a SozialBank-specific name: several other German banks answer at the same address. What identifies you to the bank is your Partner ID and User ID, which arrive with your EBICS agreement.
- Can I see SozialBank's EBICS order types before activating?
- Yes. SozialBank publishes its full order-type schedule as a public PDF, including the mapping from each EBICS 2.5 order type to its EBICS 3.0 business transaction format. The EBICS protocol itself will not tell you: the HAA, HTD and HKD orders that list order types are signed downloads that require an activated subscriber.
- Does SozialBank support MT940?
- No. SozialBank's published order-type schedule contains no STA and no VMK, which are the EBICS order types that carry MT940 and MT942. Statements are camt only: camt.053 end-of-day as C53, camt.052 intraday as C52 and camt.054 notifications as C54. A system that can only read MT940 cannot be pointed at this bank.
- Which EBICS order type delivers SozialBank camt.053 statements?
- C53 delivers SozialBank's end-of-day camt.053 account statement in a ZIP container. In EBICS 3.0 the same business transaction format is service EOP, scope DE, message camt.053. Intraday camt.052 arrives as C52 and debit and credit notifications as C54.
- Does SozialBank support Verification of Payee?
- Yes, since 9 October 2025. SozialBank has separate order types for payee-checked and unchecked submission on both SEPA credit transfers (CTV and CCT) and SEPA instant (CIV and CIP), plus a dedicated status report, VPZ. The check can be declined per batch.
- What changes for SozialBank EBICS in November 2026?
- At 00:01 on 14 November 2026 SozialBank stops accepting pain.001.001.03, pain.008.001.02 and pain.002.001.03, and requires pain.001.001.09 and pain.008.001.08 in their GBIC_4 or GBIC_5 variants. The DTAZV file format for foreign payments is switched off the same night, so the AZV order type gives way to AXZ. Unstructured postal addresses stop being accepted at the same moment. These are Deutsche Kreditwirtschaft dates rather than SozialBank ones, so they land on every German bank together.
- Can I connect my ERP to SozialBank?
- Yes. BankConnector connects an ERP or any other system to SozialBank over EBICS. You send canonical JSON and we produce the pain.001 credit transfer file SozialBank expects under the German DK Anlage 3 rulebook, then read camt.053, camt.052, camt.054 and pain.002 back into one normalised format. SEPA credit transfers, SEPA instant, same-day urgent 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.03 stops being accepted and pain.001.001.09 replaces it. Our engine emits both versions today, and which one a connection sends is a setting on the bank profile, not a rebuild. Nothing changes in what you send us.
DTAZV stops being a DK standard. Foreign payments move from the AZV order type to AXZ, carrying ISO 20022 instead of the old fixed record file. We have never produced DTAZV, so we drive AXZ and there is nothing here to migrate.
Addresses must be structured. A postal address written as free text is no longer accepted anywhere in the file. Our canonical input has carried street, building number, post code, town and country as separate fields since version 1.1, so the shape the bank now demands is the shape we already take. What it asks of you is that your ERP holds those fields separately.
RSA 2048 keys stop being enough. Every EBICS key pair has to be at least 4096 bits. Our key generator is sized per bank and already issues 4096-bit keys for banks that require them today. The move needs new keys and a new initialisation letter, which we generate and print as we did at setup.
If all of this looks like a lot, it does not have to be
Five steps to a live SozialBank 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 SozialBank
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 SozialBank 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 SozialBank 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 SozialBank 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 SozialBank: payments go out as pain.001, statements come back as camt, and the connection runs unattended from here.
Sources: SozialBank’s EBICS page, its order-type schedule dated April 2026, its own page on the 2026 changes and the EBICS specifications published by Die Deutsche Kreditwirtschaft. SozialBank AG was formerly named Bank für Sozialwirtschaft AG. BankConnector is not affiliated with SozialBank AG.
How BankConnector handles the November 2026 pain.001.001.09 migration for SozialBank →