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
Sage Payment Solutions | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Sage Payment Solutions

Sage Payment Solutions

Posted: April 21, 2014 at 4:40 pm

Viewing 1 reply thread


bdeevers

April 21, 2014 at 4:40 pm

I’m told by a representative of Sage that their back end connection is through TSYS and that we should be able to work with that. Is this something a developer should handle if we move our gateway to Sage? Would this be compatible with EE? I am not a developer and need to know if this is something I should leave alone.


Dean

  • Support Staff

    •

April 22, 2014 at 3:51 am

Hi,

At this moment is time Sage is not a supported gateway for EE3.

EE4 will support Sage (country dependant) via the Mijireh gateway http://www.mijireh.com/docs/payment-gateways/

If you wanted Sage to work with EE3 or as a standalone gateway for EE4 then it would require a custom gateway to be developed.
Viewing 1 reply thread

The support post ‘Sage Payment Solutions’ 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.

The original Forum description...

Status: closed

Updated by Dean 10 years, 9 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server