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 Notification - Gateway Variable Dump | Event Espresso - Staging Server
I have authorize.net set up, live and working fine. Only Auth.net SIM and Invoice payent gateways are active. For every transaction, we receive an email addressed to the Primary Contact Email set in the General Settings with the subject: Authorize.net Notification – Gateway Variable Dump. The email includes:
An authorize.net payment notification was successfully recieved
from “customeremailaddress” on 12/15/2012 at 9:45 AM followed by the order variables
Details:
x_response_code: 1
x_response_reason_code: 1
x_response_reason_text: This transaction has been approved.
x_avs_code: Y
x_auth_code: 05232C
etc., etc.
It looks like it is coming from EE/WordPress and not Auth.net. How do we prevent this email from being sent? Searching these forums, I see others have reported this issue, but no solutions have been provided.
In the authnet gateway folder, there is a file that is named authnet_ipn.php. On line 78 there is a variable that sets the transaction email dump to true. If you set variable to false, it will not send the email.
The support post ‘Authorize.net Notification – Gateway Variable Dump’ 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.