Interest charged

Gep

Hi all, I've been "stoozing" using borrowed money from Virgin Atlantic MBNA credit card. Everything seemed to go perfectly when just one month before the end of the investment, I made a transaction on the card which made me go over the credit limit for a couple of days (I bought a damn seasonal train ticket!).
Virgin Atlantic immediately cancelled the 0% offer and charged me £400 straight away without notifying me or anything.
I was in good faith since I just thought I had enough credit left to buy the train ticket and anyway why did they authorise the transaction if I didn't have enough credit?
Did this happened to anybody?
Is there anything I can do?
I've called AMEX and they said they can't do anything. Obviously this is how they make money, but isn't it unfair?

YorkshireBoy

Why on earth did you make a purchase on the card? It doesn't have 0% on purchases...only BT's.

You're told in the T&C's what will happen if you breach the T&C's, ie immediate loss of promotional rates.

The general advice (when breaching by paying late) is to call retentions on 0800 783 1116, but going overlimit might be considered more serious?

Gep

I did have 0% on purchases until the end of December, but that's not the point.
The point is that by going over my credit limit (even £1) it instantly invalidates the 0% offer on balance transfer.
I used it because I genuinly believed I had at least another £2000 credit limit left.
I'm really upset because they don't tell you anything. Not only they authorised the transaction that made me go over the limit, but they kept authorising transactions in the following days...
Why should they care? After all they just make lots of money out of these silly mistake.... and unlike most company they don't care about loosing customers (just so you know and you don't waste your time on the phone).

YorkshireBoy

Don't get mad...get even. Stooz another of their cards and get your own back.

Look on the bright side, you won't make the same mistake again!

neas

indeed stupid... card should've been locked away... until end of int free period... tough lesson to learn... but learnt nonetheless.