WaMu-Chase account conversion creates yet another security hole
A new twist on a problem Chase has had converting accounts from WaMu over to Chase. We previously reported on a woman whose account was combined with that of her ex-boyfriend of a decade prior when it was converted over to Chase; she had a very hard time getting the problem corrected.
This story involves a business account where an ex-partner was previously removed from the account but the transition to Chase added him back such that the ex-partners email become the primary email contact for the account. Following Chase’s advice to the letter didn’t solve the problem and as of yet, Chase has been unable to fix it, while sensitive personal and business information continues to be emailed to the ex-partner.
I’ve said it before and I’ll scream it again; Chase doesn’t seem to be very good at the small details.
A few years ago I had a business account with an old business partner. This account was with WaMu and came through to Chase along with my personal accounts. Though the partner left the company a couple years ago and was removed from the account his information was apparently migrated from WaMu to Chase.
I setup one of Chase’s online features – account alerts. I get a daily summary of account activity every morning and alerts when certain things happen. Things like purchases, transfers or deposits over thresholds I set.
A few months ago I logged into the Chase online account manager and noticed on the home page the e-mail address of the old business partner was listed as the primary e-mail address for my accounts. I reported this to Chase online customer service. They sent me instructions on how to change it; which I did right away. Problem solved, right? Wrong.
About 5 weeks later the e-mail address came back. I changed it again. A few weeks later it came back. Now you understand why I am spending my time writing about this.
I called Chase online and they gave me some additional steps (disable your alerts, change the e-mail, setup my alerts again). The problem continued.
I got my branch involved. They had me change it at the branch on their computer. Still not fixed. Then it got worse.
Ineptitude | admin July 28, 2010
