At no time you assumed that it could be a failure of Digital River, maybe they have a "perfect" system. I´ll have to contact them to apply and share this infallible system in my company.
That's your problem, you are assuming things, without even trying my suggestion:
Have you ASKED you YOUR CC issue WHY the transaction from Digital River has been denied ? What was their reply about *that* particular transaction, which I assure you HAS been logged ?
In my opinion it was a Digital River glitch
Keyword here "in my opinion". Until you do what I suggested several times by now, you don't have all the facts form a correct opinion.
But that's besides the point, really.
Assuming it WAS a "Digital River glitch" that happened in a specific case. SO WHAT ? It's not as if we are the only weirdos using Digital River, it's just the largest ecommerce provider in the world, it's a company traded on Nasdaq, and as they used to say back in the day, nobody should be fired for having chosen Digital River, even if the original was referring to IBM...
I hope you are not trying to say we should switch to a different ecommerce EACH time they have a glitch, or that you can say in good faith you can guarantee there's another payment provider out there that has NO GLITCHES, EVER.
Don't want to sound patronizing, but you asked for it:
- Early June, I was in the US for the Flight Sim Expo in Orlando so, obviously, when the Expo ended, I went with the wife and kids to visit the Kennedy Space Center. And guess what, my Credit Card, which is a VISA Business Gold, was rejected twice in two different shops, and of course, when I called my bank, they said "everything's fine".
That same Credit Card worked fine the day *before*, and the same Credit Card worked fine *after*. So yes, it must have been a "glitch" in both those shops.
Should I have made a scene of it in the middle of the Kennedy Space Center, to complain with the shop owner it's their fault for having chosen their payment provider, and my Credit Card was working fine before, and worked fine after ? SHOULD I ?
The topic is now locked.