06-17-2014 05:21 AM
We are currently using AIM for CC processing. This is working in our production env.
We want to make a change.
In order to do this, I setup a developer account, so I have a dev API Login and Transaction key.
I am using the same code to process the CC trans in DEV as I am in PROD, no changes yet.
I changed the setup to use the test url for AIM (https://test.authorize.net/gateway/transact.dll), entered my dev login and trans key in the setup, and tried to process a test transaction.
I'm getting error 102 (A password or Transaction Key was submitted with this WebLink request. This is a high security risk.)
I don't understand this response. It looks like the TEST instance of the AIM API behaves differently than the live one?
Solved! Go to Solution.
06-18-2014 04:11 AM - edited 06-18-2014 04:13 AM
I don't have full access to the prod env- so I need to ask the admn to give me the settings - which complicates things.
What settings do you refer to ?
I went through all the setting on the sandbox settings page, but could not find anything that seemed related to the error.
06-18-2014 04:12 AM - edited 06-18-2014 04:12 AM
@Richard: I did see that. However, upgrading the interface is not an option at this point.
And still, if it works in the live environment, it should work in test, right ?