Official pluginLast verified 2026-09-12 · Reviewed by a person 2026-09-14
Stripe connects to WooCommerce through the free WooCommerce Stripe Payment Gateway extension. It is developed in the WooCommerce GitHub organisation and listed on the WooCommerce Marketplace as by Stripe. It covers cards, Apple Pay and Google Pay, BNPL and local payment methods, and works with both the block checkout and the classic checkout. Webhooks are configured automatically, and you can test in Stripe test mode.1
UAT-Ops testing: Stripe's sandbox was verified by UAT-Ops on 2026-09-11 with the directory's card flow (6 passed) → evidence on the Stripe hub. The WooCommerce integration itself has not been run.
Sources checked: 22 claims from 5 sites, listed at the foot of the page.
Connects through WordPress plugin (WooCommerce Stripe Payment Gateway), connected to a Stripe account from WooCommerce > Settings > Payments > Stripe. Biggest gotcha: The two listings are updated separately.
How it connects
Method
WordPress plugin (WooCommerce Stripe Payment Gateway), connected to a Stripe account from WooCommerce > Settings > Payments > Stripe
Maintained by
WooCommerce (Automattic); the marketplace listing credits Stripe1
WooCommerce 10.8 and PHP 7.4; WordPress 6.9 per WordPress.org (the Marketplace lists 6.8)1
Checkout modes
checkout block, classic shortcode checkout, express checkout buttons, pay for order page3
PCI scope
SAQ A for most merchants: card data is entered in the gateway's own fields or page, so it never touches your server. The gateway or your acquirer can still require a different questionnaire.4
What works on this platform
Yes: a source confirms it on this integration. Limited: supported, but only under meaningful conditions or through a subset of connector paths. Not verified here: the gateway supports it, but no source confirms this integration exposes it. No: not available. A capability with no source either way is left off.
The extension's core function; WooCommerce's own documentation names Visa, Mastercard, American Express, Discover, Diners and JCB among the cards it accepts.
Refunds are issued from the WooCommerce order screen. A payment that was authorised but not captured has to be cancelled, not refunded. Partial refunds are confirmed at the gateway level only.
One-time purchases only, through Adaptive Pricing: shoppers see prices and pay in their own currency. The store currency must match the Stripe payout currency, orders stay in the store currency, and it does not work with subscriptions, express checkouts or authorise-now-capture-later. WooCommerce recommends a dedicated multi-currency plugin for anything more.
Level II data is sent automatically. Level III is sent only for US merchants, on Visa or Mastercard, for orders with no physical products and complete billing details.
Capability status reflects the integration and documentation available at the time of verification, not necessarily every capability of the underlying gateway or platform.
Testing it
Go to WooCommerce > Settings > Payments > Stripe > Settings, choose Configure connection, open the Test tab and create or connect a test account, then tick Enable test mode. Pay with Stripe test cards: 4242 4242 4242 4242, or a 3DS card such as 4000 0000 0000 3220. The plugin creates its webhook automatically, at https://<site>/?wc-api=wc_stripe, separately for test and live. Stripe only delivers to publicly reachable HTTPS URLs, so a local site needs a tunnel (for example ngrok) or the Stripe CLI's stripe listen --forward-to. Testing Apple Pay also needs a registered HTTPS domain and a real card in a wallet, used with test keys.11
UAT-Ops runs integration flows like this against the real sandbox and keeps the evidence. Get one email when it opens.
Gotchas
The two listings are updated separately
The WooCommerce Marketplace credits the extension to Stripe, while WordPress.org lists WooCommerce and Automattic as contributors, and the source code is in the WooCommerce GitHub organisation. The two listings are maintained separately, so their details can lag each other for a while after a release. On 2026-09-11 both showed version 11.0.0 but gave different WordPress minimums: 6.8 on the Marketplace and 6.9 on WordPress.org. Before you file a bug, check the version you actually have installed, and report it against the WooCommerce repository.
Webhooks are per mode and point at ?wc-api=wc_stripe
Since 8.6.1, connecting the account creates the webhook automatically at https://<site>/?wc-api=wc_stripe. Test and live each get their own endpoint. If orders stay pending, open Configure connection and check that both the Live and Test tabs say Configured. After a migration or a domain change, use Reconfigure webhooks. Stripe only delivers to public HTTPS URLs, so a local store needs a tunnel.
Express checkout buttons need the whole site on HTTPS. Apple Pay also needs port 443 open, TLS 1.2, and the domain registered on Stripe's payment method domains page. Stripe requires every domain that shows the button to be registered, including www and other subdomains, in both production and testing. Apple Pay and Google Pay can only be switched on together. The buttons stay hidden on virtual products when tax is calculated from the billing address.
Block checkout is the default; custom gateway code must opt in
Stores created after WooCommerce 8.3 use the Cart and Checkout blocks. The Stripe extension supports them, but your own gateway customisations or add-ons won't appear there unless they have a blocks integration. If only incompatible gateways are active, shoppers see a "no payment methods" notice. You can transform the blocks back to the classic shortcode, but do it for both cart and checkout.
When you authorise a payment now and capture it later, no money moves until the capture. The WooCommerce refund button therefore can't reverse an uncaptured payment; cancel the order instead. The extension's refund guide does not describe partial refunds, so test a partial refund in test mode before you rely on one in production.
https://stripe.com/guides/pci-complianceofficial documentation · describes the gateway · a claim here is implied by this source, not stated · checked 2026-09-10
Last verified 2026-09-12 · Reviewed by a person 2026-09-14
Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.
Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.