Jump to content

Payment Gateways Not Engaging


Recommended Posts

Hi,

Apologies in advance as this will be a bit long.

A bit of background.  I handed the site over to the client and he set up a payment gateway with authorize.net.  However, subsequent tests returned Error 103.  In short, that means that the Transaction Key on the site does not match the one on registered with authorize.net.  For reasons beyond my ken, when I tried to access his account with authorize.net, I was not able to get in.

In response, I suggested that we try a different gateway: simplify commerce by MasterCard.  He set that up and tested it.  However, using their test card numbers failed, returning: "There was a problem with your payment: Request data is invalid"

I followed El Patron's instructions here for turning on error reporting in PrestaShop.  Either I did not follow them correctly, or there were no errors to report.

I then used Chrome's console to search for errors in the site. Here's what was returned.

Upon one page checkout page lod:

The page at 'https://packsofsnacks.com/quick-order' was loaded over HTTPS, but is submitting data to an insecure location at 'http://packsofsnacks.com/search': this content should also be submitted over HTTPS.

quick-order:1 

The page at 'https://packsofsnacks.com/quick-order' was loaded over HTTPS, but is submitting data to an insecure location at 'http://packsofsnacks.com/': this content should also be submitted over HTTPS.

quick-order:2 Uncaught ReferenceError: loadCSS is not definedquick-order:2 (anonymous function)

Upon entering the authorize.net test credit card number, this was the result:

On the page it says:

Error detail from AuthorizeAIM : (TESTMODE) This transaction cannot be accepted.

Chrome reports:

quick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:148 The page at 'https://packsofsnacks.com/quick-order?step=3&cgv=1&aimerror=1&message=%28TESTMODE%29+This+transaction+cannot+be+accepted.' was loaded over HTTPS, but is submitting data to an insecure location at 'http://packsofsnacks.com/search': this content should also be submitted over HTTPS.

quick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:719 The page at 'https://packsofsnacks.com/quick-order?step=3&cgv=1&aimerror=1&message=%28TESTMODE%29+This+transaction+cannot+be+accepted.' was loaded over HTTPS, but is submitting data to an insecure location at 'http://packsofsnacks.com/': this content should also be submitted over HTTPS.

quick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:857 Uncaught ReferenceError: loadCSS is not definedquick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:857 (anonymous function)

Returning to Simplify Commerce by MasterCard, this is what Chrome says:

quick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:148 The page at 'https://packsofsnacks.com/quick-order?step=3&cgv=1&aimerror=1&message=%28TESTMODE%29+This+transaction+cannot+be+accepted.' was loaded over HTTPS, but is submitting data to an insecure location at 'http://packsofsnacks.com/search': this content should also be submitted over HTTPS.

quick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:719 The page at 'https://packsofsnacks.com/quick-order?step=3&cgv=1&aimerror=1&message=%28TESTMODE%29+This+transaction+cannot+be+accepted.' was loaded over HTTPS, but is submitting data to an insecure location at 'http://packsofsnacks.com/': this content should also be submitted over HTTPS.

quick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:857 Uncaught ReferenceError: loadCSS is not definedquick-order?step=3&cgv=1&aimerror=1&message=(TESTMODE)+This+transaction+cannot+be+accepted.:857 (anonymous function)

Limited as my skills are in this area, it looks to me like there is nothing in the shop that is causing these problems.  However, I would readily accept any comments-critiques to the contrary.

My current belief is that there is a problem in the way that the server, godaddy.com, is set up, given that two different payment gateways have failed.

My most sincere appreciation to any and all comments-suggestions-help on this matter.

Link to comment
Share on other sites

  • 8 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...