I had a call today.
The site was training a new server last night but instead of using a training login they used a live one.
I have no idea why outside of sheer stupidity they decided to rung up 10,000,000 190 pound prime ribs (for cookouts etc.).
That's a grand total of about $41,000,000,000 ($41 billion).
Normally that's OK if you void the check, delete the items, etc,, but no, they left the check all night so at end of day (where the system processes all the sales) it closes all open checks out to cash.
So, their deposit is now about $41 billion short.
* edit - that's $41 billion after taxes.
Oh, and going back to a previous day and editing that out is nearly impossible (fraud prevention).
The site was training a new server last night but instead of using a training login they used a live one.
I have no idea why outside of sheer stupidity they decided to rung up 10,000,000 190 pound prime ribs (for cookouts etc.).
That's a grand total of about $41,000,000,000 ($41 billion).
Normally that's OK if you void the check, delete the items, etc,, but no, they left the check all night so at end of day (where the system processes all the sales) it closes all open checks out to cash.
So, their deposit is now about $41 billion short.
* edit - that's $41 billion after taxes.

Oh, and going back to a previous day and editing that out is nearly impossible (fraud prevention).


I AM the evil bastard!
She reported this, and they corrected the problem - by reversing the transaction. Slight problem - when they reversed the transaction, HER pay was taken out of her account at the same time the other people's pay was. Needless to say, this resulted in a number of automatic debits bouncing. Bank didn't want to refund the NSF charges that resulted from their error.
Comment