SA Hosted Checkout for WooCommerce
by Sleek Algo 5 (1 reviews)

SA Hosted Checkout for WooCommerce

Take customers from WooCommerce cart to Stripe Checkout with hosted, embedded or popup checkout, free branding and WooCommerce coupon support.

SA Hosted Checkout for WooCommerce ranks #62,658 among WordPress.org plugins with 1+ active installations, is #7,243 of 14,124 in the E-commerce category, a 5/5 rating from 1 reviews, and was last updated Oct 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v1.2.0 Current Version v1.2.0
Updated 1 week ago Last Update on 27 Oct, 2026
Refreshed 1 week ago Last Refreshed on
#7,243 of 14,124 in E-commerce Downloads +64.9% this week Actively maintained
View on WordPress.org
Rank
#62,658
— No change
Active Installs
1+
-80%
KW Avg Position
56
1 worse
Downloads
781
+86 today
Support Resolved
100%
— No change
Rating
100%
Review 5 out of 5
5 (1 reviews)

Next Milestone 10

Total Progress 20%
0+ 10+
49,721
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 8 more installs to reach 10+

Rank Changes

59,525 61,092 62,658 64,224 65,791 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
45,959 53,235 60,512 67,789 75,066 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #62,658
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 100 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 100 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0
1 reviews
Overall 100%
5
1 (100%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Support Threads Overview

Resolved
Unresolved
1
Total Threads
1
Resolved
0
Unresolved
100%
Resolution Rate

Frequently Asked Questions

Common questions about SA Hosted Checkout for WooCommerce

Yes. When the plugin is enabled and configured and the cart requires payment, supported cart and mini-cart buttons take customers to the selected Stripe Checkout experience. Direct visits to the ordinary checkout page also open Stripe Checkout instead of displaying the standard WooCommerce form. Both classic Checkout shortcode pages and WooCommerce Checkout block pages are supported by this replacement flow. Customers do not need to fill in two checkout forms. The plugin replaces the standard form rather than adding a payment-method choice inside the WooCommerce Checkout block. JavaScript must be enabled. Empty carts, orders with no payment due, order-payment links, receipt pages and API requests are not taken over by the ordinary checkout-page replacement. The separate classic gateway remains available for supported existing-order payment flows. Custom checkout buttons, themes and checkout extensions require compatibility testing. In popup mode, intercepted cart-button clicks do not emit WooCommerce's cart_proceed_to_checkout event, so extensions that depend on this event need separate testing.
Yes. In Stripe Settings, choose Hosted Checkout, Embedded payment page, or Embedded popup. Hosted redirects to Stripe and remains the default for existing installations. Embedded page and popup display Stripe's payment interface within your website. Some payment methods still redirect customers to their bank or payment provider for authorization. Embedded Checkout needs a publishable key from the same Stripe account and mode as the configured secret or restricted key. Use HTTPS in production. Apple Pay and Google Pay also depend on Stripe payment-method domain registration, an eligible account, browser and device.
Use Automatic to create a dedicated payment page when you save Stripe Settings. Alternatively, publish a page containing the [sahcfwc_checkout] shortcode and select it. The page must not be password protected or assigned as the WooCommerce Cart, Checkout or My Account page. Customers reach it through a private order-payment link; adding the shortcode alone does not create a payable order. Popup checkout uses the same payment page for existing-order payment links and returns from payment providers. Closing the popup does not cancel the order or create another payment session; customers can reopen it while the session remains payable. Exclude the payment page and its query-string URLs from page caching. After an administrator changes the checkout mode, an existing popup session may continue on the dedicated payment page instead of being replaced. If payment has already been verified for the shopper's unchanged cart, reopening checkout returns the existing order receipt. If the paid cart cannot be matched safely, checkout stops with a review notice instead of starting another payment.
Yes. Enable Checkout branding in Stripe Settings to set the checkout display name, background and button colors, font and corner shape. Leave individual fields empty, or disable the override, to use Stripe Dashboard branding. Custom logo overrides apply to Hosted Checkout only. Stripe's Embedded Checkout does not accept per-session logo or icon overrides, so those images are not sent in Embedded page or popup mode. A Hosted logo must be a publicly accessible HTTPS image with a URL path ending in .png, .jpg, .jpeg, .jfif, .pjpeg, .pjp or .svg. Query strings are allowed. WebP, localhost, private-network and password-protected images cannot be used. Branding changes apply to new checkout sessions and do not change your Stripe account settings, receipts or invoices. An already-open session retains its existing settings. Stripe controls the payment interface, so arbitrary WordPress CSS cannot style the inside of its protected payment frame.
WooCommerce calculates the cart before Stripe Checkout opens. The plugin creates an order and uses that saved total, including eligible discounts, fees, shipping and taxes, for payment. Positive fees and taxes are shown as separate lines, with shipping shown as a separate charge. Changing an address on Stripe Checkout does not recalculate WooCommerce shipping or taxes. Optional quantity changes affect eligible product amounts, but leave these charges and existing discount amounts fixed. Stores with address-dependent shipping, tax or discount rules should test their calculation and checkout paths before going live.
Yes. To use coupons, enable "Enable the use of coupon codes" under WooCommerce > Settings > General and save your changes. The plugin respects this setting; it does not enable or disable coupons automatically. Customers apply coupon codes in the WooCommerce cart before opening Stripe Checkout, and eligible discounts are included in the payment total. This does not add coupon-code entry to Stripe Checkout. Coupon eligibility and usage restrictions still apply. Coupons limited to one use per customer require login. For higher per-customer limits, guests must have a valid billing email available before applying the coupon; otherwise, they must log in.
Enter the appropriate Stripe API credentials and webhook signing secret in Stripe Settings, select the matching test or live mode, and enable checkout. Start in test mode and check any setup notice if checkout remains unavailable.
Setup & health provides a checklist for saved Stripe settings, the selected checkout experience, payment-page configuration, HTTPS and webhook setup. Refresh checks reads local settings and any cached connection result. Check Stripe connection makes one read-only Stripe account request; it does not create a payment or verify every restricted-key permission, payment method or wallet. The webhook indicator records recent verified Checkout delivery for the matching configuration and test/live mode. A received event is not proof that an order was paid, and sandbox delivery does not verify live delivery. Complete a sandbox checkout and confirm its order status as part of setup. Copy support report includes version information and diagnostic states, excluding API keys, signing secrets, site addresses and customer/order details. Review the report before sharing it with support.
Open an eligible paid order and find the Stripe refunds panel. Select Refresh Stripe status to verify the original payment and existing refunds. Enter a partial amount or choose Use remaining amount, then review the amount, currency and original payment mode before confirming. Opening the panel and refreshing status do not request a refund. WooCommerce records the refund only after Stripe confirms success. Refunds are amount-only: they do not restock products, allocate amounts to product, fee, shipping or tax lines, or revoke downloads. Keep the original payment's test/live API credentials available, including permissions to read the original payment and create/read refunds. The panel requires a matching saved Checkout Session, payment reference and order snapshot; older orders without these records cannot be refunded automatically. If a refund is pending, unknown or requires review, refresh its status and inspect the original payment in Stripe. Do not create another refund or add a manual WooCommerce refund for the same Stripe refund. An uncertain request is not automatically resubmitted; an available retry uses the saved request identity. Resolve review warnings before requesting more money back. Stripe-initiated refunds can be synchronized for eligible plugin orders through the configured refund events or Refresh Stripe status.
Yes. In Payment Methods, keep the default card-only mode or select a custom set of methods from the supported catalog. Examples include Cards, Link, iDEAL | Wero, Klarna, SEPA Direct Debit, ACH Direct Debit and USD bank transfer. Card brands such as Visa and Mastercard are included under Cards, not separate payment-method choices. USD bank transfer and ACH Direct Debit are different methods. Enable the relevant methods in your Stripe account. Stripe determines availability using the account, business and customer countries, currency, order amount and other eligibility rules; selecting a method does not guarantee it will be displayed. See Stripe's payment-method support. Link requires Cards to be selected. Canadian pre-authorized debit also requires a Personal or Business mandate type in the plugin settings. Delayed-payment methods require a configured, working Stripe webhook.

Sign In / Register

You need to sign in or register to use this feature.