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
Integration of new payment services | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Integration of new payment services

Integration of new payment services

Posted: October 9, 2013 at 3:51 am

Viewing 1 reply thread


Jan

October 9, 2013 at 3:51 am

Hi Espresso,
Is it possible to use any other payment service than the defaults? Is it hard to implementate? We want to use GP webpay.

Thanks


Dean

  • Support Staff

    •

October 9, 2013 at 5:43 am

Hi Jan,

Adding another payment gateway would require custom development. You could create this yourself/hire a developer, we advise to use the existing gateways as templates and we have some basic guidelines in the documentation.

It would be up to you/your developer to maintain the gateway.

We do offer a gateway development service, you can request further information here – http://staging.eventespresso.com/rich-features/multiple-payment-options/custom-payment-gateway-development/ – in which case we will look to maintain the gateway. We do not always have resources available, so it’s best to send that form and the sales/development team can advise in more detail.

We have a list of recommended third party developers here – http://staging.eventespresso.com/developers/event-espresso-pros/
Viewing 1 reply thread

The support post ‘Integration of new payment services’ 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 Dean 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server