Switzerland · Zuger Kantonalbank · EBICS
Connect ZugerKB without learning EBICS.
EBICS 2.5 and 3.0 on Host ID ZGKBEBICS, bank key and certificate hashes on a published parameter sheet, free to use, with single or joint signatures through the distributed electronic signature. 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="H003">02.40</VersionNumber> <VersionNumber ProtocolVersion="H004">02.50</VersionNumber> <VersionNumber ProtocolVersion="H005">03.00</VersionNumber> </ebicsHEVResponse>
Host ID
ZGKBEBICS
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.21 s
Published by the bank
The bank's contact, portrait, legal-form and shareholder pages and the law on Zuger Kantonalbank it publishes; the Swiss UID register, GLEIF and FINMA.
Bank details
| BIC | KBZGCH22 · KBZGCH22XXX |
| Clearing number (IID) | 00787 |
| QR-IID | 30787 |
| Legal name | Zuger Kantonalbank |
| Legal form | Company limited by shares under a special cantonal law (spezialgesetzliche Aktiengesellschaft, Art. 763 CO) · UID register: institution under public law |
| Registered office | Bahnhofstrasse 1, 6300 Zug |
| Postal address | Bahnhofstrasse 1, Postfach, 6301 Zug |
| UID | CHE-105.744.410 |
| Commercial register | CH-170.8.000.001-9 |
| LEI | 529900PVNQ0FQUKJQ049 |
| Founded | 1892 |
| Share capital | CHF 144,144,000 — 288,288 registered shares of CHF 500 nominal |
| Owner | Canton of Zug — by law at least half of the share capital, which it may not sell · 50.1% of shares and 33% of voting rights at 31 Dec 2025 |
| Voting cap | No shareholder may vote more than one third of the share capital plus one share |
| Listing | SIX Swiss Exchange · ISIN CH0493891243 |
| State guarantee | The Canton of Zug is liable for the bank's liabilities insofar as its own funds are insufficient — subordinated liabilities excluded |
| Supervision | FINMA — authorised bank, supervisory category 3 |
| Business customers | 041 709 12 12 · Mon–Fri 08:00–18:00 |
Checked live
Measured against the live host, at the address and Host ID on the bank's parameter sheet.
Access data
| EBICS address | https://ebics.swisscom.com/ebics-server/ebics.aspx |
| Host ID | ZGKBEBICS |
| Port | 443 |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.00) |
Published by the bank
The bank's EBICS parameter sheet and its EBICS page.
Keys, signatures and the agreement
| Scope | Interface from your ERP for submitting payment orders (pain) and retrieving account information (camt) |
| Price | Use of EBICS free of charge |
| Requirements | An account with ZugerKB, internet access and EBICS-capable software |
| Getting access | Once your software is EBICS-capable, through your adviser or 041 709 12 12 |
| Versions on the sheet | 3.0 (schema H005) and 2.5 (schema H004) |
| Authentication | X002 |
| Encryption | E002 |
| Electronic signature | A006 (standard) · A005 still possible, not recommended |
| Key length | Not published |
| Bank key hashes | Published on the sheet for X002 and E002 — public-key hashes and X.509 certificate hashes |
| Initialisation | INI and HIA, then the initialisation letter signed by the customer and sent by post to ZugerKB, so the EBICS user can be activated |
| Checking the bank keys | After ZugerKB has checked and released the customer keys: download the bank keys with HPB and verify them in the client software against the sheet's hash values |
| Key change | HCA (authentication and encryption) · HCS (signature, authentication and encryption) |
| Blocking access | SPR |
| Signature classes, single signature (EU) | E single signature · T transport without signature |
| Signature classes, distributed signature (VEU) | E single signature · A joint, second visa A, B or E · B joint, second visa A or E |
| Recommended | The distributed electronic signature, with signatures given from separate software clients and the submitting client network-separated from the signing one — the VEU mobile app ZugerKB offers is particularly suited to this |
| End of EBICS 2.5 | Not published |
Published by the bank
The bank's EBICS parameter sheet (as of May 2024).
Order types published by ZugerKB
| 2.x | What it does | Dir | 3.0 BTF | Option | Container | Version |
|---|---|---|---|---|---|---|
| XE2 | Customer credit transfer initiation, Swiss Payment Standards | BTU | MCT · CH · pain.001 | — | — | 03 |
| — | Customer credit transfer initiation, Swiss Payment Standards | BTU | MCT · CH · pain.001 | — | — | 09 |
| XE3 | Swiss direct debit submission | BTU | SDD · CH · pain.008 | — | — | 02 |
| Z01 | Status report, bank to ordering party | BTD | PSR · CH · pain.002 | — | ZIP | 03 · 10 |
| Z52 | Intraday and pre-advised account movements | BTD | STM · CH · camt.052 | — | ZIP | 04 · 08 |
| Z53 | End-of-day account statement | BTD | EOP · CH · camt.053 | — | ZIP | 04 · 08 |
| Z54 | Additional information on collective bookings | BTD | REP · CH · camt.054 | — | ZIP | 04 · 08 |
| ZDF | Digital bank document | BTD | DAR · CH · documents | — | ZIP | — |
| STA | Account statement in SWIFT format | BTD | EOP · CH · mt940 | — | — | — |
Uploads run as BTU and downloads as BTD. The status report, the three camt reports and bank documents come in a ZIP container; MT940 carries none.
The distributed-signature order types: adding a signature, VEU status, cancelling, transaction details, the overview and the overview with additional information.
The administration order types: key initialisation, the status protocol, retrievable order types, key changes, supported versions, the bank’s public keys, customer and subscriber data, bank parameters and blocking. You never see one — we run them during setup and afterwards.
Published by the bank
The bank's structured-address page, which covers pain.001 files submitted via EBICS.
Cut-off times and execution
| Cut-off for EBICS files | Not published |
| Errors in a pain.001 file | Partial processing — up to ten faulty transactions are rejected and the rest processed · more than ten and the whole file is rejected |
| Date the address rule applies to | The requested execution date, not the date of capture or transmission |
Published by the bank
The bank's EBICS parameter sheet and its structured-address page.
Formats
| pain.001 | Swiss Payment Standards, versions 03 and 09 |
| pain.008 | Swiss direct debit submission, version 02 |
| pain.002 | Versions 03 and 10, delivered in a ZIP |
| camt.052 · camt.053 · camt.054 | Versions 04 and 08, delivered in a ZIP |
| MT940 | STA |
| Structured addresses | Required in pain.001 files from execution date 14 Nov 2026, whatever the pain.001 version — at least name, town and country in their own fields; unstructured addresses no longer permitted |
| Recommended | Fully structured addresses — name, street, house number, postcode, town and country |
| pain.001 version 2009 (V3) | Supported for a transition period beyond 14 Nov 2026 · expected to end mid-2027, after which version 2019 (V9) is required |
| Charge bearer | Not published |
| Batch booking | Not published |
| Debtor agent | Not published |
| Remittance information | Not published |
| End of MT940 | Not published |
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) |
| Guideline | Swiss Payment Standards 09/ch.03, published by SIX |
| 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 Zuger Kantonalbank's EBICS Host ID and URL?
- Host ID ZGKBEBICS, address https://ebics.swisscom.com/ebics-server/ebics.aspx, port 443. ZugerKB publishes both on its EBICS parameter sheet, together with the hash values of its X002 and E002 public keys and X.509 certificates.
- Which EBICS versions does ZugerKB support?
- The parameter sheet names EBICS 3.0 (schema H005) and 2.5 (schema H004); the host answers H003 (02.40), H004 (02.50) and H005 (03.00). ZugerKB has published no end date for EBICS 2.5.
- Which keys and signature does ZugerKB use for EBICS?
- X002 for authentication, E002 for encryption and A006 as the standard electronic signature; A005 is still possible but not recommended. After INI and HIA the signed initialisation letter goes to ZugerKB by post, and once the bank releases your keys you download its keys with HPB and verify them against the hashes on the sheet.
- Does ZugerKB support the distributed electronic signature (VEU)?
- Yes, and it recommends it. VEU signature classes are E (single), A (joint, second visa A, B or E) and B (joint, second visa A or E); outside the VEU, class E signs alone and class T transports without a signature. The VEU order types are HVE, HVD, HVS, HVT, HVU and HVZ.
- Which order types does ZugerKB use for EBICS 3.0?
- Payments upload as BTU MCT/CH/pain.001, version 03 or 09, and Swiss direct debits as BTU SDD/CH/pain.008 version 02. Downloads are BTD: PSR/CH/pain.002, STM/CH/camt.052, EOP/CH/camt.053, REP/CH/camt.054 and DAR/CH for bank documents, all in a ZIP, plus EOP/CH/mt940. The EBICS 2.x equivalents are XE2, XE3, Z01, Z52, Z53, Z54, ZDF and STA.
- What is ZugerKB's payment cut-off time for EBICS files?
- ZugerKB publishes no cut-off time for files submitted via EBICS.
- What happens to a pain.001 file with errors?
- ZugerKB allows partial processing. If a file contains up to ten faulty transactions, only those are rejected and the correct ones are processed. If it contains more than ten, the whole file is rejected.
- What changes at ZugerKB in November 2026?
- From execution date 14 November 2026, pain.001 files, including those sent via EBICS, must carry structured addresses — at least name, town and country in their own fields — whatever the pain.001 version. ZugerKB keeps accepting pain.001 version 2009 (V3) beyond that date for a transition period it expects to end in mid-2027.
- Can I connect my ERP to Zuger Kantonalbank?
- Yes. You send canonical JSON and BankConnector produces the pain.001.001.09 file the Swiss Payment Standards describe, 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
Structured addresses required. pain.001 files with an execution date from this day must carry structured addresses — at least name, town and country in their own fields. Our engine already produces pain.001.001.09 for ZugerKB.
If all of this looks like a lot · it does not have to be
Five steps to a live ZugerKB 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 ZugerKB
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 ZugerKB 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 ZugerKB will check. You sign it by hand and send it.
- 4
Verify ZugerKB 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 ZugerKB
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Zuger Kantonalbank’s EBICS page, its EBICS parameter sheet, its structured-address page, its contact, portrait, legal-form and shareholder pages and the law on Zuger Kantonalbank; the Swiss UID register, GLEIF and FINMA’s list of authorised banks. BankConnector is not affiliated with Zuger Kantonalbank.