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 duplicate charging - Charging a credit card 3 times instead of once! | Event Espresso - Staging Server
We had a customer that registered and paid at 9am 8/29/13 and then for some reason her credit card was charged for the same exact amount at 10am 8/30/13 and then again at 10:30. her name only appears once in the event as paying one time – we called our authorize.net and they said there is NO recurring billing setup so they dont know why she would have been charged twice again today – they said it had to come from your system sending in another payment – please advise as to what could have happened and how to prevent this duplicate charging
I do not know how this could have happened, short of the customer’s browser window being left open and the payment being submitted again later.
Are the transaction ID’s in the Authorize.net account the same or different for each transaction? Can you check the log files in /wp-content/uploads/espresso/logs to see if there was a response from Authorize.net at those times?
Interesting – we have had an occurrence of a double charge lately as well (Auth.net too). We’re also having other issues, looks like since upgrade to 3.1.34. I’ll open a separate ticket on that.
Thanks for the feedback Bill. Please let us know about any information you can find that will help troubleshoot this issue.
Viewing 3 reply threads
The support post ‘duplicate charging – Charging a credit card 3 times instead of once!’ 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.