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 Feature Request: Gateway specific surcharges | Event Espresso - Staging Server
I would like to request the ability to preset surcharges for each gateway. As such, rather than adding the surcharge manually (or at least as the only way), I’d like to be able to:
1) create my price options,
2) set the surcharge to be used for the total cost
3) Add the surcharge, once the gateway has been selected or perhaps before by showing the different cost (fees) associated with each payment gatewau/
4) The surcharge should be able to be entered as as formula. For instance X% + Y. e.g. Paypal is 2.9% of total cost + $0.30.
The ability to write a name and description for the surcharge is also fine.
If this isn’t readily doable, another option which is closer to the one current is the ability to create the different surcharges based on formulas of % and a flat fee and then be able to add them to total again. Right now, I had to enter the fee on each option manually by calculating ahead of time, how much paypal would charge me and adding it as a surplus.
The support post ‘Feature Request: Gateway specific surcharges’ 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.