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
AIM and SIM transactions | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › AIM and SIM transactions

AIM and SIM transactions

Posted: October 2, 2013 at 2:10 pm

Viewing 1 reply thread


kolaughlin

October 2, 2013 at 2:10 pm

We have our EE set up for Authorize.net SIM transactions. However, we are receiving different transaction results for the transactions on our site…some are AIM and some are SIM. I consulted with Authorize.net and they said it is not a setting in their account, but something on the website (in EE I assume.). Do you have any suggestions as to how this is being caused? I can provide our website login if needed. The site is operationparent.org. Thank you!


Dean

  • Support Staff

    •

October 2, 2013 at 11:43 pm

Hi,

This is the first we have heard of mixed aim/sim transactions.

Can you give us some extra info – what is actually wrong? Is it a case that the event overview is showing the wrong result or that the results in your Authorize.net account are wrong?
Viewing 1 reply thread

The support post ‘AIM and SIM transactions’ 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.

The original Forum description...

Status: closed

Updated by Dean 11 years, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server