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
Change Fee from Payer to Payee | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Change Fee from Payer to Payee

Change Fee from Payer to Payee

Posted: March 14, 2014 at 11:35 am

Viewing 3 reply threads


Thomas Bliss

March 14, 2014 at 11:35 am

Event Esporesso has the ability to add in a flat fee that we want to use to cover transaction cost. I am using the WePay capability. How do I change the the cost to come from Payer to Payee when sending the information to WePay?

Change “fee_payer”: “payer” to “fee_payer”:”payee”.


Josh

March 14, 2014 at 11:38 am

Hi Thomas,

I took a look at the WePay developer API and it turns out there is a way to set it so the Payee pays the fees. It’s set with a single line of code:

$fields['fee_payer'] = 'payee';

The above can be added to the Event Espresso WePay gateway’s wepay_vars.php file on line 23. The wepay folder can then be copied over to /wp-content/uploads/espresso/gateways to prevent it from being overwritten on an update.


Thomas Bliss

March 14, 2014 at 11:48 am

Thanks. I’ll work it with your feedback.


Josh

March 17, 2014 at 9:05 am

You’re welcome.
Viewing 3 reply threads

The support post ‘Change Fee from Payer to Payee’ 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 10 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server