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 Inconsistent Surcharge with PayPal | Event Espresso - Staging Server
We have set up an event using PayPal standard payment, and a 3% surcharge (set through the event pricing settings). During registration, the amount is displayed inconsistently (or at least confusingly), and then the wrong fee is charged through PayPal. The 3% is being charged as $3. Screenshot below. What’s odd is that on the item line, the total is correct ($545 * 1.03 = $561.35), but then the subtotal shows the amount with the surcharge as a dollar amount ($545 + $3 = $548), but then the surcharge balance is added back in as a negative discount ( $548 – – $13.35 = $561.35). But then the amount sent to PayPal is the total with the incorrect surcharge ($548 – should be $561.35).
Thanks for the detailed report. I raised a high priority support ticket for a developer to look into this. In the meantime, I can suggest that if it’s possible for you to use a different payment gateway for the time being, this issue can be worked around. One of the off-site gateways that works very well is 2 checkout, and the on-site gateway that’s a snap to set up is Stripe.
Viewing 1 reply thread
The support post ‘Inconsistent Surcharge with PayPal’ 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.