|
After Plumadona has some success I thought I'd try my credit card again. At first I had no luck, just got the "There was a problem with your credit card number or security code. Please check that you have provided both numbers and that they match your credit card." message.
I was about to just use the PayPal option, like I normally do, when I thought I'd give their chat support a try. A nice lady got me to try a few things, such as clearing cookies, but that didn't help. Then she asked me to try a different browser. I normally use the Opera browser (have done for years, I just love all the features that come built into it) but I thought I'd humour her and try the Chrome browser.
Wonder of wonders it worked!
Exactly the same credit card info, on the same Kobo account, trying to buy the same ebook. The only difference is using Chrome instead of Opera.
My day job is as a web designer, and I've worked on several shopping sites over the years, so I know how credit card processing companies integrate their cc processing with shopping sites (although I don't have any experience with WorldPay). I'm very surprised that the choice of browser would cause a problem like this, as normally the shopping site talks directly to the cc processor in the background and the browser shouldn't have any interaction with the cc processor (using the model that Kobo is using, there are other ways that involve redirecting the user to the cc processor for secure processing, but Kobo don't appear to be using this method).
I did a bit of Googling but couldn't really find anyone else complaining that the WorldPay service doesn't work in the Opera browser. On WorldPay's own support site they recommend that shopping site owners should test the cc processing on all major browsers, and they give a list that includes Opera.
|