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
WorldPay XML Redirect | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › WorldPay XML Redirect

WorldPay XML Redirect

Posted: February 6, 2014 at 12:23 pm

Viewing 1 reply thread


Robin Nicholl

February 6, 2014 at 12:23 pm

I’m days away from this site going live, and have just received the WorldPay integration info from our client. It’s XML Redirect, and nothing seems to correspond with the WorldPay Settings in Event Espresso. Help! I tried getting them to use Stripe, but they will only use WorldPay XML Redirect and there’s no chance of changing their minds.

Robin


Sidney Harrell

  • Support Staff

    •

February 6, 2014 at 6:20 pm

Unfortunately, our WorldPay integration uses their Buisness Gateway hosted payment page api, and not their Corporate Gateway hosted payment page api. We do have some documentation on how our gateway modules are written, as well as custom gateway integration service.
Viewing 1 reply thread

The support post ‘WorldPay XML Redirect’ 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 Sidney Harrell 10 years, 11 months ago ago

Topic Tags

Tagged: , , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server