-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NL13TEST0123456789 is validated true #139
Comments
The extra check runs against any valid banks in the country. Is this valid BICs? I would advise against adding checks that blocks users from using new/unknown banks, as there might not have been time to update before such accounts starts to be used. |
I am not sure if I got you right :) but I would appreciate if that could be an optional extra check (so the consumer could have the decision about validating strict - even on BBAN level - or not). |
Bank code (and or branch) validation is currently not part of IbanNet, as I do not have access to a comprehensive list of BIC's or bank code abbreviations (nor do I have the capacity to maintain such a list for accuracy). And as @NiKiZe points out, technically it is not relevant to IBAN validation, but to BBAN validation. So rather, it is not really a bug, just a missing feature. Besides getting this list there's a few options:
IbanNet also does not perform BBAN check digit validation for similar reasons, as I outlined here: I'd be happy to facilitate but am a bit stuck to progress on this on my own. |
Describe the bug
iban
NL13TEST0123456789
is validated as valid but actually is not - I think it might fit the rulesets but...--
To Reproduce
Expected behavior
IsValid == false
IbanNet library/version
.NET runtime
Operating system
The text was updated successfully, but these errors were encountered: