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

Support

Home Forums Event Espresso Premium different payment gateways for different events

different payment gateways for different events

Posted: April 7, 2014 at 12:36 am

Viewing 3 reply threads


Rebekah

April 7, 2014 at 12:36 am

I would like to have paypal available for some events, and only bank drafts available as the payment method for others. Is there a way to do this?


Josh

April 7, 2014 at 9:45 am

Hi Rebekah,

There is a way to make this happen with some PHP coding if you are using Event Espresso 3. Here’s a link to a github gist that has some example code that can be adapted to assign different payment options for different events:

https://gist.github.com/joshfeck/6768792


Rebekah

April 7, 2014 at 4:24 pm

Thank you this is wonderful! Yes I’m using EE3.
Do I paste this code into into the event itself, or elsewhere? (Yes, I am quite new to this).

This is going to solve a lot of my problems!


Josh

April 7, 2014 at 5:38 pm

Hi Rebekah,

The code can be adapted and pasted into the custom file add-on’s custom_functions.php file or into a custom snippet plugin

Please be sure to swap in the corresponding event ID. Also, since you mentioned you’re new to this, please note that it’s important to make sure that if your funcitons file already has an opening <?php tag, then you do not copy the opening <?php tag from the gist I posted.

Viewing 3 reply threads

The support post ‘different payment gateways 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.

Event Espresso - Staging Server