Re: AW: [PEAR-DEV] Validate_DE

On 21 Oct 2003 at 12:18, Hartmut Holzgraefe wrote: > Stephan Schmidt wrote: > >>>- bankcode (only format) > > > > I think this will make the whole thing quite complex... > > You will later have 5 small classes for 5 simple methods. > > I'm not sure if this will be useful... > > german "Bundesbank" publishes and regulary updates a list of > algorithms that can be used to verify that a bank code and > an account number are a plausible combination > > the list includes the algorithms in use by german banks > (about 90 afair) and which bank uses which algorithm > (based on bankcode ranges afaik) > > and yes, this is *very* usefull as it helps you to detect > typos (for real customers) and to identify fake data That's what I thought of, yeah. So we would already need a to grab- and-cache the bankcode-list every few month (which is okay imho) - and would benefit from it because we're also able to check if a certain bankaccount-number is okay. For Germany please note: The "Bundesbank" told me there are some rare circumstances under which accountnumbers don't conform with their appropriate checking-algorithms for that bank. This is due to historical reasons and will not change in the near future. I heard in other countries you can easily judge if the accountnumber is okay or not by using the algo. Here in Germany you can just ask the user to check again the number he entered - but if he confirms again you MUST accept the number as he entered it - demanded by the "Bundesbank"! So for a general interface to support accountnumber-checks for German, Swiss, Austria etc. we would need a three-way-logic meaning "number valid, number invalid, recheck number". And this was a step I planed on integrating in Validate-Finance under DE.php - with advanced bankcode-checks and even accountnumber-checks. imho this would be very helpful for some projects I've been working on up to now. Stefan