Connect apoBank without learning EBICS.
apoBank runs its own gateway on Host ID EBXDXC, serving four EBICS versions. It switches off several older payment formats on 1 October 2026, six weeks before the rest of Germany.
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
EBXDXC
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.11 s
Published by the bank
The bank's imprint.
Bank details
| BIC | DAAEDEDD |
| Bank code | 300 606 01 |
| Legal name | Deutsche Apotheker- und Ärztebank eG |
| Registered office | Richard-Oskar-Mattern-Str. 6, 40547 Düsseldorf |
| Register | GnR 410, Amtsgericht Düsseldorf |
| Group | Genossenschaftliche FinanzGruppe Volksbanken Raiffeisenbanken |
Checked live
Measured against the live host.
Access data
| EBICS address | https://ebics.apobank.de/ |
| Host ID | EBXDXC (upper case, case-sensitive) |
| Protocol versions | H002 (02.30), H003 (02.40), H004 (02.50), H005 (03.00) |
| Gateway | apoBank's own, on its own network |
| Your IDs | Partner ID, User ID and System ID, issued with the contract |
| Distributed signature | Supported, and apoBank ships its own signing app |
| Statement formats | camt.053 v8 and camt.052, while MT940 and MT942 still run |
Published by the bank
From the bank's own instant-payment and payee-check factsheets.
Order types published by apoBank
| 2.5 | What it does | 3.0 BTF | Direction |
|---|---|---|---|
| CTV | SEPA credit transfer, payee check opt-in | SCT//VOI/pain.001 | Send |
| CCT | SEPA credit transfer, payee check opt-out | SCT//VOO/pain.001 | Send |
| CIV | Instant credit transfer, payee check opt-in | SCI//VOI/pain.001 | Send |
| CIP | Instant credit transfer, payee check opt-out | SCI//VOO/pain.001 | Send |
| XIV | Instant, opt-in, with fallback execution | SCI//VOI/pain.001 | Send |
| XIP | Instant, opt-out, with fallback execution | SCI//VOO/pain.001 | Send |
| VPZ | Payee verification status report | REP/DE/VOP/pain.002/ZIP | Download |
| CIZ | Payment status report, instant transfers | REP/DE/SCI/pain.002/ZIP | Download |
| C5N | Incoming instant payments | STM/DE/SCI/camt.054/ZIP | Download |
Two rules decide how payee verification behaves in an automated flow. A file holding a single payment must use an opt-in order type or the payment is rejected. And with opt-in, authorisation happens only after the status report arrives, through the distributed signature, so a signature given before that point is discarded.
Published by the bank
The bank's price and services list. These are electronic-channel deadlines, not EBICS-specific.
Cut-off times
| Germany and EEA, in EUR or an EEA currency | 17:00 on bank business days |
| SEPA credit transfers, EEA and SEPA third countries | 17:00 on bank business days |
| Non-EEA currency, or outside the EEA and SEPA | 12:00 on bank business days |
| SEPA instant | No deadline: 24 hours, 7 days, 365 days |
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 |
| Character set | Latin, transliterated before the bank sees it |
| Read back | camt.053 and pain.002, normalised into one format |
| Not supported | Direct debits |
BankConnector
Questions
- What is apoBank's EBICS Host ID and URL?
- Host ID EBXDXC, address https://ebics.apobank.de/. The Host ID is case-sensitive and must be upper case. apoBank runs its own gateway on its own network rather than a shared sector platform. Your Partner ID, User ID and System ID arrive from the bank with your contract documents.
- Which EBICS versions does apoBank support?
- Four: EBICS 2.3 (protocol H002), 2.4 (H003), 2.5 (H004) and 3.0 (H005).
- Does apoBank still support MT940?
- Yes, for now, and this is unusual among German banks. apoBank states it will keep MT940 and MT942 until further notice but will not develop them further, and reserves the right to retire them in the medium term. It offers camt.053 version 8 today, so the two run in parallel. No end date has been published.
- Does apoBank support Verification of Payee?
- Yes, on SEPA credit transfers and instant payments, but not on direct debits or Target2 urgent payments. Opt-in and opt-out are chosen by order type: CTV and CIV opt in, CCT and CIP opt out, and VPZ returns the status report. Two rules matter for automation. A file containing a single payment must use an opt-in order type or it is rejected outright. And with opt-in, authorisation happens only after the status report arrives, through the distributed signature, so any signature given before that is discarded.
- What changes at apoBank on 1 October 2026?
- apoBank stops accepting several older formats across every channel, including EBICS: pain.001.002.03, pain.001.003.03, pain.001.001.03 in its GBIC_3 form, pain.008.003.02, pain.008.001.02 in its GBIC_3 form, and DTAZV for foreign payments. That is six weeks earlier than the German industry-wide format change in November 2026. BankConnector already produces pain.001.001.09. It is one of the two versions our engine emits, and other banks run on it today.
- Can I connect my ERP to apoBank?
- Yes. You send canonical JSON and BankConnector produces the pain.001 credit transfer file the German DK Anlage 3 rulebook requires, then reads camt.053 and pain.002 back into one normalised format. SEPA credit transfers, SEPA instant, domestic 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
Older formats stop being accepted on every channel: pain.001.002.03, pain.001.003.03, pain.001.001.03 in its GBIC_3 form, pain.008.003.02, pain.008.001.02 GBIC_3, and DTAZV. Six weeks ahead of the industry date. pain.001.001.09 is already one of the two versions our engine produces, and other banks run on it today.
Foreign payments move to pain.001.001.09 in the AXZ form under the 3.9 rulebook. We have never produced DTAZV.
The German industry-wide change: pain.001.001.09 replaces pain.001.001.03, and unstructured postal addresses stop being accepted anywhere in the file. Covered on both counts: we produce .09, and canonical input 1.1 has taken addresses as separate fields since it shipped.
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 apoBank 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 apoBank
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 apoBank 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 apoBank 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 apoBank 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 apoBank: payments go out as pain.001, statements come back as camt, and the connection runs unattended from here.
Sources: apoBank’s EBICS page and its factsheets on instant payments, payee verification and address formats, its price and services list, its terms for remote data transmission, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Deutsche Apotheker- und Ärztebank eG.
How BankConnector handles the November 2026 pain.001.001.09 migration for apoBank →