Switzerland · Valiant Bank AG · EBICS
Connect Valiant without learning EBICS.
EBICS 2.5 and 3.0 on Host ID VABEBICS, bank key hashes on its EBICS page, free of charge, with every payment released through the distributed signature. 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
VABEBICS
EBICS 2.5
H004
EBICS 3.0
H005
Answered in
0.15 s
Published by the bank
The bank's imprint, IBAN/SWIFT page and portrait factsheet; the Swiss UID register, GLEIF and FINMA.
Bank details
| BIC | VABECH22XXX |
| Clearing number (BC number) | 6300 |
| Legal name | Valiant Bank AG (Banque Valiant SA) |
| Legal form | Aktiengesellschaft (AG) — company limited by shares |
| Registered office | Bundesplatz 4, 3011 Bern |
| UID | CHE-105.944.759 |
| Commercial register | CH-035.3.014.676-4, Bern |
| LEI | 529900Z7NMGN5XV0RV34 |
| Parent | Valiant Holding AG — direct consolidating parent in GLEIF |
| Presence | Active only in Switzerland · locally rooted in 15 cantons |
| Supervision | FINMA — authorised bank, supervisory category 3 |
| Switchboard | +41 31 320 91 11 |
Checked live
Measured against the live host, at the address and Host ID on the bank's EBICS page.
Access data
| EBICS address | https://ebics.swisscom.com/ebics-server/ebics.aspx |
| Host ID | VABEBICS |
| Port | 443 |
| Protocol versions | H003 (02.40), H004 (02.50) and H005 (03.00) |
| Customer ID and User ID | Issued by Valiant |
Published by the bank
The bank's EBICS page, its EBICS product description and its VEU-app installation guide.
Keys, signatures and the agreement
| Price | Free of charge |
| Availability | Around the clock |
| Versions on the EBICS page | H004 and H005 |
| Authentication | X002 |
| Encryption | E002 |
| Electronic signature version | Not published |
| Key length | Not published |
| Bank key hashes | Published on the EBICS page for X002 and E002, one value each for H004 and H005 |
| Key changes | HCA (authentication and encryption) · HCS (signature, authentication and encryption) |
| Blocking access | SPR |
| Distributed signature (VEU) | EBICS offered only with VEU · orders are transmitted to the bank but not booked until the authorised signatories release them |
| VEU app | EBICS VEU-App by Subsembly, iOS and Android, free of charge · access data from the enclosed letter · INI letter printed, signed and sent to Valiant |
| INI letter address | Valiant Bank AG, Electronic Banking, Postfach, 3001 Bern |
| Key release | Valiant checks the keys from the INI letter and releases them within at most two working days |
| Checking the bank keys | Compared in the app against the bank keys in the «EBICS-Zugangsdaten» letter before confirming |
| End of EBICS 2.5 | Not published |
| Customer centre | 031 320 91 11 · Mon–Fri 07:30–21:00 · Sat 09:00–17:00 |
Published by the bank
The “Bankparameter für EBICS” list on the bank's EBICS page.
Order types published by Valiant
| Order type | Dir | What it does | Container |
|---|---|---|---|
| XE2 | Send | Payment orders in ISO 20022 format (CH) — pain.001, CH schema | — |
| Z01 | Download | Payment status report for everything (CH) | — |
| C52 | Download | Pending entries, camt.052 | ZIP |
| C53 | Download | Account statements, camt.053 | ZIP |
| C54 | Download | Credit and debit notifications, camt.054 | ZIP |
Valiant publishes EBICS 2.5 order types only. EBICS 3.0 BTFs: Not published.
The distributed-signature order types: adding a signature, cancelling, the overview with additional information, the overview, VEU status and transaction details.
The administrative order types: key initialisation, the customer protocol, supported versions, the bank’s public keys and parameters, retrievable order types, customer and subscriber data, blocking, key changes and certificate submission. You never see one — we run them during setup and afterwards.
Published by the bank
The bank's EBICS page and its Basisdokument (AGB), clause 14.
Cut-off times and execution
| EBICS cut-off | Not published |
| Cut-off times | Communicated to the customer in suitable form |
| Orders after the cut-off | As a rule executed on the next bank working day |
| No execution date in the order | Executed taking the applicable cut-off times into account |
Published by the bank
The formats list on the bank's EBICS page and its EBICS product description.
Formats
| pain.001 | Payment order, CH schema — version not published |
| pain.002 | Status report |
| pain.008 | LSV direct debit order |
| camt.052 | Intraday statement |
| camt.053 | Account statement · account statement with detail |
| camt.054 | Booking notification · ESR detail notification |
| Bank documents | E-documents (zdf) · EVV documents (zcp) |
| MT940 | With IBAN — listed as a former format |
| Charge bearer | Not published |
| Batch booking | Not published |
| Debtor agent | Not published |
| Remittance information | Not published |
| Structured addresses | 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 Valiant's EBICS Host ID and URL?
- Host ID VABEBICS, address https://ebics.swisscom.com/ebics-server/ebics.aspx, port 443. Valiant publishes both on its EBICS page, together with the hash values of its X002 and E002 bank keys. Your customer ID and user ID are issued by Valiant.
- Which EBICS versions does Valiant support?
- Valiant's EBICS page names protocol versions H004 (EBICS 2.5) and H005 (EBICS 3.0); the host answers H003 (02.40), H004 (02.50) and H005 (03.00). Valiant has published no end date for EBICS 2.5.
- Does Valiant require the distributed electronic signature (VEU)?
- Yes. Valiant offers EBICS only with VEU. Payment orders are transmitted to the bank but not booked until the authorised signatories release them, for example in the free EBICS VEU-App by Subsembly. Valiant checks the keys on the signed INI letter and releases them within at most two working days.
- Which order types does Valiant publish for EBICS?
- Payments upload with XE2 (pain.001, CH schema). Downloads are Z01 (payment status report), C52 (camt.052), C53 (camt.053) and C54 (camt.054), the camt files in a ZIP archive. The VEU order types are HVE, HVS, HVZ, HVU, HVD and HVT. Valiant publishes no EBICS 3.0 BTF list.
- What is Valiant's payment cut-off time for EBICS files?
- Valiant publishes no cut-off time for EBICS. Its general terms state that cut-off times are communicated to the customer in suitable form, and that an order received after the cut-off can as a rule only be executed on the next bank working day.
- Can I connect my ERP to Valiant?
- 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 Valiant 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 Valiant
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 Valiant 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 Valiant will check. You sign it by hand and send it.
- 4
Verify Valiant 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 Valiant
Payments go out as pain.001 and statements come back as camt. The connection runs unattended from here.
Sources — Valiant’s EBICS page, its EBICS product description, its VEU-app installation guide, its Basisdokument (general terms), its portrait factsheet, its imprint and its IBAN/SWIFT page; the bank’s entries in the Swiss UID register, in GLEIF and in FINMA’s list of authorised banks. BankConnector is not affiliated with Valiant Bank AG.