Switzerland · Thurgauer Kantonalbank · EBICS
Connect TKB without learning EBICS.
EBICS 2.5 and 3.0 on Host ID TGKBEBICS, bank key hashes on a published parameter sheet, free to use, with payment approval through the distributed signature app. 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
TGKBEBICS
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.22 s
Published by the bank
The bank's imprint, important-numbers, portrait, organisation and participation-certificate pages and the TKB law it publishes; the Swiss UID register, GLEIF and FINMA.
Bank details
| BIC | KBTGCH22 · KBTGCH22XXX in GLEIF |
| Clearing number (IID) | 784 |
| Legal name | Thurgauer Kantonalbank |
| Legal form | Independent institution under public law (selbständige Anstalt des öffentlichen Rechtes) |
| Registered office | Bankplatz 1, 8570 Weinfelden |
| UID | CHE-108.954.458 |
| Commercial register | CH-440.8.003.247-3 |
| LEI | 529900F00S0DTFX1D404 |
| Founded | 1871 |
| Owner | Canton of Thurgau — CHF 320 million endowment capital, 80% of the bank's capital, sole voting rights |
| Listing | Non-voting participation certificates, CHF 80 million (20% of capital) — SIX Swiss Exchange since 2014 |
| State guarantee | The Canton of Thurgau is liable for the bank's liabilities insofar as its own funds are insufficient |
| Supervision | FINMA — authorised bank, supervisory category 3 |
| Switchboard | 0848 111 444 |
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 | TGKBEBICS |
| Port | 443 |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.00) |
Published by the bank
The bank's EBICS connection-parameter sheet, its Terms of use for EBICS and VEU, its EBICS page and its VEU-app guides.
Keys, signatures and the agreement
| Agreement | EBICS agreement, with the Terms of use for EBICS and VEU as Annex 4 — they prevail over the General Terms and Conditions where the two conflict |
| Price | Use of EBICS free of charge · setting up the contract may incur costs, depending on effort |
| Requirements | An account with TKB, EBICS-capable software and internet access — TKB may refuse access, e.g. for insufficient IT security |
| Versions on the sheet | 3.0 (schema H005) and 2.5 (schema H004) |
| Authentication | X002 |
| Encryption | E002 |
| Electronic signature | A006 / A005 |
| Key length | Not published |
| Customer and subscriber IDs | Delivered to you personally |
| Bank key hashes | Published on the sheet for X002 and E002 — public-key hashes for EBICS 2.5, certificate hashes for EBICS 3.0 |
| Checking the bank keys | Required of the EBICS user, to make sure no data is exchanged with an unauthorised third party |
| Key change | HCS |
| Blocking access | SPR |
| Signature models | Electronic single signature, permissions kept in your ERP · or single signature with release through the VEU, users registered with TKB |
| VEU flow | File submitted with transport right T · TKB checks content and ISO structure and places it in the VEU folder · released in the app with signature A or B (collective) or E (single) |
| VEU app | EBICS VEU-App by Subsembly GmbH, iOS and Android · User ID starts with V · INI letter printed, signed and sent to TKB · usable once TKB activates the access |
| VEU access data | Sent to each VEU user personally by post |
| Incomplete orders | May be left unexecuted and deleted — missing collective or VEU release, insufficient balance or doubt about legitimacy |
| Submitted payments | Not visible in OLIVIA E-Banking until finally booked · status via pain.002 |
| Electronic bank documents | May be deleted 90 days after being made available, collected or not |
| Complaints about bank documents | Within 30 calendar days |
| Termination | By either party at any time, with immediate effect |
| Place of jurisdiction | Weinfelden, Swiss law |
| End of EBICS 2.5 | Not published |
| E-Banking helpdesk | 0848 111 447 · Mon–Fri 08:00–18:00 |
Published by the bank
The bank's EBICS connection-parameter sheet (as of 22 November 2025).
Order types published by TKB
| 2.5 | What it does | Dir | 3.0 BTF | Option | Container | Version |
|---|---|---|---|---|---|---|
| XE2 | Payment file, Swiss Payment Standards, V2009 | BTU | MCT · CH · pain.001 | — | — | 03 |
| — | Payment file, Swiss Payment Standards, V2019 | BTU | MCT · CH · pain.001 | — | — | 09 |
| — | Payment file, Swiss Payment Standards, V2009 / V2019 | BTU | MCT · CH · pain.001 | — | — | — |
| Z01 | Status report, bank to ordering party | BTD | PSR · CH · pain.002 | — | ZIP | 03 · 10 |
| ZDF | Electronic bank documents | BTD | DAR · CH · documents | — | ZIP | — |
| Z52 | Intraday account statement | BTD | STM · CH · camt.052 | — | ZIP | 04 · 08 |
| Z53 | End-of-day account statement | BTD | EOP · CH · camt.053 | — | ZIP | 04 · 08 |
| Z54 | Account statement, details of collective bookings | BTD | REP · CH · camt.054 | — | ZIP | 04 · 08 |
| STA / ZB2 | Account statement, SWIFT MT940 | BTD | EOP · CH · mt940 | — | — | — |
| ZD2 | Foreign-exchange deal confirmation | BTD | FXC · GLB · mt300 | — | — | — |
| ZD3 | Money-market and fixed-term fiduciary deposit confirmation | BTD | FXC · GLB · mt320 | — | — | — |
| ZD4 | Money-market and call-money fiduciary deposit confirmation | BTD | FXC · GLB · mt330 | — | — | — |
| ZD5 | Interest payment confirmation, loan or deposit | BTD | FXC · GLB · mt350 | — | — | — |
| ZW1 | Securities transaction confirmation | BTD | STR · GLB · mt515 | — | — | — |
| ZW2 | Custody account statement | BTD | SSM · GLB · mt535 | — | ZIP | — |
| ZW3 | Custody account movements | BTD | SSM · GLB · mt536 | — | ZIP | — |
| ZW4 | Corporate action confirmation | BTD | SEV · GLB · mt566 | — | — | — |
Uploads run as BTU and downloads as BTD. The sheet’s delivery notes: Z01, Z52, Z53 and Z54 come in a ZIP container except for a single file, ZDF always in a ZIP, and all SWIFT messages as single files.
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, key change, blocking, supported versions, the bank’s public keys, the status protocol and customer and subscriber data. You never see one — we run them during setup and afterwards.
Published by the bank
The bank's payments FAQ and its business-customer OLIVIA FAQ.
Cut-off times and execution
| Same value date, files through the offline interface (including EBICS) | Delivered by 11:45 |
| Same day, OLIVIA E-Banking | Captured and released by 12:00 on bank working days · Express from 12:00 to 16:00, for a fee |
| Execution | Orders are processed once the execution date is reached |
| Per-currency cut-offs for EBICS | Not published |
| Errors in a file | No partial processing — a file delivered through the interface must be 100% correct, otherwise it is rejected with a pain.002 (status Rejected) |
Published by the bank
The bank's EBICS connection-parameter sheet, its business-customer OLIVIA FAQ, its structured-address page and its QR-bill details page.
Formats
| pain.001 | Swiss Payment Standards V2009 (version 03) and V2019 (version 09) |
| pain.002 | Versions 03 and 10 |
| camt.052 · camt.053 · camt.054 | Versions 04 and 08, delivered in a ZIP |
| MT940 | STA / ZB2 |
| Domestic payments | Account number in IBAN format only, since 2020 |
| Structured addresses | Required in pain.001 files for execution dates after 13 Nov 2026 — at least name, town and country in separate fields; other orders are rejected |
| Recommended | Fully structured addresses, including street, house number and postcode |
| Orange and red payment slips | No longer usable |
| Charge bearer | Not published |
| Batch booking | Not published |
| Debtor agent | Not published |
| Remittance information | Not published |
| 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 |
| 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 Thurgauer Kantonalbank's EBICS Host ID and URL?
- Host ID TGKBEBICS, address https://ebics.swisscom.com/ebics-server/ebics.aspx, port 443. TKB publishes both on its EBICS connection-parameter sheet, together with the hash values of its X002 and E002 keys. Your customer and subscriber IDs are delivered to you personally.
- Which EBICS versions does TKB 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). TKB has published no end date for EBICS 2.5.
- Which keys and signature does TKB use for EBICS?
- X002 for authentication, E002 for encryption and A006 or A005 for the electronic signature. TKB publishes public-key hashes for EBICS 2.5 and certificate hashes for EBICS 3.0, and requires the EBICS user to check them. Keys are changed with HCS and access is blocked with SPR.
- Does TKB support the distributed electronic signature (VEU)?
- Yes. Your software submits the file with transport right T; TKB checks its content and ISO structure and places it in the VEU folder, where it is released in the EBICS VEU-App by Subsembly with signature A or B (collective) or E (single). The VEU order types are HVE, HVD, HVS, HVT, HVU and HVZ.
- Which order types does TKB use for EBICS 3.0?
- Payments upload as BTU MCT/CH/pain.001, version 03 or 09. Downloads are BTD: PSR/CH/pain.002, STM/CH/camt.052, EOP/CH/camt.053, REP/CH/camt.054, EOP/CH/mt940 and DAR/CH for bank documents, plus SWIFT FX, money-market and securities messages with scope GLB. The EBICS 2.5 equivalents include XE2, Z01, Z52, Z53, Z54, STA and ZDF.
- What is TKB's payment cut-off time for EBICS files?
- Payments delivered through the offline interface, including EBICS, for execution with the same value date must arrive by 11:45. TKB publishes no per-currency cut-offs for EBICS.
- What changes at TKB in November 2026?
- Payment files from accounting software must carry structured addresses for execution dates after 13 November 2026 — at least name, town and country in separate fields. TKB rejects orders that do not follow this structure.
- Can I connect my ERP to Thurgauer 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. Payment files with an execution date after this day must carry structured addresses — at least name, town and country; other orders are rejected. Our engine already produces pain.001.001.09 for TKB.
If all of this looks like a lot · it does not have to be
Five steps to a live TKB 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 TKB
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 TKB 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 TKB will check. You sign it by hand and send it.
- 4
Verify TKB 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 TKB
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Thurgauer Kantonalbank’s EBICS page, its EBICS connection-parameter sheet, its Terms of use for EBICS and VEU, its VEU-app guides for iOS and Android, its payments FAQ, its business-customer OLIVIA FAQ, its structured-address page, its QR-bill details page, its imprint, its important-numbers page, its portrait, organisation and participation-certificate pages and the law on Thurgauer Kantonalbank; the Swiss UID register, GLEIF and FINMA’s list of authorised banks. BankConnector is not affiliated with Thurgauer Kantonalbank.