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
surcharge in payments with EE3 | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › surcharge in payments with EE3

surcharge in payments with EE3

Posted: March 6, 2014 at 9:38 am

Viewing 1 reply thread


Riccardo Pinardi

March 6, 2014 at 9:38 am

I am going to buy the business licence of EE 3 and I have a question:

I need to use two payment options for my events: paypal and offline. I want to surcharge the payment with paypal due to some handling fees, but I don’t understand if it is possible with EE 3 (I’m testing the lite version my website and I am also doing the “test-drive”).

Furthermore, I saw that there is the multiple ticketing functionality in EE 4 (beta) that could be useful for that porpuse but I don’t know if the version 4 is ready yet for a stable use.

How could I resolve this issue?


Lorenzo Orlando Caum

  • Support Staff

    •

March 6, 2014 at 10:06 am

Hi Riccardo,

Surcharges are available in Event Espresso 3 and Event Espresso 4. However, both of these are applied to the ticket itself and are not set per payment gateway.

This means that the surcharges would apply for offline payments and PayPal payments.

—
Lorenzo
Viewing 1 reply thread

The support post ‘surcharge in payments with EE3’ 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.

Status: closed

Updated by Lorenzo Orlando Caum 10 years, 10 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server