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
Add a fixed price surcharge on per transaction (not ticket) | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Add a fixed price surcharge on per transaction (not ticket)

Add a fixed price surcharge on per transaction (not ticket)

Posted: March 25, 2013 at 1:56 pm

Viewing 3 reply threads


Rupert Abrahams

March 25, 2013 at 1:56 pm

Hi I want to be able to charge a £1.50 transaction fee when someone buys their tickets from our website. I don’t want to do this on a per ticket basis but just for the whole transaction. For example if someone buys one ticket they would be charged £1.50 and if they buy 10 tickets they would still be charged £1.50


Dean

  • Support Staff

    •

March 26, 2013 at 3:22 am

Hello Rupert,

We do not have a facility for a basket surcharge, only a surcharge per ticket.


Rupert Abrahams

March 27, 2013 at 3:59 am

Hi Thanks for that. Is there any way round this, we need to add on a fixed charge of £1.50 per transaction.


Josh

March 27, 2013 at 7:38 am

Hi Rupert,

One possible work around is to the payment gateway’s shipping cost add-on. If this is an available option with your payment method, you may be able to use it to charge your additional fee.
Viewing 3 reply threads

The support post ‘Add a fixed price surcharge on per transaction (not ticket)’ 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 Josh 11 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server