← All supported banks

Germany  ·  Volksbanken Raiffeisenbanken  ·  EBICS

Connect a Volksbank or Raiffeisenbank without learning EBICS.

One shared EBICS gateway, Host ID MULTIVIA, on EBICS 2.5 and 3.0. Your own bank issues your IDs and sets the rest. We produce pain.001.001.09 for the whole sector.

The shared gateway, checked live

<ebicsHEVResponse xmlns="http://www.ebics.org/H000">
  <SystemReturnCode>
    <ReturnCode>000000</ReturnCode>
    <ReportText>[EBICS_OK] OK</ReportText>
  </SystemReturnCode>
  <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.18 s

A shared gateway: the same host answers for every bank on it. Each bank issues its own Kunden-ID and Teilnehmer-ID.

Published by the sector

Atruvia, DZ BANK, the BVR and Die Deutsche Kreditwirtschaft.

The sector

IT and platformAtruvia AG — more than 900 customers, including all German Volksbanken and Raiffeisenbanken
EBICS bank systemMultivia Business — operated by Atruvia for its banks and their corporate customers
Central institutionDZ BANK — apex institution of the Genossenschaftliche FinanzGruppe and central bank for the cooperative banks
AssociationBVR — Bundesverband der Deutschen Volksbanken und Raiffeisenbanken, the umbrella association of the cooperative banks
Cooperative banks646 at the end of 2025 — Volksbanken, Raiffeisenbanken, Sparda-Banken, PSD Banken and other cooperative banks
Format rulebookDFÜ-Abkommen Anlage 3 — Die Deutsche Kreditwirtschaft, of which the BVR is a member

Published by the sector

Atruvia's Multivia page and DZ BANK's EBICS access data, the same values member banks publish, e.g. Frankfurter Volksbank. Versions from our live check.

What is the same at every member bank

EBICS addresshttps://ebics.multivia-suite.de/ebicsweb/ebicsweb
Host IDMULTIVIA — shared, names the platform rather than your bank
Protocol versionsH004 (02.50) and H005 (03.00)
OperatorAtruvia — Multivia Business
Bank key hash X00288 74 C8 0B 8C 15 F3 B8 36 B2 2A 6B A6 71 73 61 7D ED 21 54 BC EE 33 36 10 27 08 29 E1 A8 29 8B
Bank key hash E002C4 03 6E 7D 17 31 7B 8F 8C DE 3C D2 C8 1E ED 3C 4E 3F BD 92 4D A3 F3 C0 B4 24 E5 16 0A 27 FE 48
Your IDsKunden-ID and Teilnehmer-ID — issued by your bank
Atruvia EBICS clientMultivia Sm@rt Connect (MVSC) — Java 1.8 or 17

The key hashes belong to the gateway, not to one bank. Verifying them proves you reached the right host. Your Kunden-ID and Teilnehmer-ID are what identify you to your own bank.

Published by the sector

The BVR's consumer notice of 23 September 2025.

Verification of Payee

ObligationFrom 9 October 2025 at the latest — most institutions from 5 October 2025
ScopeTransfers and instant transfers in euro, within the euro area first
ExtensionAll EU member states by mid-2027
Opt-outCompanies, in certain cases — private customers cannot opt out
ResultsMatch · close match, with the correct name shown · no match
DecisionThe payer decides whether to execute or cancel

Published by member banks

As published by member banks on the Atruvia platform, e.g. Volksbank Mittelhessen eG.

Payee verification order types

2.5What it does3.0 BTF
CCTSEPA credit transfer, payee check opt-outSCT//VOO/pain.001/
CIPInstant credit transfer, payee check opt-outSCI//VOO/pain.001/
CTVSEPA credit transfer, payee check opt-inSCT//VOI/pain.001/
CIVInstant credit transfer, payee check opt-inSCI//VOI/pain.001/
VPZPayee verification status report, 1..n pain.002 in a ZIPREP/DE/VOP/pain.002/ZIP

A file holding a single transaction goes under an opt-in order type; sent under opt-out, the bank system rejects it. An opt-in file is authorised or cancelled as a whole, through the distributed signature, once its VPZ report is final.

No sector body publishes a full order-type schedule. The complete set on your connection is fixed by your EBICS agreement with your bank.

Published by member banks

Each cooperative bank is an independent institution.

What each bank sets itself

BICSet by your bank
Bank codeSet by your bank
Legal name and registerSet by your bank
Kunden-ID · Teilnehmer-IDSet by your bank
Order types in your agreementSet by your bank
pain.001.001.09 switch dateSet by your bank
End of DTAZV · MT940Set by your bank
Statement formatsSet by your bank
Cut-off timesSet by your bank
EBICS feesSet by your bank
Contract and DFÜ conditionsSet by your bank
Security mediumSet by your bank

For one member bank’s own values on each of these, see the Berliner Volksbank guide.

BankConnector

What is built and shipped for the cooperative sector today.

What our engine produces

ProfileOne profile for the whole cooperative sector
Payment formatpain.001.001.09
RulebookGerman DK Anlage 3 v3.9, shared cooperative format
Charge bearerSLEV
Batch bookingFalse
Remittance limit140 characters
Name limit70 characters
Character setLatin — transliterated before the bank sees it
Debtor BICNo single-BIC rule — your own bank's BIC is accepted
Payment types builtSEPA credit transfer · SEPA instant · domestic account transfer · international
Read backcamt, pain.002 — one normalised format
Not supportedDirect debits

If all of this looks like a lot  ·  it does not have to be

Five steps to a live connection with your cooperative bank.

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. 1

    Request the agreement from your cooperative bank

    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. 2

    Set up and send your keys

    Enter the values from the agreement your cooperative bank 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. 3

    Prove your identity on paper

    EBICS confirms the key exchange on paper, by design. We print the initialisation letter carrying the fingerprints your cooperative bank will check. You sign it by hand and send it.

  4. 4

    Verify your cooperative bank 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. 5

    You are now in production with your cooperative bank

    Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.

Sources — Atruvia’s Multivia page, its facts and figures, DZ BANK’s EBICS page, its profile, the BVR’s description of its role, its results release of 10 March 2026 and its notice on payee verification, Frankfurter Volksbank’s EBICS parameters, Volksbank Mittelhessen’s payee verification notes for EBICS, the Die Deutsche Kreditwirtschaft member list and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Atruvia AG, DZ BANK AG, the BVR or any cooperative bank.

How BankConnector handles the pain.001.001.09 migration, bank by bank →

← Back to all supported banks