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 Stripe and SSL | Event Espresso - Staging Server
hI – I have just moved my client’s site to live, it’s password protected while I work this out.
Have run a transaction through Stripe (using Live keys) for $1 and it was processed ok as far as I can tell – all emails sent and the $1 shows in the Stripe account.
What I’m concerned about is that the docs all mention Stripe requiring an SSL certificate on the server. The clients site is on a brand new Bluehost account, and I’ve checked there are no SSL certs present – and yet the transaction went through fine.
Am I misunderstanding something here? Should I get an SSL cert for the domain anyway eg either through Bluehost or startSSL.com?
Yes, whenever you use an on-site payment option like Stripe there should be an SSL cert installed for the domain, and the pages that handle the payments should be set to load as https. We’ve prepared a guide here that outlines how to do this:
I’ve seen it where the transaction will still go through when using some of the on-site gateways without using https. I know some will not work at all without it (like PayPal Pro). It may be that the Stripe gateway doesn’t check for https so it would still work, just not securely. Typically any of the gateways will work without SSL if they are in test mode too.
Viewing 1 reply thread
The support post ‘Stripe and SSL’ 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.