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 Payment gateways on EE4 restricted | Event Espresso - Staging Server
We run a conference each year and use wordpress as our website CMS. I am looking at purchasing this event expresso plugin so we can get registration and payments online.
I am leaning towards the EE4 version however I notice that the options for payment gateways are reduced to authorize.net. We bank with CBA and they use e-way which is available on the EE3 version.
Is e-way available on EE4. Also we offer group discount registrations, you can register 5 people for the price of 4. Are are able to do this on the customisable rego form.
EE4 is relatively new and as such has limited features and gateways.
At this time E-way is not available for EE4. We are reviewing which gateways will be included in the future, no decisions have been finalised yet.
Also there is no discount system in place yet (this is in the works).
As such right now it looks like EE3 is probably your best bet. It has the gateway you need, and an addon called Volume discount that can be used to take a percentage or fixed amount off the total when it reaches a certain threshold (e.g. when 4 or more tickets are added to cart. Volume Discounts requires the Multiple Event Registration add on to function.
Viewing 1 reply thread
The support post ‘Payment gateways on EE4 restricted’ 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.
Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.