It’s Monday – start of a new business week. I started out getting myself organized for the week, and was doing pretty good. That is, until I visited the website of my favorite paper supplier to purchase more paper stock for some upcoming print work I need to get done. I went through their process of ordering – and then hit the checkout. I figured, in a few minutes, I’d have ordered what I needed – - and then check that off my list so I could move on to the next order of business for the day.
That is – until my card, which is tied to my bank account, was declined. Don’t you hate that feeling? Though, I have to say – it’s much better to have that happen when shopping online, rather than standing in line at the local grocery when there are 20 people waiting in line behind you. Either way, though, it really bites. Problem is. . I know what my balance is in that account, so I knew it wasn’t a balance issue. It had to be something else. I tried the checkout again – making sure I typed all the numbers and information in correctly this time and hit Submit.
Declined. Thanks for playing . . .
I immediately got on the phone with a rep. from Wells Fargo to find out what was going on. They pulled up my account and told me that there have been at least 50 transactions on that card – - all originating from France. All 50 of those transactions were for $0.03 (3 cents). The rep. said that whenever they see transactions like that – - they assume that someone has gotten ahold of my card and are trying different security codes until they find the one that works. Except, Wells Fargo shut down the card after the very FIRST 3 cent transaction from France. They didn’t wait for a second one – - they figured I would call when I found that I was unable to use my card.
Call, I did. Within 5 minutes – the card was cancelled and they are issuing me a new one that I should have in 4-5 days. While having to change all of my accounts that use that card will be a pain in the butt – - I am forever grateful that Wells Fargo is so tight with their banking security.
This isn’t the first time I’ve had that card shut down. The first time was in 2006 when Chris and I were in New York – the week of our wedding. I was using that card to pay for the caterer, tuxedo rentals, wedding cake and other various odds and ends. Because the amount of the purchases were so high, originating from a state I don’t normally use the card in – - it triggered Wells Fargo’s security and they suspended the card. A quick phone call to them was all it took to release it. It happened again when were were out of the country (in Bonaire) on our honeymoon…because the purchases were originating from outside the US – again, it triggered the security and the card got suspended.
Now, in those last two cases – I will admit it was really a pain. Especially during the week of wedding preparation – - we were on very limited time to get ready for the wedding, and running around New York City trying to get everything done wasn’t very easy. So, to have my card declined at the bakery when I had a meeting with the caterer in less than 20 minutes across town….yea, pain in the butt!
However – I would much, much rather Wells Fargo have a very tight secure system. I would much rather they err on the side of caution each and every single time there is a question – - rather than to find out that my account has been drained by some lowlife.
So – thank you, Wells Fargo. Happy Monday!