All supported banks

Switzerland  ·  Banque Cantonale Vaudoise  ·  EBICS

Connect BCV without learning EBICS.

EBICS 2.5 and 3.0 on Host ID BCVDEBICS, bank key hashes on a published sheet, and pain.001.001.09 on EBICS 3.0. 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.02</VersionNumber>
</ebicsHEVResponse>

Host ID

BCVDEBICS

EBICS 2.5

H004

EBICS 3.0

H005

Answered in

0.33 s

Published by the bank

The bank's general-information and investor-relations pages, the UID register, GLEIF and FINMA.

Bank details

Legal nameBanque Cantonale Vaudoise
Legal formPublic-law limited company (société anonyme de droit public), Vaud commercial register
Registered officePlace Saint-François 14, 1003 Lausanne
UIDCHE-105.934.376
LEIK1MOBB3OPSBBQO554R76
BICBCVLCH2LXXX
Clearing number767
SupervisionFINMA — authorised bank and securities firm
Majority shareholderCanton of Vaud — 66.95% of the share capital
State guaranteeNone — BCV's commitments are not underwritten by the Canton

Checked live

Measured against the live host. The port is from the bank's parameter sheet.

Access data

EBICS addresshttps://ebics.bcv.ch/ebics.aspx
Port443
Host IDBCVDEBICS
Protocol versionsH004 (02.50) and H005 (03.02)

Published by the bank

The bank's EBICS parameter sheet and product sheet, and the terms of use of BCV-connect EBICS (2019 edition).

Keys, signatures and the agreement

Service nameBCV-connect EBICS — free of charge for BCV clients
AgreementBCV EBICS membership declaration (déclaration d'adhésion), under the terms of use of BCV-connect EBICS
Also applicableBCV's general terms and its special conditions for payment transactions
Versions on the sheet2.5 (H004) · 3.0 (H005)
AuthenticationX002
EncryptionE002
Electronic signatureA005 or A006
Key lengthAt least 2,048 bits on EBICS 3.0, with keys exchanged as X.509 certificates
Key initialisationINI and HIA · the bank validates the key it receives, then activates the protocol
Initialisation letterNot published
Bank key hashesPublished on the parameter sheet for X002 and E002
Bank keys on EBICS 3.0Retrieved as a certificate with HPB
Key updateHCS updates the signature and EBICS user keys
SignaturesManaged in your financial software, with a corporate seal
UsersDesignated by the client alone, in any number — the bank receives no information about them
Distributed signatureNot published
End of EBICS 2.5Not published

Published by the bank

The bank's EBICS parameter sheet, 44-516/25.02.

Order types published by BCV

2.5What it doesDirServiceScopeContainerMessageVersion
XE2Payment order, Swiss Payment Standards 2009SendMCTCHpain.00103
Payment order, Swiss Payment Standards 2019SendMCTCHpain.00109*
Z01Payment status reportDownloadPSRCHZIPpain.00203 · 10*
Z52Intraday account statementDownloadSTMCHZIPcamt.05204 · 08
Z53End-of-day account statementDownloadEOPCHZIPcamt.05304 · 08
Z54QR-IBAN collection fileDownloadREPCHZIPcamt.05404 · 08
STAEnd-of-day account statement, SWIFTDownloadEOPCHmt940
ZDFElectronic account documents, PDFDownloadDARCHZIPdocuments

Versions marked * — pain.001 09 and pain.002 10 — are available on EBICS 3.0 only. pain.001 09 has no EBICS 2.5 order type. Uploads run as BTU and downloads as BTD. pain.002, camt and PDF files are always delivered in a ZIP.

The rest are system order types: key initialisation, the bank’s public keys, customer and user data, available order types, the customer protocol and key updates. You never see one — we run them during setup and afterwards.

INIHIAHPBHTDHKDHAAHACHCS

Published by the bank

The bank's special conditions for payment transactions (September 2024) and its payment-transactions page.

Cut-off times and execution

Same-day cut-off, EBICSNot published
Cut-off timesAvailable from the bank at any time, on request
Orders after the cut-offGenerally executed on the next bank working day
Execution dateThe requested date, when the cut-off is met — the account is debited with that value date
SEPA treatmentEUR · beneficiary IBAN · beneficiary bank in SEPA · charge option SEPA · sent electronically
Year endA payment made after the last working day is booked on the first working day of the next year
Instant paymentsCHF only · BCV states it is currently equipped only to receive them

Published by the bank

The bank's EBICS parameter sheet, its electronic account reports page and its payment-transactions page.

Formats

pain.001.001.03 (Swiss Payment Standards 2009)Accepted — XE2 on EBICS 2.5, MCT/CH on EBICS 3.0
pain.001.001.09 (Swiss Payment Standards 2019)Accepted over EBICS 3.0 only
pain.002Version 03 · version 10 over EBICS 3.0 only
camt.052 · camt.053 · camt.054Versions 04 and 08
camt.052Intraday, generated several times a day
camt.053Daily · also available weekly or monthly
camt.054 contentPayments from QR-bills with a QR-IBAN, and direct debits (LSV)
camt over EBICSEnabled on request through the business banking hotline
MT940Delivered over EBICS — activated by your BCV advisor
E-statementsPDF account documents under ZDF
End of pain.001.001.03Not published
End of MT940Not published
Structured addressesHybrid addresses must already meet the new requirements; unstructured ones are rejected for execution dates after 14 November 2026

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 BCV's EBICS Host ID and URL?
Host ID BCVDEBICS, address https://ebics.bcv.ch/ebics.aspx on port 443. BCV publishes the hash values of its authentication (X002) and encryption (E002) keys on its BCV-connect EBICS parameter sheet.
Which EBICS versions does BCV support?
EBICS 2.5 (H004) and 3.0 (H005); the host answers H005 in version 03.02. On EBICS 3.0, keys are exchanged as X.509 certificates of at least 2,048 bits. No end date for EBICS 2.5 has been published.
Which signature version does BCV use for EBICS?
BCV accepts electronic signatures A005 and A006, with X002 for authentication and E002 for encryption. Signatures are managed in the client's financial software with a corporate seal, and the client alone designates its users.
Does BCV accept pain.001.001.09?
Yes, as Swiss Payment Standards 2019 under MCT/CH, on EBICS 3.0 only; it has no EBICS 2.5 order type. On EBICS 2.5, BCV accepts pain.001.001.03 under XE2. Status reports follow the same split: pain.002 version 10 on EBICS 3.0 only, version 03 on both.
Which order types does BCV publish?
XE2 for pain.001; Z01 for pain.002; Z52, Z53 and Z54 for camt.052, camt.053 and camt.054; STA for MT940; and ZDF for PDF account documents. Under EBICS 3.0 these are MCT, PSR, STM, EOP, REP and DAR with scope CH.
What are BCV's payment cut-off times?
BCV does not publish an EBICS cut-off. Its special conditions for payment transactions state that cut-off times are available from the bank at any time, and that an order received after the cut-off is generally executed on the next bank working day.
When does BCV stop accepting unstructured addresses?
BCV states that payments and standing orders with unstructured addresses and an execution date after 14 November 2026 will be rejected. Hybrid addresses must already meet the new requirements.
Can I connect my ERP to BCV?
Yes. You send canonical JSON and BankConnector produces pain.001.001.09 to the Swiss Payment Standards ch.03 schema, 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. Payments and standing orders with unstructured addresses and an execution date after this day are rejected.

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

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

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

  4. 4

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

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

Sources — BCV’s BCV-connect EBICS page, its EBICS parameter sheet in French (44-516/25.02) and English (44-516e/24.04), its BCV-connect EBICS product sheet, the terms of use of BCV-connect EBICS (2019 edition), its special conditions for payment transactions (September 2024 edition), its electronic account reports page, its changes to payment transactions page, its general information and its investor relations overview; the Swiss UID register, the GLEIF LEI record and FINMA’s list of authorised banks. BankConnector is not affiliated with Banque Cantonale Vaudoise.

Back to all supported banks

Other banks

Connection guides for the other banks we have built.