Garreth,
That is my email above, which I actually took some time to write because I wanted to be fair. I also want to be logical.
To be fair, you obviously have so many tickets URSAY was unable to recall the order information in detail I posted just a couple pages before the one where he says I provide no meaningful information. That is not to mention the numerous emails (at first) to make sure everything is logged, and then a PM to him directly with the same information. So I get that you all are effing slammed.
But you keep leading us to believe it will be "just any second." It's been 4/5 days now. I could have already been refunded and bought btc from you again already.... now that it works.
1. You have my MT GOX account number.
2. At least two transfers are logged on BI.com since I am registered. There is no searching or finding the trxn like the guest transfers.
3. You have Mt. Gox funds at your disposal.
4. I don't care if you cancel, amend, refund and reissue, WHATEVER you need to do to make sure you Mt. Gox account sends money to my Mt. Gox account is really all we care about.
5. I think when you say manually, we assume that means its a workaround and that means it will work. it hasn't. When i say manually I mean you literally log into Mt. Gox with you username and password and start transferring funds immediately. MANUALLY.
Yes, i know it will mess up your accounting and the system issues must be addressed. But you are underestimating the impact that some of these transactions are now having on our personal lives. Your personal life is bitinstant.... so its different for you. For us, bitinstant has BECOME our life for a week where we are spending literally hours a day......
you all could have handled, and still could handle this in a way that would have minimized damage. you have done almost every single thing wrong so far, except show up here. even though no one is getting helped, you are here.
The problem is that messing up our accounting endangers our ability to comply with regulations and thus risks the whole company - we have to ensure transactions are logged properly in case of audits or whatever.
For what it's worth here's an update:
We have a batch of 127 orders (out of 2106 zipzap payments) which are having issues, it seems most of them are failing due to invalid addresses caused by whitespace and after fixing the formatting some of these are executing UNLESS they have already auto-retried the maximum number of times, in which case they're failing again. To resolve this our dev team is working on a patch so that all these orders can be batch processed correctly.
The vast majority of outstanding delayed orders are now fixed, and it's only this last batch that's causing so much trouble, but we are all working to get it resolved.
Some customers have been told to wait on coinapult, it turns out that a large proportion of these orders are still failing due to the above mentioned issue with addresses, and this is something that coinapult can address on their end - customer support are now being told to get valid addresses for all outstanding orders and verify them, with the aim being to batch process them no later than sunday.