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 SagePay | Event Espresso - Staging Server
I have a client in the UK using EE with paypal. They are reviewing moving their accounting onto Sage so Sage Pay would be an option. Do you have plans/timescale to included a Sagepay gateway?
Would also be useful to hear which other payment solutions users recommend as a reliable and cheaper alternative to paypal in the UK.
Sagepay is meant to be a great gateway by all accounts.
We have been in discussion with one or two customers recently about them sponsoring the development of the gateway, but we have not heard anything back from them.
There are no current plans to include the gateway unless it is a sponsored development.
We have paid a developer to build a Sagepay gateway which is now in operation. As it stands it would need a little bit more work to make it more generally useful (it works fine on the site it’s installed on) and we’d be looking to recover some of our costs. But it should work out a lot cheaper than sponsoring a new development from scratch. Is it possible to get in touch with other users via this site? Is it okay to post a contact email address?
Many thanks for the information. I’ll take it back to my client and get in touch if we want to follow it up.
Viewing 5 reply threads
The support post ‘SagePay’ 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.