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 Captured/Pending Settlement | Event Espresso - Staging Server
Authorize.net shows my transaction as Captured/Pending Settlement. Event Espresso shows my transasction as “declined.” Is this by design? Thanks.
Event Espresso – Calendar by Event Espresso version 2.0.6,
Event Espresso – MailChimp Integration by version 1.0.4,
Event Espresso – Multi Event Registration by Seth Shoultes version 1.0.4,
Event Espresso – Social Media by Event Espresso version 1.1.5.1,
Event Espresso by Event Espresso version 3.1.33.1,
(apologies if I posted multiple threads… my post didn’t appear to be going through..)
There isn’t a payment status built into Event Espresso for each Authorize.net status.So what it does is check the response from Authorize.net and if it comes back as “Approved” it sets the payment status as complete. Any other response will display the error message from Authnet and the “Payment Declined” status is set. These transactions can be updated in the admin once they’ve been completed.
Thanks Josh. I don’t know how much programming it requires but handling additional response codes would be a plus. I’m looking forward to version 4.
Regards, Tomas
It might be something where they could record the error code and store it in the payment record. I’ll make a note for the dev team.
Viewing 4 reply threads
The support post ‘Captured/Pending Settlement’ 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.