Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Issues with Authorize.net AIM version 2.1


Aarjun74

Recommended Posts

Hi,

 

We are using osCommerce Online Merchant v2.3, after the recent change with authorize.net API - credit card payment stopped working - now as suggested on forums we upgraded the authorize.net AIM plugin to 

Version: 2.1 (online status) icon_info.gif API Version: 3.1

 

but it changes nothing - Test mode is working fine - but on live mode we keep getting the error "There has been an error processing your credit card”

we checked with authorize.net there is no transaction id or response code for this transaction - checked with hosting company to see if any port is blocked, which is not. 

 

We are kind of lost. Would appreciate any help in fixing this.

 

Thanks :(  

Link to comment
Share on other sites

They upgraded their certificate in May.  You need to follow these instructions.

http://www.oscommerce.com/forums/topic/407407-authorizenet-changes-causing-problems/?p=1726127

 

I think this is the one I added to ext/modules/authorize.net.crt

-----BEGIN CERTIFICATE-----
MIIDVDCCAjygAwIBAgIDAjRWMA0GCSqGSIb3DQEBBQUAMEIxCzAJBgNVBAYTAlVT
MRYwFAYDVQQKEw1HZW9UcnVzdCBJbmMuMRswGQYDVQQDExJHZW9UcnVzdCBHbG9i
YWwgQ0EwHhcNMDIwNTIxMDQwMDAwWhcNMjIwNTIxMDQwMDAwWjBCMQswCQYDVQQG
EwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjEbMBkGA1UEAxMSR2VvVHJ1c3Qg
R2xvYmFsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2swYYzD9
9BcjGlZ+W988bDjkcbd4kdS8odhM+KhDtgPpTSEHCIjaWC9mOSm9BXiLnTjoBbdq
fnGk5sRgprDvgOSJKA+eJdbtg/OtppHHmMlCGDUUna2YRpIuT8rxh0PBFpVXLVDv
iS2Aelet8u5fa9IAjbkU+BQVNdnARqN7csiRv8lVK83Qlz6cJmTM386DGXHKTubU
1XupGc1V3sjs0l44U+VcT4wt/lAjNvxm5suOpDkZALeVAjmRCw7+OC7RHQWa9k0+
bw8HHa8sHo9gOeL6NlMTOdReJivbPagUvTLrGAMoUgRx5aszPeE4uwc2hGKceeoW
MPRfwCvocWvk+QIDAQABo1MwUTAPBgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBTA
ephojYn7qwVkDBF9qn1luMrMTjAfBgNVHSMEGDAWgBTAephojYn7qwVkDBF9qn1l
uMrMTjANBgkqhkiG9w0BAQUFAAOCAQEANeMpauUvXVSOKVCUn5kaFOSPeCpilKIn
Z57QzxpeR+nBsqTP3UEaBU6bS+5Kb1VSsyShNwrrZHYqLizz/Tt1kL/6cdjHPTfS
tQWVYrmm3ok9Nns4d0iXrKYgjy6myQzCsplFAMfOEVEiIuCl6rYVSAlk6l5PdPcF
PseKUgzbFbS9bZvlxrFUaKnjaZC2mqUPuLk/IH2uSrW4nOQdtqvmlKXBx4Ot2/Un
hw4EbNX/3aBd7YdStysVAq45pmp06drE57xNNB6pXE0zX5IJL4hmXXeXxx12E6nV
5fEWCRE11azbJHFwLJhWC9kXtNHjUStedejV0NxPNO3CBWaAocvmMw==
-----END CERTIFICATE-----

I'm not really a dog.

Link to comment
Share on other sites

  • 3 months later...

The cert here is required to connect to Authorize.net and is not the same as your domain cet.  Add it to ext/modules/authorize.net.crt at the bottom and it won't cause any problems.  However, if you are connecting already without a problem then it's probably covered somewhere else.  You can find more info on this at the forums on Authorize.net.  If you aren't connecting successfully give this a try. 

I'm not really a dog.

Link to comment
Share on other sites

I believe that is the failure to connect error.  Go through your setup and make sure everything is correct.  You mentioned GoDaddy and I don't know if they have CURL enabled by default on their php setups.  I remember seeing some problems with that.  Search for that and check it out.  On your Admin you can look at the server info and see if it shows curl enabled.  If not, that's a problem.

I'm not really a dog.

Link to comment
Share on other sites

  • 4 months later...

That cert I added in my post above works with the live server.   if you have the line below in your authorizenet_cc_aim.php module comment it out and try again.  If you try to use anything below TLS 1.0 it will fail.  php.net recomends leaving it at default.  Or you can set it to a higher setting like 6 if you support TLS 1.2.

        curl_setopt($curl, CURLOPT_SSLVERSION, 3);

I'm not really a dog.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...