# Changelog of IBAN Validator & Bank Enricher – Bulk IBAN API (`lwsdjfls/iban-validator-enricher`) Actor

- **URL**: https://apify.com/lwsdjfls/iban-validator-enricher/changelog.md
- **Full Actor documentation**: https://apify.com/lwsdjfls/iban-validator-enricher.md

## Changelog

### 0.1 – 2026-09-17

- Initial release: offline validation of IBANs from all 89 countries and territories in the Swift IBAN Registry (TXT edition, read on 15 September 2026), with the ISO 13616 mod-97 check digits, the length and the national BBAN format of each country. The 16 territories that use another country's format (the French overseas departments and collectivities, the Crown dependencies, Åland) are validated with that country's format.
- Bank code, branch code and account number split as the registry defines them per country; bank name and BIC from the Bundesbank's Bankleitzahlendatei (Germany, 3,432 codes, complete), the National Bank of Belgium's list of bank identification codes (Belgium, 782 codes, complete) and a hand-curated list of the major Dutch banks (45 codes). A valid German or Belgian IBAN whose bank code is in neither complete list gets a warning naming the list and its version, because no bank uses that code.
- Up to three suggested corrections for an invalid IBAN of the right length: letter/digit confusions (O/0, I/1, L/1, S/5, B/8, Z/2, G/6), two adjacent characters swapped and corrected check digits, each kept only when it passes both the check digits and the national format, and each with the bank name of the corrected IBAN when a bundled list knows the bank code. Switch them off with `suggestCorrections`.
- Nothing leaves the run and nothing is kept between runs: the registry and the bank lists are bundled with the Actor, so IBANs of natural persons stay in the input, the dataset and the key-value store of your own run.
- One record per distinct IBAN: a duplicate in the same batch is validated and charged once, empty lines are skipped for free, and IBANs above `maxIbansPerRun` or above what the run's memory holds (20,000 below 1 GB of memory, 50,000 below 2 GB) are skipped, named in the log and not charged.