BTF parameters (EBICS 3.0)
This page refers to BTF parameters according to the EBICS 3.0 specification. Under the EBICS 2.5 specification there are order types instead of BTF parameters. Please read more here.
The different formats for transferring and retrieving files via EBICS 3.0 are defined via BTF parameters (Business Transactions & Formats) and the associated service names. Depending on how the BTF parameters are set, different file formats are then implied. In order to define the payment types and BTF parameters for an EBICS contact in konfipay, click in the navigation bar on the left on Master data
and then EBICS
. Select the EBICS contact in the list and click on Business transactions
.
When setting up an EBICS contact, your bank automatically provides a list with the available business transactions and the associated service names and BTF parameters (via the so-called HTD file), from which konfipay automatically reads the available business transactions for upload and download:

If you click on Refresh
the HTD file is retrieved and read out again by the bank and the order types are updated to the status of the HTD file. With Download
you can also save the HTD file on your computer.
Upload
Here you can control the assignment of payment types to BTF parameters. The various payment types are permanently defined by konfipay, and each is assigned a service name or the appropriate BTF parameters with which the corresponding payment is executed. For example: If the payment type SEPA credit transfer is associated with the service name SCT
and thus the BTF parameters SCT DE pain.001 XML
all SEPA credit transfers are transferred with this service name and BTF parameters.
You can assign a different service name and therefore different BTF parameters to a payment type by selecting the payment type and then clicking on Edit
. You can then select from the available service names.
Under Signing authority
you will find the information for each order type, which EBICS signature class your bank grants this EBICS contact for this service name and for which bank accounts.
Download
Here you can control the assignment of file retrievals to BTF parameters. The available retrievable data, e.g. account transactions and earmarked items, are permanently defined by konfipay. If you select a retrieval format and click on Edit
button, you can assign one or more order types to the download format.
Assigning several order types at once is explicitly permitted here. For example, interim bookings are often displayed via different services or BTF parameters, and the assignment of several EBICS services ensures that all available data is retrieved when interim bookings are retrieved.
With Activate
or Deactivate
you can deactivate a retrieval format if required, in which case, for example, no more account transactions will be retrieved.

By clicking in the toolbar on Historic download
you can change the settings for the historical retrieval of transaction files. You can deactivate the historical retrieval here or activate the negative acknowledgement for historical retrievals.
Retrievable data is often only made available for retrieval once. Once it has been retrieved, it cannot be retrieved again without further ado. This is where the historical download comes in - it can be used to retrieve this data multiple times. As a rule, data that already exists in konfipay from a previous retrieval is then sorted out using a duplicate check. Alternatively, you can use the acknowledgement per API key to keep the databases up to date independently of each other via various API interfaces.
In exceptional cases, a historic download may affect the productive dataset on the bank side - you can then activate the negative acknowledgement for historical downloads.

Download (Misc)
Here you can define business transactions for the retrieval of miscellaneous files. These miscellaneous files are not payment or transaction files but, for example, PDF or text files that banks make available via EBICS on the basis of special agreements.
To configure the retrieval of various file types, click in the toolbar on Add
. You can then select from the drop-down list of existing service names for various files and assign the corresponding file format to the order type (e.g. PDF, TXT or CSV).
If you are missing a service name here, you may first need to configure it as an available order type - see the following section.
To delete a configuration for miscellaneous files, select it and click on Delete
in the toolbar.
Available
All service names and BTF parameters that are available for an EBICS contact are collected here. Your bank automatically provides konfipay with a list of the available service names or BTF parameters (so-called HTD file).
If you want to manually add further available configurations (to set them up later for retrieval or transfer), click on Add
.
The input options are described in the following table. Mandatory fields are marked in bold. Further information on these fields can be found in section 5.5.1.1.3 (page 96 ff.) of the EBICS specification 3.0.2.
Option | Description |
---|---|
Service name | 3-digit abbreviation of the service name (target system for further processing of the order) |
Area of application | Defines which rules apply to the service. If not specified, a global definition is assumed. Codes: 2-digit ISO country code or 3-digit issuer code (EBICS) |
Service options | Additional option for the service specified above |
Message name | Name of the message, e.g. pain.001 or mt101. National message names (from DK, CFONB or SIC) are also permitted |
News version | Version number of the message type (can be used for ISO 20022 messages) |
Message format | Encoding format of the message (e.g. XML, ASN1, JSON, PDF) |
Message variant | Variant number of the message type (usable for ISO 20022 messages) |
Container format | Defines the container type - External code list from EBICS (start values: XML, ZIP, SVC) |
Description | Clear free text description of the business transaction |
IBAN | Determines for which bank account this configuration may be transferred (see Signature authorizations for upload) |
Type | Determines whether this configuration is to be set up for transfer/upload or for retrieval/download |
Signature class | EBICS signature class stored at the bank for this configuration |