How to Fix an Insecure WordPress Checkout When Customers Are Redirected to HTTP After Paying with Stripe

Fix the checkout by forcing WordPress, WooCommerce, and every return URL to use HTTPS before Stripe sends the customer back. Stripe expects live payment flows to run through HTTPS, and their security guidance is clear about using TLS for payment traffic [source: Stripe]. If customers pay through Stripe and land on an http:// “order received” page, the sale may still work, but trust drops fast. Some browsers show warnings, some tracking breaks, and a few shoppers will think the payment failed.

TLDR: Install and configure WP Force SSL, set your WordPress and WooCommerce URLs to HTTPS, then update the Stripe return and webhook settings. For example, if 100 people pay and 12 hit an insecure thank-you page, even a small 3% support-ticket rate means extra manual checks every week. The fastest fix is usually a forced HTTPS rule plus a cleanup of old HTTP links in the database and cache.

Why Stripe Sends Customers Back to HTTP

This usually happens because WordPress still thinks the site lives at http://yourstore.com. Stripe finishes the payment, then uses the return URL WooCommerce gives it. If WooCommerce built that URL from old settings, the customer lands on HTTP.

Honestly, it feels like such a small setting should not cause this much trouble. But one old URL can trigger browser warnings, broken redirects, mixed content, and confused “Did my order go through?” emails.

Image not found in postmeta

The most common causes are:

  • WordPress Address or Site Address still uses HTTP.
  • WooCommerce checkout pages were created before SSL was added.
  • Stripe webhook or return URLs were copied with HTTP.
  • A cache plugin keeps serving old redirects.
  • Your host uses a proxy or CDN, but WordPress does not detect HTTPS correctly.
  • Old links inside menus, buttons, or page builders still point to HTTP.

Step 1: Install WP Force SSL

Start with the plugin that solves the exact problem: WordPress serving HTTP pages when it should not. Install WP Force SSL from the WordPress plugin screen, or download it from the plugin repository. Then open its settings and turn on SSL redirection.

This makes visitors land on HTTPS even if they click an old HTTP link. It also helps with checkout pages, account pages, and order confirmation pages. That matters because payment pages need to feel clean and safe, not patched together.

  1. Go to Plugins > Add New.
  2. Search for WP Force SSL.
  3. Install and activate it.
  4. Open the plugin settings.
  5. Enable Force SSL and run the SSL checks.

If the plugin reports an SSL certificate issue, fix that first. Do not test Stripe until the certificate is valid and the site opens cleanly with https://.

Step 2: Update WordPress URLs

Next, check the core site settings. Go to Settings > General. Both of these fields must begin with HTTPS:

  • WordPress Address (URL)
  • Site Address (URL)

If either one says HTTP, change it. Save the settings. You may be logged out. That is normal. Log back in using the HTTPS version of your admin URL.

If these fields are locked, they may be set in wp-config.php. In that case, check for lines like this:

define('WP_HOME', 'http://example.com');
define('WP_SITEURL', 'http://example.com');

Change both to HTTPS. Be careful here. A typo can lock you out until you fix the file.

Step 3: Check WooCommerce Checkout Pages

Now check WooCommerce. Go to WooCommerce > Settings > Advanced. Confirm that the cart, checkout, account, and terms pages are correct.

Then open each page in the editor. Look for buttons, shortcodes, custom blocks, and page builder links that may still use HTTP. It is annoying, but yes, a single hard-coded button can send buyers to the wrong version of the checkout.

Also visit these pages in a private browser window:

  • https://yourstore.com/cart/
  • https://yourstore.com/checkout/
  • https://yourstore.com/my-account/
  • https://yourstore.com/checkout/order-received/

If any URL flips back to HTTP, WP Force SSL should catch it. If it does not, your host, CDN, or another plugin may be overriding redirects.

Step 4: Update Stripe Webhooks and Return Links

Open your Stripe dashboard and check your webhook endpoints. If you see HTTP, replace it with HTTPS. For WooCommerce Stripe, the webhook often looks like this:

https://yourstore.com/?wc-api=wc_stripe

Then return to WordPress and open the Stripe payment gateway settings inside WooCommerce. Save the settings again, even if nothing changed. This can refresh stored URLs.

Run a test payment using Stripe test mode. Use a low test order, such as $1.00. After payment, watch the address bar. The order confirmation page must stay on HTTPS from start to finish.

Step 5: Clear Cache Everywhere

Expect to waste time on cache. It is one of the least fun parts of this fix. Clear all of it:

  • WordPress cache plugin
  • WooCommerce transients
  • Server cache from your host
  • CDN cache, such as Cloudflare
  • Browser cache

Then test again in a private window. Do not only test while logged in as admin. Logged-in users often bypass cache, while real shoppers do not.

Step 6: Fix Mixed Content

Even after the redirect works, your browser may still show a warning if images, scripts, or fonts load over HTTP. WP Force SSL can help detect insecure content, but you should still inspect the page.

Open Chrome DevTools, click Console, and reload the checkout page. Any HTTP asset should be replaced with HTTPS. Common offenders include logo images, background images, tracking scripts, and old theme files.

Final Test Before Going Live

Place one real order with a small product or coupon. Pay through Stripe. Confirm these items:

  • The checkout page starts with HTTPS.
  • The Stripe payment step completes without warnings.
  • The thank-you page stays on HTTPS.
  • The order appears in WooCommerce.
  • The payment appears in Stripe.
  • The customer email links use HTTPS.

If all six pass, the insecure redirect is fixed. Keep WP Force SSL active, monitor checkout for a few days, and check support messages for payment confusion. A clean HTTPS checkout is not just a technical detail. It removes doubt right when the customer is deciding whether your store can be trusted.