All supported banks

Switzerland  ·  St.Galler Kantonalbank  ·  EBICS

Connect SGKB without learning EBICS.

EBICS on Host ID SGKB, signature A006, bank key hashes on a published parameter sheet, free of charge, with payment approval in the free VEU 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="H004">02.50</VersionNumber>
  <VersionNumber ProtocolVersion="H005">03.00</VersionNumber>
</ebicsHEVResponse>

Host ID

SGKB

EBICS 2.5

H004

EBICS 3.0

H005

Answered in

0.40 s

Published by the bank

The bank's imprint, portrait, state-guarantee and QR-bill pages, its articles of association and 2025 annual report; the Swiss UID register, GLEIF and FINMA.

Bank details

BICKBSGCH22 · KBSGCH22XXX for worldwide transactions
Clearing number781
QR-IID30781
Legal nameSt.Galler Kantonalbank AG
Registered translationsBanca Cantonale di San Gallo SA · Banque Cantonale de St-Gall SA · Cantonal Bank of Saint Gall Ltd
Legal formCompany limited by shares (Aktiengesellschaft) under Art. 620 ff. of the Code of Obligations, in particular Art. 762
Registered officeSt. Leonhardstrasse 25, 9001 St. Gallen
UIDCHE-105.845.146
Commercial registerCH-320.8.000.310-5, Canton of St. Gallen
LEI549300GFRG6OK00RG957
Founded1868, as St.Gallische Kantonalbank
ListingSIX Swiss Exchange since 2 April 2001 · ISIN CH0011484067
Share capitalCHF 479,493,280 · 5,993,666 registered shares of CHF 80 nominal
Majority ownerCanton of St. Gallen — 51.0% of the share capital with voting rights, 31 December 2025
State guaranteeThe Canton of St. Gallen is liable by law (Art. 6 Cantonal Bank Act) for all liabilities of St.Galler Kantonalbank AG insofar as its own funds are insufficient — not for share capital, subordinated loans or St.Galler Kantonalbank Deutschland AG
SupervisionFINMA — authorised bank, supervisory category 3
SubsidiarySt.Galler Kantonalbank Deutschland AG, Munich — wholly owned, investment business only

Checked live

Measured against the live host, at the address and Host ID on the bank's connection-parameter sheet.

Access data

EBICS addresshttps://ebics.sgkb.ch/
Host IDSGKB
Port443
Protocol versionsH004 (02.50) and H005 (03.00)

Published by the bank

The bank's EBICS connection-parameter sheet, its SGKB EBICS and VEU pages, its EBICS factsheet, its VEU App installation guide and its conditions for electronic services.

Keys, signatures and the agreement

ServiceSGKB EBICS — free of charge · payment prices and conditions apply
AgreementNot published
RequirementsEBICS-capable software · an account with St.Galler Kantonalbank · internet access
OrderingThrough the E-Banking Help Line, once your software is EBICS-capable
EBICS version, parameter sheet3.0 (schema version H005)
Subscriber ID and customer IDSent in a separate letter
Authentication keyX002
Encryption keyE002
Electronic signatureA006
Key lengthNot published
Bank key hashesPublished on the parameter sheet for X002 and E002
Initialisation letter, VEU App guidePrinted after initialisation, legally signed according to your signing rules and returned to SGKB in the reply envelope
Activation, VEU App guideSGKB reports as soon as the access is released — about three working days
Bank key check, VEU App guideBank keys compared with the details in SGKB's licence-code letter
Distributed signatureVEU supported · free VEU App for Android and iOS
VEU AppA payment can only be accepted or cancelled — not changed
Collective paymentsOnly the whole payment file can be released or cancelled — not a single payment in it
Cancelled paymentThe submitter is notified and must submit a new payment file via EBICS
TermsConditions for electronic services, version 11.2025
Unused accessSGKB may close an access unused for 18 consecutive months, without notice
E-Banking Help Line0844 88 44 88 · info@sgkb.ch · Monday to Friday, 07:30 to 17:30
ClassAuthorisationWhat it allows
TTransport signatureTransmitting payment orders only — no initialling or releasing
EIndividual signatureA natural person transmits and releases payment orders alone
A & BCollective signatureFour-eyes release in the VEU App — one person either initials or releases, never both
E, A, BCombinationE releases payments initialled by A or B, or releases at once without initialling

Published by the bank

The bank's EBICS connection-parameter sheet.

Order types published by SGKB

ServiceWhat it doesDirScopeOptionContainerMessageVersion
MCTPayment submission (CH)BTUCHpain.00109
PSRPayment status reportBTDCHZIPpain.00210
DARE-documentsBTDCHZIPdocuments
STMIntraday account statementBTDCHZIPcamt.05208
EOPAccount statementBTDCHZIPcamt.05308
REPCredits (QRR / SCOR)BTDCHZIPcamt.05408
EOPAccount statement, SWIFTBTDDE0ZB2mt940
FXCForeign exchange tradesBTDGLBmt300
FXCMoney market and fiduciary trades, timeBTDGLBmt320
FXCMoney market and fiduciary trades, callBTDGLBmt330
FXCInterest payments, money market and fiduciary tradesBTDGLBmt350
STRStock exchange contract noteBTDGLBmt515
SSMCustody account statementBTDGLBmt535
SSMCustody account transactionsBTDGLBmt536
SEVCorporate actionsBTDGLBmt566

The EBICS 3.0 BTFs on the parameter sheet. Payments upload as BTU and everything else downloads as BTD. pain.002, camt and e-documents come in a ZIP; the SWIFT statement runs on scope DE with service option 0ZB2, and the treasury and securities messages on scope GLB.

The distributed-signature order types: order status, transaction details, overview, signature folder with additional information, adding a signature and cancelling one.

HVDHVTHVUHVZHVEHVS

The administration order types: customer protocol, available order types, customer and subscriber data, the bank’s public keys and parameters, key submission and key changes. You never see one — we run them during setup and afterwards.

HACHAAHKDHTDHPBHPDPUBHCAHCSHIAINI
EBICS 2.5 order typesNot published

Published by the bank

The bank's special conditions for SEPA transactions and its price list (valid from 1 July 2026).

Cut-off times and execution

Cut-off for EBICS ordersNot published
After the cut-off, SEPA conditionsAs a rule executed on the next bank working day
Weekend or holiday date, SEPA conditionsCredit or debit may be booked on the next bank working day
SEPA creditAt most 3 days after the debit
Collective order, SEPA conditionsEvery payment must meet the conditions — otherwise the whole collective order may be rejected
Order prices, EBICSNot published
Charge option OURCHF 20 surcharge
Incomplete order (missing IBAN, BIC)CHF 12

Published by the bank

The bank's EBICS connection-parameter sheet, its camt handbook, its SGKB EBICS page and its page on paying invoices with accounting software.

Formats

pain.001, parameter sheetpain.001 version 09 (MCT, scope CH)
pain.002, parameter sheetpain.002 version 10 (PSR, scope CH)
camt.052 · camt.053 · camt.054ISO 20022 version 2019 · handbook valid from 15 August 2025
camt messagesOne account per message
camt.054Credits with QR reference (QRR) or SCOR reference
GuidelineSwiss Payment Standards business rules and implementation guidelines
SWIFT statementMT940
Treasury confirmationsMT300 · MT320 · MT330 · MT350
SecuritiesMT515 · MT535 · MT536 · MT566
Bank documentsDownloadable
Faulty pain.001 via EBICSCorrect the payments named in the pain.002 and submit only those — never the whole file again, risk of double execution
Batch bookingNot published
Structured addressesNot published
End of pain.001.001.03Not published
End of MT940Not published
ISO 20022 questionsiso20022@sgkb.ch

BankConnector

What is built and shipped for this bank today.

What our engine produces

Payment formatpain.001.001.09 (Swiss Payment Standards, ch.03 schema)
GuidelineSwiss Payment Standards 09/ch.03, published by SIX
Charge bearerSLEV on SEPA payments · SHAR on all others
Batch bookingFalse
Debtor BICRequired
Remittance limit140 characters
Name limit70 characters
Character setLatin — transliterated before the bank sees it
Payment types builtSEPA credit transfer · Swiss domestic transfer · QR-bill payment · international
Read backcamt, pain.002 — one normalised format
Not supportedDirect debits

BankConnector

Questions

What is St.Galler Kantonalbank's EBICS Host ID and URL?
Host ID SGKB, address https://ebics.sgkb.ch/ on port 443. SGKB publishes both on its EBICS connection-parameter sheet, together with the hash values of its X002 and E002 keys. Your subscriber ID and customer ID are sent to you in a separate letter.
Which EBICS versions does SGKB support?
The host answers H004 (2.5) and H005 (3.0). SGKB's connection-parameter sheet names EBICS 3.0 with schema version H005 and lists its order types as EBICS 3.0 BTFs.
Which keys and signature does SGKB use for EBICS?
X002 for authentication, E002 for encryption and A006 for the electronic signature. The hash values of SGKB's X002 and E002 keys are printed on its connection-parameter sheet.
Does SGKB support the distributed electronic signature (VEU)?
Yes. SGKB supports the VEU order types HVD, HVT, HVU, HVZ, HVE and HVS, and offers a free VEU App. Class T only transmits, E releases alone, and A and B release together under the four-eyes principle. In the app a payment can only be accepted or cancelled, and only the whole payment file, never a single payment in it.
Which order types does SGKB use for EBICS 3.0?
Payments upload as BTU MCT/CH/pain.001 version 09. Downloads are BTD: PSR for pain.002 version 10, STM for camt.052, EOP for camt.053 and REP for camt.054, all version 08 with scope CH in a ZIP, and DAR for e-documents. The MT940 statement is EOP with scope DE and option 0ZB2; treasury and securities messages run on scope GLB.
What are St.Galler Kantonalbank's payment cut-off times?
SGKB publishes no cut-off for EBICS orders. Its conditions for SEPA transactions state that a payment submitted after the cut-off is as a rule executed on the next bank working day.
Which formats can I exchange with SGKB over EBICS?
You send pain.001 and fetch pain.002 status reports, camt.052, camt.053 and camt.054 statements in ISO 20022 version 2019, MT940 statements, e-documents, treasury confirmations (MT300, MT320, MT330, MT350) and securities messages (MT515, MT535, MT536, MT566).
Can I connect my ERP to St.Galler 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.

If all of this looks like a lot  ·  it does not have to be

Five steps to a live SGKB 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. 1

    Request the agreement from SGKB

    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. 2

    Set up and send your keys

    Enter the values from the agreement SGKB 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. 3

    Prove your identity on paper

    EBICS confirms the key exchange on paper, by design. We print the initialisation letter carrying the fingerprints SGKB will check. You sign it by hand and send it.

  4. 4

    Verify SGKB 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. 5

    You are now in production with SGKB

    Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.

Back to all supported banks

Other banks

Connection guides for the other banks we have built.

Aareal Bank

EBICS 2.5 and 3.0

SozialBank

EBICS 2.5 and 3.0

Warburg Bank

EBICS 2.5 and 3.0

apoBank

EBICS 2.3 to 3.0

BayernLB

EBICS 2.5 and 3.0

Berenberg

EBICS 2.4, 2.5 and 3.0

Berliner Sparkasse

EBICS 2.5 and 3.0

Berliner Volksbank

EBICS 2.5 and 3.0

Haspa

EBICS 2.5 and 3.0

Helaba

EBICS 2.5 and 3.0

Naspa

EBICS 2.5 and 3.0

NORD/LB

EBICS 2.5 and 3.0

OLB

EBICS 2.3 to 3.0

Postbank

EBICS 2.3 to 3.0

ProCredit Bank

EBICS 2.4, 2.5 and 3.0

SaarLB

EBICS 2.5 and 3.0

Sparkasse an Ennepe und Ruhr

EBICS

Sparkasse Bremen

EBICS 2.5 and 3.0

Sparkasse Darmstadt und Dieburg

EBICS 2.5 and 3.0

Sparkasse Fürth

EBICS

Sparkasse Heidelberg

EBICS

Sparkasse KölnBonn

EBICS 2.5 and 3.0

Südwestbank

EBICS

Bankhaus Werhahn

EBICS

HypoVereinsbank (UniCredit)

EBICS 2.5 and 3.0

Volksbanken Raiffeisenbanken

EBICS 2.5 and 3.0

Bank Connect

Danish banks on Bankdata, BEC and NBS

Nordea

Corporate Access Webservice · E-Gateway

Danske Bank

EDI Webservices

OP Financial Group

OP Web Services

DNB

PGP-encrypted SFTP

Deutsche Bank

EBICS 2.3 to 3.0

Jyske Bank Hamburg

EBICS 2.3 to 3.0

HSBC

HSBCnet SFTP

Aargauische Kantonalbank

EBICS 2.5 and 3.0

BancaStato

EBICS 2.4, 2.5 and 3.0

Bank CIC (Schweiz)

EBICS 2.4, 2.5 and 3.0

Bank Cler

EBICS 2.5 and 3.0

Banque Cantonale de Fribourg

EBICS 2.5 and 3.0

Banque Cantonale de Genève

EBICS

BCV

EBICS 2.5 and 3.0

Basellandschaftliche Kantonalbank

EBICS 2.5 and 3.0

Basler Kantonalbank

EBICS 2.5 and 3.0

Berner Kantonalbank

EBICS 2.4, 2.5 and 3.0

Graubündner Kantonalbank

EBICS 2.5 and 3.0

Hypothekarbank Lenzburg

EBICS 2.5 and 3.0

Luzerner Kantonalbank

EBICS 2.4, 2.5 and 3.0

PostFinance

EBICS 2.5 and 3.0

Raiffeisen

EBICS 2.5 and 3.0

Schwyzer Kantonalbank

EBICS 3.0

Thurgauer Kantonalbank

EBICS 2.4, 2.5 and 3.0

Urner Kantonalbank

EBICS 2.4, 2.5 and 3.0

Valiant Bank

EBICS 2.5 and 3.0

Zürcher Kantonalbank

EBICS 2.5 and 3.0

Zuger Kantonalbank

EBICS 2.4, 2.5 and 3.0

Commerzbank

EBICS 2.5 and 3.0

ING Germany

EBICS 2.4, 2.5 and 3.0