Switzerland · Luzerner Kantonalbank · EBICS
Connect LUKB without learning EBICS.
EBICS on Host ID LUKBEBIX, bank key hashes on a published parameter sheet, free of charge, with payment approval through the distributed signature. From 13 November 2026 LUKB processes pain.001.001.09 only. 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
LUKBEBIX
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.34 s
Published by the bank
The bank's imprint, portrait and legal-basis pages; the Swiss UID register, GLEIF and FINMA.
Bank details
| BIC | LUKBCH2260A |
| Clearing number | 778 |
| Legal name | Luzerner Kantonalbank AG |
| Legal form | Company limited by shares under private law (Aktiengesellschaft) — converted from an institution under public law on 1 January 2001 |
| Registered office | Pilatusstrasse 12, 6003 Luzern |
| UID | CHE-105.845.092 |
| Commercial register | CH-100.8.011.092-9 |
| LEI | 549300C2XKS86VQDGV41 |
| Listing | SIX Swiss Exchange · ISIN CH1252930610 |
| Shareholders | Canton of Lucerne — 61.5% of the share capital, 38.5% widely held; the law requires the canton to hold at least 51% of capital and votes |
| State guarantee | The Canton of Lucerne is liable for all of LUKB's liabilities insofar as its own funds are insufficient |
| Supervision | FINMA — authorised bank, supervisory category 3 |
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.lukb.ch/ebicsweb/ebicsweb |
| Host ID | LUKBEBIX |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.00) |
Published by the bank
The bank's Direct EBICS parameter sheet, its EBICS, EBICS 3.0 and help pages, its Direct EBICS, App and Port product sheets and its Port initialisation guide.
Keys, signatures and the agreement
| Service | Direct EBICS — free of charge |
| Agreement | Not published |
| Ordering | Through your corporate client adviser |
| Subscriber data | User ID, customer ID and subscriber name, on the parameter sheet |
| Authentication key | X002 |
| Encryption key | E002 |
| Electronic signature | A005 or A006 |
| Key length, EBICS 3.0 | At least 2048 bits for A005, E002 and X002 · keys in X.509 format |
| Transport encryption, EBICS 3.0 | TLS 1.2 or higher |
| Bank key hashes | Published on the parameter sheet for X002 and E002, EBICS 3.0 (H005) |
| Bank keys on EBICS 3.0 | Provided as a certificate |
| Moving to EBICS 3.0 | Reported to LUKB with H005 · active subscriber keys are kept — no new initialisation |
| Key update | HCS, or HCA and PUB |
| Initialisation letter | Submitted to LUKB, which confirms the activation · the bank key is verified afterwards |
| Direct EBICS Port activation | INI letter signed on both pages and returned in original · usually 3 to 5 working days after it arrives, confirmed by email |
| Blocking | SPR |
| Distributed signature | VEU order types supported, where your software allows them |
| Release outside the ERP | Direct EBICS App or Direct EBICS Port — both free of charge |
| VEU across versions | Users on different EBICS versions can submit and sign the same files |
| Cancelled payment file | Rejected in full, even where valid signatures were given |
| Direct EBICS App | Android 13 or iOS 16 at least |
| Availability | Basically 24/7 |
| Switch to EBICS 3.0 | Required by November 2026 |
| Cash Management | +41 844 822 811 · cash@lukb.ch |
| E-Banking helpdesk | 0844 844 866 · info@lukb.ch |
Published by the bank
The bank's Direct EBICS parameter sheet and its Direct EBICS help page.
Order types published by LUKB
| Service | What it does | Dir | Scope | Container | Message | Version |
|---|---|---|---|---|---|---|
| MCT | Collective payment order, pain.001.001.03 CH | BTU | CH | — | pain.001 | 03 |
| SDD | Direct debit, pain.008 CH-TA | BTU | CH | — | pain.008 | 02 |
| DDD | Direct debit, TA875 | BTU | CH | — | ta875 | — |
| EOP | End-of-day statement, SWIFT MT940 | BTD | CH | — | mt940 | — |
| STM | Intraday account movements, SWIFT MT942 | BTD | CH | — | mt942 | — |
| DAR | Electronic bank documents, PDF | BTD | CH | ZIP | documents | — |
| PSR | Status report, pain.002.001.03 CH | BTD | CH | ZIP | pain.002 | 03 |
| STM | Intraday account movements, camt.052.001.04 CH | BTD | CH | ZIP | camt.052 | 04 |
| EOP | End-of-day statement, camt.053.001.04 CH | BTD | CH | ZIP | camt.053 | 04 |
| REP | Collective bookings, camt.054.001.04 CH | BTD | CH | ZIP | camt.054 | 04 |
| MCT | Collective payment order, pain.001.001.09 CH | BTU | CH | — | pain.001 | 09 |
| PSR | Status report, pain.002.001.10 CH | BTD | CH | ZIP | pain.002 | 10 |
| STM | Intraday account movements, camt.052.001.08 CH | BTD | CH | ZIP | camt.052 | 08 |
| EOP | End-of-day statement, camt.053.001.08 CH | BTD | CH | ZIP | camt.053 | 08 |
| REP | Collective bookings, camt.054.001.08 CH | BTD | CH | ZIP | camt.054 | 08 |
The EBICS 3.0 BTFs marked active on the parameter sheet. Uploads run as BTU and downloads as BTD. pain.002, camt and PDF documents come in a ZIP; pain.001, pain.008, TA875, MT940 and MT942 carry no container.
| 2.5 | Dir | What it does |
|---|---|---|
| XE2 | Send | Payment order, pain.001 CH |
| XE3 | Send | Direct debit, pain.008 CH-TA |
| XL1 | Send | Direct debit, TA875 |
| Z01 | Download | Status report, pain.002 CH |
| Z52 | Download | Intraday account movements, camt.052 CH |
| Z53 | Download | End-of-day statement, camt.053 CH |
| Z54 | Download | Credit / debit notification, camt.054 CH |
| STA | Download | Account statement, SWIFT MT940 |
| VMK | Download | Intraday account statement, SWIFT MT942 |
| ZDF | Download | Electronic bank documents |
| PTK | Download | Customer protocol |
| HAC | Download | Customer protocol, XML |
The distributed-signature order types: signature folder, order status, order details, adding a signature and cancelling an order.
The system order types: key initialisation, the bank’s public keys and parameters, customer and user data, available order types, the customer protocol, key changes and blocking. You never see one — we run them during setup and afterwards.
Published by the bank
The bank's per-currency cut-off sheet (December 2025), its pain.001 handbook and its business price list.
Cut-off times and execution
| Currency | Country | Cut-off, CET | Value date | Incoming too |
|---|---|---|---|---|
| ALL | Albania | 16:00 | Same value date as submission day | — |
| AUD | Australia | 16:00 | Submission day + 2 days | Yes |
| BAM | Bosnia and Herzegovina | 16:00 | Same value date as submission day | — |
| BRL | Brazil | 16:00 | Same value date as submission day | — |
| CNY | China | 16:00 | Submission day + 2 days | Yes |
| DKK | Denmark | 16:00 | Submission day + 2 days | Yes |
| EUR | Europe | 14:00 | Same value date as submission day | Yes |
| GEL | Georgia | 16:00 | Same value date as submission day | — |
| GBP | United Kingdom | 13:00 | Same value date as submission day | Yes |
| HKD | Hong Kong | 16:00 | Submission day + 2 days | Yes |
| INR | India | 07:30 | Submission day + 2 days | Yes |
| IDR | Indonesia | 16:00 | Same value date as submission day | — |
| ISK | Iceland | 16:00 | Same value date as submission day | Yes |
| ILS | Israel | 16:00 | Submission day + 2 days | Yes |
| JPY | Japan | 16:00 | Submission day + 2 days | Yes |
| CAD | Canada | 16:00 | Submission day + 2 days | Yes |
| HRK | Croatia | 16:00 | Same value date as submission day | — |
| MUR | Mauritius | 16:00 | Same value date as submission day | — |
| MXN | Mexico | 16:00 | Submission day + 2 days | Yes |
| NPR | Nepal | 16:00 | Same value date as submission day | — |
| NZD | New Zealand | 16:00 | Submission day + 2 days | Yes |
| NOK | Norway | 16:00 | Submission day + 2 days | Yes |
| OMR | Oman | 16:00 | Same value date as submission day | — |
| PHP | Philippines | 16:00 | Same value date as submission day | — |
| PLN | Poland | 16:00 | Submission day + 2 days | Yes |
| RON | Romania | 16:00 | Same value date as submission day | — |
| SAR | Saudi Arabia | 16:00 | Submission day + 2 days | Yes |
| SEK | Sweden | 16:00 | Submission day + 2 days | Yes |
| CHF | Switzerland | 16:00 | Same value date as submission day | Yes |
| RSD | Serbia | 16:00 | Same value date as submission day | — |
| SGD | Singapore | 16:00 | Submission day + 2 days | Yes |
| LKR | Sri Lanka | 16:00 | Same value date as submission day | — |
| ZAR | South Africa | 16:00 | Submission day + 2 days | Yes |
| KRW | South Korea | 16:00 | Same value date as submission day | — |
| THB | Thailand | 16:00 | Submission day + 2 days | Yes |
| CZK | Czech Republic | 16:00 | Submission day + 2 days | Yes |
| TND | Tunisia | 16:00 | Same value date as submission day | — |
| TRY | Turkey | 16:00 | Submission day + 2 days | Yes |
| HUF | Hungary | 16:00 | Submission day + 2 days | Yes |
| USD | United States | 15:00 | Same value date as submission day | Yes |
| AED | United Arab Emirates | 16:00 | Submission day + 2 days | Yes |
| VND | Vietnam | 16:00 | Same value date as submission day | — |
| Channel on the cut-off sheet | Not stated |
| Cut-off for EBICS orders | Not published |
| After the cut-off | Executed on the next bank working day |
| Before public holidays | Cut-offs may be earlier |
| V+2 | Accepted and processed on the submission day · account debited and payment forwarded two bank working days later |
| SEPA euro payments | Received after 13:00 — processed on the next bank working day |
| Same-day euro payment | As a non-SEPA payment until 14:00, with charge option OUR |
| Future execution date | Executed in the first processing run on that day |
| Weekend or holiday date | Moved to the next bank working day |
| Date past the currency cut-off | Value moved to the next possible bank working day |
| Execution date range, cut-off sheet | File-transfer orders: at most 10 days in the past and 1 year in the future |
| Execution date range, pain.001 handbook | E-Banking: at most 365 calendar days ahead and 10 back — these limits do not apply to Direct EBICS transfers |
| Priority HIGH | Express surcharge · no effect on domestic CHF and EUR payments |
| Order price, Direct EBICS | Domestic CHF and foreign or foreign-currency orders free of charge |
Published by the bank
The bank's pain.001 and camt handbooks, its MT940/MT942 document, its interfaces page and its structured-address page.
Formats
| pain.001 | pain.001.001.03.ch.02 and pain.001.001.09.ch.03 |
| pain.002 | pain.002.001.03.ch.02 and pain.002.001.10.ch.01 |
| camt.052 · camt.053 · camt.054 | Versions 04 and 08, Swiss schema · one account per message, delivered in a ZIP |
| camt.052 | Hourly from 06:00 to 23:00, when bookings exist |
| camt.053 | End of day |
| MT940 | Previous day's statement from about 24:00, once per bank working day · no trailer over Direct EBICS |
| MT942 | Hourly from 06:00 to 18:00 · uncollected files deleted daily from 24:00 |
| Also sent | pain.008 CH-TA and TA875 (LSV) |
| Bank documents | Signed PDF |
| Payment types accepted | D domestic · S SEPA · X foreign currency and abroad — files with type C (cheque) are rejected |
| SEPA | Automatic for EUR with creditor IBAN, a SEPA-participant bank, charges SLEV (type S) or SHAR (type X), no instructions for forwarding agents and no express |
| Charge bearer | SLEV mandatory for SEPA · SHAR applied when none is given |
| Debtor agent | LUKBCH2260A or CHBCC/778 — other values not supported |
| Debtor account | IBAN only, without spaces |
| Batch booking | true — one collective booking per B-level · false — one booking per transaction · empty — treated as true |
| Single payment in a B-level | Booked as a collective debit |
| Mixed currencies in a B-level | Regrouped into single-currency collective debits |
| Errors | No partial processing — one error rejects the whole file |
| pain.002 over EBICS | Technical ACTC first, then ACCP, ACWC or RJCT |
| Duplicate checks, Direct EBICS | Same order number with the same customer ID and order type within 5 days · identical content within 10 days, even under another file name |
| Remittance information | 140 characters, unstructured or structured (QR, IPI or SCOR reference) — never both |
| Creditor name | Up to 70 characters |
| Ignored | Forwarding agent · intermediary agent · instruction for creditor agent · charges account |
| End of pain.001.001.03 | 13 Nov 2026 |
| Structured addresses | Required in pain files from 13 November 2026 — at least name, town and country in separate fields |
| Hybrid addresses | Supported since 22 November 2025 |
| QR-bill | Structured, complete addresses only in the QR code, since 21 November 2025 |
| End of MT940 / MT942 | 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 Luzerner Kantonalbank's EBICS Host ID and URL?
- Host ID LUKBEBIX, address https://ebics.lukb.ch/ebicsweb/ebicsweb. LUKB publishes both on its Direct EBICS parameter sheet, together with the hash values of its X002 and E002 keys for EBICS 3.0. Your user ID, customer ID and subscriber name are entered on your own copy of the sheet.
- Which EBICS versions does LUKB support?
- The host answers H003 (2.4), H004 (2.5) and H005 (3.0). LUKB states that the switch to EBICS 3.0 and to the ISO 20022 version 2019 messages must be complete by November 2026, and recommends that new users start directly on EBICS 3.0.
- Which keys and signature does LUKB use for EBICS?
- X002 for authentication, E002 for encryption and A005 or A006 for the electronic signature. On EBICS 3.0 subscriber keys are at least 2048 bits in X.509 format, transport runs on TLS 1.2 or higher, and LUKB's own keys are provided as a certificate. Active subscriber keys carry over to EBICS 3.0 without a new initialisation.
- Does LUKB support the distributed electronic signature (VEU)?
- Yes. Direct EBICS supports the VEU order types HVU, HVZ, HVD, HVT, HVE and HVS where your software allows them. Payment files can also be released outside the ERP in the free Direct EBICS App or Direct EBICS Port; a cancelled file is rejected in full, even where valid signatures were already given.
- Which order types does LUKB use for EBICS 3.0?
- Payments upload as BTU MCT/CH/pain.001, version 03 or 09; direct debits as SDD/CH/pain.008 and DDD/CH/ta875. Downloads are BTD with scope CH: PSR for pain.002, STM for camt.052 and MT942, EOP for camt.053 and MT940, REP for camt.054 and DAR for PDF documents. pain.002, camt and PDF files come in a ZIP.
- What are Luzerner Kantonalbank's payment cut-off times?
- LUKB publishes no cut-off for EBICS orders. Its per-currency cut-off sheet, which names no channel, gives 16:00 CET for CHF and most currencies, 15:00 for USD, 14:00 for EUR, 13:00 for GBP and 07:30 for INR. SEPA euro payments received after 13:00 are processed on the next bank working day.
- How does LUKB handle batch booking in pain.001?
- Batch booking true books one collective debit per B-level, false books each transaction on its own, and an empty value counts as true. LUKB books even a single payment in a B-level as a collective debit, and regroups a B-level with mixed currencies into single-currency collective debits.
- When does LUKB stop accepting pain.001.001.03?
- On 13 November 2026. From that date LUKB processes only pain.001.001.09 with structured or hybrid addresses. The minimum is name, town and country in separate fields; LUKB recommends fully structured addresses.
- Can I connect my ERP to Luzerner 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
EBICS 3.0 and ISO 20022 version 2019 required. The switch to EBICS 3.0 and to pain.001.001.09, camt.052.001.08, camt.053.001.08 and camt.054.001.08 must be complete. Our engine already produces pain.001.001.09 for LUKB.
pain.001.001.03 is discontinued. Payment files are processed only as pain.001.001.09 with structured or hybrid addresses.
If all of this looks like a lot · it does not have to be
Five steps to a live LUKB 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 LUKB
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 LUKB 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 LUKB will check. You sign it by hand and send it.
- 4
Verify LUKB 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 LUKB
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Luzerner Kantonalbank’s Direct EBICS page, its Direct EBICS parameter sheet, its EBICS 3.0 page, its Direct EBICS help page, its product sheets for Direct EBICS, Direct EBICS App and Direct EBICS Port, its Direct EBICS Port initialisation guide, its ISO 20022 handbooks for pain.001 and camt, its MT940 and MT942 document, its cut-off times per country, its price list for business customers, its interfaces page, its structured-address page, its imprint, its portrait and its legal basis and state guarantee page; the Swiss UID register, GLEIF and FINMA’s list of authorised banks. BankConnector is not affiliated with Luzerner Kantonalbank.