Hi,

I have followed the directions listed here: http://www.datasprings.com/news/blo...b-billing, but I get the error: User authentication failed due to invalid authentication values.

Based on the debug info, it seems like the module is connecting to the production API. Is there any way to test ARB using a test/sandbox account? I don't have a production account yet, but I would like to get this functionality working so that we can just turn it on when we are ready.

Best,
Chris

Hi Chris - Hmm... Yes, I see this here:

http://developer.authorize.net/test.../#userauth

I checked the source code and I do know that it should be logging the specific URL listed when this processes (the web service URL). Can you please test / check this under Admin, Event Viewer? You might need to enabled "DEBUG INFO" you can enable this if you go to Admin, Event Viewer and click "Edit Log Settings" and then add "DEBUG INFO" as an option to appear.

Thanks,

Chad

Hi Chad,

I only have a test account at this point. Here is what the event viewer shows, "Web service url: https://api.authorize.net/soap/v1/Service.asmx". I am assuming that is the production URL. Is there a way to point the module to the test environment? In the module settings, "Test Mode" is checked.

Best, Chris

I should clarify that test mode is checked under Payment Gateway, but not under General settings.

Chad - is there any way to test ARB with a test account?

Hi Chris - After reviewing the code, unfortunately I do not believe that this is possible at this time. We will add this to the list to review/change in the future to allow for the test account. The Authorize.NET ARB was only recently added so we are working on future enhancements related to the module and this feature, apparently this is one of those! I am surprised this has not come up before actually.


Thanks,

Chad

Chad,

Thanks for reviewing the code and letting me know. I will plan to get everything setup as best I can and then test once we get our production account setup. That would be great if the module's code was updated to allow a connection the sandbox with ARB.

Kind Regards,
Chris