fints-institute-db is a JavaScript package providing a structured database of German banking institutes, primarily for use with FinTS/HBCI client applications. It contains crucial connection details such as Bankleitzahl (BLZ), Business Identifier Code (BIC), bank name, location, FinTS endpoint URLs (e.g., `pinTanURL`), and supported FinTS protocol versions. The current stable version is 0.16.0. The package typically receives updates as the German banking landscape changes (e.g., mergers, updated FinTS endpoints) or new data becomes available, making its release cadence data-driven. It serves as a static registry, differentiating itself by offering a readily consumable, open-source dataset specifically tailored for integrating with the German FinTS standard.
npm install fints-institute-dbVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to import the bank database, find a specific bank by BLZ, filter banks by organization, and access their properties.
Always review the release notes for new versions for schema changes. Consider adding runtime data validation or using TypeScript with up-to-date type definitions if available.
For mission-critical applications, consider implementing a fallback mechanism, an external endpoint validation service, or a configuration overlay to override potentially outdated URLs.
Assume the overall package version reflects the data freshness. Monitor the package's release frequency and changelog on npm or GitHub for updates to the underlying data.
If a specific bank is missing or has incorrect data, verify against official bank sources or contribute to the project to improve data accuracy.
Run `npm install fints-institute-db` in your project directory. Ensure your module bundler or Node.js environment is configured to find `node_modules`.
Ensure you are using the correct import statement for the default export: `import banks from 'fints-institute-db';` (ESM) or `const banks = require('fints-institute-db');` (CommonJS).Check for `@types/fints-institute-db` or ensure the package's built-in types (if any) are correctly referenced. If the types are genuinely missing or incorrect for a specific field, consider using type assertions (`(bank as any).blz`) or extending the type definitions in your project.
No dependency data recorded yet.