Jump to content

authorize aim module problem?


Recommended Posts

Chrome & Firefox

Error, please verify the card information

 

IE9

Authorize.net returned a malformed response, aborted.

 

 

 

It was working. but i dont know why it stopped.

 

so I did upgrade 1.4.7.3 to 1.4.8.2 but still in problem.

 

 

PrestaShop™ 1.4.8.2

Authorize.net AIM (Advanced Integration Method) v1.3.2 by PrestaShop

 

correct Login ID , Key for Authorize AIM

Billing Address and Everything match

SSL Works

 

 

Please help

Edited by kkim (see edit history)
Link to comment
Share on other sites

Hi kkim,

What sort of changes have you made to your site recently leading up to this error? Additionally, you're actually using an outdated version of the Authorize.net module. The latest version, which you can download here, is actually version 1.4.2.

 

I hope this helps.

 

-Mike

Link to comment
Share on other sites

Hi kkim,

This is merely Authorize.net's default error message that the transaction was refused. Please make sure you are using your Production credentials in Production mode (you should have both Production and Sandbox credentials; don't mix them up!).

 

Also, please try re-entering the credentials by hand rather than copy-paste. We've seen the occasional pasting error cause issues in the past.

 

If that does not resolve this, you will want to check directly with Authorize.net. Their error logs should be able to provide more information.

 

I hope this helps.

 

-Mike

Link to comment
Share on other sites

After getting unclear complaints from users today, we upgraded the authorizeaim module from 1.3.2 to 1.4.2 and this problem is persistent even after deleting uninstalling, reinstalling, changing credentials etc...

 

Other payment modules work!

Link to comment
Share on other sites

I reverted back to authorize aim v1.3.2 and functionality returned.

 

Mike, please note that the similarities between our cases are:

 

1. We both upgraded from 1.4.7.3 to 1.4.8.2 wit authorize aim v1.3.2 installed and running.

 

2. My module maintained functionality while Kim's did not.

 

3. I updated the module after some complaints (that I now believe were user error) to v1.4.2 and ended up with the same error as Kim.

 

4. I disabled -> uninstalled -> deleted v1.4.2 and uploaded the old version from a backup I had.

 

I am back in business. I will follow this thread to see when I can upgrade. I also wonder if you will add functionality for the CIM feature of Authorize.net???

Link to comment
Share on other sites

  • 2 years later...
×
×
  • Create New...