Works with your stack
Cookie consent for the WooCommerce Stripe extension
stripe on product pages
The Stripe extension for WooCommerce loads Stripe’s script on product, cart and checkout pages, not only when the visitor pays. It has no consent setting, and card payments work only if that script loads from Stripe and runs normally.
By WooCommerce, Inc. · woocommerce.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
WooCommerce Stripe Gateway
WordPress plugin
- Tested version
- 11.1.1
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 11.1.1 tested
- Active installs
- 700,000+
What WooCommerce Stripe Payment Gateway adds to your visitors’ browser
No trackers In our test of WooCommerce Stripe Gateway 11.1.1 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with WooCommerce Stripe Payment Gateway
Pages beyond checkout
Stripe’s script loads on product and cart pages too, even with express buttons off there. A developer filter can stop that. It never loads on the home page, posts or the shop.
Do not break the payment
Before a card payment, the extension checks that the script came from Stripe. A rewrite or delay that changes it breaks the checkout.
Its own storage
The shop scripts write no cookie and nothing in local storage. An express payment redirect sets one short cookie.
What our tests found on WooCommerce Stripe Payment Gateway
Good to know · WooCommerce Stripe Payment GatewayWhat WooCommerce Stripe Payment Gateway stores in visitors' browsers
WooCommerce Stripe Payment Gateway: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for wc_stripe_express_checkout_redirect_urlcookie Necessary Keeps an express payment (Apple Pay, Google Pay) going Read in its code, 2 November 2026, WooCommerce Stripe Payment Gateway.
Full detail
WooCommerce Stripe Payment Gateway can store these in a visitor's browser: wc_stripe_express_checkout_redirect_url (cookie, necessary: Keeps an express payment (Apple Pay, Google Pay) going). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Set before the choice · WooCommerce Stripe Payment GatewayWooCommerce Stripe loads Stripe.js on product, cart and checkout by default
- Not on the home page, posts or shop.
- On product and cart pages it loads even when express buttons are off there.
- With express buttons, it adds early connections to four Stripe hosts.
- An express redirect sets wc_stripe_express_checkout_redirect_url (10 minutes).
Read in its code, 16 October 2026, WooCommerce Stripe Payment Gateway 11.1.1.
Full detail
The Stripe extension for WooCommerce loads Stripe.js (js.stripe.com) on product, cart, checkout, pay-for-order and add-payment-method pages by default, not only at checkout, and never on the home page, posts or shop. On product and cart pages it still loads when express buttons are off there, because two filters (wc_stripe_load_scripts_on_product_page_when_prbs_disabled and the cart one) default to true. When express buttons show, it adds preconnect hints to js.stripe.com, m.stripe.network, q.stripe.com and b.stripecdn.com in the head, and sets wc_stripe_express_checkout_redirect_url (10 minutes) on an express redirect. Its shop bundles write no cookie or localStorage.
Good to know · WooCommerce Stripe Payment GatewayWooCommerce Stripe has no consent setting and needs Stripe.js at its address
It does not read WP Consent API or set Consent Mode. Its checkout checks that Stripe.js came from js.stripe.com, so the script must run normally for card payments to work.
Read in its code, 16 October 2026, WooCommerce Stripe Payment Gateway 11.1.1.
Full detail
The Stripe extension for WooCommerce has no consent setting, does not read WP Consent API and sets no Consent Mode. Before charging, its checkout code checks that Stripe.js was loaded from https://js.stripe.com, so the script must stay on Stripe's address and run normally for card payments to work.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- WooCommerce Stripe Gateway 11.1.1, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: WooCommerce Stripe Gateway 11.1.1 on 7 November 2026, with WordPress 7.1.3.
Online shops
Other plugins of the same kind.
Questions
Is Stripe a tracker at checkout?
At checkout it is part of paying. On product and cart pages it loads before the visitor buys anything.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Stripe users
Card payments that keep working.
checkout must stay intact
Every feature of the complete plugin for 30 days, no card. The Stripe extension keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.