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 Payment Pro configuration | Event Espresso - Staging Server
You’ll need to create an API username for PayPal that’s different from your shopping cart’s username.
Follow these steps:
1. Log in to your PayPal Business account.
2. Click the My Account tab.
3. Click the Profile tab. If you haven’t already done so, you need to verify your account before requesting API credentials.
4. Click Request API credentials under Account information.
5. Click Set up PayPal API credentials and permissions under Option 1.
6. Click Request API Credentials.
7. Click Request API signature.
8. Click Agree and Submit.
9. Copy and paste the API username, password, and signature into your Event Espresso payment gateway settings.
I could not provide a link, because Paypal requires you to log in to access this information.
Does Payment Pro required IPN to be turned on? And if so, is the correct IPN url the transactions page in EE? Does the url need to be http:// or https:// ?
The PayPal Pro gateway uses the API response to verify payments, so that should suffice. Please let us know if you run into any difficulties with getting the PayPal Pro gateway set up.
Viewing 3 reply threads
The support post ‘PayPal Payment Pro configuration’ 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.