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
Separate payment channels for different events? | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Separate payment channels for different events?

Separate payment channels for different events?

Posted: October 20, 2012 at 2:27 pm

Viewing 1 reply thread


Simon Knight

October 20, 2012 at 2:27 pm

Hi, doing some preliminary enquiries for a client. Couple of key questions;

1 – Partner organisations of the client who are each running events to be listed on the website could presumably each be given access by ‘Role’ of some sort, with no knowledge of each other and control of only their own events?

2 – Those Partner Organisations may have some events that are paid events. Can each Organisations paid events be set to go through separate payment channels relating to each partner (either PayPal or UK SSL style Payment Gateway?

Thanks


Sidney Harrell

  • Support Staff

    •

October 20, 2012 at 9:53 pm

  1. Yes, we have a roles and permissions add-on that has this capability.
  2. Yes. While it’s not been built-in, yet, we have figured out how to do it based on the event-meta fields that can be added to each event. It requires a couple lines of php added to check the event being registered for for the appropriate event-meta field, and if it’s there, modify which gateway is to be used and which account to use.
Viewing 1 reply thread

The support post ‘Separate payment channels for different events?’ 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 Sidney Harrell 12 years, 3 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server