Try asking your question in English.
Them's fightin' words. Challange accepted.
I would like to be able to use services like Mint or iBank's Direct Access that keep track of all of your financial transactions across different banks. The way they accomplish this is by logging into those bank's websites with your password. This is the same password that allows you to do stuff like transfer money to another bank or send a "bill pay" check to someone. So, by giving Mint your password you are giving them the ability to steal your money. Obviously it wouldn't be in Mint's best interest to steal your money. But they are storing your password in a way that makes it possible for a hacker that gains access to Mint's store of passwords to get your password and steal your money.
Now, this is different from the way that the original bank stores your password (we hope). The best way to implement a login system for a bank or any other website is to store a "hash" of a user's password, but not the password itself. The current best practice changes often and it wouldn't be useful to go into the weeds here, but they best way to think of it is that they transform your password in a way that throws away information from it so it's impossible to ever figure out what the user's real password was. But that transformation is deterministic so if you apply it to the same password over and over you'll always get the same result. So we store that result (the "hash") and when a user attempts to log in we apply that transformation to the password that they just gave and compare the transformed password to the stored transformation in the database.
tl;dr: The bank stores your password in a "secure" way and Mint stores it in an "insecure" way. (There are subtlities that I'm ignoring in that statement)
Now, back to my original question. I'd like to be able to use services like Mint (or write similar software myself) without the security (and financial) risk of having my password stored in an insecure way.
One way to accomplish this would be if the bank allowed me have two passwords: one that gives me full access to all of my money and data and one that only allows me to read the data (i.e. I can't write checks or transfer money). That way if a hacker ever gets that password they will only be able to read the data, never steal anything. As it turns out, Wells Fargo now has this functionality. They call it a "Guest Account".
It surprises me that more banks haven't done this. It seems like it would reduce their liability.
