Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Authorize.NET test mode not working. Getting same errors. | Event Espresso - Staging Server
I’m trying to do a couple of test transactions, but it doesn’t seem to be working. I have the merchant account set to TEST MODE, but when I try to complete the transaction with any of the credit card numbers EE provided I keep getting these errors. The AIM settings are set to – Account Uses Authorize.net development Server as well.
The merchant login ID or password is invalid or the account is inactive.
Response Code: 3
Response Subcode: 2
I’m adding my API Login ID and Transaction Key as well. I’m not sure if these are what should be added? Is this seprate form the AIM Login ID?
This topic was modified 10 years, 12 months ago by Alex Howell.
If you are using an account that you can switch back and forth between live and test, then it is probably an account on the live server. The development server system accounts are completely separate, and have to be signed up for on Authorize.net’s development server. To submit a test transaction to your live server account, just check the second option, ‘Submit a Test Transaction’, in the EE payment settings.
Ah, okay that was indeed the issue. Thanks for the quick reply!
Viewing 2 reply threads
The support post ‘Authorize.NET test mode not working. Getting same errors.’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.