← All supported banks

Germany  ·  Nassauische Sparkasse  ·  EBICS

Connect Naspa without learning EBICS.

EBICS 2.5 and 3.0 on Host ID HE7-ELKO, a 16:00 cut-off for remote data transmission, and statements in camt only. We handle the payments and every protocol step underneath.

The host, 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
HE7-ELKO
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.29 s

Published by the bank

The bank's imprint and annual report.

Bank details

BICNASSDE55XXX
Bank code510 500 15
Legal nameNassauische Sparkasse, Anstalt des öffentlichen Rechts
Registered officeRheinstraße 42–46, 65185 Wiesbaden
Register · LEIHRA 4647, Wiesbaden · 529900CJAJ0HDPPKUI53
VAT IDDE 113821300
TrägerSparkassenzweckverband Nassau — a Körperschaft des öffentlichen Rechts
Zweckverband membersWiesbaden · Frankfurt am Main · Hochtaunuskreis · Limburg-Weilburg · Main-Taunus · Rheingau-Taunus · Rhein-Lahn · Westerwaldkreis
SupervisionBaFin · European Central Bank · Hessisches Wirtschaftsministerium

Checked live

Measured against the live host.

Access data

EBICS addresshttps://he7ebics.sparkasse-banking.de/ebicsweb/ebicsweb
Host IDHE7-ELKO
Protocol versionsH004 (02.50) and H005 (03.00)
Answered in0.29 s
Gateway operatorFinanz Informatik — one instance per institute
Bank key hashesOne authentication key hash and two certificate hashes
Distributed signatureVEU — required to release an order that carried a payee check
Statement formatscamt.053, camt.052, camt.054 — version 08
Same-day cut-off16:00 on Naspa business days, remote data transmission
Direct debit lodgement28 calendar days to 1 business day before due date, by 12:00

The gateway is a Sparkassen-Finanzgruppe platform with one instance per institute. The Host ID and the address are the same for every Naspa customer. Your Kunden-ID and Teilnehmer-ID are what identify you, and both are issued with the agreement.

Published by the bank

The schedule the bank publishes, dated 25 February 2020.

Order types published by Naspa

Send
2.5What it doesDirMessageServiceScopeOptionContainer
CCTSEPA credit transferSendpain.001SCT
CCCSEPA credit transfer, XML containerSendpain.001SCTDEXML
XCTSEPA credit transfer, wages and salarySendpain.001SCTBIL
CIPInstant credit transfers, batchSendpain.001SCIDE
CCUSame-day urgent transfer in euroSendpain.001XCTDEURG
AZVForeign credit transfer, DTAZVSenddtazvXCTDE
CDDSEPA core direct debitSendpain.008SDDCOR
CDCSEPA core direct debit, XML containerSendpain.008SDDDECORXML
CDBSEPA B2B direct debitSendpain.008SDDB2B
C2CSEPA B2B direct debit, XML containerSendpain.008SDDDEB2BXML
GBZGeldKarte transaction dataSendbzahlOTHDE
AIAImport letter of creditSenddtalcIDCDE
AIDImport letter of credit, document lodgementSenddtalcaIDCDE
Download
2.5What it doesDirMessageServiceScopeOptionContainer
C53End-of-day account statementDownloadcamt.053EOPDEZIP
STAEnd-of-day statement, SWIFT MT940Downloadmt940EOPDE
C52Intraday transactions, not yet bookedDownloadcamt.052STMDEZIP
VMKIntraday transactions, SWIFT MT942Downloadmt942STMDE
C54Debit and credit notification, batch detailDownloadcamt.054STMDEZIP
CRZPayment status report, credit transfersDownloadpain.002REPDESCTZIP
CIZPayment status report, instant transfersDownloadpain.002REPDESCIZIP
CDZPayment status report, direct debitsDownloadpain.002REPDESDDZIP
BKAAccount statement as a signed PDFDownloadpdfEOPDEZIP
DKIForeign-exchange rates in euroDownloadmiscOTHBIL0DKI
EABExport letter of creditDownloaddtaeaEDCDE
EADExport letter of credit, settlementDownloaddtaeadEDCDE
AKAImport letter of creditDownloaddtalcrIDCDE
AKDImport letter of credit, settlementDownloaddtalcdIDCDE
GRCGeldKarte processing result filesDownloadmiscOTHBIL0GRC

Two rows of that schedule are already dead. STA and VMK carry MT940 and MT942, and Naspa switched both off in November 2025 along with camt version 02. Statements arrive as camt version 08.

Three more submit through a service data centre and are settled inside the distributed signature.

CCXCDXC2X

The rest are key management and protocol housekeeping. You never see one — we run them during setup and afterwards.

INIHIAHPBHCAHCSPUBSPRHAAHTDHKDHPDHEVHACPTKHVEHVSHVDHVTHVUHVZ

Published by the bank

The bank's notice on the statutory credit-transfer changes.

Payee verification order types

2.5What it does3.0 BTFDirection
CTVSEPA credit transfer, payee check opt-inSCT / — / VOI / pain.001Send
CIVInstant credit transfer, payee check opt-inSCI / — / VOI / pain.001Send
CCTSEPA batch transfer, payee check opt-outSCT / — / VOO / pain.001Send
CIPInstant batch transfer, payee check opt-outSCI / — / VOO / pain.001Send
VPZPayee verification status reportREP / DE / VOP / pain.002 / ZIPDownload

All five are available since 5 October 2025. A single credit transfer is always checked; a batch of more than one transaction is the corporate’s choice. Under EBICS a checked batch can only be released or refused whole — partial authorisation is not possible — and the distributed electronic signature is required to do either.

Published by the bank

The bank's price and services list, Fassung 10.07.2026, v22.3.

What the bank charges to set it up

Set up a Kunden-ID50,00 EUR once
Provide a Kunden-ID7,50 EUR per month
Set up an additional Kunden-ID50,00 EUR once
Provide an additional Kunden-ID7,50 EUR per month
Set up a Teilnehmer-IDFree
Set up an accountFree
Account number for a DATEV or other data-centre Kunden-IDFree
Add an access or participation authorisation25,00 EUR per order
Other changes to electronic account keeping25,00 EUR per order
Set up an account for processing via a data centre25,00 EUR once
Data transfer per file, with or without electronic signature0,35 / 0,25 / 0,12 EUR
Electronic statement, camt.0537,50 EUR per account per month
Electronic advice, camt.052Free
Access via Online-Banking Business Pro300,00 EUR once, 15,00 EUR per month, plus VAT

The three per-file figures are the Giro Business, Giro Business Plus and Giro Business Pro account models in that order. Per-transaction pricing follows the same split and is not in this table.

BankConnector

What is built and shipped for this bank today.

What our engine produces

Bank keynaspa-de
Payment formatpain.001.001.03
Also producedpain.001.001.09 — live for other banks today
RulebookGerman DK Anlage 3 v3.9 / 2025-03
Charge bearerSLEV
Batch bookingfalse
Remittance limit140 characters
Name limit70 characters
Character setLatin — transliterated before the bank sees it
Payment types builtSEPA credit transfer · SEPA instant · domestic · international
Read backcamt.053, camt.052, camt.054, pain.002 — one format
Not supportedDirect debits

Naspa offers CDD, CDC, CDB and C2C for direct debits. Our engine produces none of them, and no payment has yet been run through this connection.

Published by the bank

Dates the bank has announced. What we do about each one is ours.

Upcoming events in our register

  1. Not published

    Savings banks on this platform replace their public EBICS bank certificates and the hash values for the authentication and encryption keys, and yearly after. Naspa publishes neither a date nor the new hash values.

  2. SEPA format versions 3.0 to 3.6 are withdrawn with the older pain formats. Credit transfers move to pain.001.001.09, direct debits to pain.008.001.08, status reports to pain.002.001.10. Naspa names the month and no day. Our engine emits pain.001.001.09 today.

  3. AXZ replaces DTAZV for foreign payments, as pain.001.001.09_AXZ_GBIC_4 and higher. Euro urgent transfers move to pain.001.001.09_CCU_GBIC_4 and higher. We have never produced DTAZV.

  4. Payment orders carrying unstructured addresses are rejected. Structured needs at least town and country; hybrid allows the rest in at most two AdrLine 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 Naspa 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. 1

    Request the agreement from Naspa

    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 Naspa 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 Naspa will check. You sign it by hand and send it.

  4. 4

    Verify Naspa 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 Naspa

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

Sources — Naspa’s EBICS page, its Electronic Banking mit EBICS order-type schedule dated 25 February 2020, its Formatabkündigung notice, its notice on the statutory changes to credit transfers, its Preis- und Leistungsverzeichnis (Fassung 10.07.2026, v22.3), its imprint and its annual report, and the EBICS specifications published by Die Deutsche Kreditwirtschaft. BankConnector is not affiliated with Nassauische Sparkasse.

How BankConnector handles the November 2026 pain.001.001.09 migration for Naspa →

← Back to all supported banks