All supported banks

Switzerland  ·  Aargauische Kantonalbank  ·  EBICS

Connect AKB without learning EBICS.

EBICS 2.5 and 3.0, free of charge, with payment approval through the distributed signature. EBICS 2.5 ends on 13 November 2026. We handle the payments, the statements and every protocol step underneath.

AKB at a glance

BIC
KBAGCH22
Clearing number
761
EBICS versions
2.5 and 3.0
Host ID
Not published
Keys
2048 bit · A005 / A006 · X002 · E002
EBICS and VEU
Free of charge

Published by the bank

The bank's website, its corporate governance page and the cantonal bank law it publishes; the commercial register, GLEIF and FINMA.

Bank details

BICKBAGCH22
Clearing number761
Legal nameAargauische Kantonalbank
Legal formIndependent institution under cantonal public law, with its own legal personality
Registered officeBahnhofplatz 1, 5001 Aarau
UIDCHE-105.845.287, commercial register of the Canton of Aargau
LEIHTQNUFL6OI5TZ7V7SI73
OwnerCanton of Aargau — 100%
State guaranteeThe canton is liable for all the bank's liabilities its own funds cannot cover — except subordinated loans and liabilities of subsidiaries
SupervisionFINMA — authorised bank, supervisory category 3

Published by the bank

The bank's EBICS page, its EBICS 3.0 migration document and its payments roadmap.

Access data

EBICS addressNot published
Host IDNot published
Authorisation dataSent in writing by AKB once the contract is concluded
Customer IDYour EBICS contract number
User IDYour EBICS user
Protocol versionsEBICS 2.5 and EBICS 3.0 — 3.0 recommended
End of EBICS 2.5Support ends 13 Nov 2026
New contracts on EBICS 2.4Not accepted
AccountsEach newly added account is reported to AKB — none is added automatically
Supporte-Banking / Mobile Banking Helpline · +41 62 835 77 99 · e-banking@akb.ch · Mon–Fri 07:30–17:30

Published by the bank

The bank's EBICS page and factsheet, its EBICS 3.0 migration document and its VEU-app guide.

Keys, signatures and the agreement

AgreementEBICS participation declaration (EBICS-Teilnahmeerklärung)
PriceEBICS and VEU are free of charge
Key length2048 bit
Signature keyA005 or A006
Authentication keyX002
Encryption keyE002
Bank key hashesNot published
Bank certificateFetched with HPB
Initialisation letterPrinted, signed and sent to AKB — AKB activates the access and confirms it
Moving to EBICS 3.0Active subscriber keys are kept — no new initialisation
Distributed signatureVEU — orders submitted with signature authorisation T, then released by one signature or two, per signature model
VEU appSubsembly EBICS VEU-App, free of charge

Published by the bank

The bank's EBICS 3.0 migration document.

Order types published by AKB

2.5What it does3.0ServiceScopeContainerMessageVersion
XE2Payment order, pain.001.001.03BTUMCTCHpain.00103
Payment order, pain.001.001.09BTUMCTCHpain.00109
Z01Status report, pain.002.001.03BTDPSRCHZIPpain.00203
Status report, pain.002.001.10BTDPSRCHZIPpain.00210
Z52Intraday account movements, camt.052.001.04BTDSTMCHZIPcamt.05204
Intraday account movements, camt.052.001.08BTDSTMCHZIPcamt.05208
Z53End-of-day statement, camt.053.001.04BTDEOPCHZIPcamt.05304
End-of-day statement, camt.053.001.08BTDEOPCHZIPcamt.05308
Z54Batch booking details, camt.054.001.04BTDREPCHZIPcamt.05404
Batch booking details, camt.054.001.08BTDREPCHZIPcamt.05408
STAEnd-of-day statement, SWIFT MT940BTDEOPCHmt940
ZDFElectronic bank documents, PDFBTDDARCHZIPDocuments

Rows without a 2.5 code carry the ISO 20022 version 2019 messages, which AKB accepts and delivers over EBICS 3.0 only. They are not switched on automatically: AKB activates pain.001.001.09 and the camt .08 versions on request through its e-Banking / Mobile Banking Helpline.

Published by the bank

The bank's instant-payment page.

Cut-off times and execution

EBICS payment ordersNot published
Instant paymentAround the clock, 365 days a year, within Switzerland
Instant executionAt most 10 seconds
Instant currencyCHF only — debit and recipient account both in CHF
Instant recipientA CH or LI IBAN
Instant amount ceilingCHF 20,000 per payment
Instant sending requirese-Banking payment authorisation on the account — entered in e-Banking and Mobile Banking
Instant priceCHF 2 per outgoing payment · incoming free

Published by the bank

The bank's EBICS page and factsheet, its EBICS 3.0 migration document and its payments roadmap.

Formats

You sendpain.001 payment orders
You receivepain.002 · camt.052 · camt.053 · camt.054 · MT940 · electronic bank documents (PDF)
camt.054 credit notificationsQRR and SCOR references
LSV+ / BDD creditsv11 and camt.054
pain.001.001.09 · camt .08EBICS 3.0 only, activated on request
ISO 20022 version 2009Ends November 2026
Unstructured addressesValid until 14 Nov 2026
Hybrid addressesValid since 22 Nov 2025
QR-billNewly created QR-bills carry structured addresses only, since 21 Nov 2025
MT940 end dateNot published

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
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 Aargauische Kantonalbank's EBICS Host ID and URL?
AKB does not publish them. Once the EBICS participation declaration is concluded, AKB sends the authorisation data for EBICS in writing. The customer ID is your EBICS contract number and the user ID is your EBICS user.
Which EBICS versions does AKB support?
EBICS 2.5 and EBICS 3.0, and AKB recommends 3.0. Support for EBICS 2.5 and older ends on 13 November 2026, after which payments and account information in the old format are no longer accepted. New contracts on EBICS 2.4 are not accepted.
Which keys does AKB require for EBICS?
2048-bit keys: A005 or A006 for the signature, X002 for authentication and E002 for encryption. Active subscriber keys carry over to EBICS 3.0 without a new initialisation; the bank's current certificate is fetched with HPB.
Does AKB support the distributed electronic signature (VEU)?
Yes, free of charge. Orders are submitted with signature authorisation T, AKB checks them and places them in the VEU folder, and authorised signatories release them in the Subsembly EBICS VEU-App with one signature or two, depending on the signature model.
Which order types does AKB use for EBICS 3.0?
Payments upload as BTU MCT/CH/pain.001, version 03 or 09. Downloads are BTD with scope CH: PSR for pain.002, STM for camt.052, EOP for camt.053 and MT940, REP for camt.054, and DAR for PDF bank documents. The 2.5 codes are XE2, Z01, Z52, Z53, Z54, STA and ZDF.
Can I connect my ERP to Aargauische 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

  1. ISO 20022 version 2009 ends. Only version 2019 messages are processed — pain.001.001.09 and the camt .08 versions, which need EBICS 3.0. Our engine already produces pain.001.001.09 for AKB.

  2. Support for EBICS 2.5 and older ends. Payments and account information in the old format are no longer accepted from then on.

  3. Structured or hybrid addresses become mandatory for domestic and foreign payments submitted as pain.001. Unstructured addresses are no longer valid.

  4. LSV+ and Business Direct Debit end. Billers need an alternative invoicing method in place by the end of September 2028.

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

Five steps to a live AKB 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 AKB

    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 AKB 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 AKB will check. You sign it by hand and send it.

  4. 4

    Verify AKB 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 AKB

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

Sources — Aargauische Kantonalbank’s EBICS page, its EBICS factsheet, its EBICS 3.0 migration document, its VEU-app guide, its payments roadmap page and roadmap for Swiss payments, its instant-payment page, its corporate governance page and the Law on the Aargauische Kantonalbank; the bank’s entries in the commercial register of the Canton of Aargau, in GLEIF and in FINMA’s list of authorised banks. BankConnector is not affiliated with Aargauische Kantonalbank.

Back to all supported banks

Other banks

Connection guides for the other banks we have built.