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
Payment-Declined Workflow for Users | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Payment-Declined Workflow for Users

Payment-Declined Workflow for Users

Posted: December 8, 2013 at 6:27 pm

Viewing 3 reply threads


Sinclair Lewis

December 8, 2013 at 6:27 pm

Using Authorize.net/SIM, when bad payment information is entered on the Authorize.net payment form, the user then goes back to the Auto Return URL page on my site. They’ll see an error, but there’s no way for them to get back to the Authorize.net payment form without re-entering all their information.

I’ve tried a hosted receipt where the user remains on the Authorize.net payment form and receives errors there, where they can still correct them. (I did this by changing x_Relay_URL to x_receipt_link_url in authnet_vars.php.) However, with this method payments aren’t being updated in the WordPress database, even when I specify a “silent post URL” with Authorize.net.

How can a user see a payment error and then be able to correct it without re-entering everything?

Thanks


Anonymous

December 9, 2013 at 4:18 am

Hi,

If you go to Event Espresso -> General Settings.

Set ‘Show payment options for “Pending Payments” on the Payment Overview page?’ to Yes and Save the settings. This will display the payment options on the overview page for any attendee status other than Complete.

Does that help?


Sinclair Lewis

December 9, 2013 at 7:06 am

I changed that setting but am still seeing the same thing: the error (payment declined), then the header “Payment Overview” with a list of payment information (stating it’s declined), but no further options to try a payment again.


Anonymous

December 9, 2013 at 7:31 am

It could also depend on any changes made to the templates within wp-content/uploads/espresso/templates/

You could try temporarily renaming the template folder to anything other than ‘templates’ for example ‘templates-temp’ and refreshing the payment overview page. Are the payment options displayed then?


Sinclair Lewis

December 9, 2013 at 8:38 am

Yes — that was it.

Thanks for your help.
Viewing 3 reply threads

The support post ‘Payment-Declined Workflow for Users’ 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 Sinclair Lewis 11 years, 1 month ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server