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 Failed Payments showing as Registered in Event Espresso and Infusionsoft | Event Espresso - Staging Server
Hello – when a user registers and their payment fails, we are seeing a record of them in Event Espresso and also in Infusionsoft with a balance owed. Is there a way to change the settings so that if the users payment fails, nothing is sent to Infusionsoft? This doesn’t make sense to record a registration before the payment goes through.
The attendee in EE and the infusionsoft contact are created when the confirmation page is loaded. Most site owners want to have that information if a payment attempt fails so they have the option of contacting the user to follow up with them.
Not out of the box. It would have to be a rewrite customization. There are post-payment hooks that the infusionsoft calls could be moved to, but it would require making sure that the data available at those hooks matches up with what the infusionsoft calls are expecting to receive from the hooks where they are located now. We have a list of recommended developers who could help you with that.
Thank you, unfortunately, we don’t want to invest any more into this “out of the box” product however. In the future upgrades, hopefully this can be an added feature, or at least something to toggle off and on. Thank you so much for your assistance.
This reply was modified 10 years, 11 months ago by Seth Shoultes. Reason: fixed text
Viewing 4 reply threads
The support post ‘Failed Payments showing as Registered in Event Espresso and Infusionsoft’ 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.