Gathering detailed insights and metrics for bankdata-germany
Gathering detailed insights and metrics for bankdata-germany
Gathering detailed insights and metrics for bankdata-germany
Gathering detailed insights and metrics for bankdata-germany
npm install bankdata-germany
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
7 Stars
36 Commits
1 Forks
1 Watching
2 Branches
2 Contributors
Updated on 21 Nov 2024
TypeScript (94.21%)
JavaScript (5.54%)
Shell (0.25%)
Cumulative downloads
Total Downloads
Last day
-20%
200
Compared to previous day
Last week
-20.6%
807
Compared to previous week
Last month
116%
2,464
Compared to previous month
Last year
250.1%
12,735
Compared to previous year
22
This TypeScript/JavaScript library contains bank data for German banks, such as names and BIC/SWIFT codes. You can use it (for example) to enhance user interfaces/forms, where a user enters an IBAN and you automatically fill out the bank name and BIC fields.
This library is not an IBAN validator itself. If you require validation, please refer to the main project. IBANTools-Germany.
Version 1.2403.* includes data from 2024-09-09 to 2024-12-08, as well as from 2024-12-09 to 2025-03-02. Validation will be based on the data that is valid according to your system time (data changes at midnight CET on 2024-12-09).
Add it to your project using a package manager like npm or yarn. You should explicitly install the latest version, as the bank data may change multiple times a year.
1$ npm install --save bankdata-germany@latest 2# or 3$ yarn add bankdata-germany@latest
If you only want the functions in your browser, you can include the following pre-built file.
1<script src="https://cdn.jsdelivr.net/npm/bankdata-germany/dist/build/browser.js"></script>
The npm package contains the code for both ESM and CJS. Therefore, in addition
to using import
as shown in the usage examples below, you can also utilize
require
.
You can retrieve detailed information for a bank using BLZ, BBAN, or IBAN.
Note: When using the BBAN/IBAN function, no verification will be performed. It solely extracts the BLZ and verifies its existence.
1import { bankDataByBLZ, bankDataByBIC, bankDataByBBAN, bankDataByIBAN } from "bankdata-germany" 2 3bankDataByBLZ("10010010"); 4bankDataByBIC("PBNKDEFFXXX"); 5bankDataByBBAN("100100100000138301"); 6bankDataByIBAN("DE48100100100000138301"); 7// { 8// bankName: "Postbank Ndl der Deutsche Bank", 9// bic: "PBNKDEFFXXX", 10// blz: "10010010" 11// }
You can validate BIC/SWIFT codes. However, despite these formats being international standards, this library exclusively validates data for Germany and will return "false" for all other countries.
1import { isValidBIC } from "bankdata-germany" 2 3isValidBIC("MARKDEFF"); // true 4isValidBIC("MARKDEFFXXX"); // true 5isValidBIC("foobar"); // false (invalid format) 6isValidBIC("BNPAFRPH"); // false (corrent but not a German BIC)
When using the pre-built version, the bankdataGermany
object is globally
defined on the window
, containing the functions.
1bankdataGermany.bankDataByBLZ("10010010"); 2bankdataGermany.bankDataByBIC("PBNKDEFFXXX"); 3bankdataGermany.bankDataByBBAN("100100100000138301"); 4bankdataGermany.bankDataByIBAN("DE48100100100000138301"); 5bankdataGermany.isValidBIC("MARKDEFF");
Bank data is sourced from the official website of Deutsche Bundesbank which publishes updated data every quarter.
These updates can encompass both technical changes, such as modifications in check digit methods, as well as content changes like alterations to BLZ, bank names, and more. Some updates might not contain any relevant changes for this library at all.
The version numbers are based on Semantic Versioning with some modifications.
1.2205.3
The first number represents the Major version. If this number increases, there may be updates that are not backward compatible, requiring adjustments to your code. In the above version string, the major version is 1.
The first two digits of the second number indicate the year of the included data and check digit methods. The third and fourth digits increase either with minor version changes that maintain backward compatibility or when new data is included. In the provided version string, the year is 2022, with a few minor updates, possibly including data updates for spring and summer.
The last number is reserved for patches and bug fixes.
Considering that the data could change up to four times a year, it's advisable
to use an appropriate version string in your package.json. As breaking changes
occur only when the first number changes, specifying something like "1.x"
should suffice.
No vulnerabilities found.
No security vulnerabilities found.