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 EE4--AIM merchent email reciept request/issue | Event Espresso - Staging Server
I was wondering if there is a way to get the Event Transaction to populate the Authorize.net “Description” line on the receipt generated by the gateway? My book keeper would like to know who or what generated the transaction, but the description line form Auth.net is blank. This is the email notification from Auth.net, not from EE4.
I’m seeing something different on the email reciepts from Authorize.net. In the Description field it has the name of the ticket followed by (For Event Name).
Are you using any other plugins on the site that process payments with Authorize.net AIM? I’m wondering if something is causing a conflict.
I’ve raised a ticket for the issue, and submitted a proposed change for the 4.1.9 release, so hopefully it will show up in an update for you within a couple of days.
Currently, the items have the description attached to them, but the whole order does not. So your bookkeeper may be able to use that information to match up past transactions.
Viewing 3 reply threads
The support post ‘EE4–AIM merchent email reciept request/issue’ 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.