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 Payment gateways and PCI compliance | Event Espresso - Staging Server
Sorry, I accidentally posted this to “Translations.” It should be a pre sales question:
Sorry for the duplicate question.
Looking over the demo I see a number of payment gateways. All except Paypal Standard have a warning about PCI compliance. Question: what does PCI compliance require? Is this just an SSL certificate for the site?
Also, if Paypal Standard is used, does that mean buyers are redirected to Paypal’s pages and therefore don’t need SSL?
Finally, the demo is EE4. Are the same payment gateways available in EE3? Thanks for your help!
A dedicated SSL certificate is a good start for PCI compliance but there are additional requirements. Please take a look at this article which compares onsite payment gateways to offsite payment gateways:
An SSL is not required for PayPal Standard since payment processing takes place offsite on PayPal’s website.
The following payment gateways are currently available for Event Espresso 4:
Authorizenet AIM, Bank Draft, Check, Invoice, PayPal Standard, PayPal Pro
—
Lorenzo
Viewing 1 reply thread
The support post ‘Payment gateways and PCI compliance’ 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.