My European bank (one of the largest in my country) doesn’t accept passwords longer than 8 characters. Imagine how bad the rest of the systems is.
Which leads to funny questions at development time like "how many characters do we reserve in the customer record for the third child of the second wife of customer X, when they're remarried, this third child is not a child of the customer but there does exist an alimentation 'agreement' between the customer and their third wife". You must make this decision knowing that whatever your answer ... it can never be changed again.
>500kb per record. And, of course, mostly it just has first and last name, address, birthdate and balance, nothing else.
Makes the web look efficient.
Of course you can have all your COBOL and your mainframes down below rolling and churning like it's 1975, but the authentication of an app is layers up above in a totally distinct system. Or this or you're crazy.
on edit: actually serious question, have been away from this area for a while but thinking about making a personal project soon.
edit: my experience only applies to UK (which were better and cheaper way before EU) and EU banks, the US is a minefield that actually is better avoided by just paying higher fees to a popular processor rather than deal with banks who think its the 1800s)