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
Multiple tickets are not separated on WorldPay | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Multiple tickets are not separated on WorldPay

Multiple tickets are not separated on WorldPay

Posted: October 10, 2013 at 10:33 am

Viewing 1 reply thread


lsjs44a

October 10, 2013 at 10:33 am

I have a site set up using Event Espresso for a while now. It has just to my attention that when a customer has a number of tickets in their cart it submits the cart to WorldPay as a single sum. As a result once the transaction has taken place the response comes back as the total payment for the first ticket.

Do all payment gateways work in this way?

Thanks

Josh


Sidney Harrell

  • Support Staff

    •

October 14, 2013 at 11:51 am

No, some gateways allow you to pass itemized order details. As far as I can tell from the WorldPay documentation (http://www.worldpay.com/support/kb/bg/htmlredirect/rhtml.html) they only allow you to pass an amount parameter.
Viewing 1 reply thread

The support post ‘Multiple tickets are not separated on WorldPay’ 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 11 years, 3 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server