Note: OpenHBCI is now outdated and no longer maintained. The successor of OpenHBCI is the library family AqBanking/AqHBCI, written by the same authors as the successful OpenHBCI library, released since August 2004. Please go to AqBanking for more information.
The following information refers to the old, unmaintained OpenHBCI library:
OpenHBCI supports almost all features needed for the account management of a home user. OpenHBCI supports almost all HBCI 2.01 and 2.1 functionality and the majority of HBCI 2.2 functionality. In particular, the following account actions (Geschäftsvorfälle) are supported by OpenHBCI:
If you are interested in the API structure for C++ and C: Here is an online version of the API documentation as generated from the source code.
Banks successfully in use
OpenHBCI is successfully in use with the following banks (but a much more exhaustive list is maintained on the LinuxWiki OpenHBCI Page, in German):
Banks that are known to be unsupported
For the following banks, it is known that OpenHBCI cannot support them (reasons below):
Complete account actions for the home user. Add more actions for the small business case. Add more actions from HBCI 2.2 like stock trading and investment accounts.
Supported Crypto Modes
The very latest HBCI version from November 2002, HBCI 3.0 (also called FinTS, Financial Transaction Services), defines the following means of authentification and/or encryption:
OpenHBCI currently supports DDV-chipcard and RDH-floppy/file.
The ZKA signature card in HBCI 3.0 would be a replacement for the authentification through older methods. These have not yet been implemented in OpenHBCI since none of the current developers has the necessary devices.
The PIN/TAN authentification over SSL is not yet implemented in OpenHBCI. The current developers lack the time to work on this new part of the specification -- so if you happen to be interested in working on this protocol part, please contact the developers.