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 for PayPal payments | Event Espresso - Staging Server
I need to add a surcharge for PayPal payments but not to another payment gateway I’ve implemented for a client. I can easily do this by altering the PayPal payment gateway code but would rather do it in the settings if it’s a built-in feature which the link above would indicate.
The surcharge is site wide or per event basis, but unfortunately not per gateway, so if you need surcharges on one gateway but not another then you will need to modify the code accordingly.
OK thanks for clarifying that. I suggest that you alter the wording on that page since it makes it seem like there is a separate surcharge feature in the PayPal payment gateway.
@adenham Thanks for pointing that out. We did at one point have a per-gateway surcharge feature (something I’ve been campaigning for bringing back) so it’s possible that was added when that feature was in place. I’ve removed it to avoid any further confusion.
Viewing 3 reply threads
The support post ‘Surcharge for PayPal payments’ 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.