Has anyone gotten the osCommerce authorize.net module to work? I’ve tried using the built-in one, and constantly get a user-id error, though it’s a test account we just set up and it’s a copy and paste of the id. I’ve also been trying to get the AIM module working. It seems to talk to the server, but a blank error is returned.
Any ideas on this or has anyone gotten this to work with a test account so we can see it in action before making it live?
How I understand it, it posts like 20+ variables as well as a user id and transaction key to either test.authorize.net or secure.authorize.net. However, it keeps getting an invalid user id or account not active, which we’ve verified multiple times to no avail. I’m also working with authorize.net support but want to cover both sides to try to get this resolved as quickly as possible for my customer.
The authorize.net guy is stating that our server isn’t hitting his server, or that the http_referrer is a long string instead of just the domain. Does anyone know where that variable is set? He states that their servers will reject a false looking referrer.
They gave me their developer php_aim.php code to try, which basically bypasses osCommerce completely. When running this, it basically appears that our side (the jodohost web servers with my site) is not getting out and talking to their side (test/secure/developer.authorize.net). Stephen, can you see any reason why it wouldn’t be able to connect out to their servers to complete this transaction?
And some more information, testing with their ASP test code, it works. So there definitely seems to be an issue with the windows side php/cURL that isn’t working to initiate the SSL connection back to their servers. Any ideas?
Ok, hopefully this is the last post before someone else can post
The Authorize.net tech stated that the issue is definitely with the php/cURL side on our server. He asked if we could recompile CURL and PHP to see if that would work. I don’t know if that can be done on the windows side or not, but that seems to be the next logical step.