Since this version uses the website to get account info,
it will need the information to login: There are two ways to login via the wachovia website,
and depending on which login method you use,
that decides which parameters you'll provide to the new() method.
If you use the Customer access number method (left form on the website) then provide "customer_access_number",
"pin",
and "code_word".
If you use the user id method (right form on the website) then provide "user_id" and "password".

Internally uses WWW::Mechanize to scrape the bank's website. The idea was to keep the interface as logical as possible. The user is completely abstracted from how the data is obtained, and to a large degree so is the module itself. In case wachovia ever offers an XML interface, or soap, or DBI (right) this should be an easy module to add to/modify, but the application interface will not change, so YOUR code won't have to either.

Returns object Finance::Bank::Wachovia object. This is when you should define your login information. There are currently two login methods, the 3 argument "can/pin/codeword" method, and the two argument "user_id/password" method. Which one you need to use depends on how you login to your account via the wachovia website.

Returns a Finance::Bank::Wachovia::Account object OR a Finance::Bank::Wachovia::Credit object. Currently the module looks at the length of the account number to decide whether you are retrieving a credit account object or a regular (savings/checkings) account object. Both the Credit and Account classes have some common attributes: name, type, number. You can use the type to figure out what kind of account you have, OR you can just look at the ref() of the object (better, since type can be unclear (like "mbna")).

Doug Feuerbach had the idea for storing login information in an encrypted file to be accessed via a password (like apple's keychain). Then he gave me the code to implement it. He thinks it's silly to thank him for something "so trivial", but he should know that it's not an official perl module without a "thanks" going out to someone by name. The program included with the module makes use of his contribution. Thanks Doug.

Also, thanks to the Giants that authored all the modules that made the conception and creation of this module so easy. Your shoulder's are awesome.

Where would we all be without Perl? Checking our account balances over the phone, that's where. Thanks to Larry Wall.

Thanks to Jason Marcell for helping me test/debug the user_id/password login in a pretty short amount of time.