If the customer then wishes to connect to another bank which also offers EBICS, they often need a new software version which, in accordance with the procedures just mentioned, will include the configuration specific to the institution. The once customer-friendly setup at once becomes much more complex; who wants to update the entire system each time you connect to a new bank? At this point a configuration-based approach would be desirable, in which the customer can register for themselves the relevant EBICS parameters for the new connection.
If the developer still then charges release fees for these updates, one cannot help feeling that there is profit being made here at the customer's expense from a relatively trivial problem. It is now the role of the banks to provide an overview for all the available solutions and to ensure this information is included in the counselling of clients, when it deals with the question of which EBICS software would be the most suitable for connecting to a specific institution.
For Swiss developers who have not installed an EBICS protocol, here is a final tip: Configuring a new EBICS connection should not be rocket science if it is ensured from the beginning that, for example, the customers themselves will control the process using a dialog window. For the integration of the EBICS protocol, we make reference at this point to the PPI EBICS-kernel (see software modules on the PPI homepage), which provides the full range of EBICS functionality in the form of a software library.
Carsten Miehling
0 comments:
Post a Comment