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 Registration Problem - Payment Type Incomplete | Event Espresso - Staging Server
Recent Event Espresso upgrade. New events created. When attendees complete signup and payment is received via Authorize.net, no email confirmation is sent and all attendees are listed as “Payment Type” Incomplete.
I tested it myself on 8/9 and again today. When I checked with my credit card company all of the payments were “pending”.
This may be a setting on the Authnet account side if the Fraud Detection is enabled. You could try approving the pending transactions by following this guide:
Thanks Josh. We do not have the Fraud Detection Suite so the functionality is available to us. For what it’s worth, the Authorize.net folks say everything is fine on their side of the fence.
As expected, we’re in a bit of a rush on this. Would a Support Token help us out here?
Hi Josh. Success was had with our friends at Event Espresso using a Priority Token. The correction made was to “…change the url that authnet’s server is pulling from your site and displaying from their server to the customer as the receipt page.”
This has happened a few times with other gateways where the default URL page permalink did not work, but the first time we’ve seen it with Authorize.net. Were working with the developers to add a function that automatically sets the URL for the response URL according to the WP Permalinks settings. Hopefully that will help in cases like these.
Viewing 5 reply threads
The support post ‘Registration Problem – Payment Type Incomplete’ 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.