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
Bypass payment method | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Bypass payment method

Bypass payment method

Posted: February 21, 2014 at 8:13 am

Viewing 3 reply threads


Helen Armour

February 21, 2014 at 8:13 am

I am selling events which can be paid for both via an online transaction (WorldPay) and by vouchers which are managed by a third party. I want customers to be able to register for an event and choose to pay immediately via WorldPay or by using these vouchers. If they select to pay via vouchers, their payment would be marked as complete and I would manage their voucher payments manually.

I see that there are many payment gateway options but I wonder whether there is a way that I can add a payment gateway which bypasses any physical payment?


Anonymous

February 21, 2014 at 8:28 am

Hi Helen,

Any event with a price requires a gateway to finalize the registration currently, the invoice gateway is one option for offline gateways. We don’t have a gateway that fits exactly to your requirements, however there is the ‘payatgate’ gateway that Dean created which you may be able to adapt to your needs. That is available here:

https://github.com/Apina/payatgate

Does that help?


Helen Armour

February 21, 2014 at 10:16 am

Hi Tony,

Thanks very much. It looks like one of those may well do the job. I’ll check them out.


Anonymous

February 21, 2014 at 10:29 am

No problem :)

Just let us know if you have any further questions.

Viewing 3 reply threads

The support post ‘Bypass payment method’ 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