Switzerland · Zürcher Kantonalbank · EBICS
Connect ZKB without learning EBICS.
EBICS 2.5 and 3.0 on Host ID ZKBKCHZZ, bank key hashes on a published parameter sheet and Datalink EBICS free to use. We handle the payments, the statements 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>
Host ID
ZKBKCHZZ
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.37 s
Published by the bank
The bank's general-information, history and state-guarantee pages; the Swiss UID register, GLEIF and FINMA.
Bank details
| BIC | ZKBKCHZZ80A |
| Clearing number (IID) | 700 |
| Legal name | Zürcher Kantonalbank |
| Legal form | Independent institution under public law, of Zurich cantonal and Swiss law (selbständige öffentlich-rechtliche Anstalt) |
| Registered office | Bahnhofstrasse 9, 8001 Zürich |
| UID | CHE-108.954.607 |
| Commercial register | CH-020.8.900.022-4 |
| LEI | 165GRDQ39W63PHVONY02 |
| In business since | 15 February 1870 |
| Endowment capital | Provided by the Canton of Zurich |
| State guarantee | The Canton of Zurich is liable for all of the bank's liabilities, except subordinated ones, insofar as its own funds are insufficient |
| Supervision | FINMA — authorised bank, supervisory category 2 |
| Systemic importance | Named by FINMA as a systemically important bank |
| Switchboard | 0844 843 823 |
Checked live
Measured against the live host, at the address and Host ID on the bank's connection-parameter sheet.
Access data
| EBICS address | https://ebicsweb.zkb.ch/ebicsweb |
| Host ID | ZKBKCHZZ |
| Port | 443 |
| Protocol versions | H004 (02.50) and H005 (03.00) |
Published by the bank
The bank's EBICS connection-parameter sheet, its Datalink EBICS page, its EBICS help page and its ISO 20022 handbook.
Keys, signatures and the agreement
| Service name | Datalink EBICS |
| Agreement | Datalink EBICS agreement with ZKB |
| Requirements | An account with ZKB, a Datalink agreement and financial software with an integrated EBICS interface |
| Price | Use of Datalink EBICS free of charge · processing of the orders is charged |
| Versions on the sheet | 2.5 (schema H004) and 3.0 (schema H005) |
| Authentication | X002 |
| Encryption | E002 |
| Electronic signature | A005 and A006 |
| Key length | Not published |
| Customer ID and user ID | Both correspond to the Datalink agreement number |
| Corporate seal | User ID and customer ID identical · exactly one user ID per Datalink agreement, with signature class single signature (E) |
| Releasing payment orders | ZKB recommends release through eBanking |
| Distributed signature (VEU) order types | Not published |
| Bank key hashes | Published on the sheet for X002 and E002 — public-key hashes for H004 and H005, certificate hashes for H005 with certificates |
| Key changes | HCA (authentication and encryption) · HCS (signature, authentication and encryption) |
| Blocking access | SPR |
| SignatureFlag | Must always be included — orders without it are rejected |
| Correcting a rejected payment | Possible in eBanking · with Datalink EBICS this requires mutation rights for eBanking |
| Multibanking | Payments to debit third-party bank accounts with an additional Multibanking agreement |
| End of EBICS 2.5 | Not published |
| Agreement requests and support | By phone, 0800 800 825 · Mon–Fri 08:00–17:00 |
Published by the bank
The bank's EBICS connection-parameter sheet (11/25).
Order types published by ZKB
| 2.5 | What it does | Dir | 3.0 BTF | Option | Container | Versions |
|---|---|---|---|---|---|---|
| XE2 | Payment initiation, CH | BTU | MCT · CH · pain.001 | — | — | 03 · 09 |
| XCT | Payment initiation, CGI with CH definitions | BTU | MCT · CGI · pain.001 | XCH | — | 03 · 09 |
| CCT | SEPA payment initiation | BTU | SCT · GLB · pain.001 | — | — | 03 · 09 |
| RFT | SWIFT payment initiation | BTU | RFT · GLB · mt101 | — | — | — |
| XL1 | CH direct debit initiation (LSV) | BTU | DDD · CH · ta875 | — | — | — |
| Z01 | Payment status report | BTD | PSR · CH · pain.002 | — | ZIP | 03 · 10 |
| Z52 | Intraday statement | BTD | STM · CH · camt.052 | — | ZIP | 04 · 08 |
| VMK | Intraday statement, SWIFT | BTD | STM · CH · mt942 | — | — | — |
| Z53 | Account statement | BTD | EOP · CH · camt.053 | — | ZIP | 04 · 08 |
| STA | Account statement, SWIFT | BTD | EOP · CH · mt940 | — | — | — |
| ZK6 | Financial-institution account statement | BTD | EOP · GLB · mt950 | — | — | — |
| ZS2 | Additional booking information report | BTD | REP · CH · camt.054 | XDCI | ZIP | 04 · 08 |
| ZK1 | Confirmation of debit | BTD | STM · GLB · mt900 | — | — | — |
| ZK2 | Confirmation of credit | BTD | STM · GLB · mt910 | — | — | — |
| ZS4 | Aggregate booking details, debit transactions only | BTD | REP · CH · camt.054 | XABK | ZIP | 04 · 08 |
| ZDF | Bank documents, PDF | BTD | DAR · CH · documents | — | ZIP | — |
| ZST | Account statement, multibanking | BTD | EOP · — · mt940 | — | — | — |
| ZVM | Intraday statement, multibanking | BTD | STM · — · mt942 | — | — | — |
| Z54 | Aggregate booking details, structured-reference credits (QRR, SCOR, LSV, IP) | BTD | REP · CH · camt.054 | — | ZIP | 04 · 08 |
| ZB6 | Aggregate booking details, LSV credits only | BTD | REP · CH · v11 | — | — | — |
| ZQR | Aggregate booking details, QRR credits only | BTD | REP · CH · camt.054 | XQRR | ZIP | 04 · 08 |
| ZRF | Aggregate booking details, SCOR credits only | BTD | REP · CH · camt.054 | XSCR | ZIP | 04 · 08 |
| ZS3 | Aggregate booking details, LSV credits only | BTD | REP · CH · camt.054 | XDDD | ZIP | 04 · 08 |
Uploads run as BTU and downloads as BTD. Each ISO 20022 BTF is also listed without a version. Scope GLB may also be left empty. XE2, XCT and CCT are validated against the CH schema of the Swiss Payment Standards and the bank’s own specifications; XE2, XCT and RFT can also debit third-party bank accounts.
Delivery notes on the sheet: STA statements come concatenated in one file, VMK every 15 minutes as a delta, HAC and PTK concatenated, ZB6 concatenated with one total record per day and customer ID.
The administration order types: key initialisation, signature key, blocking, available order types, customer and user data, key changes, supported versions, the bank’s public keys and parameters, and the customer and status protocols. We run them during setup and afterwards.
Published by the bank
The bank's cut-off times and provision of data sheet (February 2026) and its ISO 20022 handbook.
Cut-off times and execution
Cut-offs for same-day execution through electronic channels, including Datalink, in CET. V is the execution date. A single payment is a file with at most one payment per B-level; everything else is a collective order.
| Currency | Single payment | Collective order |
|---|---|---|
| CHF | 16:30 V | 12:00 V |
| EUR, non-SEPA | 15:00 V | 12:00 V |
| EUR, SEPA | 15:00 V | 12:00 V |
| USD | 15:00 V | 12:00 V |
| GBP | 15:00 V | 12:00 V |
| CAD | 15:00 V | 12:00 V |
| DKK, NOK, SEK, ZAR, MXN | 11:00 V | 09:00 V |
| CZK, HUF, PLN, TRY | 09:00 V | 07:00 V |
| AUD, CNY, HKD, JPY, NZD, SGD | 14:00 V−1 | 12:00 V−1 |
| AED, ILS, RON, SAR | 13:00 V−1 | 11:00 V−1 |
| THB | 09:00 V−1 | 07:00 V−1 |
| INR, KWD, MAD, QAR, TND | 13:00 V−2 | 11:00 V−2 |
| RUB | Not possible at the moment | Not possible at the moment |
| CHF single payments | Issued between 13:00 and 16:30 for a surcharge |
| Urgent single payments | EUR until 15:30 · USD until 16:00 — for an additional charge |
| KWD, QAR, SAR | Friday not permitted as value date |
| MXN | Only to Mexico |
| Before public holidays | Earlier cut-offs may apply |
| Orders after the cut-off | Executed on the next possible bank working day |
| Execution date, file transfer | At most 10 days in the past and 1 year in the future · a non-working day moves to the next bank working day |
| More than 99 single payments in one file | Collective-order cut-offs apply from the 100th payment |
Published by the bank
The bank's ISO 20022 V2019 handbook, its connection-parameter sheet and its cut-off times and provision of data sheet.
Formats and validation
| pain.001 schemas accepted | pain.001.001.09.ch.03 · pain.001.001.03.ch.02 · pain.001.001.09 · pain.001.001.03 · pain.001.003.03 |
| Validation | Against the SIX schema (V2019 or V2009) and the bank's own specifications, whatever schema is submitted |
| Payment types | D (domestic), S (SEPA) and X (cross-border and domestic in foreign currency) |
| pain.002 | pain.002.001.10 for pain.001.001.09.ch.03 · pain.002.001.03.ch.02 for pain.001.001.03.ch.02 |
| pain.002 over Datalink EBICS | Two statuses — ACTC or RJCT from the EBICS server, then ACCP, ACWC, PART or RJCT from processing |
| Schema errors | The entire message is rejected |
| camt.052 · camt.053 · camt.054 | Versions 08 and 04, in a ZIP |
| SWIFT | mt101 upload · mt940, mt942, mt950, mt900 and mt910 download |
| Maximum transactions | 99,999 C-levels per pain.001 |
| Duplicate checks | Hash of the file on the EBICS server, identical file rejected for 5 days · message ID unique for 90 days · matching count and control total over 10 days for files above ten payments |
| Batch booking | true or empty: one collective booking per B-level · false: single bookings · always true for salary and pension payments |
| Charge bearer | DEBT, CRED, SHAR or SLEV · SLEV for SEPA · SHAR when absent · not at B- and C-level together |
| Debtor agent | BIC ZKBKCHZZ or ZKBKCHZZ80A, or IID 700 with code CHBCC — not both · the third-party BIC for multibanking |
| Instruction for debtor agent | At most 140 characters · usually leads to manual post-processing |
| Unstructured addresses | Accepted until 13 Nov 2026 |
| Structured addresses | Mandatory from 14 Nov 2026 — at least name, town and country · unstructured addresses with a later execution date are rejected |
| Hybrid addresses | Supported |
| End of the V2009 schemas | Nov 2026 |
| End of MT940 | Not published |
Delivery of reporting over Datalink EBICS, as the bank gives it:
| camt.053 · MT940 | End-of-day processing, from 23:00 · daily, or only when there are movements |
| camt.052 · MT942 | Between 06:00 and 18:00 when there are movements · newly added bookings only · quarter-hourly, half-hourly, hourly or at chosen intervals |
| camt.054 QRR/SCOR/LSV, collective | Once a day from 05:00, or five times: 05:00, 09:00, 13:00, 15:00, 17:30 · Mon–Fri |
| camt.054 QRR/SCOR instant credits | Immediately after booking, every day |
| camt.054 grouped notification | 07:15 once a day, or at chosen intervals · Mon–Fri |
| camt.054 DBTN/CDTN · MT900/MT910 | Immediately after booking |
| PDF bank documents | All documents of the day at the time of retrieval |
BankConnector
What is built and shipped for this bank today.
What our engine produces
| Payment format | pain.001.001.09 (Swiss Payment Standards, ch.03 schema) |
| Charge bearer | SLEV on SEPA payments · SHAR on all others |
| Batch booking | False |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Character set | Latin — transliterated before the bank sees it |
| Payment types built | SEPA credit transfer · Swiss domestic transfer · QR-bill payment · international |
| Read back | camt, pain.002 — one normalised format |
| Not supported | Direct debits |
BankConnector
Questions
- What is Zürcher Kantonalbank's EBICS Host ID and URL?
- Host ID ZKBKCHZZ, address https://ebicsweb.zkb.ch/ebicsweb, port 443. ZKB publishes both on its EBICS connection-parameter sheet, together with the hash values of its X002 and E002 keys. Your customer ID and user ID both correspond to your Datalink agreement number.
- Which EBICS versions does ZKB support?
- EBICS 2.5 (schema H004) and 3.0 (schema H005); the host answers H004 (02.50) and H005 (03.00). ZKB has published no end date for EBICS 2.5.
- Which keys and signature does ZKB use for EBICS?
- X002 for authentication, E002 for encryption and A005 or A006 for the electronic signature. ZKB publishes public-key hashes for H004 and H005 and certificate hashes for H005 with certificates. Keys are changed with HCA or HCS and access is blocked with SPR. The SignatureFlag must always be included; orders without it are rejected.
- How are payments released at ZKB?
- With a corporate seal, one user ID per Datalink agreement signs with signature class single signature (E). ZKB recommends releasing payment orders through eBanking. It publishes no distributed-signature (VEU) order types on its parameter sheet.
- Which order types does ZKB use for EBICS 3.0?
- Payments upload as BTU MCT/CH/pain.001 (XE2), MCT/CGI/pain.001 with option XCH (XCT), SCT/GLB/pain.001 (CCT) or RFT/GLB/mt101 (RFT). Downloads are BTD: PSR/CH/pain.002, STM/CH/camt.052, EOP/CH/camt.053, REP/CH/camt.054 with and without service options XDCI, XABK, XQRR, XSCR and XDDD, EOP/CH/mt940, STM/CH/mt942 and DAR/CH for PDF bank documents.
- What are ZKB's payment cut-off times for EBICS files?
- For electronic channels including Datalink, collective orders in CHF, EUR, USD, GBP and CAD must arrive by 12:00 CET on the execution date for same-day execution; single payments by 16:30 in CHF and 15:00 in EUR, USD, GBP and CAD. Other currencies have earlier cut-offs, some one or two days before the execution date.
- What changes at ZKB in November 2026?
- The V2009 schemas (pain.001.001.03.ch.02 and the camt version 04 messages) are valid until November 2026. Unstructured addresses are accepted until 13 November 2026; from 14 November 2026 structured addresses are mandatory, with at least name, town and country, and payments with unstructured addresses and a later execution date are rejected.
- Can I connect my ERP to Zürcher Kantonalbank?
- Yes. You send canonical JSON and BankConnector produces pain.001.001.09 to the Swiss Payment Standards ch.03 schema, then reads camt and pain.002 back into one normalised format. SEPA credit transfers, Swiss domestic transfers, QR-bill payments 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 V2009 schemas reach the end of their validity — pain.001.001.03.ch.02, pain.001.001.03, pain.001.003.03 and camt version 04. Our engine already produces pain.001.001.09 for ZKB.
Last day unstructured addresses are accepted. Payments with unstructured addresses and a later execution date are rejected.
Structured addresses become mandatory — at least name, town and country.
If all of this looks like a lot · it does not have to be
Five steps to a live ZKB 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 ZKB
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 ZKB 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 ZKB will check. You sign it by hand and send it.
- 4
Verify ZKB 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 ZKB
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Zürcher Kantonalbank’s Datalink EBICS page, its EBICS help page, its EBICS connection-parameter sheet in German and English, its cut-off times and provision of data sheet, its ISO 20022 V2019 handbook in English and German, its general-information page, its history page and its state-guarantee page; the bank’s entries in the Swiss UID register, in GLEIF and in FINMA’s list of authorised banks, and FINMA’s page on systemically important banks. BankConnector is not affiliated with Zürcher Kantonalbank.