php-iban

Still better is grouped alphanumeric without potentially ambiguous characters (ie. generate number-1's but not letter-I's, generate number-0's but not letter-O's). I wrote a disambiguation library based upon the checksums present in IBAN @ https://github.com/globalcitizen/php-iban .. it's surprising how accurate the mistranscription suggestions are. In general, pure-number systems are better if possible, but where you have issues squashing in enough data in suitably compact form, transitioning to alphanumeric is better. You can also consider the use prefix-based systems, either utilizing temporal epochs or node-specific prefixes, both of which can utilize readable aliases. Finally, for anything expecting human transcription, checksum systems are awesome!

The correct solution to a transcription error is a checksum algorithm. See for example the implementation I made for reverse-searching incorrect IBAN from a liberal list of probable transcription errors @ https://github.com/globalcitizen/php-iban/ .. it's very fast, cheap and accurate.

Just yesterday I found myself reverse engineering checksum algorithms in various domestic bank account systems about the world. https://github.com/globalcitizen/php-iban/issues/39 I went for an explanation of some of the newer ones I hadn't heard of before (Damm) and it was painful. (The code was only a few lines, though!) While some algorithms had a pre-existing implementation, wiser than rewriting I simply nabbed them and evaluated. Most of the implementations were unreadable/undocumented and of dubious origin, many of the implementations claiming to provide the same algorithm delivered different results. Some of these work for some countries, some for others. No idea where the differences lie and not enough interest to bother finding out. Then of course there's the origin of these 'standards', ISO, who insist on charging 88CHF for a 5