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 Confusion over payment Gateways | Event Espresso - Staging Server
We have just purchase Event Espresso Premium and are working to integrate the system into our website. We have a PayPal Payflow Pro Gateway for another piece of our site, and are trying to figure out how/whether this will work with EE.
Can you help me understand the difference between the types of PayPal gateways, and what I need to communicate to our processor to get the correct one set up, if indeed Payflow Pro is not supported?
I don’t know how this question was marked “Resolved” as I never received an answer. I have since spoken with PayPal, and I am told that PayPal Payments Pro and Payflow Pro are the same thing, and our Payflow Pro credentials should work, but I am unclear as to what information is to be entered where in the set-up panel of the PayPal Pro screen in EE.
Thank you. I had a conversation earlier today with someone from PayPal who incorrectly told me that Payflow and Payments Pro are interchangeable, but a later conversation with a different tech set me straight.
I am working with our Merchant Services account to set up an Authorize.net gateway to our existing merchant account.
Thanks for the response.
Viewing 3 reply threads
The support post ‘Confusion over payment Gateways’ 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.