Posted September 16, 2016


(pasting part of my reply to a different thread)
It seems to affect only a handful of users. Some reported that switching to another browser helped, while for one it was persistent across two browsers. Some reported that trying again after a while fixed the problem. Unfortunately the issue only became apparent after regular office hours, our devs did what they could remotely, but they will have to continue the investigation first thing tomorrow morning.
For now, all I can suggest is:
1) try a different browser,
2) try again after some time,
3) use a credit/debit card directly, and avoid using redirect-type payments until this issue is resolved.
We're sorry about the trouble. :(
Are you using a proxy server, by any chance? The issue would affect the same user trying to use paysafecard as well, I'm afraid.
For now it looks like this occurs on a per-user basis. We're gathering as much information as we can, to help with our colleagues' investigation tomorrow morning.
Post edited September 16, 2016 by Firek