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 PayPal to Stripe.com and back to PayPal? | Event Espresso - Staging Server
A couple months ago I was trying to use PayPal SandBox and it didn’t play well with EE. I think Josh found out they have had a bug that was messing things up for everyone using it. It was recommended to try Stripe.com which worked great. Now it comes time to make a secure safe credit card transaction. I explored SSL/HTTPS and don’t like the costs or complexity. Stripe.com doesn’t do 3rd party transactions and PayPal does. So it is back to PayPal, I think. I’m just wondering about whether I can use my client’s basic PayPal or do I have to do the business or Premier account so PayPal talks to EE and lets it know when a customer has paid? Do I have to have PayPal doing the IPN thing?
This topic was modified 12 years, 3 months ago by Kirk Tirakian.
Okay I’ve got the business account. I’ve set the transaction URL in PayPal. Just found this page after Googling and poking around the EE site for hours. Would be nice if this was a tutorial and had a link on the payment settings under PayPal. I’ve finally got PayPal to work right in EE. http://staging.eventespresso.com/wiki/troubleshooting-event-espresso/#gateways
This reply was modified 12 years, 3 months ago by Kirk Tirakian.
We are currently overhauling the documentation and I plan to make sure the gateway documentation is centralised and as detailed as we can make it.
Viewing 3 reply threads
The support post ‘PayPal to Stripe.com and back to PayPal?’ 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.