EBICS version 3.0 combines the previous country-specific EBICS versions into one common standard, ensuring secure data transmission between client and bank. This is made possible thanks to a new identifying characteristic called “Business Transaction Format” (BTF).
EBICS 3.0 at a glance
EBICS 3.0 at a glance
Secure
Uniform security standards ensure greater security
Standardized
Transaction types can be identified by a uniform set of formats (BTF)
Proactive
Prerequisite for the new ISO20022 version from November 2022
SIX published the “Swiss Market Practice Guidelines EBICS” for EBICS 3.0 in July 2020. These will come into force in November 2021. After this date, SIX will stop publishing the existing guidelines for version 2.4 and older. They will stop publishing the guidelines for version 2.5 from November 2023. We recommend that software manufacturers and clients get to know the benefits, requirements and functions of EBICS 3.0 ahead of time, and that they actively plan and implement the switch to this new EBICS version.
Discuss switching to the new EBICS version with your software provider. The EBICS user keys (A005, E002, X002) must have a minimum length of 2,048 bits. The keys can be updated using order types HCS or HCA and PUB. After implementing EBICS 3.0 you can activate EBICS 3.0 (H005). There is generally no need to re-initialize your user.
Recommendations for bank clients
- Talk to your software provider as soon as possible about updating your software.
- Inform your IT department about the planned changes.
- Configure the BTF used by ۶Ƶ in your software.
- After introducing EBCICS 3.0, switch the EBICS user in your software (activation H005) and then retrieve the current bank keys. These will then be delivered as a certificate.
Recommendations for software manufacturers
- Check the new EBICS specifications in version 3.0.
- Configure the BTF used by ۶Ƶ according to our connection parameters, in addition to the standard BTF.
- Enable your clients to update the key to at least 2,048 bits (HCS or HCA and PUB).
- Show your client how to activate the new EBICS version (activation H005).
- Provide your client with instructions on how to switch to EBICS 3.0 in their software.
- Describe the changes in the user interface or in the process flows.
The new identifying characteristic called “Business Transaction Format” (BTF) facilitates uniform, structured labeling of transaction types and the permitted formats. BTF replaces the existing order types in EBICS 3.0. You can find a full list of transaction types possible at ۶Ƶ below at the section “Important information for clients and software partners”.
Examples of key transaction types
Transaction types / New BTF parameters (from EBICS 3.0) | Transaction types / New BTF parameters (from EBICS 3.0) | Previous order type (before EBICS 2.5) | Previous order type (before EBICS 2.5) | New BTF parameters - Order Type | New BTF parameters - Order Type | New BTF parameters - Service Name | New BTF parameters - Service Name | New BTF parameters - Scope | New BTF parameters - Scope | New BTF parameters - Service Option | New BTF parameters - Service Option | New BTF parameters - Container | New BTF parameters - Container | New BTF parameters - MsgName | New BTF parameters - MsgName | New BTF parameters - Version | New BTF parameters - Version |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Transaction types / New BTF parameters (from EBICS 3.0) | Submitting payment orders in Swiss Payment Standards format | Previous order type (before EBICS 2.5) | XE2 | New BTF parameters - Order Type | BTU | New BTF parameters - Service Name | MCT | New BTF parameters - Scope | CH | New BTF parameters - Service Option | - | New BTF parameters - Container | - | New BTF parameters - MsgName | pain.001 | New BTF parameters - Version | 03 |
Transaction types / New BTF parameters (from EBICS 3.0) | Retrieving the status of submitted payment orders in Swiss Payment Standards format | Previous order type (before EBICS 2.5) | Z01 | New BTF parameters - Order Type | BTD | New BTF parameters - Service Name | PSR | New BTF parameters - Scope | CH | New BTF parameters - Service Option | - | New BTF parameters - Container | ZIP | New BTF parameters - MsgName | pain.002 | New BTF parameters - Version | 03 |
Transaction types / New BTF parameters (from EBICS 3.0) | Retrieving bank statements in Swiss Payment Standards format | Previous order type (before EBICS 2.5) | Z53 | New BTF parameters - Order Type | BTD | New BTF parameters - Service Name | EOP | New BTF parameters - Scope | CH | New BTF parameters - Service Option | - | New BTF parameters - Container | ZIP | New BTF parameters - MsgName | camt.053 | New BTF parameters - Version | 04 |
Transaction types / New BTF parameters (from EBICS 3.0) | Retrieving collective booking details in camt.054 format | Previous order type (before EBICS 2.5) | Z54 | New BTF parameters - Order Type | BTD | New BTF parameters - Service Name | REP | New BTF parameters - Scope | CH | New BTF parameters - Service Option | - | New BTF parameters - Container | ZIP | New BTF parameters - MsgName | camt.054 | New BTF parameters - Version | 04 |
Transaction types / New BTF parameters (from EBICS 3.0) | Retrieving bank statements in SWIFT format | Previous order type (before EBICS 2.5) | ZK3 | New BTF parameters - Order Type | BTD | New BTF parameters - Service Name | EOP | New BTF parameters - Scope | CH | New BTF parameters - Service Option | - | New BTF parameters - Container | - | New BTF parameters - MsgName | mt940 | New BTF parameters - Version | - |
