Switzerland · Urner Kantonalbank · EBICS
Connect UKB without learning EBICS.
EBICS 2.5 and 3.0 on Host ID EBICSUKB, signature A006, bank key and certificate hashes on a published parameter sheet. UKB does not support the distributed 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.02</VersionNumber> </ebicsHEVResponse>
Host ID
EBICSUKB
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.36 s
Published by the bank
The bank's imprint, portrait, history, figures and law pages, the Gesetz über die Urner Kantonalbank; the Swiss UID register, GLEIF and FINMA.
Bank details
| BIC | URKNCH22 · URKNCH22XXX |
| Clearing number | 785 |
| Legal name | Urner Kantonalbank (Banque Cantonale d'Uri) |
| Legal form | Independent institution under cantonal public law (selbstständige Anstalt des kantonalen öffentlichen Rechts) |
| Registered office | Bahnhofplatz 1, 6460 Altdorf |
| UID | CHE-108.954.665 |
| Commercial register | CH-120.8.000.993-9 |
| LEI | 5299002ZG5ZSOLMPJ232 |
| Founded | 1915 — operating since 1 July 1915 |
| Owner | Canton of Uri — 100% |
| State guarantee | The Canton of Uri is liable for all of UKB's liabilities insofar as its own funds are insufficient — participation capital, subordinated liabilities and subsidiaries' liabilities excluded |
| Total assets | CHF 4,048,407 thousand at 31 December 2025 |
| Supervision | FINMA — authorised bank, supervisory category 4 |
| Contact | +41 41 875 60 00 · info@ukb.ch |
Checked live
Measured against the live host, at the address and Host ID on the bank's parameter sheet.
Access data
| EBICS address | https://www.ebics.swisscom.com/ebics-server/ebics.aspx |
| Port | 443 |
| Host ID | EBICSUKB |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.02) |
Published by the bank
The bank's EBICS connection parameter sheet (05.2024) and its EBICS page.
Keys, signatures and the agreement
| Agreement | Not published |
| Price | Not published |
| Requirements | An account with UKB, internet access and EBICS-capable software |
| Versions | EBICS 3.0 and 2.5 |
| Partner ID and user ID | Sent by separate letter — Partner ID alias contract number, Teilnehmer ID alias user ID |
| IID / BC number on the sheet | 785 |
| Authentication key | X002 |
| Encryption key | E002 |
| Electronic signature | A006 (standard) · A005 still supported, not recommended |
| Key length | Not published |
| Bank key hashes | Published on the sheet for X002 and E002 — key hashes and certificate hashes |
| Key initialisation | INI and HIA · H3K for certificates, all three keys at once |
| Key changes | HCA (authentication and encryption) · HCS (signature, authentication and encryption) |
| Blocking access | SPR |
| Distributed signature (VEU) | Not supported |
| Multibanking | Yes — with an EBICS client in your ERP or finance software |
| End of EBICS 2.5 | Not published |
Published by the bank
The bank's EBICS connection parameter sheet (05.2024) and its EBICS page.
Order types published by UKB
| Order type | Dir | Message | Versions |
|---|---|---|---|
| XE2 | Send | pain.001 | 03 · 09 |
| XL3 | Send | pain.008 | 02 |
| Z01 | Download | pain.002 | 03 · 10 |
| Z52 | Download | camt.052 | 04 · 08 |
| Z53 | Download | camt.053 | 04 · 08 |
| Z54 | Download | camt.054 | 04 · 08 |
| STA | Download | mt940 | — |
The EBICS 2.5 order types on the parameter sheet, sending and receiving. Versions read ISO 2009/2013 · ISO 2019. UKB publishes no EBICS 3.0 BTFs.
The administration order types: key initialisation including H3K, the EBICS status protocol, available order types, key changes, supported versions, the bank’s public keys, customer and subscriber data, bank parameters and blocking access. We run them during setup and afterwards.
Published by the bank
The bank's EBICS page, its business payments page and its structured-address page.
Formats and execution
| Message types over EBICS | pain.001, pain.002, pain.008, camt.052, camt.053, camt.054 and mt940 |
| pain.001 | Versions 03 and 09 |
| pain.002 | Versions 03 and 10 |
| camt.052 · camt.053 · camt.054 | Versions 04 and 08 |
| Cut-off for EBICS orders | Not published |
| Batch booking | Not published |
| Charge bearer | Not published |
| Debtor agent | Not published |
| Instant payments | Received · sending not yet possible |
| Structured addresses, payment orders | Mandatory from 21 November 2026 |
| Structured addresses, QR-bills | Only structured addresses from 21 November 2025 |
| End of pain.001.001.03 | 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 |
| Debtor BIC | Optional — when given, URKNCH22 or URKNCH22XXX |
| Remittance limit | 140 characters |
| Name limit | 70 characters |
| Character set | Latin — transliterated before the bank sees it |
| Signature | A006 |
| Key initialisation | H3K |
| 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 Urner Kantonalbank's EBICS Host ID and URL?
- Host ID EBICSUKB, address https://www.ebics.swisscom.com/ebics-server/ebics.aspx on port 443. UKB publishes both on its EBICS connection parameter sheet, together with the key and certificate hash values of its X002 and E002 keys. Your Partner ID and user ID are sent by separate letter.
- Which EBICS versions does UKB support?
- UKB supports EBICS 2.5 and 3.0. The host answers H003 (02.40), H004 (02.50) and H005 (03.02). No end date for EBICS 2.5 has been published.
- Which keys and signature does UKB use for EBICS?
- X002 for authentication, E002 for encryption and A006 as the standard electronic signature; A005 is still supported but not recommended. UKB lists INI and HIA as well as H3K, which sends all three subscriber keys as certificates in one order. Key changes run through HCA or HCS.
- Does UKB support the distributed electronic signature (VEU)?
- No. Urner Kantonalbank's parameter sheet states that it does not support the distributed electronic signature, and it lists no VEU order types.
- Which order types does UKB use for EBICS?
- Sending: XE2 for pain.001 (versions 03 and 09) and XL3 for pain.008 (version 02). Receiving: Z01 for pain.002 (03 and 10), Z52, Z53 and Z54 for camt.052, camt.053 and camt.054 (04 and 08), and STA for MT940. UKB publishes no EBICS 3.0 BTFs.
- What are Urner Kantonalbank's cut-off times for EBICS payments?
- UKB publishes no cut-off time for EBICS orders.
- When does UKB require structured addresses?
- Structured addresses are mandatory in payment orders from 21 November 2026, with addresses split into elements such as street, building number, postcode and town. QR-bills may contain only structured addresses since 21 November 2025.
- Can I connect my ERP to Urner 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 become mandatory in payment orders. Address details must be split into separate elements such as street, building number, postcode and town.
If all of this looks like a lot · it does not have to be
Five steps to a live UKB 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 UKB
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 UKB 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 UKB will check. You sign it by hand and send it.
- 4
Verify UKB 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 UKB
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Urner Kantonalbank’s EBICS page, its EBICS connection parameter sheet (05.2024), its business payments page, its structured-address page, its imprint, its portrait, history and key figures pages, its law and ordinance page with the Gesetz über die Urner Kantonalbank and its state guarantee page; the bank’s entries in the Swiss UID register, in GLEIF and in FINMA’s list of authorised banks. BankConnector is not affiliated with Urner Kantonalbank.