It is, without a doubt, a "stuck on server" error. These do happen, and CS cannot see them, and will report them as having been "processed".
This "x to y business days to appear" is BULLSHIT Neteller and Moneybookers simply DO NOT WORK LIKE THIS.
As soon as the request to transfer is actually RECEIVED by Moneybookers or Neteller from Inexia (the JF processor), the appearance of funds in the player's account is INSTANT (the speed it takes the computer at Moneybookers to execute the instruction, likely under one second.
The "stuck on server" error is when the instruction to "process" is generated, but is never received by the eWallet. SHOCKINGLY, JF have NO WARNING system in place to detect such failures, the ONLY option is to badger away at CS, and turn the heat up bit by bit, swear if necessary if they continue to spew the bullshit, until they sort it.
How to I know all this,
I suffered this REPEATEDLY over a period of months, and then complained to eCogra. It turned out that a series of errors were occurring within the JF group's processor, and they were simply "fobbing off" the complainant because as far as they were concerned, they submitted the process batch, and it was therefore "done", and the fault was with the eWallet.
There is a simple way to diagnose this though, on the FIRST call, low heat, but INSIST on being told the return transaction codes that you NEED to take this up with Moneybookers. The diagnosis of the above is proven if CS see the payment as "processed", but cannot retrieve the codes from the system. These codes will be confirmation from the eWallet that the transactions have been received and actioned.
IF you can get these codes, THEN put the blame on Moneybookers, give the codes and ask for an investigation.
I once had a "stuck" transaction for THIRTEEN DAYS - and EACH DAY I was fobbed off, and one can only imagine the kind of pressure, impolite, but necessary, it took for someone to actually get their ass over and investigate properly. It was this incident that finally lead to me asking eCogra to launch a formal investigation, and how I found out just how "shaky" their processor can be at times.
They have had AMPLE time to sort this issue out, yet have just dished out the same BULLSHIT to Edward.
About time someone got a PROGRAMMER in to implement a failed transaction "trap" into the systems that gives a near IMMEDIATE warning to the staff, so that a PROPER "excuse" can be passed to the player in the event that the system isn't so efficient the player doesn't even get to notice anything went wrong to start with.
32Red seem to have NO PROBLEM keeping "cashcheck" up to date, so I suspect this is yet more deflection of blame from the casinos to Microgaming. Likely it is the processor that hangs around before updating the cashcheck databases held at Microgaming that players use to check histories.
Empty Fruities Astern Capt'n
Back to port for unloading.
Full Sails - before we get raided ourselves.
LinkBack URL
About LinkBacks
Reply With Quote
Originally Posted by Jasminebed
Bookmarks