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
Miscalculation in EE to Authorize.net | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Miscalculation in EE to Authorize.net

Miscalculation in EE to Authorize.net

Posted: January 9, 2014 at 8:44 am

Viewing 3 reply threads


Carina Hume

January 9, 2014 at 8:44 am

We have had two separate occurrences recently where customers were charged an extra $45 at checkout. Any idea what may be causing this?

Calendar: 2.2.1.p

MailChimp Integration: 1.2

Members Addon: 1.9.8.p

Multi Event Registration:: 1.0.5.p

Permissions: 1.5.2

Recurring Events: 1.1.8.p

Social Media: 1.1.7.p

Ticketing: 2.1.p

Event Espresso: 3.1.36.2.P

WordPress: 3.6.1


Sidney Harrell

  • Support Staff

January 9, 2014 at 10:18 am

Can you give any more specifics? Which events were in the cart? What were the itemized charges on the authorize.net report? Are you using authnet SIM or AIM?


Carina Hume

January 10, 2014 at 3:43 pm

We are using AIM. Below are a couple of links to screenshots that might help.

https://www.crookedtree.org/wp-content/uploads/2014/01/Screenshot-1.jpg

https://www.crookedtree.org/wp-content/uploads/2014/01/Screenshot-2.jpg


Josh

January 10, 2014 at 5:26 pm

Hi Carina,

Is there a miscalculation on the first one? It looks correct to me. The second one is definitely off by $45. Can you check the log file in /wp-content/uploads/espresso/logs to see if there is a discrepancy there?

Viewing 3 reply threads

The support post ‘Miscalculation in EE to Authorize.net’ 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.

Event Espresso - Staging Server