A large proportion of the data that I get from a bank computer as a corporate client relates to an account. But how can I control, already at the point of access, which of my employees can obtain which bank statements for this data? Controls on the bank’s side can be helpful here. Continue reading
Since 1995, corporate customers in Germany have handled payment transactions securely with every bank via a standard product and an electronic signature.
Already in 2003, the enhancement of the DFÜ Agreement was initiated by an internet-based version This variant of the DFÜ procedure was called EBICS “Electronic Banking Internet Communication Standard”. With this extension, the German banking industry met the requirement of customers and institutes for internet-based solutions in electronic banking.
In the “EBICS – a European standard for mobile payments” series, we will examine the situation in France.
A mobile solution allowing all users to sign for transactions remotely – in compliance with the EBICS TS protocol – would satisfy the requirements of the increasing number of “nomadic” signatories who are hoping that mobile banking with EBICS will soon finally become a reality.
European inter-bank payment transactions move several trillion euros a day. This gigantic volume is processed bilaterally via national and European clearers such as TARGET2, STEP2 and SEPA-Clearer. The unobstructed flow of money is essential for the economy and for our entire way of life. For this reason, the IT systems involved are highly security-critical. Only the redundant use of the two transport protocols EBICS and SWIFT provides the necessary high-availability transport.
With all the developments currently taking place in mobile payments, it’s easy to get lost. New solution providers are almost sprouting like mushrooms and there’s a whole maze of technical standards. In a growing field of business, banks risk being left behind. Could a European standard such as EBICS be an answer?
Do you have any idea how many versions of EBICS are available? Do you know the status of your EBICS client? Which versions does the banking server allow? This article summarises the situation and explains how a proliferation of versions affects users.
It is actually undisputed that EBICS will establish itself as a transaction banking protocol in Switzerland. Major banks and larger cantonal banks already offer EBICS or are in the process of implementing an EBICS interface for their business customers. The next step would be a shared-use “EBICS as a service” platform, for which there is currently no provider.
The EBICS standard is currently gaining ground in Europe. That’s why experts are also taking an interest in the financial centre, Luxembourg. Payment transaction experts from the field and IT departments of Luxembourg banks met there on 28th January 2015 to learn more about EBICS. They had been invited to the event, entitled “EBICS – A New Communication Protocol for Payment Activities”, by the Luxembourg banking association, ABBL.
On the initiative of large French banks (BPCE, CM-CIC, Société Générale, BNP Paribas, Crédit Agricole), SEPAmail™ has been designed to facilitate electronic exchanges between economic institutions of non-accounting documents for payments such as invoices, mandates, advices etc., using flows. This secure messaging system between banks therefore allows traditional payment operations (transfers, debits, etc.) to be carried out with new payment services geared towards client use.
Is it really true that the requirements for corporate clients in e-banking are only geared towards file-based data exchange? Or are on-line administrative operations also affected? Why else do small corporate clients in particular often use e-banking solutions which are designed for private costumers?