This is where we report on current milestones in the development of the EBICS standard and further technical topics in the context of EBICS.
Some new codes for services were defined, e.g. in anticipation of current projects a code for Request to Pay. You can find the updated code list under Specification.
Initially created as a real-time notification service for the receipt of SCT inst the new concept "Real-Time Notifications" which is based on the WebSocket protocol offers further added value for EBICS users.
The new specification is no part of the EBICS standard and EBICS does not necessarily require this function. EBICS-Client and WebSocket-Client are systemically separated from each other.
However, this the concept is an ideal supplement to the EBICS procedure.
EBICS has been used for many years in bank-bank communication (especially with CSMs). In order to enable the clearing of instant payments according to the SCTinst regulations of the European Payments Council EBICS a delta document was created which fulfils the necessary performance and security requirements. The delta document is applicable within the framework of EBICS V 3.0, but is only permitted for the scenario described. The delta document can be found under Specification.
During the implementation of EBICS V 3.0 an obvious mistake in the EBICS specification was noticed. Details can be found under Maintain&Advance...
An extended version of the Common Implementation Guide was published - already taking into consideration first implementation experience for EBICS V 3.0 - you can download it on Implementation Guide.
Change Requests for the next EBICS version (specification and the corresponding Implementation Guide as well) came up. The approved CRs can be found on Passed CRs. Please note that most of the CRs are clarifications and can already be considered now.
In the external BTF code list new service names and some rules for service options were added. The current version can be downloaded on EBICS specification...