-
Notifications
You must be signed in to change notification settings - Fork 110
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
Add a method to obfuscate IBAN for presentation for relative identification #99
Comments
Thanks for the feature request. I am not completely sure I understand what you mean. An IBAN is a public identifier. To provide any utility at all, it needs to be shared completely. If you are suggesting that only part of an IBAN is shared identification purposes (as credit card numbers are sometimes presented: Generally this is done with credit cards when, for example, the user can store multiple credit cards along with their account and instead of repeating the information the cards are presented for 'relative identification' (which is which) instead of 'absolute identification' (use this for a transaction). The challenge with an IBAN is that all countries' IBAN have different structures. Some of them have greater variation away from the final few digits. This is a good feature request. I will implement it. Thanks. |
I have decided to avoid the checksum digits as they may be used to infer the other digits with knowledge of local banks and branches (some countries have very few valid banks and branches). Therefore, I have decided to implement the obfuscation with only the country code followed by asterisks and the last four characters of the IBAN. |
Here is the sample output (source followed by obfuscated form).
|
Released in version 2.7.4. |
Hello,
I think tere is a missing feature to obfuscate IBAN, to prevent IBAN being stolled, but allow it to be matched.
I use a simple line of code, you could improve it as you better know IBANs, but it's a start :)
Thank for your work!
The text was updated successfully, but these errors were encountered: