Switzerland · Basler Kantonalbank · EBICS
Connect BKB without learning EBICS.
EBICS 2.5 and 3.0, approval by distributed signature, and structured addresses required from 14 November 2026. We handle the payments, the statements and every protocol step underneath.
BKB at a glance
- BIC
- BKBBCHBBXXX
- Clearing number
- 770
- EBICS versions
- 2.5 and 3.0
- Host ID
- Not published
- Same-day orders, EBICS terms
- Until 13:00
- Connection
- About 2 weeks · free of charge
Published by the bank
The bank's imprint, the cantonal bank law and governance page it publishes; the Swiss UID register, GLEIF and FINMA.
Bank details
| Legal name | Basler Kantonalbank (Banque Cantonale de Bâle, Banca Cantonale di Basilea, Cantonal Bank of Basel) |
| Legal form | Independent institution under public law |
| Registered office | Aeschenvorstadt 41, 4051 Basel |
| UID | CHE-108.954.493 |
| Commercial register | CH-270.8.000.002-2 |
| LEI | HV5W8PGLJ127N2SFSM23 |
| BIC | BKBBCHBBXXX · SWIFT BKBBCHBB |
| Clearing number | 770 |
| Owner | Canton of Basel-Stadt — all endowment capital and all voting rights; participation certificates without votes trade on SIX Swiss Exchange |
| State guarantee | The bank's own funds answer for its liabilities first, the Canton of Basel-Stadt second — not for participation capital, subordinated liabilities, or liabilities to or of subsidiaries |
| Supervision | FINMA — authorised bank, supervisory category 3 |
| Group | Parent company of the BKB Group, with Bank Cler AG |
Published by the bank
The bank's BKB-EBICS page, its EBICS terms of use and its technical specifications page.
Access data
| EBICS address | Not published |
| Host ID | Not published |
| Access data | Sent by post once BKB holds the signed agreement — bank URL, identification number, host name and user ID |
| Identification number | Assigned by BKB, given after you sign the agreement |
| EBICS 3.0 | Offered from December 2024 |
| EBICS 2.5 | Offered and maintained until further notice |
| EBICS 2.4 | Still available, no longer maintained |
| Set-up time | About 2 weeks |
| Price | The connection is free of charge |
| Unused access | BKB may close an access never used within a year of the agreement, or unused for more than a year |
| Support | E-Banking Service · +41 61 266 36 36 |
Published by the bank
The bank's EBICS terms of use (June 2024), its BKB-EBICS page and its technical specifications page.
Keys, signatures and the agreement
| Agreement | Agreement on the use of the EBICS services of Basler Kantonalbank (Vereinbarung über die Nutzung der EBICS Dienstleistungen der Basler Kantonalbank) |
| Terms | Legal notes and terms of use for EBICS, as of June 2024 |
| Signature version | A005 — named in the initialisation document |
| Key length, EBICS 3.0 | At least 2048 bits, keys sent as X.509 certificates |
| A004 | Not part of EBICS 3.0 |
| Bank key hashes | Not published |
| Initialisation letter | “Public key for electronic signature A005”, generated in your software, legally signed and sent to BKB |
| Activation | BKB releases the access after checking the signature, and you verify the hash values of BKB's public keys in your software |
| Approval | In your finance software or ERP, or by distributed signature (VEU) with the authorisations held and checked by BKB |
| Submitted orders | Cannot be changed or deleted |
| Blocking | By phone — access resumes only after a new key exchange |
| Complaints on a transaction | Within 30 days of execution |
| Class | Signature authorisation |
|---|---|
| E | Individual signature, alone or with any other |
| A | Collective signature, with an individual, group A or group B signatory |
| B | Collective signature, with an individual or group A signatory only |
| T | Transport signature and account enquiry, with information rights |
Published by the bank
The bank's technical specifications page and its payments FAQ.
What you send and fetch over BKB-EBICS
| Message | What it does | Direction |
|---|---|---|
| pain.001 | Payment file in ISO format | Send |
| pain.008 | Direct debit file in ISO format | Send |
| pain.002 | Status report | Download |
| camt.052 | Intraday account report | Download |
| camt.053 | Account statement | Download |
| camt.054 | Credit notification | Download |
| MT940 | Account statement, SWIFT format | Download |
| Account statement as e-document | Download | |
| Credit and debit advices | Download |
| EBICS 2.5 order type codes | Not published |
| EBICS 3.0 BTF codes | Not published |
| EBICS 3.0 order identification | BTF — upload (BTU) and download (BTD) |
| Customer protocol | HAC as text under 2.5 · an XML version under 3.0 |
| EBICS 3.0 order details | Additional order information, e.g. the file name |
| Banks without EBICS | BKB sends your pain.001 payment orders to them and fetches their camt.053 statements for you |
Published by the bank
The bank's cut-off time sheet, its EBICS terms of use and its foreign-payments page.
Cut-off times and execution
| Currency | Name | EBICS and SWIFT cut-off, CET | Give as execution date |
|---|---|---|---|
| CHF | Swiss franc | 15:30 | On the value date |
| EUR | Euro | 14:30 | On the value date |
| USD | US dollar | 15:30 | On the value date |
| GBP | Pound sterling | 13:30 | On the value date |
| CAD | Canadian dollar | 15:30 | On the value date |
| AUD | Australian dollar | 10:00 | 1 bank business day before value |
| CZK | Czech koruna | 09:00 | 1 bank business day before value |
| DKK | Danish krone | 09:30 | On the value date |
| HKD | Hong Kong dollar | 10:00 | 1 bank business day before value |
| HUF | Hungarian forint | 15:30 | 1 bank business day before value |
| JPY | Japanese yen | 13:30 | 1 bank business day before value |
| MXN | Mexican peso | 09:30 | On the value date |
| NOK | Norwegian krone | 09:30 | On the value date |
| NZD | New Zealand dollar | 10:00 | 1 bank business day before value |
| PLN | Polish zloty | 09:00 | On the value date |
| SAR | Saudi riyal | 15:30 | 2 bank business days before value |
| SEK | Swedish krona | 09:30 | On the value date |
| SGD | Singapore dollar | 10:00 | 1 bank business day before value |
| THB | Thai baht | 15:30 | 2 bank business days before value |
| TRY | Turkish lira | 09:30 | On the value date |
| ZAR | South African rand | 08:30 | On the value date |
| Time basis | Time the order is received · CET |
| Before public holidays | Earlier cut-offs may apply |
| After the cut-off | Executed on a best-effort basis |
| Same-day execution, EBICS terms | Transmission possible until 13:00 — later, or for very large payment files, same-day execution is not guaranteed |
| Weekend or holiday | BKB may execute the order on the next bank business day |
| SEPA | Automatic for EUR orders from Digital Banking or EBICS with IBAN and BIC, charges SHA, and a SEPA-participant beneficiary bank |
| Default charge option | SHA — OUR and BEN also accepted |
Published by the bank
The bank's technical specifications page, its payments FAQ, its structured-address page and its QR-bill page for billers.
Formats
| Payment orders | pain.001 |
| pain.001 version | Not published |
| Direct debits | pain.008 |
| Statements | camt.052 · camt.053 · camt.054 |
| MT940 | Available — SWIFT messages such as MT940 and MT571 are not replaced |
| camt.054 for QR-bills | Extended with all QR-bill data, available since 30 June 2020 |
| References | QR reference with QR-IBAN · SCOR reference with IBAN |
| Structured addresses | Required from 14 November 2026 in payment orders and standing orders, payroll included — ordering party and payee |
| Files covered | pain.001, pain.008 SDD and MT101 |
| Address variants supported | Minimum: name, town, country · fully structured · hybrid, from November 2025 |
| QR-bill | New rules since 21 November 2025 · unstructured QR-bills processed until 30 September 2026 |
| 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 |
| Batch booking | False |
| Debtor BIC | Required |
| 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 Basler Kantonalbank's EBICS Host ID and URL?
- BKB does not publish them. Once it holds your signed EBICS agreement, it sends the access data by post: the bank's URL, the identification number, the host name and the user ID.
- Which EBICS versions does BKB support?
- EBICS 3.0, offered from December 2024, and EBICS 2.5, offered and maintained until further notice. EBICS 2.4 is still available but no longer maintained, and BKB recommends moving to 3.0.
- Which keys and signature does BKB use for EBICS?
- The initialisation document is the public key for electronic signature A005, generated in your software, legally signed and sent to BKB. Under EBICS 3.0 keys are at least 2048 bits and are sent as X.509 certificates; A004 is not part of 3.0. After activation you verify the hash values of BKB's public keys in your software.
- Does BKB support the distributed electronic signature (VEU)?
- Yes. You either control approvals in your finance software or ERP, or use VEU with the authorisations held and checked by BKB. Signature class E is an individual signature, A and B are collective signatures that let groups A and B approve together, and T is a transport signature with account enquiry.
- What are Basler Kantonalbank's cut-off times for EBICS payments?
- BKB's cut-off sheet for EBICS and SWIFT gives 15:30 CET for Swiss franc, US dollar and Canadian dollar payments and 14:30 for euro payments on the value date, 13:30 for pound sterling. Australian, Hong Kong, New Zealand and Singapore dollars, Czech koruna, Hungarian forint and Japanese yen need the order one bank business day before value, Saudi riyal and Thai baht two. Its EBICS terms state that orders for same-day execution can be transmitted until 13:00, and same-day execution is not guaranteed after that or for very large files.
- Which formats can I exchange with BKB over EBICS?
- You send pain.001 payment files and pain.008 direct debit files, and fetch pain.002 status reports, camt.052, camt.053 and camt.054 statements, MT940 and PDF statements and advices. BKB states that SWIFT messages such as MT940 are not being replaced.
- When does BKB require structured addresses?
- From 14 November 2026, payment orders and standing orders, payroll included, must carry structured addresses for both the ordering party and the payee, including in pain.001, pain.008 SDD and MT101 files. Unstructured QR-bills are processed until 30 September 2026.
- Can I connect my ERP to Basler 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
Last day BKB processes unstructured QR-bills (address type K). QR-bills after that carry structured addresses only.
Structured addresses only (address type S) in payment orders and standing orders, payroll included, for both the ordering party and the payee. Incoming payments and payment orders with unstructured addresses can no longer be processed — this covers pain.001, pain.008 SDD and MT101 files.
If all of this looks like a lot · it does not have to be
Five steps to a live BKB 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 BKB
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 BKB 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 BKB will check. You sign it by hand and send it.
- 4
Verify BKB 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 BKB
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Basler Kantonalbank’s BKB-EBICS page, its technical specifications page, its legal notes and terms of use for EBICS (June 2024), its cut-off time sheet, its foreign-payments page, its structured-address page, its payments and data exchange FAQ, its QR-bill page for billers, its imprint, its law page and the Law on the Basler Kantonalbank, and its corporate governance page; the Swiss UID register, GLEIF and FINMA’s list of authorised banks. BankConnector is not affiliated with Basler Kantonalbank.