Authorize.Net, Processor or Custom Gateway?

[ZLA]

We're trying to switch to a new payment processor. We will still be using Authorize.Net as our gateway. We've tried to configure our test environment with the new merchant login and transaction key. But when we try using it we get various errors:

• When we set the gateway to Production Gateway, Test Mode, we get this error -
  (TESTMODE) This account has not been given the permission(s) required for this request. (123)
• When we set the gateway to Test Gateway, Test Mode, we get this error:
  (TESTMODE) The merchant login ID or password is invalid or the account is inactive. (13)
• When we set the gateway to Test Gateway, Live Mode, we get this error:
  The merchant login ID or password is invalid or the account is inactive.

When we contacted Authorize.Net, we got the following information:

• If you are posting your transaction requests to the gateway URLs https://test.authorize.net/gateway/transact.dll or https://certification.authorize.net/gat ... ansact.dll and you are using an account given to you by an Authorize.Net Reseller or from Authorize.Net Sales, you may encounter this error. The gateway URLs mentioned above only work with specific test accounts, available upon request by completing the form at http://developer.authorize.net/testaccount/
  
  Try posting your transaction request to https://secure.authorize.net/gateway/transact.dll instead. If you need to submit a test transaction, you may do so by setting the field x_test_request to "TRUE". You may then remove x_test_request or set it to "FALSE" when you have completed your testing.
  
  Note: If you are integrating your website with Advanced Integration Method (AIM) using PHP, please be aware that the gateway URL is listed twice--once in the cURL configuration, and once again in the main body of the code. Using the test gateway URL in the cURL section of the code will create an Error 13 as cURL would connect to the incorrect server.
• Please check your script and verify you are posting the API Login ID for the account in question. If you are not posting the correct API Login ID, please edit the script and confirm that the field x_login is set to the API Login ID that you may obtain from the Authorize.Net Merchant Interface. Please see the Merchant Integration Guide at http://www.authorize.net/support/merchant_guide.pdf for instructions on obtaining the API Login ID. For further information on the API Login ID, Transaction Key, or Test Mode, please check out our online video tutorials at http://www.authorize.net/videos/.
• If you are unable to log into the Authorize.Net Merchant Interface, this could indicate that your account is inactive. If this is the case please contact us directly to reactivate the account. You can reach us toll-free at 877-447-3938. We will be happy to assist you at that time.
• If the account is active and the API Login ID is correct, you will want to use the Data Validation URL to see which variables are being passed. For more details, please visit http://developer.authorize.net/tools/datavalidation/*]

I assume most of their response is stuff that AC7 is already taking care of behind the scenes.

Can someone tell me what I need to do to test out our gateway credentials for the new processor? Or at least suggest who I need to contact (authorize.net or the processor)?

Thank you.

[plugables]

If AbleCommerce implementation of Authorize.NET needs to send data to a different URL then the one it is currently sending then the only way for you to tackle it is to create your own custom gateway for Authorize.NET using the AbleCommerce's code for Authorize.NET that they have made available as a reference.
ftp://ftp.ablecommerce.com/evals/AuthorizeNet.zip

This may also be helpful http://wiki.ablecommerce.com/index.php/ ... nt_Gateway

[hautebox]

Plugables,

That wiki link is not very informative.

The zip file is more insightful, but not entirely clear. I posted a new topic related to many providers that have auth.net emulators (ie. they just change the url that is being called).

I was able to open many of the files with notepad ++ and look around.

However, it does indicate in the wiki that a new dll needs to be compiled...how does that take place...and where exactly are those urls...i see a few in various parts of the code, but its not well documented.

Any insight.

Thanks in advance

[AbleMods]

The URL's for Authorize.Net are hard-coded into the AbleCommerce ANet gateway code. There's no way to modify just the URL and use the existing gateway written by AbleCommerce.

The easiest thing to do is buy full source code and modify the Authorize.Net payment gateway written by AbleCommerce to use the new URL's. Then recompile the gateway using Visual Studio Professional or above. That way you're not reinventing the wheel.

Not ideal from a cost perspective, it's a lot of money just to change a URL. But at least the bulk of the hard work in the gateway itself is already done.